COM class factory 8000401a error

[abbase]

On my system i had installed Windows Xp. Just few days back i had created charts on my web page using chart control and then saved those charts in temp folder. I was able to export these charts to excel file . The good thing is, I was able to that on my local machine. But when I put the same code in server 2003 , I start getting error : Retrieving the COM class factory for component with CLSID {00024500-0000-0000-C000-000000000046} failed due to the following error: 8000401a. can any one tell me that what i need to do in order to resolve COM class factory 8000401a error? Does any body knows about it? Kindly help me out to resolve the above issue. Thanks.

[kattman]

This is actually an security issue. since 8000401a is a documented error code. The communicator API is a client API that runs in the context of a user running the communicator client. You should look at UCMA 2.0 for and ASP.net managed application.

[ThoMas321]

The server process could not be started because the configured identity is incorrect. The best solution is to make the OPC-server service logon as the same user as the OPC-client service.Check the username and password. Does the server 2003 machine have the excel assemblies in its GAC?

[chroma]

Have you installed MS Office 2003 on your server? If you have a restrictive environment (for example, some configurations of Windows XP) then you may need to ensure that 'Enforce Access checks' is unticked on the Controller COM+ package. I believe it's not in your code because your code works perfectly fine in your developing system.

[Sam.D]

Using COM / DCOM from an ASP.NET page forces the page to run in STA threading model and is a drag on performance. Make sure MS Office 2003 is installed in your server machine. The Global Assembly Cache tool allows you to view and manipulate the contents of the global assembly cache and download cache: Gacutil.exe. Configure ASP.NET properly so that it will be allowed to use some resources in your system.

[Raine]

Make some changes also in ASP.Net Site’s web.config file. It seems the problem about the path of your word document. It would be so much easier if e-work could run under the local system account like most enterprise applications.There may be always a problem if you want to manipulate the file outside of the "WWWROOT" derectory.