Software Deployment

What does a verbose log tell you?

Nothing as far as I can tell, the error you get isnt generated by Windows Installer it appears to be an error screen generated by the DLL's in the BDE Merge module.

Ill carry on looking but, as stated, nothing jumping out at me.

Paul

Ok, well, if it were me, I'd be running the app as the user with ProcMon running side-by-side as administrator (you'll need to use 'RunAs', obviously) to see what registry activity is causing the problem.

Yeh, ill give that a go and see what I can find, if anything.

Ill let ya know how it goes ;)

Paul

Right, just an update on this problem.

1) My application installs with no problems and is able to merge my new BDE configuration of I install it as an admin
2) During the installation of the same application when i log in as a bog standard user I get a BDE merge error which I have pin pointed down to a custom action called BDEConfig.
3) I have allowed the user write access to the Borland registry key as well as the temp folder and installation folder to ensure that they can update a, the idapi32.cfg file that exists, and b, create the required files in the temp folder.

I am assuming that there is something else that this custom action is the cause of my problems however have no idea what I can do to fix it.

Has anyone else installed BDE in a user environment and knows how to work around this problem, or is there a vbscript custom action that I can use to merge my idapi32.cfg file with an existing one which would save me having to use the BDE custom actions alltogether!

Thanks for your help in advance.

Paul

Did you not use ProcMon to see what that CA is doing? It *has* to be either trying to write a file or a registry entry which your permissioning isn't allowing. There's no short way you're going to find that out without some sort of monitor. The beauty of using ProcMon is that as soon as you see the error you can stop the trace and see within a few lines what's causing the problem. I can pretty much guarantee you'll see one or more entries with 'ACCESS DENIED'...

In the meantime, I found this and this

BTW, I routinely assign users Full Control rather than just Write (or Change) to registry keys as that's bitten me on the rear more than once. Obviously, this is only on the required keys, not the whole registry!

Should of said, I did run processmon which showed a problem with the Borland key, this was down to the position of secedit in the installer, basically it was allowing permisions on a key that didnt exist at that point in time. I have since moved the key to the start of the installation and precided it with a dummy vbscript that pre-creates the bde registry key and file folders and sets permissions on it.

Something I haven't done is set the permissions to full control so that is something that I will try now.

Paul