Application Center 2000 Request Forwarding Is Limited to 50 Active Sessions By Default (281439)

SUMMARY

IMPORTANT: This article contains information about editing the metabase. Before you edit the metabase, verify that you have a backup copy that you can restore if a problem occurs. For information about how to do this, see the "Configuration Backup/Restore" Help topic in Microsoft Management Console (MMC).

By default, the Application Center 2000 Request Forwarding (RF) feature is limited to 50 active sessions. If you have more than 50 active sessions, your clients will receive 502.1 errors.

MORE INFORMATION

WARNING: If you edit the metabase incorrectly, you can cause serious problems that may require you to reinstall any product that uses the metabase. Microsoft cannot guarantee that problems that result if you incorrectly edit the metabase can be solved. Edit the metabase at your own risk.

NOTE: Always back up the metabase before you edit it.

If you must change the maximum number of active sessions, you can create the metabase property 57622 (MD_RF_CONCURRENT_FORWARDS_LIMIT) under /Appcenter/Cluster on the cluster controller. By using this property, you can set the maximum number of active forwarding sessions for each member in the cluster.

You can create 57622 (MD_RF_CONCURRENT_FORWARDS_LIMIT) and apply the setting that you want by running Mdutil.exe, which is located in the Support folder on the Application Center 2000 installation media.

To run Mdutil.exe, type the following at a command prompt:

mdutil set /appcenter/cluster -prop 57622 -dtype dword -value <MaxNumberOfSessions>

The placeholder <MaxNumberOfSessions> is the numeric value that you want to set as the maximum number of forwarded sessions.

NOTE: By setting <MaxNumberOfSessions> to 0, you allow an unlimited number of forwarding sessions. Use this setting with care because it will allow unlimited resource consumption on your cluster members.