Posted by a ceTe Software moderator
This post has been resolved. The problem was a permissions issue on the DynamicPDF dll files.
The solution was to first figure out which user the Forms Authentication was being logged in with so that they could grant that user the correct permissions needed. Take a look at the following MSDN link if you need assistance determining the identity of certain configuration setting,
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/SecNetAP05.asp.
Once the user identity is know then the solution was just a matter of making sure that that user identity (typically "IUSR_MACHINE" or "ASPNET") has at least “read & execute” permissions on the dll. Keep in mind that this will require you to clear out the Temporary ASP .NET Files for that project in order for this change to take affect. Here are the steps to follow to complete this:
- Go to the DynamicPDF dll file in the bin folder of your application and add/give the appropriate account (typically "IUSR_MACHINE" or "ASPNET") “read & execute” permissions.
- Next you will need to stop the “WWW Publishing” service so that you can clear the Temp ASP files.
- Once the "WWW Publishing" service is stopped then explore to the “C:\WINDOWS\Microsoft.NET\Framework\v[your_framework_version]\Temporary ASP.NET Files” folder and then delete the folder associated with this particular application (if you are unsure you can just delete every folder in the folder).
- Once the folders have been deleted then Start the “WWW Publishing” service again.
- Now run the application again.
If anyone is receiving a similair error message and is not using forms authentication then you will likely need to follow the above steps for the ASPNET user since this is typically the identity of the default user account.
Thanks,
ceTe Software Support Team