TDM Portal Installation Fails with 'ReadserverXMLFileForPort script error'

book

Article ID: 208201

calendar_today

Updated On:

Products

CA Test Data Manager (Data Finder / Grid Tools)

Issue/Introduction

We are trying to upgrade our TDM Portal to a more recent release. When starting the TDM Portal installer, we noticed some unexpected behavior, and it appears the installation has hung and never progresses. We also noticed CA Test Data Manager Portal service and the OrientDB service was uninstalled by the installer. Therefore, we can't revert to our previous installation, and we can't move forward with the update? When we try running the installation again, it is throwing the following error: 

Error 1720. There is a problem with this Windows Installer package. A script required for this install to complete could not be run. Contact your support personnel or package vendor. Custom action ReadserverXMLFileForPort script error -2146827864, Microsoft VBScript runtime error: Object required: 'Root' Line 12, Column 1, MSI (c) (BC:94) [18:32:31:230]: Product: CA Test Data Manager Portal -- Error 1720. There is a problem with this Windows Installer package. A script required for this install to complete could not be run. Contact your support personnel or package vendor. Custom action ReadserverXMLFileForPort script error -2146827864, Microsoft VBScript runtime error: Object required: 'Root' Line 12, Column 1, Action ended 18:32:31: ReadserverXMLFileForPort. Return value 3. MSI (c) (BC:28) [18:32:31:233]: Doing action: FatalError Action 18:32:31: FatalError. Action start 18:32:31: FatalError.

In an attempt to get around the issue, we decided to try running a clean install. So, we have uninstalled Portal, cleaned the Windows registry, cleaned all TEMP folders, and rebooted the system, but still get the same error. 

 

Cause

To troubleshoot the Windows Installer it's recommended to install a copy of Microsoft's Sysinternal Process Monitor utility (Procmon), and get a capture of the processes initiated during the TDM Installation. 

In this instance, from the Procmon log we could see that the system was not creating the TDM Portal as expected for a fresh installation. This was confirmed by a closer look at the TDM installation log:

FindRelatedProducts: Found application: {78143AE1-7991-45AE-AB0B-A71F6FE4FEAD}
MSI (c) (54:3C) [16:30:51:869]: PROPERTY CHANGE: Adding OLDPRODUCTS property. Its value is '{78143AE1-7991-45AE-AB0B-A71F6FE4FEAD}'.
MSI (c) (54:3C) [16:30:51:869]: PROPERTY CHANGE: Adding MIGRATE property. Its value is '{78143AE1-7991-45AE-AB0B-A71F6FE4FEAD}'.
Action ended 16:30:51: FindRelatedProducts. Return value 1

This appears to be caused by corrupt Windows Installer cache (old Windows Registry Settings)

Environment

Release : 4.8

Component : CA Test Data Manager

Resolution

To resolve this issue we launched the Windows RegEdit utility, and ran a search for '78143AE1-7991-45AE-AB0B-A71F6FE4FEAD'. We reviewed the contents of '78143AE1-7991-45AE-AB0B-A71F6FE4FEAD' and verified this is referencing the older TDM Portal installations, and deleted the registry entry. 

After cleaning the Windows registry we were able to run the installation and perform a fresh installation of TDM Portal.