hotfixHere’s a new Knowledge Base article we published today. This one talks about an issue where upgrading to Microsoft Forefront Unified Access Gateway 2010 SP1 fails with error 1603 and rolls back:

=====

Symptoms

When upgrading to Microsoft Forefront Unified Access Gateway 2010 (UAG) Service Pack 1 (SP1), the upgrade fails with error 1603 and rolls back. You may also see the following in the UAG SP1 Setup log files for UAG which are located at %ProgramData%\Microsoft\UAG\Logs:

Hybrid_Default_Web_App_Access.
MSI (s) (48!98) [08:51:45:640]: Closing MSIHANDLE (577708) of type 790531 for thread 5016
MSI (s) (48!98) [08:51:45:662]: Creating MSIHANDLE (577709) of type 790531 for thread 5016
UAG CA (Info): Error: Caught error (will rethrow after rollback): System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at Microsoft.UAG.Transformer.Core.PolicyConverter.ProcessTrunk(String trunkName, XmlNode trunkNode, String policySettingsNodeXPath)
at Microsoft.UAG.Transformer.Core.PolicyConverter.ConvertData()
at Microsoft.UAG.Transformer.Core.SchemaConversionRuntime.Run()
MSI (s) (48!98) [08:51:45:662]: Closing MSIHANDLE (577709) of type 790531 for thread 5016
MSI (s) (48!98) [08:51:45:663]: Creating MSIHANDLE (577710) of type 790531 for thread 5016
UAG CA (Info): Info: Firing ProgressChanged event: Step: 0%, Description: 'Conversion aborted due to error, Rolling back.'.
Cause

This can occur if UAG is configured with the Sharepoint-specific download and upload endpoint policies prior to running the SP1 upgrade. The installation process raises an exception and rolls back when the name of one (or more) of the existing standard policies is in use by an application.

Resolution

To resolve this issue, create new custom policies with the same data and use those instead of the Sharepoint-specific download and upload endpoint policies.

More Information

For more information see the following:

Configuring Forefront UAG access policies : http://technet.microsoft.com/en-us/library/dd857309.aspx

=====

For the most current version of this article please see the following:

2685784 : Upgrading to Microsoft Forefront Unified Access Gateway 2010 Service Pack 1 fails with error 1603

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/