Hi,
I have been using wwPDF50 (west-wind) for years. It has worked flawlessly in windows 2000 server and windows xp (prior to sp2). I placed the class a project that I use to create a single threaded exe server. I have used the server from the vfp command prompt and in asp.net web forms to print my vfp reports in pdf format. I have registered the sever in dcom so that the aspnet user has full launch and access rights. I also have given the aspnet user full control of the actual server's exe file.

The Problem:
I migrated my development efforts to a new computer that hosts windows xp **SP2**. The Amynuni Printer Driver fails to print the report form. I set up the new computer **EXACTLY** as the old computer is set up (ie: dcom , aspnet user rights, etc. ) If I instantiate the server from the vfp command window everything works perfectly. The problem only occurs when I use the server on an asp.net web form. All functionality of the server works perfectly when it is used on an asp.net web form. The only functionality that fails in the server is the usage of the Amyuni Printer Driver. I have to think it is something in the SP2 lock down because the server works perfectly when instatiated from the vfp command line (ie: different user at that point). I checked my web.config file and no impersonation is being used. The user of my asp.net application is the ASPNET user. Could printing be an issue from an asp.net application? I also gave the ASPNET user to the Amyuni Printer Driver. Also.... the ASPNET user also has full rights to cdintf210.dll and fll210.fll which reside in system32 along with the vfp server.

Any thoughts?
Dr. G. (Neil)