| Event Information | According to Microsoft :
Diagnose :
This error might be caused by one of the following conditions:- There is a network connectivity problem between the terminal server and the license server
- The license server is not correctly configured to be automatically discovered.
- The terminal server cannot automatically discover (contact) a Terminal Services license server.
- The Terminal Services Licensing service is not running on the license server.
To resolve this issue :
Cause :
There is a network connectivity problem between the terminal server and the license server
Resolution :
Identify and fix network connectivity issues
To resolve this issues between the terminal server and the Terminal Services license server.
Note : The following procedures include steps for using the ping command to perform troubleshooting. Before performing these steps, check whether the firewall or Internet Protocol security settings on network allow Internet Control Message Protocol traffic.ICMP is the TCP/IP protocol that is used by the ping command.
To perform these procedures,must have membership in the local Administrators group or must have been delegated the appropriate authority.
If can successfully ping the license server by IP address, but not by FQDN, this indicates a possible issue with DNS host name resolution.
If cannot successfully ping the license server by IP address, this indicates a possible issue with network connectivity, firewall configuration, or IPsec configuration.
The following are some additional troubleshooting steps:- Ping other computers on the network to help determine the extent of the network connectivity issue.
- If can ping other servers but not the license server, try to ping the license server from another computer. If cannot ping the license server from any computer, first ensure that the license server is running.If the license server is running, check the network settings on the license server.
- Check the TCP/IP settings on the local computer by doing the following:
- Click Start, click Run, type cmd, and then click OK.
- At the command prompt, type ipconfig /all, and then press ENTER. Make sure that the information listed is correct.
- Type ping localhost to verify that TCP/IP is installed and correctly configured on the local computer.If the ping is unsuccessful,it may indicate a corrupt TCP/IP stack or a problem with network adapter.
- Type ping IP_address, where IP_address is the IP address assigned to the computer. If can ping the localhost address but not the local address, there may be an issue with the routing table or with the network adapter driver.
- Type ping DNS_server, where DNS_server is the IP address assigned to the DNS server.If there is more than one DNS server on network,should ping each one. If cannot ping the DNS servers, this indicates a potential problem with the DNS servers, or with the network between the computer and the DNS servers.
- If the license server is on a different subnet, try to ping the default gateway. If cannot ping the default gateway, this might indicate a problem with the network adapter, the router or gateway device, cabling, or other connectivity hardware.
- In Device Manager, check the status of the network adapter.To open Device Manager, click Start, click Run, type devmgmt.msc, and then click OK.
- Check network connectivity indicator lights on the computer and at the hub or router.Check network cabling.
- Check firewall settings by using the Windows Firewall with Advanced Security snap-in.
- Check IPsec settings by using the IP Security Policy Management snap-in.
Cause :
The license server is not correctly configured to be automatically discovered
Resolution :
Configure the discovery scope for the Terminal Services license server
To resolve this issue,use Review Configuration in TS Licensing Manager to identify and if possible correct any issues that prevent the Terminal Services license server from being automatically discovered by terminal servers.
To perform this procedure must have membership in the local Administrators group or must have been delegated the appropriate authority.
To review the configuration of the license server:- 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.If the User Account Control dialog box appears, confirm that the action it displays is what wanted, and then click Continue.
- In the left pane, click All Servers, click the name of the license server, and then on the Action menu, click Review Configuration.
- In the Configuration dialog box, review any messages that indicate that terminal servers will not be able to automatically discover this license server.
- If the discovery scope for the license server is set to Forest, but the license server is not published in AD DS, can click Publish in AD DS in the Configuration dialog box to publish the license server to AD DS.To publish the license server in AD DS,must be logged on as an enterprise administrator to the forest in which the license server is a member.
- If the discovery scope for the license server is set to Domain, but the license server is not a domain controller,should consider changing the discovery scope of the license server to Forest.To change the discovery scope of the license server, click Change Scope in the Configuration dialog box.
Cause :
The terminal server cannot automatically discover (contact) a Terminal Services license server
Resolution :
Specify a Terminal Services license server for the terminal server to use
To resolve this issue :
To perform this procedure,must have membership in the local Administrators group or must have been delegated the appropriate authority.
To specify a license server to use:- On the terminal server, open Terminal Services Configuration. To open Terminal Services Confiiguration, click Start, point to Administrative Tools, point to Terminal Services, and then click Terminal Services Configuration.
- If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
- Under Licensing, double-click License server discovery mode.
- Select Use the specified license servers, and then enter the name or IP address of the license server for the terminal server to use.
- Click OK, and then click OK.
Note: You can also specify a Terminal Services license server for the terminal server to use by using Group Policy.
Cause :
The Terminal Services Licensing service is not running on the license server
Resolution :
Start the Terminal Services Licensing service on the license server
To resolve this issue :
To perform this procedure, must have membership in the local Administrators group, or must have been delegated the appropriate authority.
To start the Terminal Services Licensing service:- 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.
- If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
- In the Services pane, right-click Terminal Services Licensing, and then click Properties.
- On the General tab, ensure that Startup type is set to Automatic.If it is not, click Automatic, and then click Apply.
- Under Service status, click Start.
- Click OK to close the Terminal Services Licensing Properties dialog box.
- Confirm that the Status column for the Terminal Services Licensing service now displays Started.
|