Installation directory is corrupt, could not find uninstaller: XMLPReportingTools4WordSetup.msi!

User is getting the following message after the reboot of the PC and trying to install BI Publisher (XML Publisher) on previously installed installation. User has deleted the original folder, and now unable to complete the Installation by running BIPublisherDesktop.exe. The installer first tries to uninstall and it fails because it count not find the original .msi file.

Solution

The uninstall information is located under 2 places.

“ C:\Program Files (x86)\InstallShield Installation Information” .

C:\Program Files (x86)\InstallShield Installation Information\{CF76FCE2-995F-479B-A004-1B67DFC7E80D}.

and under the following registry Key. Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{CF76FCE2-995F-479B-A004-1B67DFC7E80D}

Renaming the registry key to {CF76FCE2-995F-479B-A004-1B67DFC7E80D}.orig and rebooting the machine fixed the issue. Without rebooting, you may get a message Close the Word.

See the registry screenshots

Location of msi file

"C:\Program Files (x86)\Oracle\BI Publisher\BI Publisher Desktop\DotNetInstallFiles\XMLPReportingTools4WordSetup.msi"

This issue was happening on Windows 7 64 bit machine.

On Oracle Support following resolution is listed, but it does not resolved the issue

BI Publisher Errors ActiveX Component Can't Create Object and Installation Directory is Corrupt [ID 1088097.1]

Query 'XXX' has Tree Prompt Option criteria defined. (241,93). Queries with Tree Prompt Option criteria cannot be used in Connected Query, XML Publisher, Query Access Services and some other Applications.

The issue was due to the fact that a new record was added to an existing query and this record was not added to query tree access group assigned to user running this query.

Once the record was added to the appropriate query tree access group, issue is resolved.

This issue was noted in PT 8.50.22. In reality, the following message should be given.

The record (XXX) used by query is not available to the access group assigned to user. Hopefully they may fix this in future release.

This issue can also happen when you modify the query using a userid that has access to query record, but the user running it does not have access to it.

Query to determine all the records available to a userid.

Query to determine which records user can see