This question was originally asked in a comment on the page http://dev.day.com/docs/en/cq/current/deploying/installing_cq.html#Installing and Starting Adobe Experience Manager as a Windows Service.
But we are having the same trouble and there does not seem to be a solution.
We have Author and Publish instances are installed as two window services in the same machine.
However, It cannot start author and publish services at the same time.
We can only ever start one of them and not both.
It is possible to start two instances by clicking the quick start jars but the services fail with this error in the startup.log....
2013-11-25 16:40:12 Commons Daemon procrun stdout initialized
2013-11-25 16:40:12 Commons Daemon procrun stderr initialized
25.11.2013 16:40:12.693 *INFO * [main] Setting sling.home=. (command line)
25.11.2013 16:40:12.701 *INFO * [main] Sent 'status' to /127.0.0.1:63000: ERR: wrong key
25.11.2013 16:40:12.702 *ERROR* [main] Sling already active in C:\development\adobeCQ\publish\crx-quickstart\.
We have one instance in "C:\development\adobeCQ\publish" and the other in "C:\development\adobeCQ\author". We have one on port 4502 and the other on 4503.
We wondered if the issue was related to the log entry "/127.0.0.1:63000" but we do not know what should be done.
Please advise.
Solved! Go to Solution.
There is variable cq_ctrlport in the instsrv.bat file. You need to modify it for one of the instance.
There is variable cq_ctrlport in the instsrv.bat file. You need to modify it for one of the instance.
I will work with the documentation team to make sure we get these instructions into the main AEM documentation. Thanks for the answer Sham!
Views
Replies
Total Likes
The port number also exists in the file crx-quickstart/conf/controlport. It only worked for me once I'd changed the value in both this file and instsrv.bat and replaced the service.
In AEM 6.2, the file prunsrv_amd64.exe is missing in the standalone OSGi quickstart installation.
Had to copy it from an older 6.1 instance for a customer.
Views
Replies
Total Likes
I am facing the same issue in a linux server. The AEM server is not getting started with the ./start command and there is no error in the error.log and stdout.log files. The only error I see in stdout.log file is "*ERROR* [main] Sling already active in /mnt/crx/publish/crx-quickstart". Any suggestions to resolve it?
Views
Replies
Total Likes
esu2805 please refer my StackOverflow answer: AEM instance is not getting started with start command - Stack Overflow
Views
Replies
Total Likes