|
Hello Greg,
Thank for your time to investigate our problem. I want to make something clear with you about our problem:
- The code that I sent to you works well on our server windows 2003 except that it leaves the status in the pinter window as you will see in the screen shot attached. All you need to do to make the 3rd party COM work is to register the file PrinterOCX.dll
- We found out that excep using Acrobat Reader to open pdf file and send the print command to the ePrint, all other 3rd party COM objects to do the same job as Acrobat Reader have left the status in the ePrint window.
- By using our web application, there are always users logging on the server as windows authentication. It means the intranet users. We have already set the administration right for the logged account using DCOM eprint as the article guided.
- Again, there is no problem when using Acrobat Reader to print to the ePrint. The problem always happens with the all testing 3rd party COM objects. The reason why we dont want to use acrobat reader to do this job is:
+ Adobe do not allow any their product using on the IIS server. That would violate their policy. They offer a product called Lite Cycle to work on the server but it costs at least 50K. There is no way to use their AcroExch.App...objects in the web application. It crashes somedays.
+ Sooner or later, they will cut off the function to allow to print a pdf file form Acrobat Reader from command line as: AcroRd32.exe /t/p...Anyway, their policy: do not use their product on the server.
Greg, please try our sample code with 3rd party COM to see the error. We would appreciate you very very much.
Best reagrds,
Nam
|