Event ID 8199 — Remote Desktop License Server Discovery

Event ID 8199 — Remote Desktop License Server Discovery

Published: January 8, 2010

Applies To: Windows Server 2008 R2

Remote Desktop license server discovery is the process by which a Remote Desktop Session Host (RD Session Host) server contacts an available license server to request Remote Desktop Services client access licenses (RDS CALs) for the clients that are connecting remotely to the RD Session Host server. If the RD Session Host server cannot discover a license server, client connections may fail.

The recommended discovery scope for a license server is forest discovery scope. If you configure forest discovery scope, RD Session Host servers, without any additional configuration, can automatically discover a license server in the same forest, because the license server is published in Active Directory Domain Services. To configure forest discovery scope, you must be logged on as an enterprise administrator to the forest in which the license server is a member.

Event Details

Product: Windows Operating System
ID: 8199
Source: Microsoft-Windows-TerminalServices-Licensing
Version: 6.1
Symbolic Name: TLS_W_TLSARW_LS_NOT_ON_DC
Message: The Remote Desktop license server is not installed on a Domain Controller and hence would not be auto-discoverable by down-level Remote Desktop Session Host servers.

Resolve
Publish the license server in Active Directory Domain Services

To resolve this issue, publish the Remote Desktop license server in Active Directory Domain Services (AD DS).

You can publish the license server in AD DS either by using Remote Desktop Licensing Manager or by using ADSI Edit. To perform these tasks, refer to the following sections.

Publish the license server by using Remote Desktop Licensing Manager

To perform this procedure, you must have membership in the local Administrators group on the license server and membership in the Enterprise Admins group in AD DS, or you must have been delegated the appropriate authority.

  1. On the license server, open Remote Desktop Licensing Manager. To open Remote Desktop 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. In the Configuration dialog box, click Publish in AD DS.

    Note:  If Publish in AD DS does not appear in the Configuration dialog box, the license server is already published in AD DS and no further action is required.

  5. Click Continue, and then click OK.

Publish the license server by using ADSI Edit

To perform this procedure, you must have membership in the Enterprise Admins group in AD DS, or you must have been delegated the appropriate authority.

  1. Open ADSI Edit. To open ADSI Edit, log on to a computer where ADSI Edit is installed (for example, a Windows Server 2008 AD DS domain controller), click Start, click Run, type adsiedit.msc, 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. On the Action menu, click Connect to.
  4. Under Connection Point, select Select a well known Naming Context, select Configuration from the drop-down list, and then click OK.
  5. Expand the Configuration container, and then expand the node that represents the domain in which the license server is a member (for example, CN=Configuration,DC=contoso,DC=com).
  6. Expand CN=Sites, and then click the container for the AD DS site in which the license server is located (for example, CN=Default-First-Site-Name).
  7. In the right pane, under Name, if there is an entry for CN=TS-Enterprise-License-Server, do the following:
    1. Right-click TS-Enterprise-License-Server, and then click Properties.
    2. Under Attributes, click siteServer, and then click Edit.
    3. Under Value to add, type in the name of the license server that you want to publish, click Add, and then click OK.
    4. Click OK to close the CN=TS-Enterprise-License-Server Properties dialog box.
  8. If under Name there is no entry for CN=TS-Enterprise-License-Server, on the Action menu, point to New, and then click Object.
  9. In the Class Object dialog box, select licensingSiteSettings, and then click Next.
  10. In Value, type TS-Enterprise-License-Server, click Next, and then click Finish.
  11. Open Active Directory Sites and Services. To open Active Directory Sites and Services, log on to a computer where Active Directory Sites and Services is installed (for example, a Windows Server 2008 AD DS domain controller), click Start, click Run, type dssite.msc, and then click OK.
  12. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
  13. Under Sites, locate the AD DS site in which the license server is located (for example, Default-First-Site-Name), and then click the name of the AD DS site.
  14. In the right pane, right-click TS-Enterprise-License-Server, and then click Properties.
  15. Under Licensing Computer, click Change.
  16. In the Enter the object name to select box, type the name of the license server, click OK, and then click OK.

Verify

To verify the discovery scope configuration of the license server, use Review Configuration in Remote Desktop Licensing Manager.

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

To verify the discovery scope configuration:

  1. On the license server, open Remote Desktop Licensing Manager. To open Remote Desktop 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.
  4. In the right pane, in the Configuration column, an entry of OK should appear in the row for the license server.
  5. To review the configuration details of the license server, right-click the license server that you want to review, and then click Review Configuration.
  6. There should not be any error or warning messages related to discovery in the Configuration dialog box.

Note:  To verify that the RD Session Host server can discover (contact) the license server, use Licensing Diagnosis in the Remote Desktop Session Host Configuration tool on the RD Session Host server.

Related Management Information

Remote Desktop License Server Discovery

Remote Desktop Services

Related:

Event ID 8199 — Server for NIS Service Availability

Event ID 8199 — Server for NIS Service Availability

Updated: December 16, 2008

Applies To: Windows Server 2008 R2

Server for NIS service availability indicates the functional state of the Server for NIS service. When Server for NIS is available, it updates NIS maps on all subordinate servers in the domain if it is running as an NIS master server, and accepts NIS replication data from Active Directory if it is running as a subordinate server.

Event Details

Product: Windows Identity Management for UNIX
ID: 8199
Source: Microsoft-Windows-IDMU-ServerForNIS
Version: 6.0
Symbolic Name: MSG_YPSERV_FREE_ARG
Message: Unable to free arguments.

Resolve
Restart Server for NIS

For some rare and undiagnosable errors, restarting Server for NIS can clear the error.

To restart Server for NIS by using the Windows interface:

  1. Open the Identity Management for UNIX management console.
  2. If necessary, connect to the computer you want to manage.
  3. Right-click Server for NIS, and then click Stop.
  4. Right-click Server for NIS again, and then click Start.

To restart Server for NIS by using a command line:

  1. Open a Command Prompt window.
  2. Type the following, and then press ENTER.
    • nisadmin [server] stop [–u user [–p password]]
  3. Type the following, and then press ENTER.
    • nisadmin [server] start [–u user [–p password]]

For more information, see the topic “Start or stop Identity Management for UNIX components” in the Identity Management for UNIX Help.

Verify

Open the Services MMC and verify that Server for NIS is operational. If the Server for NIS service properties show that the service is not running, errors are preventing Server for NIS from operating normally.

To verify that Server for NIS is running

  1. Click Start, point to Administrative Tools, and then click Services.
  2. In the Results pane of the Services MMC, double-click Server for NIS.
  3. In the Service status area of the Server for NIS Properties dialog box, verify that the Server for NIS service shows as Started.

Use the ypcat command on a client computer in the domain on which the error was generated to verify that the Server for NIS service is available.

To use the ypcat command to verify Server for NIS service availability:

  1. On a client computer in the domain on which the error was generated, open a Windows Command Prompt with elevated privileges. To do this, right click Command Prompt on the Start menu, and then click Run as administrator.
  2. Type the following command, and then press Enter: ypcat -hNISServer-dDomain Mapname. NISServer represents the name of the server on which you want to verify that the Server for NIS Service is available. Domain represents the domain name on which you want to verify that the Server for NIS service is available. Mapname represents the name or nickname of a specific NIS map that the server on which you want to verify Server for NIS availability is expected to update.
  3. If you are prompted to provide the domain administrator account name and password, type the account name and password, and then press Enter.
  4. The ypcat Windows command-line utility prints the values of all keys from the NIS database specified by Mapname, which can be a map name or a map nickname. If the ypcat utility returns a list of key values for the maps you specified, the Server for NIS service is available.

Related Management Information

Server for NIS Service Availability

Identity Management for UNIX

Related:

Calendaring agent failed in message save notification with error error code on user name: file name.

Details
Product: Exchange
Event ID: 8199
Source: EXCDO
Version: 6.5.6940.0
Component: Microsoft Exchange Collaboration Data Objects
Message: Calendaring agent failed in message save notification with error error code on user name: file name.
   
Explanation

This Error event indicates that a user tried to save an appointment, but the operation failed. Other EXCDO source events such as 8213 and 8206 may accompany event 8199.

Viewing the description of EXCDO source events that accompany Event 8199 may provide information about the underlying cause of this error. For example, you may see event 8213 with a description that states “Calendaring agent failed with error code 0x80040215 while saving appointment”. Event 8123 may be logged if the MSExchangeFBPublish registry key, or one of its subkeys, is missing from the Microsoft Windows registry.

For more information about events that can be related to Event 8199, see Microsoft Knowledge Base article 310440, You receive an “unable to perform the operation” error message when you save Calendar items in Exchange 2000 and Exchange 2003.

Error event 8199 might also be caused by a corrupted calendar item.

   
User Action

To resolve this error, try one or more of the following:

  • Verify that the Free/Busy service (MSFBPublish) is functioning correctly.
  • Examine the Application log for an event message that may provide more information about the actual error.
  • Compare the settings on the server on which the Error event occurred with those on an Exchange server that is not experiencing this error.

  • Examine the server to determine whether the MSExchangeFBPublish key exists in the registry. For information about restoring the correct registry key setting, see Microsoft Knowledge Base article 310440, You receive an “unable to perform the operation” error message when you save Calendar items in Exchange 2000 and Exchange 2003.
  • If you determine that this error was caused by a corrupted calendar item, try to identify the corrupted item. After you identify the corrupted item, deleting the item should resolve this error.

If the problem persists and if you cannot locate an event message that provides you more information about troubleshooting this issue, contact Microsoft Product Support Services.

Related:

Calendaring agent failed in message save notification with error on : .

Details
Product: Exchange
Event ID: 8199
Source: EXCDO
Version: 6.5.7638.0
Component: Microsoft Exchange Collaboration Data Objects
Message: Calendaring agent failed in message save notification with error <error code> on <user name>: <file name>.
   
Explanation

This Error event indicates that a user tried to save an appointment, but the operation failed. Other EXCDO source events such as 8213 and 8206 may accompany event 8199.

Viewing the description of EXCDO source events that accompany Event 8199 may provide information about the underlying cause of this error. For example, you may see event 8213 with a description that states “Calendaring agent failed with error code 0x80040215 while saving appointment”. Event 8123 may be logged if the MSExchangeFBPublish registry key, or one of its subkeys, is missing from the Microsoft Windows registry.

For more information about events that can be related to Event 8199, see Microsoft Knowledge Base article 310440, You receive an “unable to perform the operation” error message when you save Calendar items in Exchange 2000 and Exchange 2003.

Error event 8199 might also be caused by a corrupted calendar item.

   
User Action

To resolve this error, try one or more of the following:

  • Verify that the Free/Busy service (MSFBPublish) is functioning correctly.
  • Examine the Application log for an event message that may provide more information about the actual error.
  • Compare the settings on the server on which the Error event occurred with those on an Exchange server that is not experiencing this error.

  • Examine the server to determine whether the MSExchangeFBPublish key exists in the registry. For information about restoring the correct registry key setting, see Microsoft Knowledge Base article 310440, You receive an “unable to perform the operation” error message when you save Calendar items in Exchange 2000 and Exchange 2003.
  • If you determine that this error was caused by a corrupted calendar item, try to identify the corrupted item. After you identify the corrupted item, deleting the item should resolve this error.

If the problem persists and if you cannot locate an event message that provides you more information about troubleshooting this issue, contact Microsoft Product Support Services.

Related:

There was a failure during startup of the Microsoft Exchange H.323 Conferencing Bridge. There were problems communicating with the Service Control Manager. Error code: {error code}; Message: {message id}