Unable to install new beacon

ChrisG (Flexera Software)

6 years ago

The "Custom action RestoreBeaconIISWebConfig script error -2146827864, Microsoft VBScript runtime error: Object required: 'targetXmlElement' Line 304, Column 4," error message can occur if another version of the beacon was previously installed, and the beacon installation files were deleted off the filesystem but the beacon Windows Installer package has not been uninstalled. When you attempt to install the new beacon version, the Windows Installer package attempts to find and upgrade existing beacon files that are installed, and fails when the files cannot be found.

The following steps may help to recover from this:

Look at the Windows Installer log from your failed attempt to install the beacon software. Look for lines in the log that look similar to the following, which identify Windows Installer package GUIDs for currently installed beacon package(s):

InstallShield 10:54:02: Checking related product {9C8FE3D8-4289-4E77-87FC-BAC37D805875}MSI (c) (18!10) [10:54:02:217]: Closing MSIHANDLE (14) of type 790531 for thread 8464MSI (c) (18!10) [10:54:02:217]: Creating MSIHANDLE (15) of type 790531 for thread 8464InstallShield 10:54:02: {9C8FE3D8-4289-4E77-87FC-BAC37D805875} ***Related***MSI (c) (18!10) [10:54:02:217]: Closing MSIHANDLE (15) of type 790531 for thread 8464MSI (c) (18!10) [10:54:02:217]: PROPERTY CHANGE: Adding IS_MAJOR_UPGRADE property. Its value is 'Yes'.MSI (c) (18!10) [10:54:02:217]: Creating MSIHANDLE (16) of type 790531 for thread 8464InstallShield 10:54:02: Checking related product {65B54495-C48F-483D-9F13-E7C548D90E3E}MSI (c) (18!10) [10:54:02:217]: Closing MSIHANDLE (16) of type 790531 for thread 8464MSI (c) (18!10) [10:54:02:217]: Creating MSIHANDLE (17) of type 790531 for thread 8464InstallShield 10:54:02: {65B54495-C48F-483D-9F13-E7C548D90E3E} ***Related***The GUID(s) may be different for you, but these identify Windows Installer packages that are still considered to be installed.
Download and run the Msizap.exe tool to delete Windows Installer database entries related to any such identified packages. For example:

msizap.exe TW {9C8FE3D8-4289-4E77-87FC-BAC37D805875}msizap.exe TW {65B54495-C48F-483D-9F13-E7C548D90E3E}

Expand Post

ChrisG (Flexera Software)
6 years ago
The "Custom action RestoreBeaconIISWebConfig script error -2146827864, Microsoft VBScript runtime error: Object required: 'targetXmlElement' Line 304, Column 4," error message can occur if another version of the beacon was previously installed, and the beacon installation files were deleted off the filesystem but the beacon Windows Installer package has not been uninstalled. When you attempt to install the new beacon version, the Windows Installer package attempts to find and upgrade existing beacon files that are installed, and fails when the files cannot be found.
The following steps may help to recover from this:
Look at the Windows Installer log from your failed attempt to install the beacon software. Look for lines in the log that look similar to the following, which identify Windows Installer package GUIDs for currently installed beacon package(s):

InstallShield 10:54:02: Checking related product {9C8FE3D8-4289-4E77-87FC-BAC37D805875}MSI (c) (18!10) [10:54:02:217]: Closing MSIHANDLE (14) of type 790531 for thread 8464MSI (c) (18!10) [10:54:02:217]: Creating MSIHANDLE (15) of type 790531 for thread 8464InstallShield 10:54:02: {9C8FE3D8-4289-4E77-87FC-BAC37D805875} ***Related***MSI (c) (18!10) [10:54:02:217]: Closing MSIHANDLE (15) of type 790531 for thread 8464MSI (c) (18!10) [10:54:02:217]: PROPERTY CHANGE: Adding IS_MAJOR_UPGRADE property. Its value is 'Yes'.MSI (c) (18!10) [10:54:02:217]: Creating MSIHANDLE (16) of type 790531 for thread 8464InstallShield 10:54:02: Checking related product {65B54495-C48F-483D-9F13-E7C548D90E3E}MSI (c) (18!10) [10:54:02:217]: Closing MSIHANDLE (16) of type 790531 for thread 8464MSI (c) (18!10) [10:54:02:217]: Creating MSIHANDLE (17) of type 790531 for thread 8464InstallShield 10:54:02: {65B54495-C48F-483D-9F13-E7C548D90E3E} ***Related***The GUID(s) may be different for you, but these identify Windows Installer packages that are still considered to be installed.

Download and run the Msizap.exe tool to delete Windows Installer database entries related to any such identified packages. For example:

msizap.exe TW {9C8FE3D8-4289-4E77-87FC-BAC37D805875}msizap.exe TW {65B54495-C48F-483D-9F13-E7C548D90E3E}
Expand Post
- MM150330
  6 years ago
  Thanks for the reply Chris. This is a new server though and has never had any installation of Flexera on it before. Is there anything else we can try?
  Expand Post
  - alexander_frit
    6 years ago
    The Windows Scripting Host might be not correctly registred on that machine.
    You could try following:
    1. Open CMD as admin
    2. Go to C:\windows\SysWow64 / C:\windows\system32
    3. Run: regsvr32 scrrun.dll
    You could check if you have the latest Windows Installer Version installed, but I would expect that on Windows Server 2019.
    Antivirus applications can also block script executions.
    Expand Post