none
Event ID 1067, event id 1009, event id 4105, event id 1061 RRS feed

  • Question

  • I have 1 Dedicated DC, I have 3 Terminal Servers that are part of that DC. I only have the problem with the 1 TS.

    I keep having these errors and I cannot find a fix. I've read articles but it's not helping. I really need help.

    1067

    The terminal server cannot register 'TERMSRV' Service Principal Name to be used for server authentication. The following error occured: The specified domain either does not exist or could not be contacted.

    1009

    Error starting the Remote App and Desktop Management Service.

    Error Code: 0x800706FD

    4105

    The Remote Desktop license server cannot update the license attributes for user "hkarovic" in the Active Directory Domain "wvchangeinc.org". Ensure that the computer account for the license server is a member of Terminal Server License Servers group in Active Directory domain "wvchangeinc.org".

    If the license server is installed on a domain controller, the Network Service account also needs to be a member of the Terminal Server License Servers group.

    If the license server is installed on a domain controller, after you have added the appropriate accounts to the Terminal Server License Servers group, you must restart the Remote Desktop Licensing service to track or report the usage of RDS Per User CALs.

    Win32 error code: 0x8007054b


    • Edited by Lakers310 Saturday, January 18, 2014 4:34 PM
    Saturday, January 18, 2014 3:33 PM

Answers

  • Hi,

    For your CAL related query I can redirect you to refer one of the thread where TP has describe so nicely regarding the whole scenario and you can reach to your solution. As highlight, I can let you know that "firstly you need to track the report and find the user who needs Per User RDS CAL and you can purchase\delete CAL as per your requirement.

    Meanwhile sharing thread with you for additional details.
    RDS CALs warning - Event ID 4106

    In respect to spn related query, I had place the comment to find duplicate spn in your thread. Please refer below link.
    Removing TS Sever From Domain And Readding

    Hope it helps!

    Thanks,
    Dharmesh
    Wednesday, January 22, 2014 2:23 AM
    Moderator

All replies

  • In this scenario,  Service Principal Name (SPN) is not registered for the Terminal server.

    To fix this issue, Register a terminal server SPN.

    Start --> Run --> cmd --> OK

    setspn -A TERMSERV/Servername Servername

    Note : Replace Servername with Terminal server name

    Also cross verify you have enough licenses are not not.

    Regards,

    Manjunath Sullad

    Saturday, January 18, 2014 5:35 PM
  • thanks for your reply!!!!!!!!, what I forgot to mention is that this server has been in production for 3 years, this just started happening. it is intermittent.

    All of a sudden nobody will be able to log into terminal services,It can last from 2 minutes to 10 minutes, then it will start working again. I have 35 licenses, but no more than 20 are used at a time. but a total of 40 within a month could be used, but never more than 20 at a time.

    Since it is intermittent, should I still do what you suggest, and also, is that the same servername typed back to back

    I get these errors too back

    Error 1/17/2014 9:48:02 AM TerminalServices-RemoteConnectionManager 1067 None
    Error 1/17/2014 9:47:45 AM RemoteApp and Desktop Connection Management 1009 Setup
    Error 1/17/2014 9:46:43 AM RemoteApp and Desktop Connection Management 1009 Setup
    Information 1/17/2014 9:45:56 AM TerminalServices-RemoteConnectionManager 1012 None
    Error 1/17/2014 9:45:40 AM RemoteApp and Desktop Connection Management 1009 Setup
    Error 1/17/2014 9:45:33 AM TerminalServices-RemoteConnectionManager 1067 None
    Information 1/17/2014 9:42:38 AM TerminalServices-Licensing 0 None
    Warning 1/17/2014 9:35:38 AM TerminalServices-Licensing 4105 None
    Error 1/17/2014 9:35:33 AM TerminalServices-RemoteConnectionManager 1061 None
    Warning 1/17/2014 9:34:05 AM TerminalServices-Licensing 4105 None
    Error 1/17/2014 9:34:00 AM TerminalServices-RemoteConnectionManager 1061 None
    Warning 1/17/2014 9:28:33 AM TerminalServices-Licensing 4105 None
    Error 1/17/2014 9:28:28 AM TerminalServices-RemoteConnectionManager 1061 None
    Warning 1/15/2014 8:53:01 AM TerminalServices-PnPDevices 36 None
    Information 1/13/2014 8:18:05 AM TerminalServices-Licensing 0 None

    BELOW I JUST FOUND OUT WHEN IT STARTED, BOTTOM DATES, SEPT 24 TO FEUBRUARY NO ISSUES

    Error 4/26/2013 7:02:18 AM RemoteApp and Desktop Connection Management 1009 Setup
    Error 4/26/2013 7:01:18 AM RemoteApp and Desktop Connection Management 1009 Setup
    Error 4/26/2013 6:51:53 AM RemoteApp and Desktop Connection Management 1009 Setup
    Error 4/26/2013 6:40:28 AM RemoteApp and Desktop Connection Management 1009 Setup
    Error 4/26/2013 6:39:28 AM RemoteApp and Desktop Connection Management 1009 Setup
    Error 4/26/2013 6:38:28 AM RemoteApp and Desktop Connection Management 1009 Setup
    Error 4/26/2013 6:29:09 AM RemoteApp and Desktop Connection Management 1009 Setup
    Error 4/26/2013 6:28:09 AM RemoteApp and Desktop Connection Management 1009 Setup
    Error 4/26/2013 6:27:09 AM RemoteApp and Desktop Connection Management 1009 Setup
    Error 4/26/2013 5:50:04 AM RemoteApp and Desktop Connection Management 1009 Setup
    Error 4/26/2013 5:49:04 AM RemoteApp and Desktop Connection Management 1009 Setup
    Error 4/26/2013 5:48:04 AM RemoteApp and Desktop Connection Management 1009 Setup
    Warning 4/18/2013 8:42:45 AM TerminalServices-PnPDevices 36 None
    Error 4/16/2013 8:04:00 PM RemoteApp and Desktop Connection Management 1009 Setup
    Error 4/16/2013 8:03:00 PM RemoteApp and Desktop Connection Management 1009 Setup
    Error 4/16/2013 8:01:59 PM RemoteApp and Desktop Connection Management 1009 Setup
    Error 4/11/2013 10:49:21 PM RemoteApp and Desktop Connection Management 1009 Setup
    Error 4/11/2013 10:48:21 PM RemoteApp and Desktop Connection Management 1009 Setup
    Error 4/11/2013 10:47:21 PM RemoteApp and Desktop Connection Management 1009 Setup
    Error 4/11/2013 10:25:54 PM RemoteApp and Desktop Connection Management 1009 Setup
    Error 4/11/2013 10:24:54 PM RemoteApp and Desktop Connection Management 1009 Setup
    Error 4/11/2013 10:23:54 PM RemoteApp and Desktop Connection Management 1009 Setup
    Error 3/14/2013 3:09:14 AM RemoteApp and Desktop Connection Management 1009 Setup
    Warning 3/13/2013 1:47:38 PM TerminalServices-PnPDevices 36 None
    Warning 3/11/2013 12:45:36 PM TerminalServices-PnPDevices 36 None
    Warning 2/19/2013 8:00:31 AM TerminalServices-PnPDevices 36 None
    Error 2/14/2013 3:28:51 AM RemoteApp and Desktop Connection Management 1009 Setup
    Error 2/14/2013 3:27:36 AM RemoteApp and Desktop Connection Management 1009 Setup
    Warning 9/24/2012 12:32:58 PM TerminalServices-PnPDevices 36 None



    • Edited by Lakers310 Saturday, January 18, 2014 7:26 PM
    Saturday, January 18, 2014 6:39 PM
  • Please refer below Technet Wiki for more information on adding SPN values.

    http://social.technet.microsoft.com/wiki/contents/articles/717.service-principal-names-spns-setspn-syntax-setspn-exe.aspx

    Since  SPN value is not registered, Kerberos authentication will not happening for client connections.


    Once you register SPN value for server, hope it will solve the problem.


    Regards,

    Manjunath Sullad



    Sunday, January 19, 2014 3:17 PM
  • i did that after you posted, thanks again for responding!!!!!!!

    Would you be able to tell me why it was happening, assuming that those errors only happen when the SPN value is not registered, and the server was working fine, which would mean that the SPN value was registered. 

    Also, error 4106, CAL reporting: Windows Server 2008 or Windows Server 2008 R2 : Per User CAL (TS or RDS) - Installed: 35, Issued: 45

    As i stated above, there have never been more than 20 users on the server at a time, is there a way to clear the issued 45, and have the server start over. Assuming this is causing a conflict, being that the server thinks there are too many licenses installed on the server?

    error 1012, Remote session from client name ASDASD-89C77C11 exceeded the maximum allowed failed logon attempts. The session was forcibly terminated.

    What Is This? Who Is ASDASD-89C77C11 


    • Edited by Lakers310 Sunday, January 19, 2014 7:29 PM
    Sunday, January 19, 2014 7:26 PM

  • We need to analyse why its happening like this,

    But as per event log, it learly says that SPN value is not registered,

    Try registering the SPN value and check.

     

    Please go through below link for more information,

    http://blogs.technet.com/b/qzaidi/archive/2010/10/12/quickly-explained-service-principal-name-registration-duplication.aspx

     

    Regards,

    Manjunath Sullad

    Monday, January 20, 2014 4:04 PM
  • Hi,

    After referring to your comment, it seems that you are facing the error in your environment because of license problem. Here I want to share some point with you for CAL. As per your description it seems you have User CAL in your environment. The Per User RDS CAL will expire after 60 days if you do not use and they will not show in your CAL usage report once it expire. 

    In respect to Event ID which you are facing, here providing little description for that part.

    Event ID 4105 cause as License Server is not member of TS License Server group in a domain, firstly please check the License Server Status.
    Event ID 1009 for this error as it cause maybe grace license period entry is not getting entered.
    Event ID 1061 is a warning stating TS unable to retrieve user Licensing information from AD.

    Event ID 4106 it gives RDS CAL reporting.

    Also agree with words of Manjunath for Event ID 1067, states to register SPN name for Terminal Server. 

    Hope it helps to understand!

    Thanks,
    Dharmesh

     
    Tuesday, January 21, 2014 6:38 AM
    Moderator
  • THANKS GUYS !!!!!

    Dharmesh,

    With the cal situation, my last post, had "Also, error 4106, CAL reporting: Windows Server 2008 or Windows Server 2008 R2 : Per User CAL (TS or RDS) -Installed: 35, Issued: 45" should i install 50 cal's?

    Thanks

    ******************************************************************************************

    i did the setspn -A TERMSERV/Servername Servername, and this was the responce.

    C:\Users\administrator.THEDOMAIN.000>setspn -A TERMSERV/WVTS WVTS
    Registering ServicePrincipalNames for CN=WVTS,CN=Computers,DC=THE DOMAIN,DC=org

            TERMSERV/WVTS
    Updated object

    *********************************************************************

    I then ran  setspn -S TERMSERV/Servername Servername, and this is what i got

    C:\Users\administrator.THE DOMAIN.000>setspn -S TERMSERV/WVTS WVTS
    Checking domain DC=THE DOMAIN,DC=org
    CN=WVTS,CN=Computers,DC=THE DOMAIN,DC=org
            TERMSERV/WVTS
            tapinego/WVTS
            tapinego/WVTS.DOMAINNAME
            WSMAN/WVTS
            WSMAN/WVTS.DOMAINNAME
            TERMSRV/WVTS
            TERMSRV/WVTS.DOMAINNAME
            RestrictedKrbHost/WVTS
            HOST/WVTS
            RestrictedKrbHost/WVTS.DOMAINNAME
            HOST/WVTS.DOMAINNAME

    Duplicate SPN found, aborting operation!

    How do i find the duplicate, and not sure how it could have got there?



    • Edited by Lakers310 Tuesday, January 21, 2014 3:09 PM
    Tuesday, January 21, 2014 2:36 PM
  • Hi,

    For your CAL related query I can redirect you to refer one of the thread where TP has describe so nicely regarding the whole scenario and you can reach to your solution. As highlight, I can let you know that "firstly you need to track the report and find the user who needs Per User RDS CAL and you can purchase\delete CAL as per your requirement.

    Meanwhile sharing thread with you for additional details.
    RDS CALs warning - Event ID 4106

    In respect to spn related query, I had place the comment to find duplicate spn in your thread. Please refer below link.
    Removing TS Sever From Domain And Readding

    Hope it helps!

    Thanks,
    Dharmesh
    Wednesday, January 22, 2014 2:23 AM
    Moderator
  • Dharmesh,

    i really appreciate that you've been staying on this with me, thanks!!!! I'll see what i can find with your suggestions.

    Friday, January 31, 2014 1:54 PM
  • Dharmesh

    Ever since i did the command i did the setspn -A TERMSERV/Servername Servername, I haven't had the problem. I am also assuming that the issue is also as you suggested with the cals. I'm going to add some more cals to the terminal server and see if that works. I'll keep you informed


    Friday, February 14, 2014 8:03 PM