While configuring to auto-reload qvw document , the message "ReloadEngine@qlikview is down" showed on management console.
Trying to start the unstarted QlikView Distribution Service of windows and failed , the message in the event log showed as followed:
Is there any resolution known? Thanks in advance.
- System
- Provider
[ Name] QlikView Distribution Service v11.20.11616
- EventID 0
[ Qualifiers] 0
Level 4
Task 0
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2013-09-06T02:51:33.000000000Z
EventRecordID 24531
Channel Application
Computer Qlikview.*****.com
Security
- EventData
Initializing QlikView Distribution Service... Please wait..
- EventData
Initializing Runtime environment. Currently Logged On User=domain\ric*****lee
- EventData
Failed to create QlikView Engine.. Exception=System.Runtime.InteropServices.COMException (0x80080005): Retrieving the COM class factory for component with CLSID {BE1F19B5-415E-11D1-934D-0040333C91CC} failed due to the following error: 80080005 Server execution failed (Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE)). at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck) at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache) at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean skipCheckThis, Boolean fillCache) at System.Activator.CreateInstance(Type type, Boolean nonPublic) at QVBWrapper.Document.CreateQVBProcess(ILogBucket logBucket, Boolean createEmptyDoc)
- EventData
Startup failure. Read the log file and/or event log for determinating the cause of this problem. Note! The service must have sufficient permissions in Publisher Application Data Folder: "C:\ProgramData\QlikTech\DistributionService". Exception=System.Exception: Could not start: CouldNotStartQVB at QDSMain.MainClass.Run()
Sorry for update late. I didn't find the root cause but found I was installed a beta release. While upgrade/re-install to a stable release, the problem had gone.
