pdfSaver4 not disposedof correctly inside a service

[guy.marom]

I noticed something weird with this process, it stays open even after I stop using the printer (And even using the RemoveOrphanPriners function leaves it open).

The problem is that I have a windows service using the API and it doesn't work.
My code, essentially does the following:
Dim objFactory As New PXCComLib.CPXCControlEx()
Dim objPrint As PXCComLib.CPXCPrinter = DirectCast(objFactory.Printer("", "MyPrinter", "", ""), PXCComLib.CPXCPrinter)
objFactory.RemoveOrphanPrinters("", "MyPrinter")

If I run these lines REPEATEDLY inside a regular application (Windows Forms application for example) it's OK.
In my win service however, this works once. If I try to restart the service then it gets stuck in the line:
Dim objFactory As New PXCComLib.CPXCControlEx()
And after a while I get the following exception:
System.Runtime.InteropServices.COMException (0x80080005): Retrieving the COM class factory for component with CLSID {217974DB-6777-4A9F-90A7-AA5EBA834BA2} failed due to the following error: 80080005

So I can't start the service again for a while (I did not notice how much time), but if I manually kill the pdfSaver4 process then everything goes back to normal.

Any comments on that?

[Ivan - Tracker Software]

Looks like for some reasons pdfSaver4 cannot create new CPXCControlEx instance. For now I don't know why.
Can you send me sample service application for testing ?

[guy.marom]

Attached is the source code of a sample service.
I'll mention that we are running the service using a user from our domain. Changing the use to the local system user and allowing it to "Interact with desktop" solved the problem (But that's not a good solution for us).

Thanks,
Guy Marom

[guy.marom]

On the same note, is the process pdfSaver necessary if I am not printing batch jobs? And if not, how do I prevent it from being loaded?

[Ivan - Tracker Software]

pdfSaver is required in any case

[guy.marom]

Any news about this?

[Ivan - Tracker Software]

For your info:
Assigning Nothing in .NET doesn't release COM object. To do this, there is method:
System.Runtime.InteropServices.Marshal.ReleaseComObject(spComObj);