A large rollup of solutions for COM errors such as "COMException", "80070005" for Office components such as Excel, Word, and so on for each Windows Server operation

The following solutions for all Excel errors also apply to Office products such as Word, PowerPoint, and so on.

In the following solution, if the "Install Excel component" appears, it is appropriate to experience Excel errors. If it is a word error, install the word component instead of the Excel component, PowerPoint is the case, and so on.

Of course, if you are wayward enough, you can choose to install the entire Office suite and no one will say anything about you.

Error:

1. Retrieving a component in a COM class factory with a CLSID of {00024500-0000-0000-c000-000000000046} failed because of the following error: 80070005.

Windows Server 2000 or Windows XP:

Solution:

1. Install the Excel component of Office on the server.
2. Enter Dcomcnfg.exe start "Component Services" in "Start", "Run" (or Win+r key to open "run")
3. Double-click "Computer", "Component Services", "My Computer", "DCOM Configuration"
4: Find "Microsoft Excel application" in "DCOM Config", right-click on it, then click "Properties", Pop Up the properties dialog box
5. Click on the "Logo" tab and select "Interactive User"
6. Click on the "Security" tab, click "Customize" on "Launch and activation Rights", then click on the corresponding "Edit" button and fill in the "Security" dialog box.
An "ASP." User (note to select the computer name) and give it local start and local activation permissions.
7. Still the "Security" tab, click "Customize" on "Access", then click "Edit" to add an "ASP" user to the "Security" dialog box, and then give "Local access" permission
8, if still does not work, then follow the above steps to add a IUSR or IUSR_ computer name account permissions
This allows us to configure DCOM permissions for the corresponding Excel.

Windows Server 2003:

Solution:

1. Install the Excel component of Office on the server.
2. Enter Dcomcnfg.exe start "Component Services" in "Start", "Run" (or Win+r key to open "run")
3. Double-click "Computer", "Component Services", "My Computer", "DCOM Configuration"
4: Find "Microsoft Excel application" in "DCOM Config", right-click on it, then click "Properties", Pop Up the properties dialog box
5. Click on the "Logo" tab and select "Interactive User"
6. Click on the "Security" tab, click "Customize" on "Launch and activation Rights", then click on the corresponding "Edit" button and fill in the "Security" dialog box.
A "NETWORK SERVICE" User (note to select the computer name) and give it the "local launch" and "Local Activation" permissions.
7. Still the "Security" tab, click "Customize" on "Access", then click "Edit" to add a "NETWORK SERVICE" user to the "Security" dialog box, and then give "Local access" permission
8, if still does not work, then follow the above steps to add a IUSR or IUSR_ computer name account permissions
This allows us to configure DCOM permissions for the corresponding Excel.

Windows Server 2008 or Windows Server R2, Windows Server 2012, Windows Server R2:

Solution:

x64:

Build Catalog: C:\Windows\SysWOW64\config\systemprofile\Desktop

x86:

Build Catalog: C:\Windows\System32\config\systemprofile\Desktop

refer to the following discussion:http://social.msdn.microsoft.com/Forums/en-US/innovateonoffice/thread/b81a3c4e-62db-488b-af06-44421818ef91

PS: not tested on server operating systems above Windows Server 2012, but I guess this solution should work the same way.

Common solutions for all server operating systems:

Use identity impersonation validation in Web. config.
Add <identity impersonate= "true" username= "Your user name" password= "password" in the <system.web> section/>

< system.web >    <  impersonate= "true"  userName= "Your user name"  password= "Password"  /></system.web>

PS: This general-purpose solution is risky and is not recommended for use in production environments.

A large rollup of solutions for COM errors such as "COMException", "80070005" for Office components such as Excel, Word, and so on for each Windows Server operation