Hi,
Am trying to install a new beacon on a fresh Windows 2019 server. Beacon software is v13.7.0 but on install I get the following error -
Would anyone know how I can resolve?
Thanks
Mark
Aug 04, 2020 03:49 AM
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:
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 8464 MSI (c) (18!10) [10:54:02:217]: Creating MSIHANDLE (15) of type 790531 for thread 8464 InstallShield 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 8464 MSI (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 8464 InstallShield 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 8464 MSI (c) (18!10) [10:54:02:217]: Creating MSIHANDLE (17) of type 790531 for thread 8464 InstallShield 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.
msizap.exe TW {9C8FE3D8-4289-4E77-87FC-BAC37D805875} msizap.exe TW {65B54495-C48F-483D-9F13-E7C548D90E3E}
Aug 04, 2020 04:34 AM
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?
Aug 06, 2020 06:28 AM
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.
Aug 06, 2020 07:34 AM