Summary:

Sometimes when an installer fails there is limited information to help diagnose the problem. Below is a logging parameter which will enable the Windows Installer logging. 

Solution:

 

Security Issues 

Check for local administrator login
Try removing the PC from any domain
Disable virus scanners

Ensure there is no existing installation

Delete Bin Directory
Delete Citect folder from common files directory
Ensure that only a full release version the .NET framework v2 is installed. v1 is OK  

 

Windows Installer Issues

Check for any msi / setup.exe processes still running in the task manager
Run Microsoft Installer Clean Up utility
Upgrade the Microsoft Installer, for XPspk2 and Server 2003. XP spk3 will not allow the upgrade.

Enable Windows installer logging.

1. Open/run regedit and navigate to the following path:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
2. Add the following string value to the Installer directory: Logging
3. Add the following data/value to the Logging string value: voicewarmup
The letters in the value field can be in any order. Each letter turns on a different logging mode. Each letter's actual function is as follows for MSI version 1.1:

v - Verbose output
o - Out-of-disk-space messages
i - Status messages
c - Initial UI parameters
e - All error messages
w - Non-fatal warnings
a - Start up of actions
r - Action-specific records
m - Out-of-memory or fatal exit information
u - User requests
p - Terminal properties
+ - Append to existing file
! - Flush each line to the logTo be replaced with the solution] 
Applies To:
  • CitectSCADA 5.31, 5.40, 5.41, 5.42, 5.50, 6.0, 6.1, 7.0
  • CitectHMI 5.31, 5.40, 5.41, 5.42, 5.50, 6.0, 6.1, 7.0
  • CitectFacilities 5.31, 5.40, 5.41, 5.42, 5.50, 6.0, 6.1, 7.0
  • CitectSCADA Batch 5.31, 5.40, 5.41, 5.42, 5.50, 6.0, 6.1, 7.0
  • CitectSCADA Pocket 5.31, 5.40, 5.41, 5.42, 5.50, 6.0, 6.1, 7.0
Keywords:
Installer, Installing

Attachments