Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Jan 15, 2021 11:26:22 AM
Sep 17, 2012 5:33:52 AM
When starting a QlikView service the following errors may occur:
Error 1067 <service> can't be started
1067 the process terminated unexpectedly
Investigating log files for the failing QlikView service (for example QlikView Distribution Service or Windows Application logs) indicates issues related to Performance Counters:
...
Exception=System.InvalidOperationException: Category does not exist.
at System.Diagnostics.PerformanceCounterLib.CounterExists(String machine, String category, String counter)
at System.Diagnostics.PerformanceCounter.InitializeImpl()
at System.Diagnostics.PerformanceCounter..ctor(String categoryName, String counterName, String instanceName, Boolean readOnly)
at System.Diagnostics.PerformanceCounter..ctor(String categoryName, String counterName, String instanceName)
at QDSMain.Diagnostics.QDSDiagnostic.get_Instance()
...
Alternatively, the following error may be seen:
The service must have sufficient permissions in Publisher Service Application Data folder
Make sure the correct version of .NET Framework is installed.
See the Qlik Online Help for System Requirements for your respective version.
Example: QlikView April 2019 (12.40) requires 4.7.2 or higher
If the version is fine and .NET is installed try to repair it
Sometimes it might be needed to recreate the Distribution Service folders, due to errors in the .XML files.
Do the following to rebuild performance counters:
If you get the following error:
Error: Unable to rebuild performance counter setting from system backup store, error code is 2
Try typing the following as the command:
lodctr /R
Alternative:
C:\Windows\SysWOW64>lodctr /R
Note: /R is uppercase. You must also have full administrative rights on the computer to successfully perform this command.
For more information see:
http://technet.microsoft.com/en-us/library/dd363694%28WS.10%29.aspx
http://support.microsoft.com/kb/300956
The Performance Counters might have been disabled on the Operating System Level.
Verify the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PerfOS\Performance
Disable Performance Counters should be set to 0
If rebuilding performance counter is not enough, and they are enabled in the registry, it might be that some counters are disabled from start and/or due to domain policies. The initial thing to do here is to compare the list of counters with another machine where the QDS is working to see what the differences are. The list of counters enabled/disabled on a machine can be exported by the command lodctr /q in command prompt.
One can then manually enable/disable counters with the lodctr /e or lodctr /d commands.