Qlik Community

QlikView Deployment

Discussion Board for collaboration related to QlikView Deployment.

Not applicable

Cannot input License info - Server service errors with Error: 1053

We were installing a QV server yesterday and the server did not have internet access. The install failed as a result. We connected the server, uninstalled and reinstalled and now the server service does not start.

We can open Management Console but the input boxes where one enters the license number are "unclickable". You cannot input any information in them. The server service is shown as not running and attempts to start it return this:

Could not start the QlikView service on Local Computer
Error 1053:The service did not respond to the start or control request in a timely fashion

We appear to be in a loop: The service won't run to take the license key. The license cannot be entered becase (it appears) the key must be present.

Thanks in advance for any ideas.

1 Solution

Accepted Solutions
Employee
Employee

Cannot input License info - Server service errors with Error: 1053

Go to start >run > and type regedit go to Computer\HKEY_Local_Machine\SOFTWARE\QlikTech and erase the QlikViewServer folder.

This should allow you to start the server then enter the key and reset all settings in the QEMC.

/Karl

4 Replies
Employee
Employee

Cannot input License info - Server service errors with Error: 1053

Go to start >run > and type regedit go to Computer\HKEY_Local_Machine\SOFTWARE\QlikTech and erase the QlikViewServer folder.

This should allow you to start the server then enter the key and reset all settings in the QEMC.

/Karl

Not applicable

Cannot input License info - Server service errors with Error: 1053

Thanks Karl, we'll give it a shot.

M

Not applicable

Cannot input License info - Server service errors with Error: 1053

This worked. Thank you for this suggestion and fix!

Emmanuelle-Bustos
Valued Contributor

Cannot input License info - Server service errors with Error: 1053

I had the same issue and was because the ports 4747 and 4774 wasn't open.