Event ID 624 — TS Gateway Server Configuration

Event ID 624 — TS Gateway Server Configuration

Updated: January 5, 2012

Applies To: Windows Server 2008

For remote clients to successfully connect to internal network resources (computers) through a Terminal Services Gateway (TS Gateway) server, the TS Gateway server must be configured correctly. The TS Gateway server must be configured to use an appropriate Secure Sockets Layer (SSL)-compatible X.509 certificate, and authorization policy settings must be configured correctly. Terminal Services connection authorization policies (TS CAPs) specify who can connect to the TS Gateway server. Terminal Services resource authorization policies (TS RAPs) specify the internal network resources that clients can connect to through a TS Gateway server.

Event Details

Product: Windows Operating System
ID: 624
Source: Microsoft-Windows-TerminalServices-Gateway
Version: 6.0
Symbolic Name: AAG_EVENT_LB_NOT_LOADBALANCING
Message: The TS Gateway server “%1” is not a member of a domain and therefore cannot be added to the TS Gateway server farm. To add this TS Gateway server to the farm, you must first add the server to a domain.

Resolve
Add the TS Gateway server to a domain

To resolve this issue, add the TS Gateway server to a domain.

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To add the TS Gateway server to a domain:

  1. Click Start, right-click Computer, and then click Properties.
  2. Under Computer name, domain, and workgroup settings, click Change settings.
  3. On the Computer Name tab, click Change.
  4. In the Computer Name/Domain Changes dialog box, under Member of, click Domain, type the name of the domain to which you want to add the TS Gateway server, and then click OK.
  5. When prompted, in the Computer Name/Domain Changes dialog box, enter the appropriate credentials.
  6. In the Computer Name/Domain Changes dialog box, a welcome message appears to confirm that the computer was successfully added to the domain. Click OK.
  7. The Computer Name/Domain Changes dialog box will appear again, stating that the computer must be restarted for the changes to be applied. Click OK.
  8. Click Close to close the System Properties dialog box.
  9. A message will appear prompting you to choose whether to restart the computer immediately or later. Click Restart now to restart the computer immediately. If you click Restart later, the computer will not be added to the domain until you restart the computer.

Verify

To verify that the TS Gateway server is configured correctly, examine Event Viewer logs and search for the following event messages. These event messages indicate that the Terminal Services Gateway service is running, and that clients are successfully connecting to internal network resources through the TS Gateway server.

To perform this procedure, you do not need to have membership in the local Administrators group. Therefore, as a security best practice, consider performing this task as a user without administrative credentials.

To verify that the TS Gateway server is configured correctly:

  1. On the TS Gateway server, click Start, point to Administrative Tools, and then click Event Viewer.
  2. In the Event Viewer console tree, navigate to Application and Services Logs\Microsoft\Windows\TerminalServices-Gateway, and then search for the following events:
    • Event ID 101, Source TerminalServices-Gateway: This event indicates that the Terminal Services Gateway service is running.
    • Event ID 200, Source TerminalServices-Gateway: This event indicates that the client connected to the TS Gateway server.
    • Event ID 302, Source TerminalServices-Gateway: This event indicates that the client connected to an internal network resource through the TS Gateway server.

Related Management Information

TS Gateway Server Configuration

Terminal Services

Related:

Event ID 624 — RD Gateway Server Configuration

Event ID 624 — RD Gateway Server Configuration

Published: January 8, 2010

Applies To: Windows Server 2008 R2

For remote clients to successfully connect to internal network resources (computers) through a Remote Desktop Gateway (RD Gateway) server, the RD Gateway server must be configured correctly. The RD Gateway server must be configured to use an appropriate Secure Sockets Layer (SSL)-compatible X.509 certificate, and authorization policy settings must be configured correctly. Remote Desktop connection authorization policies (RD CAPs) specify who can connect to the RD Gateway server. Remote Desktop resource authorization policies (RD RAPs) specify the internal network resources that clients can connect to through an RD Gateway server.

Event Details

Product: Windows Operating System
ID: 624
Source: Microsoft-Windows-TerminalServices-Gateway
Version: 6.1
Symbolic Name: AAG_EVENT_LB_NOT_LOADBALANCING
Message: The RD Gateway server “%1” is not a member of a domain and therefore cannot be added to the RD Gateway server farm. To add this RD Gateway server to the farm, you must first add the server to a domain.

Resolve
Add the RD Gateway server to a domain

To resolve this issue, add the RD Gateway server to a domain.

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To add the RD Gateway server to a domain:

  1. Click Start, right-click Computer, and then click Properties.
  2. Under Computer name, domain, and workgroup settings, click Change settings.
  3. On the Computer Name tab, click Change.
  4. In the Computer Name/Domain Changes dialog box, under Member of, click Domain, type the name of the domain to which you want to add the RD Gateway server, and then click OK.
  5. When prompted, in the Computer Name/Domain Changes dialog box, enter the appropriate credentials.
  6. In the Computer Name/Domain Changes dialog box, a welcome message appears to confirm that the computer was successfully added to the domain. Click OK.
  7. The Computer Name/Domain Changes dialog box will appear again, stating that the computer must be restarted for the changes to be applied. Click OK.
  8. Click Close to close the System Properties dialog box.
  9. A message will appear prompting you to choose whether to restart the computer immediately or later. Click Restart now to restart the computer immediately. If you click Restart later, the computer will not be added to the domain until you restart the computer.

Verify

To verify that the RD Gateway server is configured correctly, examine Event Viewer logs and search for the following event messages. These event messages indicate that the Remote Desktop Gateway service is running, and that clients are successfully connecting to internal network resources through the RD Gateway server.

To perform this procedure, you do not need to have membership in the local Administrators group. Therefore, as a security best practice, consider performing this task as a user without administrative credentials.

To verify that the RD Gateway server is configured correctly:

  1. On the RD Gateway server, click Start, point to Administrative Tools, and then click Event Viewer.
  2. In the Event Viewer console tree, navigate to Application and Services Logs\Microsoft\Windows\TerminalServices-Gateway, and then search for the following events:
    • Event ID 101, Source TerminalServices-Gateway: This event indicates that the Remote Desktop Gateway service is running.
    • Event ID 200, Source TerminalServices-Gateway: This event indicates that the client is connected to the RD Gateway server.
    • Event ID 302, Source TerminalServices-Gateway: This event indicates that the client is connected to an internal network resource through the RD Gateway server.

Related Management Information

RD Gateway Server Configuration

Remote Desktop Services

Related:

%1 (%2) %3The version store for this instance (%4) cannot grow because it is receiving Out-Of-Memory errors from the OS. It is likely that a long-running transaction is preventing cleanup of the version store and causing it to build up in size. Updates will be rejected until the long-running transaction has been completely committed or rolled back. Current version store size for this instance: %5Mb Maximum version store size for this instance: %6Mb Global memory pre-reserved for all version stores: %7Mb Possible long-running transaction: SessionId: %8 Session-context: %9 Session-context ThreadId: %10 Cleanup: %11

Details
Product: Exchange
Event ID: 624
Source: ESE
Version: 8.0
Symbolic Name: VERSION_STORE_OUT_OF_MEMORY_ID
Message: %1 (%2) %3The version store for this instance (%4) cannot grow because it is receiving Out-Of-Memory errors from the OS. It is likely that a long-running transaction is preventing cleanup of the version store and causing it to build up in size. Updates will be rejected until the long-running transaction has been completely committed or rolled back.
Current version store size for this instance: %5Mb
Maximum version store size for this instance: %6Mb
Global memory pre-reserved for all version stores: %7Mb
Possible long-running transaction:
SessionId: %8
Session-context: %9
Session-context ThreadId: %10
Cleanup: %11
   
Explanation

This Warning event indicates that the version store cannot grow because it is receiving out-of-memory errors from the operating system. The version store is where the Exchange Information Store service keeps records of transactions that are not yet finished. It is likely that a long-running transaction is preventing cleanup of the version store and causing it to increase in size. Updates to the database are rejected until long-running transactions are rolled back or deleted. When the version store is full, any updates to the database are rejected until the long-running transaction is completely committed or rolled back. This causes a service interruption for users.

   
User Action

No user action is required. However, if this warning persists, contact Microsoft Product Support. For more information, visit the Contact Us page of the Microsoft Help and Support Web site.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

process name (process id) idThe version store for this instance (name) cannot grow because it is receiving Out-Of-Memory errors from the OS. It is likely that a long-running transaction is preventing cleanup of the version store and causing it to build up in size. Updates will be rejected until the long-running transaction has been completely committed or rolled back.Current version store size for this instance: numberMbMaximum version store size for this instance: numberMbGlobal memory pre-reserved for all version stores: numberMbPossible long-running transaction: SessionId: id Session-context: value Session-context ThreadId: thread id

Details
Product: Exchange
Event ID: 624
Source: ESE
Version: 6.5.0000.0
Message: process name (process id) idThe version store for this instance (name) cannot grow because it is receiving Out-Of-Memory errors from the OS. It is likely that a long-running transaction is preventing cleanup of the version store and causing it to build up in size. Updates will be rejected until the long-running transaction has been completely committed or rolled back.Current version store size for this instance: numberMbMaximum version store size for this instance: numberMbGlobal memory pre-reserved for all version stores: numberMbPossible long-running transaction: SessionId: id Session-context: value Session-context ThreadId: thread id
   
Explanation
The version store is where the Exchange Information Store service keeps records of transactions that are not yet finished. The version store cannot grow because it is receiving out-of-memory errors from the operating system. It is likely that a long-running transaction is preventing cleanup of the version store and causing it to increase in size.

When the version store is full, any updates to the database are rejected until the long-running transaction is completely committed or rolled back. This causes a service interruption for users.

   
User Action
No user action is required.

If the problem persists, contact Microsoft Product Support Services.

Related:

{process name} ({process id}) The version store for instance {id} (“{name}”) cannot grow because it is receiving Out-Of-Memory errors from the OS. It is likely that a long-running transaction is preventing cleanup of the version store and causing it to build up in size. Updates will be rejected until the long-running transaction has been completely committed or rolled back. Current version store size for this instance: {number}Mb Maximum version store size for this instance: {number}Mb Global memory pre-reserved for all version stores: {number}Mb Possible long-running transaction: SessionId: {id} Session-context: {value} Session-context ThreadId: {thread id}

Details
Product: Exchange
Event ID: 624
Source: ESE98
Version: 6.0
Component: Extensible Store Engine
Symbolic Name: VERSION_STORE_OUT_OF_MEMORY_ID
Message: {process name} ({process id}) The version store for instance {id} (“{name}”) cannot grow because it is receiving Out-Of-Memory errors from the OS. It is likely that a long-running transaction is preventing cleanup of the version store and causing it to build up in size. Updates will be rejected until the long-running transaction has been completely committed or rolled back. Current version store size for this instance: {number}Mb Maximum version store size for this instance: {number}Mb Global memory pre-reserved for all version stores: {number}Mb Possible long-running transaction: SessionId: {id} Session-context: {value} Session-context ThreadId: {thread id}
   
User Action
No user action is required. If the problem persists, contact Microsoft Product Support Services.

Related: