Event ID 37 — Terminal Services License Server Availability

Event ID 37 — Terminal Services License Server Availability

Updated: January 5, 2012

Applies To: Windows Server 2008

The Terminal Services license server relies on the Terminal Services Licensing service to be running in order to install, issue, and track the availability of Terminal Services client access licenses (TS CALs).

Event Details

Product: Windows Operating System
ID: 37
Source: Microsoft-Windows-TerminalServices-Licensing
Version: 6.0
Symbolic Name: TLS_E_SERVICEINIT
Message: The Terminal Services Licensing service cannot start. The following error occurred: %1!s!To resolve this issue, ensure that required groups are granted the correct permissions to the TermServLicensing registry key and that the value of the DBPath registry key matches the location of the LServer directory. If the problem persists, shut down and then restart the Terminal Services license server.

Resolve
Ensure that registry permissions and values are correct on the license server

To resolve this issue, do the following on the Terminal Services license server:

  • Ensure that the required permissions are set on the TermServLicensing registry subkeys.
  • Ensure that the value of the DBPath registry subkey matches the location of the TS Licensing database.
  • Start the Terminal Services Licensing service.

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

Ensure that the required permissions are set on the TermServLicensing registry subkeys

Caution:  Incorrectly editing the registry can severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.

To check the permissions on the TermServLicensing registry subkeys:

  1. On the license server, open Registry Editor. To open Registry Editor, click Start, click Run, type regedit, and then click OK.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. Locate the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermServLicensing registry subkey.
  4. Do the following for both the Data and Parameters registry subkeys:
    1. Right-click the registry subkey (for example, Data), click Permissions, and then click Advanced.
    2. Ensure that SYSTEM, NETWORK SERVICE, Administrators, and TermServLicensing each have Full Control permissions assigned.
    3. If the permissions are not correctly assigned, click Edit to change the permissions.
    4. Click OK until all dialog boxes are closed.

Ensure that the value of the DBPath registry subkey matches the location of the TS Licensing database

By default, the TS Licensing database is located in the %systemroot%\system32\lserver folder (where %systemroot% is the folder in which the operating system is installed, which is, by default, c:\windows).

To confirm the location of the TS Licensing database:

  1. On the license server, open TS Licensing Manager. To open TS Licensing Manager, click Start, point to Administrative Tools, point to Terminal Services, and then click TS Licensing Manager.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. In the left pane, click All Servers, click the name of the license server, and then on the Action menu, click Review Configuration.
  4. The database location is listed at the top of the Configuration dialog box.

Caution:  Incorrectly editing the registry can severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.

To check the DBPath registry subkey:

  1. On the license server, open Registry Editor. To open Registry Editor, click Start, click Run, type regedit, and then click OK.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. Locate the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermServLicensing\Parameters registry subkey.
  4. In the right pane, locate the DBPath entry, and then view the value for the entry in the Data column.
  5. If the TS Licensing database folder location is incorrect, right-click DBPath, click Modify, type the correct TS Licensing database folder location in Value data, and then click OK.

Start the Terminal Services Licensing service

To start the service:

  1. On the license server, open the Services snap-in.To open the Services snap-in, click Start, point to Administrative Tools, and then click Services.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. In the Services pane, right-click Terminal Services Licensing, and then click Properties.
  4. On the General tab, ensure that Startup type is set to Automatic. If it is not, click Automatic, and then click Apply.
  5. Under Service status, click Start.
  6. Click OK to close the Terminal Services Licensing Properties dialog box.
  7. Confirm that the Status column for the Terminal Services Licensing service displays Started.

Verify

To verify that the Terminal Services license server is available, ensure that the Terminal Services Licensing service is running.

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

To verify that the Terminal Services Licensing service is started:

  1. On the license server, open the Services snap-in. To open the Services snap-in, click Start, point to Administrative Tools, and then click Services.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. In the Services pane, locate Terminal Services Licensing.
  4. Confirm that the Status column for the Terminal Services Licensing service displays Started.

Related Management Information

Terminal Services License Server Availability

Terminal Services

Related:

Event ID 37 — Remote Desktop License Server Availability

Event ID 37 — Remote Desktop License Server Availability

Published: January 8, 2010

Applies To: Windows Server 2008 R2

The Remote Desktop license server relies on the Remote Desktop Licensing service to be running to install, issue, and track the availability of Remote Desktop Services client access licenses (RDS CALs).

Event Details

Product: Windows Operating System
ID: 37
Source: Microsoft-Windows-TerminalServices-Licensing
Version: 6.1
Symbolic Name: TLS_E_SERVICEINIT
Message: The Remote Desktop Licensing service cannot start. The following error occurred: %1!s!To resolve this issue, ensure that required groups are granted the correct permissions to the TermServLicensing registry key and that the value of the DBPath registry key matches the location of the LServer directory. If the problem persists, shut down and then restart the Remote Desktop license server.

Resolve
Ensure that registry permissions and values are correct on the license server

To resolve this issue, do the following on the Remote Desktop license server:

  • Ensure that the required permissions are set on the TermServLicensing registry subkeys.
  • Ensure that the value of the DBPath registry subkey matches the location of the RD Licensing database.
  • Start the Remote Desktop Licensing service.

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

Ensure that the required permissions are set on the TermServLicensing registry subkeys

Caution:  Incorrectly editing the registry can severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.

To check the permissions on the TermServLicensing registry subkeys:

  1. On the license server, open Registry Editor. To open Registry Editor, click Start, click Run, type regedit, and then click OK.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
  3. Locate the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermServLicensing registry subkey.
  4. Do the following for both the Data and Parameters registry subkeys:
    1. Right-click the registry subkey (for example, Data), click Permissions, and then click Advanced.
    2. Ensure that SYSTEM, NETWORK SERVICE, Administrators, and TermServLicensing each have Full Control permissions assigned.
    3. If the permissions are not correctly assigned, click Edit to change the permissions.
    4. Click OK until all dialog boxes are closed.

Ensure that the value of the DBPath registry subkey matches the location of the RD Licensing database

By default, the RD Licensing database is located in the %systemroot%\system32\lserver folder (where %systemroot% is the folder in which the operating system is installed, which is, by default, c:\windows).

To confirm the location of the RD Licensing database:

  1. On the license server, open Remote Desktop Licensing Manager. To open RD Licensing Manager, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Licensing Manager.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
  3. In the left pane, click All Servers, click the name of the license server, and then on the Action menu, click Review Configuration.
  4. The database location is listed at the top of the Configuration dialog box.

Caution:  Incorrectly editing the registry can severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.

To check the DBPath registry subkey:

  1. On the license server, open Registry Editor. To open Registry Editor, click Start, click Run, type regedit, and then click OK.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
  3. Locate the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermServLicensing\Parameters registry subkey.
  4. In the right pane, locate the DBPath entry, and then view the value for the entry in the Data column.
  5. If the RD Licensing database folder location is incorrect, right-click DBPath, click Modify, type the correct RD Licensing database folder location in Value data, and then click OK.

Start the Remote Desktop Licensing service

To start the service:

  1. On the license server, open the Services snap-in.To open the Services snap-in, click Start, point to Administrative Tools, and then click Services.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
  3. In the Services pane, right-click Remote Desktop Licensing, and then click Properties.
  4. On the General tab, ensure that Startup type is set to Automatic. If it is not, click Automatic, and then click Apply.
  5. Under Service status, click Start.
  6. Click OK to close the Remote Desktop Licensing Properties dialog box.
  7. Confirm that the Status column for the Remote Desktop Licensing service displays Started.

Verify

To verify that the Remote Desktop license server is available, ensure that the Remote Desktop Licensing service is running.

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

To verify that the Remote Desktop Licensing service is started:

  1. On the license server, open the Services snap-in. To open the Services snap-in, click Start, point to Administrative Tools, and then click Services.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
  3. In the Services pane, locate Remote Desktop Licensing.
  4. Confirm that the Status column for the Remote Desktop Licensing service displays Started.

Related Management Information

Remote Desktop License Server Availability

Remote Desktop Services

Related:

The logon to Outlook Web Access failed. If the problem continues, contact technical support for your organization and tell them the following: The Active Directory profile for “%1” does not have a primary SMTP address.This may have happened because the user’s account was not created with the Exchange Management Console or Exchange Server’s command-line tools. The following Exchange Management Shell steps provide one way of correcting the most common cause of the problem. Get-User “%2” | Disable-Mailbox. Get-User “%3” | Enable-Mailbox At the prompt, enter the mailbox database name (normally “Mailbox Store”).

Details
Product: Exchange
Event ID: 37
Source: MSExchange OWA
Version: 8.0
Symbolic Name: PrimarySmtpAddressUnavailable
Message: The logon to Outlook Web Access failed. If the problem continues, contact technical support for your organization and tell them the following: The Active Directory profile for “%1” does not have a primary SMTP address.This may have happened because the user’s account was not created with the Exchange Management Console or Exchange Server’s command-line tools. The following Exchange Management Shell steps provide one way of correcting the most common cause of the problem. Get-User “%2” | Disable-Mailbox. Get-User “%3” | Enable-Mailbox At the prompt, enter the mailbox database name (normally “Mailbox Store”).
   
Explanation

This Error event indicates that the user referenced in the event description could not log on to their mailbox using Microsoft® Office Outlook® Web Access because their mailbox does not have a primary Simple Mail Transfer Protocol (SMTP) address. Each user can have one or more SMTP addresses, but one of these addresses must be the primary address. The primary SMTP address displays in bold in the Exchange Management Console. This event may occur if the user mailbox was not created by using the Exchange Management Console or the Exchange Management Shell.

   
User Action

To resolve this error, follow these steps:

  1. Disable the mailbox for the user.

  2. Create a new mailbox for the user.

You can perform these procedures by using the Exchange Management Console or the Exchange Management Shell.

For information about how to disable a mailbox, see How to Disable a Mailbox.

For information about how to create a mailbox, see How to Create a Mailbox for a New User.

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:

A user hit their quota limit on volume %2.

Details
Product: Windows Operating System
Event ID: 37
Source: ntfs
Version: 5.0
Symbolic Name: IO_FILE_QUOTA_LIMIT
Message: A user hit their quota limit on volume %2.
   
Explanation

The administrator-configured quota limit for a specific user was reached. The user can no longer save new data to the disk until files are deleted to create more space or the administrator changes the quota limit.

   
User Action

Delete any unnecessary files.

Related: