I have a deployment issue with a COM server built in VFP9 that is called from a .Net web service.

The web service is done in VB.Net under Visual Studio 2008.

My IT test environment has Server 2003 32-bit OS, and there is no problem deploying to it, registering the COM dlls, etc. The service instantiates the COM object with no problem there.

The UAT environment is Server 2003 R2 x64. When we deploy the web service there, and the COM dll, we get this error when the web service tries to instantiate the COM object:

"Retrieving the COM class factory for component with CLSID {XXXX} failed due to the following error: 80040154." where XXXX is the CLSID in the windows registry.

On the UAT server itself, there are no errors registering the COM component, and it can be instantiated from inside VFP9.

I found this post and read through it.

http://stackoverflow.com/questions/1036856/retrieving-the-com-class-factory-for-component-with-clsid-xxxx-failed-due-to-th

I tried un-registering the component and re-registering it using the regsvr32 found in the c:\windows\SysWOW64\ folder. No effect. Other suggestions say to change the target CPU of the web service to x86 in the compile options. I could not find such a setting.

Also, my production server is 2003 R2 x64, and I have another web service/COM back end deployed there that are built like these new ones. The production web service runs fine, and I did not have to target it to x86 when building it. I can't figure out what's different...