I thought my issue of the QV Management Service not starting was resolved using a cmd prompt command lodctr /R. However, when I reboot the server the problem occurs again. The user account I am using is a local admin and it is in the QlikView Administrator Group. Below are the event log messages of the error. I'm not sure at this point what is causing this issue.
Any information to resolve this issue would be greatly appreciated. Thank you!
Source: .NET Runtime
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
Source: Application Error
Faulting application name: QVManagementService.exe, version: 11.20.12347.0, time stamp: 0x53480302
Faulting module name: KERNELBASE.dll, version: 6.1.7600.17206, time stamp: 0x50e669a2
Hey Alec, Did you get your issue resolved by support? Make sure you reboot the server after you redo the performance counters. Make sure you have all the .net updates installed. You can also make your services have delayed start. Your QlikTech folder could be corrupted. Stop the services, rename the QDS and QMS folder to old and start the services.
Attached is the support information on resolving the issue. I got QMC running by executing the lodctr /r command at the command prompt. However, when the server is rebooted, QMC won't start again. I have a follow up call with support. I'll pass on what I find out. I hope the attached helps your issue.
Switch your services( I am assuming you have a 2008 server) from "Automatic" to "Automatic( delay start)". I would highly suggest to reach you internal IT team to check your machine, if lodctr /r fixes the problem, that means something is corrupting the registry performance counters, so a rebuilt (/r) is needed after a reboot.
Giuseppe Novello Principal Technical Support Engineer @ Qlik
I do have the services set to a delayed start. Running the lodctr /r rebuild fixes the issue until I re-boot the server. I'll look into what is corrupting the registry performance counters and will let everyone know what I find.