Hi,
I'm using the PDF Converter V 2.51 on Vista Ultimate, and cannot enable it. The EnablePrinter call works just fine, but regardless of that I get the error code -40 when trying to print or setting up the printer.
The printer is created correctly using DriverInit and PDFDriverInit respectively (if DriverInit fails, I do a PDFDriverInit and then a DriverInit), and all calls work fine.
The situation does not change if I do the DriverInit with elevated user rights.
Any Ideas?
[Solved] Printer not activated, error code - 40, on Vista
Hi Joan,
no I do not, although I call EnablePrinter in the ENABLEDPRE event. We are using the converter to render Word format et al, so the actual printing is done by an external app.
The ENABLEDPRE event is called, EnablePrinter succeeds and then the error message appears.
Any additional hint? Can I enable any log or so?
Thanks in advance
no I do not, although I call EnablePrinter in the ENABLEDPRE event. We are using the converter to render Word format et al, so the actual printing is done by an external app.
The ENABLEDPRE event is called, EnablePrinter succeeds and then the error message appears.
Any additional hint? Can I enable any log or so?
Thanks in advance
Axel Kroll
Chief Technology Officer
SAPERION AG
Chief Technology Officer
SAPERION AG
Hello,
The PDF Converter Developer version can't be used to enable end users of your application to print any Word or other documents they select using your application, a special reason is needed here. Iif this is the case then this might be the reason for the error message.
Please check if you are getting the error message on all documents or only on large ones.
Hope this helps.
The PDF Converter Developer version can't be used to enable end users of your application to print any Word or other documents they select using your application, a special reason is needed here. Iif this is the case then this might be the reason for the error message.
Please check if you are getting the error message on all documents or only on large ones.
Hope this helps.
Both were not successful. I had already tried the first option (see my initial post), and the second option also did not change anything.
Also, I use the ENABLEDPRE ewvent just as outlined in the manual, and while this is called when I print, still the message appears.
Also, I use the ENABLEDPRE ewvent just as outlined in the manual, and while this is called when I print, still the message appears.
Axel Kroll
Chief Technology Officer
SAPERION AG
Chief Technology Officer
SAPERION AG
Hello,
I will check this issue furthermore, meanwhile please note the following:
If you are logging in as Administrator to the system you should be able to call PDFDriverInit() and EnablePrinter with no problems.
If you are logging in as a User you will not be able to call PDFDriverInit, in this case you need to have the PDF Printer installed on the system using Install.exe and in your application call DriverInit() and if the user has no writes to right to the registry then calling EnablePrinter and some other functions like (SetFileNameOptions by example) will fail because these functions need to write data to the registry.
I will check this issue furthermore, meanwhile please note the following:
If you are logging in as Administrator to the system you should be able to call PDFDriverInit() and EnablePrinter with no problems.
If you are logging in as a User you will not be able to call PDFDriverInit, in this case you need to have the PDF Printer installed on the system using Install.exe and in your application call DriverInit() and if the user has no writes to right to the registry then calling EnablePrinter and some other functions like (SetFileNameOptions by example) will fail because these functions need to write data to the registry.
Hello,
I understand this, however the calls work just fine. And yes, the system is running as administrator, and it can write to the registry. There are two options IMHO:
a) the key is wrong. We use the last key received from you, however as SPERION AG is a registered customer, we probably should compare the keys we have and the ones you have on file.
b) while writing to the registry works, probably the data is written to the wrong place in the registry. Note that this Vista here runs with a German UI, and changes a lot of names in the file system. I', not sure whether it does the same trick in the registry. Perhaps, if you could send me the items which you are expecting to be written, I could check this.
Thanks in advance
Axel
I understand this, however the calls work just fine. And yes, the system is running as administrator, and it can write to the registry. There are two options IMHO:
a) the key is wrong. We use the last key received from you, however as SPERION AG is a registered customer, we probably should compare the keys we have and the ones you have on file.
b) while writing to the registry works, probably the data is written to the wrong place in the registry. Note that this Vista here runs with a German UI, and changes a lot of names in the file system. I', not sure whether it does the same trick in the registry. Perhaps, if you could send me the items which you are expecting to be written, I could check this.
Thanks in advance
Axel