>>>>I have a COM dll built to serve an ASP application. It works fine on my development PC including running from the development website. I'm now ready to test it on the production webserver which is running Server2003. To do this I built an installation setup.exe using Installshield Express and included all of the VFP merge modules plus MSVCR70.dll and GDIPlus.dll. The build and install goes without a hitch and I manually registered the DLL just to make sure. The new DLL however refuses to load when called from the ASP page.
>>>>
>>>>Can someone tell me what I've missed?
>>>>
>>>>This same server is already running a different VFPdll I built several years ago without a hitch for another webapp.
>>>>
>>>>Thanks.
>>>
>>>What version of VFP?
>>>If it is VFP9, it requires MSVCR71.dll.
>>>Also what error you get?
>>
>>Its ver 9 sp2 and MSVCR71.dll is also included in the redistributables. The error is:
>>error '80004005'
>>/ContactManager/export.asp, line 77
>>
>>The line in question is

set oServer = createobject("ContactManager.CMTools")

>
>Google: error 80004005 ASP and see if any of the results can help you.
>The first link I click said:
>

>Microsoft OLE DB Provider for ODBC Drivers error '80004005'
>[Microsoft][ODBC Microsoft Access Driver] The Microsoft Jet database engine cannot open the file '(unknown)'. It is already opened exclusively by another user, or you need permission to view its data.
>
>or
>
>Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
>[Microsoft][ODBC Microsoft Access Driver] '(unknown)' isn't a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.
>
>or
>
>Microsoft OLE DB Provider for ODBC Drivers error '80004005'
>[Microsoft][ODBC Microsoft Access 97 Driver] Couldn't use '(unknown)'; file already in use.
>

Borislav -
I thought you might like to know, after a lot of digging we finally compared the registry entries for my dll with the registry entries on my development box. We found the production server was missing several of the entries that were on the development box. This even though the regsvr32 routine reported that it completed OK. When the missing entries were added manually it worked OK. I don't understand it but at least it works now.
- Don