Home > Event Id > The Terminal Server Cannot Issue A Client License Windows 2000

The Terminal Server Cannot Issue A Client License Windows 2000


x 38 Jacob Langballe This happened to us when the remote registry services was set to manual. We're a friendly computing community, bustling with knowledgeable members to help solve your tech questions. Verify To verify that the terminal server can discover (contact) a Terminal Services license server with the appropriate type of Terminal Services client access licenses (TS CALs), use Licensing Diagnosis in Terminal On the Edit menu, point to New, and then click String Value 4. Source

Had the problem that when TS server was in Admin mode, no problems connecting at all. See Microsoft TechNet and the usage of RegMon and FileMon for additional information. How many Terminal Servers generate the error(s) and are the Terminal Servers on the same subnet/domain as the TSCAL Server? Click Start > Run, type regedit, and click OK. https://technet.microsoft.com/en-us/library/cc775148(v=ws.10).aspx

The Terminal Server Cannot Issue A Client License Windows 2000

Confirm that all license servers on the network are registered in WINS\DNS, accepting network requests, and the Terminal Services Licensing Service is running. More resources Tom's Hardware Around the World Tom's Hardware Around the World Denmark Norway Finland Russia France Turkey Germany UK Italy USA Subscribe to Tom's Hardware Search the site Ok About In the Access Control Settings for MSLicensing, click Apply, then OK. Restart the terminal server and the client computer and then try again to connect remotely to the terminal server from the client computer.

Is Control Panel - MSLicensing set to per-server or per-seat? 9. Issue 1 When connecting with a Citrix ICA Client after downloading a Remote Desktop Protocol (RDP) Web Client, the RDP Client may not exhibit any problems and continue to connect. Disable the TSCAL Server from this server. 5. No Terminal Server License Servers Available To Provide A License No, create an account now.

To open Registry Editor, click Start, click Run, type regedit, and then click OK. Can't Create Certificate Context Error 0. Event Id 38 Event ID 1009 may also be observed when Windows Server 2003 terminal servers are installed in per-user mode from the start, resulting in the LicensingGracePeriodEnded registry key not being set.This key Rely on default permissions 1 - Do not allow enumeration of SAM accounts and shares 2 - No access without explicit anonymous permissions For example: say you have 2 terminal servers, Login here!

Isolation Steps Isolate the problem server to a workgroup and/or promote it to a domain controller. Event Id 1004 Application Error If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue. From the same notebook through a VPN tunnel across a remote access broadband connection, I can only initiate Terminal Services sessions on the two servers that have Terminal Services installed in If this is the problem, you have to change the MTU size.

Can't Create Certificate Context Error 0. Event Id 38

To open Terminal Services Configuration, click Start, point to Administrative Tools, point to Terminal Services, and then click Terminal Services Configuration. http://kb.eventtracker.com/evtpass/evtPages/EventId_1004_TermService_45698.asp Clients were not able to login. The Terminal Server Cannot Issue A Client License Windows 2000 Solution-2 For Windows 2003 Terminal Server, follow Microsoft TechNet article How to override the license server discovery process in Windows Server 2003 Terminal Services to add the Terminal Server License Server. Event Id 1004 Msiinstaller Note that this Group Policy setting will take precedence over the setting configured in Terminal Services Configuration and takes precedence over the Set client connection encryption level policy setting.

If you are making a desktop connection, then opening ICA connection inside the desktop session (Pass-through) and the subsequent ICA connection will fail. this contact form Covered by US Patent. For more information about encryption levels, see "Configure Server Authentication and Encryption Levels" in the Terminal Services Configuration Help in the Windows Server 2008 Technical Library (http://go.microsoft.com/fwlink/?LinkId=101637). Attempt to create an ICA session. Error Id 1004 Quick Heal

For more detailed information, see the Microsoft White Paper: “MS Windows 2000 Terminal Services Licensing.” Cause 1 The event log does not specify the client device that provided the invalid license. Note: If this group is not found, click Add, select the Users Group, and click OK. - In Permission Entry for MSLicensing, provide full control to the Users Group and click OK. - In the Access Control Before deleting the subkeys, back up the RCM subkey. have a peek here NOTE: If using a NON Native Windows Client (Macintosh, Linux, or a Thin Terminal) without a local registry, the above permissions must be made to the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\MSLicensing Issue

You may not be able to recieve a licence from the DC if you aren't authenticating to it. 0 LVL 1 Overall: Level 1 Message Expert Comment by:scarpenter104 ID: 92965592003-09-05 Event Id 1004 Ipmidrv TechNet Products Products Windows Windows Server System Center Browser   Office Office 365 Exchange Server   SQL Server SharePoint Products Skype for Business See all products » IT Resources Resources Evaluation Terminal Server Licensing Terminal Server Licensing Server on same server as Termina..

In my case, this problem was a permissions issue on the Windows XP client computer.

Is Q315404 applied? Get 1:1 Help Now Advertise Here Enjoyed your answer? When there is insufficient permissions to the following registry key, connection failures occur. No Remote Desktop Client Access Licenses Available For This Computer Event Type: Warning Event Source: TermService Event Category: None Event ID: 1004 Date: 08/02/2005 Time: 09:01:08 User: N/A Computer: LAWLONTS1 Description: The terminal server cannot issue a client license.

I logged in with a privileged account to establish the license, then logged in with the user account with no problems. Click the Advanced key. To start Remote Desktop Connection, click Start, click Run, type mstsc.exe, and then press ENTER. Check This Out Citrix is not responsible for inconsistencies, errors, or damage incurred as a result of the use of automatically-translated articles.

No: The information was not helpful / Partially helpful. NOTE: If you are making a desktop connection, then opening Program Neighborhood inside the desktop session (Pass-through) and the subsequent ICA connection is failing, the affected Workstation, in this case, is When i changed the values in this string the problem dissapeard. When testing, attempt to create an RDP connection after removing the MSLicense key in the registry as a user (no Domain Admin or Power User Group); the RDP connection also fails.