About Inabus

Inabus · ‎May 16, 2011

The ODBC entries are entry points into the MSI as they are created via the ODBC table. If you remove the ODBC table entries and add the registry keys for the ODBC settings directly into a components registry instead then the problem will be removed. Remember if you set a keypath to one of the registry keys which will get deleted when a user removes the odbc entry then it will still self repair.

Inabus · ‎May 03, 2011

Try opening up the .ISM in Orca and dropping the table from there. P

Inabus · ‎Aug 18, 2008

Set the component that the FONT is in to "Permanent" P

Inabus · ‎Aug 08, 2008

How will you handle silent installations or isnt it a consideration? Paul

Inabus · ‎Aug 08, 2008

1) Does the setup your calling run and install successfully on its own, outside of this "parent" MSI? 2) If its a pre-requisite deploy it seperatly 3) If its a post-requisite deploy it seperatly To conclude, run the setup.exe either before or after the MSI, as calling setup.exes from an MSI is asking for trouble and going to cause you heart ache, especially if the setup.exe is infact a wrapper for another MSI 😉 Paul

Inabus · ‎Mar 17, 2008

If you dont have your ProgID's linked to ClassID's the files will not link together and add themselves to the registry. If you use com extaction and see no class info, just progid, then you will need to add the progid's to the registry rather than the ProgID table. C:\Program Files\InstallShield\AdminStudio\7.5\Editor\Support\regspyui.exe The program above will allow you to look at the COM info. P

Inabus · ‎Jan 21, 2008

Have you set the correct conditions on your installs custom actions? Not Installed REMOVE~="ALL" P

Inabus · ‎Jan 18, 2008

Create new directories in the Directory table, lets call them DIRONE and DIRTWO, TARGETDIR as destination and . as the DefaultDir. Set your feature and components in question to point to those 2 directorys as their destination, all you then need to do is set those properties to what ever directory you need during install, lets say C:\Windows\Pen. I was updating the directory names using the command line when running msiexec but you could easily set the properties via the UI as part of a dialog box. P

Inabus · ‎Jan 18, 2008

Use: msiexec /i /l*c c:\ .txt That will fully log your msi installation. P

Inabus · ‎Oct 01, 2007

Glad ya figured it out. Paul

Inabus · ‎Oct 01, 2007

To be honest you will need to check the entries to find out what they are linked too. To show you what I mean The registry entry 'HKEY_CLASSES_ROOT\CLSID\{C27CCE3A-8596-11D1-B16A-00C0F0283628}\InprocServer32\ ' in component 'RegistryData_HKCR' is causing a conflict Looking at that key on my machine points to it being a part of C:\WINDOWS\system32\MSCOMCTL.OCX, so basically what that tells me is you have caught a common control OCX file that isnt part of a merge module. If your killing Citrix by installing this I would be looking inside HKLM for the problem 1st and then looking in CLSID. Does the problem on Citrix arrise once you install it or after you uninstall? The following keys look very dodgy to me though: ACE24 The registry entry 'HKEY_CLASSES_ROOT\.cdx\ ' in component 'RegistryData_HKCR' is causing a conflict. ACE24 The registry entry 'HKEY_CLASSES_ROOT\.dsn\ ' in component 'RegistryData_HKCR' is causing a conflict. ACE24 The registry entry 'HKEY_CLASSES_ROOT\.html\ ' in component 'RegistryData_HKCR' is causing a conflict. ACE24 The registry entry 'HKEY_CLASSES_ROOT\.js\ ' in component 'RegistryData_HKCR' is causing a conflict. ACE24 The registry entry 'HKEY_CLASSES_ROOT\.asa\ ' in component 'RegistryData_HKCR' is causing a conflict. ACE24 The registry entry 'HKEY_CLASSES_ROOT\.vbs\ ' in component 'RegistryData_HKCR' is causing a conflict. ACE24 The registry entry 'HKEY_CLASSES_ROOT\.asp\ ' in component 'RegistryData_HKCR' is causing a conflict. What your doing here is overriting common file associations, like .html and .vbs. If you uninstall this package there is a potential that these file associations are stripped out as well. Also looking at the following key: ACE24 The registry entry 'HKEY_CLASSES_ROOT\ODBC.FileDSN\DefaultIcon\ ' in component 'RegistryData_HKCR' is causing a conflict. Tells me you may be deploying a ODBC datasource, and if this isnt properly configured could overright something on the machine currently. Paul

Inabus · ‎Jul 09, 2007

Thanks for the info, as it wasnt for me ill let the person know who requested it and we shall see if its what they where after. Regards, Paul

Inabus · ‎Jul 06, 2007

Does anyone know if it is possile to link to ODBC data sources inside Workflow manager and if so how this is configured? Regards, Paul

Inabus · ‎Jun 20, 2006

Let there be light!! 🙂

Inabus · ‎Jun 20, 2006

You should be using the conflict solver. Basically we use it to find multiple conflicts between packages. The usual 1 we see is 2 different packages deploying the same file however the files are different versions. We have both our terminal server and desktop environment builds inside the system and add the packages in and resolve them agaisnt the builds etc. Very useful tool to ensure no issues arise with your packages! Paul

Online Status	Offline
Date Last Visited	‎Mar 18, 2019 12:10 PM

Re: ODBC Resource Key File

Try...

Component

Yup

Well...

Correct

Conditions

Not sure if you have done this yet...

msiexec

Cool

Hmm

Thanks

Workflow manager

yay...

Er...