We use Crystal Reports .NET 2005 for all our reporting needs, however we all know that its PDF exporting leaves a LOT to be desired.
We are exploring our options to improve the quality of our PDF exporting and Adobe PDF printer driver seems like a great alternative.
So I use the ReportDocument.PrintToPrinter("Adobe PDF") command, set the Adobe PDF driver not to prompt for file name and this way I can use that printer drive to export programatically from my ASP.NET application. This works great in debug mode in visual studio on the server and I can see the request going to the printer under my user id.
Once I place the application in IIS - the request gets send to the Adobe PDF printer however it gets stuck in the queue - and Adobe Distiller (the conversion engine) does not start at all... I have to kill the Print Spooler service and then delete the job. The request gets made under the NETWORK SERVICE account, which I have given all sorts ...
Go to the complete details ...