Software Deployment

If you look at your fileset in the Installation Expert tab in Wise you will see what is being installed.

It sounds to me like you have another app that is conflicting with your install.

It might be Wise conflicting with it or another one.

What version if Wise are you using......does it have Conflict Manager?

Thanks for replying so quick first of All.

When I install the app on a completely bare machine with only windows on it. It fails. If Wise package Studio 5.1 is installed in any capacity, even the most basic client install which is pointing to a server and running the wfwi.exe /r from the server, and I install the app then it works straight off the bat.

So I'm thinking Wise is installing some files on the local machine which are needed by this other app. This is a pure fluke because even if I run the setup.exe of the other app on a totally clean machine with nothing not even office on it it fails. If I add wise onto it, the app starts to work. So are there Crystal reports .dll's or drivers.. or something that Wise client installs into system32. I can see that it's installing something into the system32 area when I click to install Wise, and this other app which has a backend connectivity and installs VB6 runtimes and MDAC 2.5.. So what's missing is what Wise installs. If I wasn't packaging this app with Wise it would've failed to work full stop.



Any idea's?

Yeah I agree......its either MDAC or the VB runtimes that Wise Client is sticking down that is making the app work.

Why not add the VB6 Runtime merge module into your package and see if that works.

Took me sometime but it's not the VB6 or the Mdac.
We're scripting on Vanilla XP machines so they should have version 2.7 of Mdac anyway.

What a strange situation that it works when I install it with Wise and with Office. When it has nothing to do with those apps.
After spending a considerable amount of time on the net checking out the Run-time '380' error, most resources say to install the app again.

Finally one of the developers of the app came over to spare me a few minutes of his time and the answer was as usual that I hadn't been given anywhere near as much information as I required to get the app working. The app requires that a dummy SQL DSN be created, nothing specific. This lets the app use the driver to connect to where ever it's connecting.

What had me baffled is that I coudn't see anything in RegMon and FileMon and I tried to use dependency walker but I've not used it that much, but there weren't any obvious indications in that either.

Typical of in-house developers though. Or from what I hear.

Thanks for your help..

Bottom Line. Error 380's are not indicative of anything specific... Isn't it lovely being a Packager!!