Configuration activation fails on some servers in a large array in Forefront Unified Access Gateway 2010

View products that this article applies to.

Symptoms

If you have a large array of servers that are running Microsoft Forefront Unified Access Gateway (UAG) 2010, configuration activation may fail on one or more of the array members. This problem occurs if activation takes longer than 10 minutes.

↑ Back to the top

Cause

This problem occurs because Forefront Unified Access Gateway 2010 has a hard-coded activation time-out of 10 minutes. In a large array of servers, one or more of the array members may fail to become active if activation takes longer than 10 minutes. This problem would typically only be an issue in arrays that have six or more members.

↑ Back to the top

Resolution

To resolve this problem, install Service Pack 4 for Microsoft Forefront Unified Access Gateway 2010.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

Service Pack 4 increases the activation time-out to 16 minutes and 40 seconds. Additionally, this service pack introduces two registry subkeys that enable configuration of the time-out value, if it is necessary.

Registry subkey information

If you have to increase the time-out to be longer than 16 minutes and 40 seconds, use the following registry subkeys:

Registry location: HKEY_LOCAL_MACHINE\Software\WhaleCom\e-Gap\Configuration\Storage
DWORD name: SyncSleepTime
Value data: interval between retries [msec] (default: 10000)

Registry location: HKEY_LOCAL_MACHINE\Software\WhaleCom\e-Gap\Configuration\Storage
DWORD name: SyncRetryNum
Value data: number of retries until the time-out (default: 100)

We recommend that you increase the SyncRetryNum value as needed and leave the SyncSleepTime value at the default value.

Total time out in minutes = (SyncSleepTime / 1000) * SyncRetryNum / 60

For example, to increase the time-out to 20 minutes, increase the SyncRetryNum value to 120.

Notes

After you make any changes to these registry settings, activate the Forefront UAG configuration, and then restart the Microsoft Forefront UAG Configuration Manager (ConfigMgrCom) service.
You only have to use these registry keys if you experience an activation failure that occurs after you apply Service Pack 4, and activation takes longer than 16 minutes and 40 seconds.

↑ Back to the top