>>>>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.
>

Well . . . I didn't think the problem had to do with data access, but just to make sure I removed the only data access code (open database) from the INIT of the class and placed it into the individual functions which are called later on the ASP page. This did change my error to

Microsoft VBScript runtime error '800a01ad'

In chasing this error I found that the files
VFP9R.dll
VFP9T.dll
VFP9RENU.dll
did not appear on the server even though they were specified as merge modules in the Installshield project. Strange?? So I copied them into the ASP folder and registered them manually. But this did not change the error. A dependancies check says dwmapi.dll is missing, but this file does not exist on my development PC either. Folder permissions are all set open so we don't think that is the problem either.

Any other thoughts?