GFI SpamTag installation fails when upgrading (manually or via GPO): Opening app.config file []
Versions / Builds Affected
GFI MailEssentials 2015, SpamTag 19.0.152.4902
Status
Resolved
Problem Summary
GFI SpamTag cannot be updated. Even after un-installing, the installation fails.
TT / JIRAID
2538
How to Identify
GFI SpamTag cannot be upgraded. Uninstalling the old version does not help. The Installation log shows something similar (the important part which should be looked for in the log file is "Opening app.config file []" ) : MSI (s) (C0:70) [14:20:16:421]: Hello, I'm your 32bit Elevated custom action server. SFXCA: Extracting custom action to temporary directory: C:\Windows\Installer\MSI9FEA.tmp-\ SFXCA: Binding to CLR version v4.0.30319 Calling custom action GFI.Installer.ManagedActions!GFI.Installer.Actions.FileActions.SetupManagedDebugLogging 1: SetupManagedDebugLogging 2: Opening app.config file [] Exception thrown by custom action: System.Reflection.TargetInvocationException: Ein Aufrufziel hat einen Ausnahmefehler verursacht. ---> System.ArgumentException: Die URL darf nicht leer sein. Parametername: url bei System.Xml.XmlTextReaderImpl..ctor(String url, XmlNameTable nt) bei System.Xml.XmlDocument.Load(String filename) bei GFI.Installer.Actions.FileActions.SetupManagedDebugLogging(Session session) --- Ende der internen Ausnahmestapelüberwachung --- bei System.RuntimeMethodHandle.InvokeMethod(Object target, Object arguments, Signature sig, Boolean constructor) bei System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object parameters, Object arguments) bei System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture) bei Microsoft.Deployment.WindowsInstaller.CustomActionProxy.InvokeCustomAction(Int32 sessionHandle, String entryPoint, IntPtr remotingDelegatePtr) CustomAction SetupManagedDebugLogging returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) MSI (s) (C0:44) [14:20:17:717]: Note: 1: 2265 2: 3: -2147287035
Workaround / Fix Details
Manually remove the following registry key/s: 1. HKEY_CLASSES_ROOT\Installer\UpgradeCodes\2BDDE4B8890D2F349AB487E49E7359F3 Optional: 2. HKEY_CLASSES_ROOT\Installer\Products\D9B1316FE13FDDF4BB9A732292026353
Required Actions
1. Apply workaround 2. Attach article to case
Priyanka Bhotika
Comments