not register with DCOM within the required timeout.

[cPdfViewerUser]

Hi

I am developing an application which is very similar to PrintDocument in the examples.
I am currently using PDF-XChange Viewer version 2.5.311.0 in watermark mode.

I am registering the components as per the ReadMe
PDFXCview.exe /RegServer
regsvr32 PDFXCviewAx.dll /s

I am also using a registry viewing tool to confirm the modules are registered.
I use the same code on windows XP, 7, 8 and 8.1 ( all of which work except XP)

I get the following errors in the event viewer.

//======================================
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date: 12/1/2014
Time: 3:32:03 PM
User: NT AUTHORITY\NETWORK SERVICE
Computer: XP
Description:
The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date: 12/1/2014
Time: 3:52:38 PM
User: XP\sbltd
Computer: XP
Description:
The server {FA8A2DAF-0603-4D2C-AB34-FAB373B571DC} did not register with DCOM within the required timeout.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
//======================================

I have checked on-line but I cannot see any reason for this error. Have you seen this error?
do you have any suggestion of areas I can look into?

I checked some registry access permissions in XP vs Win 7 to see if this was the case but no luck.

Thanks

[Ivan - Tracker Software]

Is it 32- or 64-bits XP ? what kind of CPU do you have at this machine?

[cPdfViewerUser]

Thank You for you response.
It is a Virtual Machine running in Oracle Virtualbox.

Virtual Box 4.3.16 r95972
Windows XP Professional
Version 5.1.2600 Service Pack 3 Build 2600
Processor = 1 (host has 8 )
Ram = 2048 MB

Thanks

[cPdfViewerUser]

Hi Guys

You can delete this thread, the issue is invalid.

I have confirmed the issue is caused elsewhere.

Thanks

[Stefan - PDF-XChange]

Glad to hear that cPdfViewerUser!

Case considered resolved by us now!

Cheers,
Stefan