Software Deployment

There are 2 entries for drivers in the ODBC branch:
   HKLM\Software\ODBC\ODBCINST.INI\[Driver name]
   HKLM\Software\ODBC\ODBCINST.INI\ODBC Drivers\[Driver name]=Installed

Both need to be removed. I imagine the error is because whichever one remains is permissioned differently to the other.

Game FULL access to HKLM\Software\ODBC\ODBCINST.INI
Checked that that all key have full access to everyone.

Thank you for reply.

What does ProcMon show you is happening when the remove takes place? It could be that the error message is, like more than one MS error message I've encountered is saying "Something happened but I don't know exactly what, so I'm going to show you a message which approximates the error which occured."

I get NAME NOT FOUND on the registry key.
When i check registry key for Adaptive Server Anywhere has been removed.
Could it be that msi is checking for the key that has been removed already?
Also i used custom action to set permissions to HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI
I used set setacl.exe and cmd argument:
"HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI" /registry /grant Everyone /Full /p:yes /silent
After the install i did not see everyone in the user permissions lest?
I am using wrong arguments?

Thank you.

That doesn't look like any SetACL command line I recognise. Try:

   SetACL -on "hklm\software\ODBC\ODBCINST.INI" -ot reg -actn ace -ace "n:[a domain]\Domain Users;p:full"

Note the quotes. Substitute your group for '[a domain]\Domain Users'

Try to test it manually before changing a package:
"hklm\software\ODBC\ODBCINST.INI" -ot reg -actn ace -ace "n:everyone;p:full"
setacl.exe "hklm\software\ODBC\ODBCINST.INI" -ot reg -actn ace -ace "n:everyone;p:full"

ERROR: Invalid parameter specified: -ace!

OK, fixed the cmd arguments and gave everyone full rights. However when error comes up the registry entry for Adaptive server is gone from ODBC Drivers as well as ODBCINST.INI. And error displays: Component not found in the registry. Verify that you have privileges to remove ODBC drivers.

Thank you for your help.

I think what's happened here is that the ODBC entries are out of kilter, in that a related registry key which the MSI is looking for, is missing. That's what's causing the error 6, I believe. Are you sure it installs properly to begin with? That is, are the registry entries complete when you do an install?

Turned on logging and from the log was able to see that one of the dll’s could not unregister. Missed a dll in a selfreg table. After deleting the file from selfreg table everything is fine.
Thank you, for your help.