Paul,

Thanks for your reply. I've nailed down all of the permissions using DCOM Config. The object is launched as the local administrator and has full rights to all folders on the machine. The web user has rights to instantiate the object and I can see that the object was lauched properly as another user - the system administrator. The task manager shows the launching user as admin.

The system uses SQL Server 2005 for the back end and I've confirmed through some logging code in the objects Init that the data is being pulled properly from the server. The logging code writes to a file in the same folder as the PDF file I'm trying to create, so I know the rights are fine there as well.

When the object is launched from VBScript in a simple ASP page I added to the same site, it works perfectly. It's only when I try to call a method from the code behind, using the com DLL wrapper, that it throws the error. I've even added the old ASPCOMPAT="true" to the headers of all pages that access the dll - what am I missing? Do I have to tell the code behind to use the DLL somewhow?

Thanks again for the response - all hope is not dead ...(yet).