We have created an SSIS package in VS 2005 that will go out and look in a directory, see a file (in this case a PDF) that is created from a subscription from a SSRS report and prints it to a network printer. If I execte the package from within VS it works perfectly. The problem is that we need this to be scheduled at a certain time of the day so we scheduled it run in a SQL Job. The job runs and reports sucessful but the printing is not happening. We have applied a proxy to the job but still no printing. The proxy's cedentials have full domain administrator rights to the entire network. All other aspects of the job are working as expected; only the SSIS will not print the documents. Any help is

oh and one more thing the service account that runs the SQL Service Agent has domain admin access as well as the proxy. :)

If you would try to execute just the PDF print command onn the SQL Agent server using the same credentials, could that be printed?Arthur My Blog

Are you asking if we run the print step within the job? That we have done with no results. If not can you please be more discriptive in what you are asking me to try? Timothy P. Early CIW-P, CIW-I, CIW-A Torrance Memorial Medical Center 3330 W. Lomita Blvd. Torrance, CA 90505 Office 310-325-9110 x2038 Mobile 310-901-0163

If i understand your reply... we did try to execute the print command from the command line and it did not work...also we do have acrobat reader installed on the SQL server

This is what I wanted to know, thank you, so we rule out SSIS as responsible now. Next stage: when you say that it did not work, you probably got an error(s), correct? What was the error? Also, it is almost clear that the server box is lacking something, may be just a route to the printer or a component, or something, that error message may carry the clue. Also you can try to print a PDF file from the server interactively, I think as most servers, it probably just does not have the printer configured.Arthur My Blog

When we open the package up in VS and execute the package manually all works perfectly. When we try to execute the package in a SQL Job the job completes successfully therefore there are no errors. The package is moving and renaming the files then nothing. It is suppose to print the files from a network directory. so nothing prints and no errors. Thank you

If you do not have the logging enabled in your package you just do not see the errors because the SQL Agent is not going to provide you with any logging. I suggest you add the logging and re-try.Arthur My Blog