topic QV10: Server hangs after COM+ error in QlikView

QV10: Server hangs after COM+ error

Mon, 26 Jan 2026 18:19:17 GMT

We're using QV10 SR1 since last friday and the server is very unstable when running tasks. Prior the Qlikview WebServer fall, in the Event Viewer > System always appears the following error:

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date: 1/21/2011
Time: 6:15:33 AM

User: N/A
Computer: AS_E5S6
Description:

The server {7D26D6D1-415E-11D1-934D- 0040333C91CC} did not register with DCOM within the required timeout.

The GUID is for "QlikViewBatch 7.0 Application". After that, there are many errors like this:

Event Type: Error
Event Source: Application Popup
Event Category: None
Event ID: 333
Date: 1/21/2011
Time: 6:16:15 AM

User: N/A
Computer: AS_E5S6
Description:

An I/O operation initiated by the Registry failed unrecoverably. The Registry could not read in, or write out, or flush, one of the files that contain the system's image of the Registry.

In the Event Viewer > Application, I've this errors:

Event Type: Error
Event Source: QlikView Distribution Service v10.0.8811
Event Category: None
Event ID: 0
Date: 1/21/2011
Time: 6:15:34 AM

User: N/A
Computer: AS_E5S6
Description:

Failed to create QlikView Engine.. Exception=System.Runtime. InteropServices.COMException (0x80080005): Retrieving the COM class factory for component with CLSID {7D26D6D1-415E-11D1-934D- 0040333C91CC} failed due to the following error: 80080005.
at QVBWrapper.Document. CreateQVBProcess(ILogBucket i_LogBucket)

and:

Event Type: Error
Event Source: QlikView Distribution Service v10.0.8811
Event Category: None
Event ID: 0
Date: 1/21/2011
Time: 6:16:11 AM

User: N/A
Computer: AS_E5S6
Description:

Failed to create QlikView Engine.. Exception=System. ComponentModel.Win32Exception: Insufficient quota to complete the requested service
at System.Diagnostics. NtProcessManager. GetProcessIds()
at System.Diagnostics. ProcessManager.GetProcessIds( String machineName)
at System.Diagnostics.Process. GetProcessById(Int32 processId, String machineName)
at QVBWrapper.Document. CreateQVBProcess(ILogBucket i_LogBucket)

I tried a clean reinstall. I set the CPU throttle at 90%. A maximun of 6 task.

Has anyone experienced the same problem? Did you find a solution/workaround?

Thanks,

dd. //

Qlikview 10 SR1 + Windows Server 2003 (without QV Publisher)

QV10: Server hangs after COM+ error

Wed, 30 Mar 2011 08:05:16 GMT

Qlikview 10 SR1 + Windows Server 2003 (with QV Publisher) + SQL server 2005

same problem here! we installed v10 SR1 2 weeks ago. and we had 3 crashes already and the server is running very unstable.

Normal 0 21 false false false DE X-NONE X-NONE MicrosoftInternetExplorer4

Any suggestions are welcome.

regards

JJ.

This Event is appearing 4-5 times in a minute in event log.

Normal 0 21 false false false DE X-NONE X-NONE MicrosoftInternetExplorer4

Event Type: Error

Event Source: Application Popup

Event Category: None

Event ID: 333

Date: 21/03/2011

Time: 09:48:52

User: N/A

Computer: RB-2K3

Description:

An I/O operation initiated by the Registry failed unrecoverably. The Registry could not read in, or write out, or flush, one of the files that contain the system's image of the Registry.

Event Type: Error

Event Source: DCOM

Event Category: None

Event ID: 10010

Date: 21/03/2011

Time: 09:48:46

User: N/A

Computer: RB-2K3

Description:

The server {7D26D6D1-415E-11D1-934D-0040333C91CC} did not register with DCOM within the required timeout.

Event Type: Error

Event Source: MSSQLSERVER

Event Category: (2)

Event ID: 26040

Date: 21/03/2011

Time: 09:48:53

User: N/A

Computer: RB-2K3

Description:

Server TCP provider has stopped listening on port [ 1433 ] due to a failure. Error: 0x2747, state: 2. The server will automatically attempt to reestablish listening.

Event Type: Error

Event Source: SNMP

Event Category: None

Event ID: 1501

Date: 21/03/2011

Time: 09:49:09

User: N/A

Computer: RB-2K3

Description:

The SNMP Service encountered an error while setting up the incoming transports.\n The IP transport has been dropped out.

Event Type: Error

Event Source: DCOM

Event Category: None

Event ID: 10000

Date: 23/03/2011

Time: 13:05:06

User: N/A

Computer: RB-2K3

Description:

Unable to start a DCOM Server: {7D26D6D1-415E-11D1-934D-0040333C91CC}. The error:

"Insufficient system resources exist to complete the requested service. "

Happened while starting this command:

"C:\Program Files\QlikView\Distribution Service\qvb.exe -Embedding

Event Type: Information

Event Source: Application Popup

Event Category: None

Event ID: 26

Date: 23/03/2011

Time: 13:05:04

User: N/A

Computer: RB-2K3

Description:

Application popup: DTExec.exe - Application Error : The application failed to initialize properly (0xc0000142). Click on OK to terminate the application.

Event Type: Error

Event Source: Application Popup

Event Category: None

Event ID: 333

Date: 23/03/2011

Time: 13:05:39

User: N/A

Computer: RB-2K3

Description:

An I/O operation initiated by the Registry failed unrecoverably. The Registry could not read in, or write out, or flush, one of the files that contain the system's image of the Registry.

QV10: Server hangs after COM+ error

Wed, 30 Mar 2011 10:02:31 GMT


An I/O operation initiated by the Registry failed unrecoverably. TheRegistry could not read in, or write out, or flush, one of the files thatcontain the system's image of the Registry.

Insufficient system resources exist to complete the requestedservice.

Based on the two error messages above, there is memory shortage.Possible causes

the data volume grew suddenly a lot
there is some error in the QV scripts
there is some error due to upgrading components (ex due to upgrading service packs in QV, in SQL server, in OLE DB drivers)

-Alex

QV10: Server hangs after COM+ error

Wed, 30 Mar 2011 15:23:38 GMT

Actually, is a resources problem. After some research, we found that QV10 multi-threading strategy seems to be too eager. So, the workaround we found was to set the "CPU throttle" at 60%, "Max concurrent reloads" to 4 (our server has 8 cores), and schedule QV services restart every night before task reload start. Using this setup, we're getting much less COM+ errors.