Web-Method & Telephone Method – problem will persist (Event 17 will get logged – this is a bug!) //Web&Telephone method code wrongly assumes that hive will not be present, //as certs My license server was doing the same but now it works ok. Which is your preferred VDI solution? Is it ok to delete theese keys on that system as well? this contact form
HKLM\Software\Microsoft\TermServLicensing\Certificates. The content you requested has been removed. Limited to 5MB res2.log Second reserve log with the same purpose of res1.log TLSLic.edb The actual licensing database file temp.edb Used to store information about in-progress transactions Once you have verified Work-Around: Delete following registry keys hives, all 3 of them. her latest blog
Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the Microsoft Customer Support Microsoft Community Forums United States (English) Sign in Home Windows Server 2012 R2 Windows Server 2008 R2 Library Forums We’re sorry. After looking at the RDS Lic Srv, there was nothing at first view very obvious.
Thanks –user46992 Jul 2 '10 at 21:47 1) Try to specify a license server manually: support.microsoft.com/kb/279561 2) Terminal Server keeps a list of license servers (if found) in registry. In the right pane, the Activation Status for the license server should be listed as Activated. Partial sum of the harmonic series between two consecutive fibonacci numbers Has an SRB been considered for use in orbit to launch to escape velocity? HKLM\System\CurrentControlSet\services\TermservLicensing\Parameters\Certificates.000 HKLM\System\CurrentControlSet\services\TermservLicensing\Parameters\Certificates.001 These keys were located under HLKM\CurrentControlSet1 and CurrentControlSet2.
Copyright © 2016, TechGenix.com. Can't Create Certificate Context Error 0. Event Id 38 Please verify your entry and try this operation again. There are three methods by which you can activate your license server: Internet (Automatic) This method requires Internet connectivity from the computer running RD Licensing Manager. https://support.microsoft.com/en-us/kb/839878 Once that’s verified, use the Licensing Wizard from the Terminal Server Licensing program to reactivate the license server.
For more information, see “Specify the Terminal Services Licensing Mode” in the Terminal Services Configuration Help in the Windows Server 2008 Technical Library (http://go.microsoft.com/fwlink/?LinkId=101638). What i had to do is install the following hotfix and reboot: http://support.microsoft.com/default.aspx?scid=kb;EN-US;983385 Hope this helps you! He has written several technical articles and whitepapers, and has spoken at several forums and conferences around the United States. A Remote Desktop license server must be activated in order to certify the server and allow the license server to issue RDS CALs.
Corruption can occur for a number of reasons, but the most popular is making the mistake of placing the licensing database on a compressed drive.The drive compression could cause a write-delay, weblink Thanks Thursday, June 24, 2010 6:55 PM Reply | Quote 1 Sign in to vote Thanks a million! I still deleted them and rebooted and the activation was back. Wednesday, June 30, 2010 6:26 PM Reply | Quote 0 Sign in to vote thanks this worked but I did NOT need to reboot.
Friday, June 04, 2010 8:40 AM Reply | Quote 0 Sign in to vote Doing all things you have written have solved my problem. Finally, sometimes trouble with activating a license server or installing CALs can be resolved simply by attempting to activate via phone. Connected via Dameware and noted that the event log entry that prompts for license server activation was not present. navigate here To verify that the license server is activated: On the license server, open TS Licensing Manager.
but for those blondes like goto Start/ Run / Regedit HKLM = HKEY_Local_Machine then proceed as above and delete the registry trees from the left panel in regedit When you have Tuesday, June 22, 2010 6:18 PM Reply | Quote 0 Sign in to vote Can anyone tell me if I follow this and I don't have a my lic handy will To resolve this issue, try reactivating the Terminal Services license server.
Create a new folder where the old one was (\Windows\System32 by default) called LServer. Once a license server is found, the Terminal Server will only start the discovery process over again if it can’t connect to any of the servers in the registry. –Sergey Jul Yes No Additional feedback? 1500 characters remaining Submit Skip this Thank you! If the problem persists, identify and resolve any possible network connectivity issues.
To install RDS CALs later, clear the Start Install Licenses Wizard now check box, and then click Finish. On the Welcome page, click Next. Event 38: Event Type: Error Event Source: TermServLicensing Event Category: None Event ID: 38 Date: 3/17/2010 Time: 3:15:32 AM User: N/A Computer: Description: Can't generate a license for client because of his comment is here If you are having technical difficulties with any of the following, contact Microsoft Product Supports Services (PSS): Troubles discovering license servers Issues with CALs not being allocated to clients correctly License
Event 17 will start getting logged every reboot asking to Re-Activate. 2. Friday, August 12, 2011 1:59 AM Reply | Quote 0 Sign in to vote I had to delete the registry hives in order to deactivate (automatically) a 2008 license server. This information is optional. You’ll be auto redirected in 1 second.
Edited by Ice4Fire Friday, November 19, 2010 11:18 PM coorected description of MS Supoort Friday, November 19, 2010 11:16 PM Reply | Quote 0 Sign in to vote Removing the registry Thank you. Keep in mind that the new database will not have any of your CALs installed; you will need to contact the Microsoft Clearinghouse to recover them. This issue might be due to a problem connecting to the Microsoft Clearinghouse over HTTPS.
Contact the Clearinghouse or PSS? Ghost Updates on Mac Why were Navajo code talkers used during WW2? Scenario was that osx boxes could not connect, windows boxes were fine (presumably because the windows rdp client still doesn't expire licenses) On reboot, I could not make rdp connections from New v6: Free Forever for 2 VMs.
The question will ultimately arise as to which side of Microsoft should you contact for a specific problem – the Microsoft Clearinghouse or Product Support Services.