Originally posted by: Staar
I used a tool that comes with visual studio 6 (depends.exe) to find the dependencies for dstxCOM.dll. I'm not sure how accurate the list is that depends.exe generated. I was at the users pc and was logged on as the user. I wonder if dstxCOM.dll gets installed during the DSTX portion of the install and not with the development kit.
Tomorrow I'm going to check and see if he has any programs running in the background that did not terminate properly that might be using the dll. Maybe that's why it can't initialize. If that doesn't work I'll have to check what files are updated by VB6 SP6. I have SP6 on my machine as well, but I already had it before I upgraded to DSTX 8.0.
Here was the list of dependencies that the depends.exe came up with. The size/modified date/time matched the files on all the other pcs that were working properly. Maybe one of them isn't registered properly. I reregistered dstxcom and dstxpi already. It's strange that it lets me declare and create the MFactory object but fails when I try to issue the InitializeAPI command. I would think one of those steps would fail if something was wrong with the dstxCOM dll. Hopefully I find a program running in the background that has a hold of it.
c:\ascential\datastagetx_8.0\DSTXCOM.DLL
c:\ascential\datastagetx_8.0\DSTXPI.DLL
c:\ascential\datastagetx_8.0\ICUDT26L.DLL
c:\ascential\datastagetx_8.0\ICUUC26.DLL
c:\ascential\datastagetx_8.0\MSVCI70.DLL
c:\ascential\datastagetx_8.0\MSVCP70.DLL
c:\ascential\datastagetx_8.0\MSVCR70.DLL
c:\ascential\datastagetx_8.0\XERCES-C_2_4_0.DLL
c:\winnt\system32\ADVAPI32.DLL
c:\winnt\system32\GDI32.DLL
c:\winnt\system32\KERNEL32.DLL
c:\winnt\system32\MSVCRT.DLL
c:\winnt\system32\NTDLL.DLL
c:\winnt\system32\OLE32.DLL
c:\winnt\system32\OLEAUT32.DLL
c:\winnt\system32\RPCRT4.DLL
c:\winnt\system32\SHLWAPI.DLL
c:\winnt\system32\USER32.DLL
#IBMSterlingTransformationExtender#IBM-Websphere-Transformation-Extender#DataExchange