can't activate Windows Server 2012 R2 from Dell

Discussion in 'Windows Server' started by pcgirl, Jan 7, 2016.

  1. pcgirl

    pcgirl MDL Novice

    Aug 22, 2014
    6
    0
    0
    I have a very weird problem. I purchased a Dell ML350 with Windows Server 2012 R2 Standard Edition. I originally activated it when I first was starting to set it up and everything seemed fine. Then about 3 months later I noticed in the bottom right hand corner "Activate Windows go to System in Control Panel to activate windows". When I do this it says the Windows is not activated and Product ID not available. So, after probably 12 hours of phone support with Dell and Microsoft, Dell finally said that I would need to re-install the OS. However, I have had programs installed by other companies and it would cost me more money to install these programs again. Not to mention the fact that the company can't be without the server for that length of time. The server is running fine. When we talked to Microsoft, they had confirmed that the server had indeed been activated but I can't get the server to recognize the activation. I believe that there has to be some solution. One of the things that Dell could not fix was the Software Protection Service will not start and this seems to be part of the problem. They say that without this service, the OS can't activate. I am interested if anybody on this forum has experienced this before or has any advice? Thanks!
     
  2. catgirl

    catgirl MDL Novice

    Jan 15, 2014
    46
    4
    0
    Since the original activation, has the automatic updates been run, or do you have it set as manual, if so, does the non-activation event run parallel to an update?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. pcgirl

    pcgirl MDL Novice

    Aug 22, 2014
    6
    0
    0
    The updates won't run without errors. Also, they were saying that it has something to so with the Software Protection Service not running.
     
  4. catgirl

    catgirl MDL Novice

    Jan 15, 2014
    46
    4
    0
    Ok did you run any updates before the problem of non-activation...the question is not will an update fix the problem, but rather did an update cause the problem..
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. xinso

    xinso MDL Guru

    Mar 5, 2009
    3,973
    5,313
    120
    #5 xinso, Jan 8, 2016
    Last edited by a moderator: Apr 20, 2017
    Could you?

    1. Run Command Prompt (Admin)

    2. Run
    Code:
    cscript slmgr.vbs /dlv >c:\status.txt
    3. Show the content of c:\status.txt

    e.g.
    Code:
    Microsoft (R) Windows Script Host Version 5.812
    Copyright (C) Microsoft Corp. 1996-2006, 著作權所有,並保留一切權利
    
    軟體授權服務版本: 10.0.10586.0
    
    名稱: Windows(R), ServerDatacenter edition
    描述: Windows(R) Operating System, VOLUME_KMSCLIENT channel
    啟用識別碼: 00091344-1ea4-4f37-b789-01750ba6988c
    應用程式識別碼: 55c92734-d682-4d71-983e-d6ec3f16059f
    延伸的 PID: 03612-02535-000-000000-03-1028-10586.0000-0082016
    產品金鑰通路: Volume:GVLK
    安裝識別碼: 220925196467028617390745435619919509757871725270679496215498400
    部分產品金鑰: Q3VJ9
    授權狀態: 已取得授權
    大量授權啟用到期: 259197 分鐘 (180 天)
    剩餘的 Windows 重設授權狀態計數: 1001
    剩餘的 SKU 重設授權狀態計數: 1001
    信任時間: 2016/1/8 下午 09:29:30
    已設定的啟用類型: KMS
    
    最近的啟用資訊:
    金鑰管理服務用戶端資訊
        用戶端電腦識別碼 (CMID): f38ebbb8-2149-409c-b2fa-7a1dadacc042
        已登錄的 KMS 電腦名稱: 192.168.1.254:1688
        KMS 電腦 IP 位址: 192.168.1.254
        KMS 電腦延伸的 PID: 05426-00206-271-791862-03-1028-9200.0000-3072015
        啟用間隔: 120 分鐘
        更新間隔: 10080 分鐘
        啟用 KMS 主機快取
     
  6. pcgirl

    pcgirl MDL Novice

    Aug 22, 2014
    6
    0
    0
    Some windows updates were done after installation. Twice actually. Then someone remotely installed a program onto the server. I have included a picture of what was installed by them on Oct.2. It seemed to me that it was after this that the activation was broken. Some other updates did install when Dell was working on it but it would not install all of them because it would get an error.
    InstalledPrograms.jpg
     
  7. pcgirl

    pcgirl MDL Novice

    Aug 22, 2014
    6
    0
    0
    OK, I ran the command above and this is what I got.
    Microsoft (R) Windows Script Host Version 5.8
    Copyright (C) Microsoft Corporation. All rights reserved.

    Error: 0x8007041D On a computer running Microsoft Windows non-core edition, run 'slui.exe 0x2a 0x8007041D' to display the error text.

    Then I ran the command in the error above and then I got this:

    ServerError.jpg
     

    Attached Files:

  8. catgirl

    catgirl MDL Novice

    Jan 15, 2014
    46
    4
    0
    #8 catgirl, Jan 12, 2016
    Last edited: Jan 13, 2016
    Ok that's a good observation. If it was me troubleshooting I would reverse the order of installs with an SFC /scannow and restart in between each uninstall.

    One other item of note; If you check the windows system / software / warning error logs you might have an event that coincides with the non -activation event....
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. SLICuser

    SLICuser MDL Novice

    Dec 26, 2009
    30
    2
    0
    Are you running as the Administrator? Is UAC on or off?

    I have seen your issue with messed up group policies.

    When you can schedule some downtime.
    Disconnect from the net.
    Create a temp Administrator account that is only in the Administrator group and Login to the temp account, turn off UAC. Reboot
    Check activation, I expect it to show up as activated. If it does it is something in your GP.
    I would reset your accounts GP. Turn UAC back on. Reboot
    Log in to your account and test it, if it doesn’t your account may have isolated malware / virus or you’ve been added to a restricted user group and you can safely ignore the issue. Remember Denial rights are higher priority than Access rights.
    If everything is working delete the temp account can connect back to the network.

    Note about your programs. None of them I would say is bad. The question is what is running in the VSS? Make sure you do not have an application that requires VSS or SQL. It could be an update that did the installing. Both of these would be there if you are running WDS or SCCM.
     
  10. pcgirl

    pcgirl MDL Novice

    Aug 22, 2014
    6
    0
    0
    I am running as the Administrator and UAC is set to "Notify Me when apps try to make changes". How do I check what is running on the VSS? I do have applications that require SQL. I am not running WDS or SCCM.
     
  11. mcl

    mcl MDL Junior Member

    Apr 17, 2011
    62
    2
    0
    Another approach to consider, particularly if you don't want to rebuild the server, is post a question on the Microsoft forums re the error with the Software Protection Service. I assume there may be some diagnostics in the Event Log. If you can't obtain a resolution via the forums you could consider opening an incident with Microsoft Technical Support. That will be chargeable, but it will only be a couple of hundred dollars - which versus the time spent already and the time you may still need to spend - could be small change.

    With a paid incident you will get access to a Microsoft engineer within 24 hours and they will either resolve the issue or they won't charge you. Also if the cause of the issue is shown to be a bug (e.g. a faulty Windows Update) then the charge will be waived as well.

    And no I don't work for Microsoft, but I have used their technical support on occasion when faced with a difficult issue and I have found it to be an effective option.

    At the end of the day time is money, sometimes it is worth spending some money to save yourself a whole lot of hassle.
     
  12. pcgirl

    pcgirl MDL Novice

    Aug 22, 2014
    6
    0
    0
    When I had Dell on the phone for two days trying to help with this issue, they also contacted Microsoft and they were not helpful at all. They just kept saying that the server was activated and they didn't understand the issue. They bounced us around to about four different people until we finally gave up.