Reply to Message

View discussion in a popup

Replying to:
JLogan3o13
Contributor
Contributor

Receiving a DLL error when launching one part of a thinapped application

I am new to ThinApp, but have had pretty decent success thus far. I have one application, however, that is giving me fits; if anyone could assist it would be greatly appreciated. The application in question is called HEAT, it is a call ticket tracking app for our Helpdesk folks. The app runs off an Oracle 10g database structure. I thinapped Oracle 10g by itself, then Heat by itself, and then set the path to the oracle exe under required applinks in the .ini for HEAT. This seems to work for most of the modules in the main application, they all start and run flawlessly. The main executable, though, throws an error that references a missing or unregistered .dll file. The specific error is Unable to locate BCGPOleAcc.dll. To see this demo properly, you need to put BCGPOleAcc.dll to your path and register it.

On a physical install of the application, this dll gets put into the System32 folder, and puts two entries into the registry - one under HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18(current user)\Components\8DA0F8E859E886D4F85A92FD4F1A7D41 and the other under HKLM\Software\Microsoft\Windows\CurrentVersion\SharedDLLs. In the thinapp directory, I have confirmed that the dll is there in the %SystemSystem% folder. I have also confirmed the above two entries under the HKEY_LOCAL_MACHINE.txt. Also, when building, I see that it states the dll has been added successfully (see attached). Thus far, after reading through literally all 58 pages on this discussion board, I have tried the following: changing between merged and write copy isolation on the main package, changing the isolation in the HKEY_LOCAL_MACHINE.txt for those entries from Write Copy to Full, specifying the dll under Required Applinks in the .ini, and even just having the .dll already existing on the machine before I try to run the thinapp - pointing the app to the physical dll file. So far, none of this has worked for me, yet all other modules in this application work fine. If anyone could provide some suggestions, or point out what I may be missing in registering this dll, that would be great.

Reply
0 Kudos