EDN Admin
Well-known member
<pre>Background
Server: Windows Server 2003 R2 SP2 Standard x64 (physical server).
Executable âAPI.exeâ compiled with Visual Basic 6.0 SP6.
The executable is registered on the server with âAPI.exe /regserverâ.
Problem
We have no idea of what exactly it is that triggers the problem. But after a undefined time/load/operations on the server the registration of the executable is lost or âcorruptedâ.
When calling the executable following error message is returned: âRetrieving the COM class factory for component with CLSID {E6A1ECAC-AB5F-4E31-96F5-A0A0CA5EB134} failed due to the following error: 80080005.â
The error is easily fixed with following commands:
API.exe /unregserver
API.exe /regserver
Indications
This problem has occurred since the application was installed on this x64 server.
Previously it was installed on a Windows Server 2003 32-bit server, and in that environment this strange thing never appeared.
So it may have something to do with the combination of 32-bit exe and the 64-bit server.
Do you have hint or suggestion on what we can try on the server or in the application to test to avoid the problem. (I do not know if I have selected the optimum forum)
[/code]
<br/>
<br/>
<br/>
View the full article
Server: Windows Server 2003 R2 SP2 Standard x64 (physical server).
Executable âAPI.exeâ compiled with Visual Basic 6.0 SP6.
The executable is registered on the server with âAPI.exe /regserverâ.
Problem
We have no idea of what exactly it is that triggers the problem. But after a undefined time/load/operations on the server the registration of the executable is lost or âcorruptedâ.
When calling the executable following error message is returned: âRetrieving the COM class factory for component with CLSID {E6A1ECAC-AB5F-4E31-96F5-A0A0CA5EB134} failed due to the following error: 80080005.â
The error is easily fixed with following commands:
API.exe /unregserver
API.exe /regserver
Indications
This problem has occurred since the application was installed on this x64 server.
Previously it was installed on a Windows Server 2003 32-bit server, and in that environment this strange thing never appeared.
So it may have something to do with the combination of 32-bit exe and the 64-bit server.
Do you have hint or suggestion on what we can try on the server or in the application to test to avoid the problem. (I do not know if I have selected the optimum forum)
[/code]
<br/>
<br/>
<br/>
View the full article