We are running the PDF Converter from a VB code run by an NT service.
The application stop when we create the object:
"...Dim PDFPrinter As New CDIntf.CDIntf ..."
Are there any considerations to use the PDF Converter under an NT Service?
Thanks,
Celso
Running PDF Converter from NT Service
Please try our latest version 2.08. You can download it from http://www.amyuni.com/en/products/pdf_c ... /demo.html
Note: I am assuming that you have the right to create objects on the NT system.
Note: I am assuming that you have the right to create objects on the NT system.
Hi,
Microsft provides a knowledge base article that explains what is needed to have Applications run from a NT Service.
http://support.microsoft.com/default.as ... s%3B152451
Thanks
Microsft provides a knowledge base article that explains what is needed to have Applications run from a NT Service.
http://support.microsoft.com/default.as ... s%3B152451
Thanks
Hi thank you for your precious feedback.
We already checked Technet's Q152451 article. We tested using both the System Account as well as an User account with administrative privileges.
We checked all items of Q152451 (copied a lot of printer config entries to the Default User hive) to have the service work with the System account - the problem persisted. When using an "admin" account, we logged interactively as the admin account to check that the Amyuni printer is present (it is, as it is installed locally) - the problem persists. Note that the error always occurs when executing the "...Dim PDFPrinter As New CDIntf.CDIntf ..." code in VB.
Our license supports only V 2.05. As we tested V 2.05 in both situtations mentioned before, and the system errors out in the "... Dim.. " line. Is this a know problem fixed by 2.08? Do you happen to have an example of code running as a Win32 service?
Again thanks for the patience!
Kind Regards,
Celso
We already checked Technet's Q152451 article. We tested using both the System Account as well as an User account with administrative privileges.
We checked all items of Q152451 (copied a lot of printer config entries to the Default User hive) to have the service work with the System account - the problem persisted. When using an "admin" account, we logged interactively as the admin account to check that the Amyuni printer is present (it is, as it is installed locally) - the problem persists. Note that the error always occurs when executing the "...Dim PDFPrinter As New CDIntf.CDIntf ..." code in VB.
Our license supports only V 2.05. As we tested V 2.05 in both situtations mentioned before, and the system errors out in the "... Dim.. " line. Is this a know problem fixed by 2.08? Do you happen to have an example of code running as a Win32 service?
Again thanks for the patience!
Kind Regards,
Celso