Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi all,
ive tried to upgrade Qlik Sense (server) from v1.1 to v2.0.1. At the end of the installation not all the services was started. Nothing interesting in the log files (no errors or warnings).
Database service and Service Dispatcher services are started. All other services are off. When try to start the Repository service - it failed. Again nothing interesting in the log files. In the event viewer also nothing interesting. There are only 2 messages from the repo service:
1) A timeout was reached (30000 milliseconds) while waiting for the Qlik Sense Repository Service service to connect.
2) The service did not respond to the start or control request in a timely fashion.
Anyone experienced something like this?
Regards!
Stefan
Managed to start it! The trick was to increase the time before timeout is called. The default windows timeout is 30 seconds. Increased it on 2 minutes and all services started from the first time!
To increase this value to 2 mins (120 seconds), follow these steps:
1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
3. In the right pane, locate the ServicesPipeTimeout entry. Note If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:
a. On the Edit menu, point to New, and then click DWORD Value.
b. Type ServicesPipeTimeout, and then press ENTER
4. Right-click ServicesPipeTimeout, and then click Modify.
5. Click Decimal, type 120000, and then click OK. This value represents the time in milliseconds before a service times out.
Note: 120000 milliseconds (2 minutes) is equal to what the default configuration should be. You may find you need increase this number. 300000 (5 minutes) may be more suitable.
6. Restart the computer.
Stefan
Managed to start it! The trick was to increase the time before timeout is called. The default windows timeout is 30 seconds. Increased it on 2 minutes and all services started from the first time!
To increase this value to 2 mins (120 seconds), follow these steps:
1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
3. In the right pane, locate the ServicesPipeTimeout entry. Note If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:
a. On the Edit menu, point to New, and then click DWORD Value.
b. Type ServicesPipeTimeout, and then press ENTER
4. Right-click ServicesPipeTimeout, and then click Modify.
5. Click Decimal, type 120000, and then click OK. This value represents the time in milliseconds before a service times out.
Note: 120000 milliseconds (2 minutes) is equal to what the default configuration should be. You may find you need increase this number. 300000 (5 minutes) may be more suitable.
6. Restart the computer.
Stefan
Hi Stefan,
Thanks for sharing this, I was having the same issue and this corrected the problem.
Much appreciated.
Kind regards,
Rod
Thx! You saved my day.
Worked like a charm, thanks!
Thanx for your sahre. It is a perfect solution to this issue,
Many things Stefan,
I faced the same issue with a new installation, and it has worked perfectly.
Thanks Stefan,
I had the exact same problem and your suggestion resolved the problem.
Fresh W2012 R2 and install of QS 2.1.1.0, all working fine
Windows Update and server restarted over the weekend, now only two of the services will start.
Made the registry change and now all services will start again.
Also upgraded to 2.2.3.0 for good measure and services all still ok.
Hello Stefan
I'm had different problem. i'm Can't stop QS Engine when this service use 80% ram ( WorkingSet High)
If I kill Engine.exe it's corrupted application in RAM.
When application consuming low RAM stop and restart success,
Give me any advice.
Hi Stefan,
I had the same issue on version 3.1.1, the upgrade to the version 3.1.3 solved the issue, but when I tried to restart the services few days after the issue came again.
The upgrade of the DotNet Framework to version 4.6.2 has solved my issue.
An other post for this issue: https://qlikcommunity.qliktech.com/thread/174460
Regards.