Software Deployment

Somehow I saw that before uninstalling the new version of Citrix, the app un-installs the previous version. During uninstall of the previous version, it deletes a folder called C:\Program Files\Common Files\ODBC\Data Sources

I looked in the ODBC\Data Sources directory and the directory is empty. But if I remove the directory, problems seem to come up and that seems to be where the issue is pointing towards.

Question - How do I make sure that the uninstall program does not remove the ODBC directory?

One thing to check is ensure that the directory key value relating to the "Data Sources" folder is not in the "RemoveFile" table.

Thanks Mr. Hunter

I opened up both the .msi files (the version of Citrix that gets uninstalled and the newer version). But, I did not find a key for ODBC directory in the "RemoveFile" table.

Here is what is happening - I have a Wise wrapper that does the uninstall of (Citrix 6.x)and then installs the 8.x version. The wise script also checks if ODBC directory was deleted after this uninstall\install. If no ODBC directory is found, I then manually create that directory C:Program Files\Common Files\ODBC\Data Sources through my wise script.

You might ask, why do I need to create the directory? Well..If I do not create the ODBC\Data Sources directory, the next time I start Word, it starts a self repair. To avoid that annoyance, I create the ODBC\Data Sources directory (if not found) after my wise script ends.

The problem further is that it works fine till Documentum is not on installed on the machine. Once I have documentum on my machine and I run the install/uninstall of Citrix- Documentum now starts a self repair automatically after my install/uninstall program runs!

Sorry to state the obvious, but it sounds like a component in Word has this directory as a key path, which makes sense. One of the other apps is removing this folder. You need to find which app has this directory in it.

What you've done in your WiseScript is a good workaround, but not a solution.

Whichever works for you. [;)]

The standard way to remove this conflict is
Identify the component installing the discussed file and folder in both the msi. Try synchronizing the GUID of both the components, which will make sure thet theis folder is not removed when the applicatin is uninstalled.
The work around from ur wise script does a good job but it will not adhere to the windows reference count which is causing the problem.

Hope this helps you...