Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
From Sept 2, 2022, most of the dashboards were getting failed in the Qlikview server when monitored from qmc. However the dashboards were getting refreshed at the backend but was not getting updated in Qlikview Access Point. We have found that the Qlikview Directory Service Connector service was stopped. We tried to start the service from the Microsoft management console (services.msc) but it was getting failed with the error “Error 1067 The process terminated unexpectedly”. The error snapshot has been attached for your reference. We also tried the solution as per the link (https://community.qlik.com/t5/Knowledge/Qlikview-Directory-Service-Connector-service-cannot-be-start...). But in vain.
Request your help to resolve the issue at the earliest.
The solution-approach suggested within the link isn't trivial and you may have missed anything - like stopping the services and ensuring that they aren't automatically restarted before you could adjust the config. Therefore you may try it again.
Before that I suggest to check if there is any backup of the config - manually saved in a more or less regular manner or if there were any routines for such tasks or maybe there exists some system-savings like the windows shadow copies or anything from a VM host or similar stuff. Even if there is no backup from the working environment on the 1. Sep you may get a general fallback and/or the efforts to re-create any new/changed settings since the xxx may be lesser as any repairing. If there are any routines they may overwrite an old working backup with the new failure - therefore you should do this check at first.
- Marcus
The solution-approach suggested within the link isn't trivial and you may have missed anything - like stopping the services and ensuring that they aren't automatically restarted before you could adjust the config. Therefore you may try it again.
Before that I suggest to check if there is any backup of the config - manually saved in a more or less regular manner or if there were any routines for such tasks or maybe there exists some system-savings like the windows shadow copies or anything from a VM host or similar stuff. Even if there is no backup from the working environment on the 1. Sep you may get a general fallback and/or the efforts to re-create any new/changed settings since the xxx may be lesser as any repairing. If there are any routines they may overwrite an old working backup with the new failure - therefore you should do this check at first.
- Marcus