Everyone knows what a pain it is to configure it correctly. Numerous articles try to lay out the possible solutions, workarounds,
Here's what worked for me (it it ever gets there), on a Win XP Pro, Visual Studio 2003, ASP.NET 1.1 configuration:
- Install Office Interop DLLs
- Add the PIA DLLs to the VS Solution
- Add ASP.NET to the Administrators group?
or - Create a user with Admininstrator permissions (at least Debugger group or Power User)?
- Impersonate the user in Web.Config
- Give permissions to the directories to be read and written by the application (in my case read the template directory and write in the directory where the word document is created)
- Give permissions in the the registry to the user to the Software Office key (http://support.microsoft.com/kb/236592)
- Modify COM permissions, allowing the user to launch and activate components (http://support.microsoft.com/kb/288366/)
- Modify Microsoft Word Component in COM+ so the user impersonates it (http://forums.asp.net/1091578/ShowPost.aspx)
- Reinstall ASP.NET (aspnet_regiis -i, http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=363330&SiteID=1)
- Reboot the machine
- Cross your fingers
Considerations:
- Don't Use It http://support.microsoft.com/?id=257757; http://support.microsoft.com/kb/317316/
- Safe Mode http://support.microsoft.com/kb/827706
Errors:
- PIA not found http://support.microsoft.com/kb/823996
- Rejected Safe Mode Action:
- Terminal Services & Outlook http://support.microsoft.com/?kbid=319517
- COM+ configuration http://support.microsoft.com/kb/288366/; http://support.microsoft.com/kb/288367/ (verify registry IDs!); http://support.microsoft.com/kb/288368/
- Start Word/Excel in "safe mode", "automation" running as the specified user
- Clean up: Help --> About ... --> Disabled Items --> Enable (http://support.microsoft.com/kb/813589; http://support.microsoft.com/kb/827706)
- Server Execution Failed
No comments:
Post a Comment