An error occurred while running the EXCEL program after Asp.net was published to IIS.

the author lu_yongchao's blog post is http://blog.csdn.net/lu_yongchao/article/details/6606624.
the method is as follows:
In the DCOM component service. the Excel component is assigned to ASP.
(1) Open the Start Menu running dialog box, enter the dcomcnfg command, and click OK. The component service window is displayed.
(2) expand computer> my computer> DCOM configuration, and find the Program node of the Microsoft Excel application.
(3) right-click-> properties, select the "Security" option, select "Custom" for all the following three projects, and click the edit button.
(4) in the "Start permission" dialog box, click the Add button to add the corresponding user (Note: if it is Win2000 or XP, add the "machine name/ASPnet" user. Here we use win2003 as an example, win2003 is used to add a "Network Service" user) and grant the maximum permission to the user.

When you run to part (3), right-click the page and the "properties" dialog box cannot be displayed. The solution to the problem of missing properties when you right-click the page in DCOM configuration is as follows:
Make sure that the following four services are open, so that the right-click attribute can appear.
1. Remote Procedure Call (RPC)
2. COM + Event System
3. DCOM server process Launcher
4. Distributed Transaction Coordinator
After entering the component service, you can see the right-click attribute in the DCOM configuration, and the red downward arrow on "My Computer" in the component service computer disappears.

When you start the 4th Distributed Transaction Coordinator service, the system prompts the error "Windows cannot start Distributed Transaction Coordinator on a local computer". The solution is as follows:
Rename the c: \ windows \ system32 \ dtclog directory (if any) and recreate the directory. Under the command line: MSDTC-resetlog, Open Control Panel-> Administrative Tools-> service, you can see the system service list on the right, click "Start type", sort by the "Startup type" and check whether the "status" of the service with the "Startup Type" as "automatic" is "started" to find the service that has not been started, then try to start the service. If the service is started normally, OK. The above error will not occur when the system is started. If the service cannot be started properly, then, find the corresponding solution based on the startup error information, which is effective in the XP system.