Was anything resolved on this - I am having the exact same problem. The DLL (VFP 6.0) is registered and runs fine on the development machine (Win2k Pro) but will not register on either of two Win2K Servers. I have the same error. I even tried to package the .dll with the setup wizard and included the VFP run time. Still no luck. Surely someone else has seen and resolved this problem!

I need this COM to acheive MS Word automation on a web services backend. My COM makes interacting with the word.application object to perform server side merges much easier.

Any more ideas?

JP Steffen


>>>Did you include an empty main program with the same name as the dll?
>>
>>I built it that way and tried to register it on the client's machine, but unfortunately got the same error as before. To be sure I understand your suggestion: the project now contains two prgs - the main prg is empty except for a comment and has the same name as the DLL, the other prg has the class definition in it. Is that what you meant?
>
>Yep! It was a shot in the dark (and it missed). About the only other thing I can think of that would cause this, I'm sure that you covered. Namely, you did include the type library and registry files, didn't you? Yeah, I know, stupid question, but I had to ask just to be sure.
>
>>----------------
>>>>A DLL I created in VFP 6 works fine on the machine on which I created it, but I cannot get it to register on any other machines. I am trying to register it manually using REGSVR32 myControl.DLL. The error message is "DLL Register Server in myControl.DLL failed. The return code was 0x80004005". The DLL was built as an MTDLL under Win98SE. I am distributing the DLL, the TLB, and the VBR. The VFP6 run times are properly installed on these other machines. The DLL is a PRG-based class defined with DEFINE CLASS myClass AS CUSTOM OLEPUBLIC. Very simple class, just a couple of methods and protected properties.
>>>>
>>>>I'm probably missing something really obvious here. Anybody see it?
>>>>
>>>>FWIW the closest thing I can find in the MSDN KB is Q307495, which is the same error message but pertains to a VB WebClass. No VB, no WebClass in my case.