Oracle Discoverer 4.1.x

[Axi0n11]

Hello Everyone...

Thanks to some useful info here I was able to ThinApp Oracle ADI 7.1.28 successfully and get it working on Windows 7 x64 Pro... Our other product Oracle Discoverer 4.1.43 is causing some real problems...

When I try to start it from a machine using the ThinApp package, starting the Desktop Edition gives me a DIS4USR.EXE > dcw.dll module could not be found... Trying to start the Administration module gives me DIS4USR.EXE > dcd.dll could not be found...

As far as I can tell those dll's are included in the package..?? Does Discoverer look for them explicitly in the path it is originally setup with???

In my case...

c:\orant\discvr4

Or can I try to kludge the problematic DLL's somewhere that is included in the system path???

So far I have tried dumping them into the %SystemSystem% folder when building the package but the DLL complaints persist...

Any thoughts, or help???

Cheers,

Matt.

[shrivastavaa]

Does it work in 32 bit OS, if yes than try following steps.

You can verify the files in package using CMD. (Enable cmd.exe in package.ini)

Considering it is a 64 bit machine , you may try following thing in case these .dll files are located in "program files x86"

Create similar directory structure in "Program files" and copy the dll files. (do it in the system, not inside package)

Now try re-launching it, if it works than you can recapture it and instead of installing it to program files, install it to some custom folder, like c:\discover.

My guess is that the application may expect the file to be located at program files and not program files x86.

[Axi0n11]

Thanks for the direction... It wasn't exact, but it got my head re-focused in the right direction...

I was making the initial clean capture on a Server 2003 box as it was a machine I had in vm completely clean and known to work with Oracle ADI and Discoverer.

Turns out what I was actually missing was the Visual C++ Runtime 2005... It seems the initial Windows 2003 had it installed somehow already prior to my "prescan" so some files were definitely getting missed when I finished up the rest of the project...

Got the vcredist_x86 from Microsoft, installed it along with ADI and Discoverer, because the registry changes would be noticed when I installed the package but possibly not the files themselves, so I made sure I added msvcp50.dll to %SystemSystem% before building the package...

Now that I have the actual software working to a point I can connect to the backend Oracle DB's I can focus on ensuring the hooks from ADI to Excel 2003 all function as expected, as well as J-Initiator / IE7 capture...

Cheers,

Matt.

[shrivastavaa]

Gr8 that you found the root cause.

I was suspecting a generic bug which I have seen occasionally on 64 bit platforms.