Se connecter
 
AccueilLibrairieFormationTéléchargementsSupport techniqueCommunautésForums
Pour les professionnels de l’informatique >
> 
> 
sconfig.cmd stopped working in Server 2008 R2 Core with Hyper-V R2

Answered sconfig.cmd stopped working in Server 2008 R2 Core with Hyper-V R2

  • mardi 15 juin 2010 12:45
     
     
    Connectez-vous pour voter
    0

    After a reboot, the hyper-v server config screen does not appear.  All I see is a Command Shell displaying the following:

    Microsoft (R) Windows Script Host Version 5.8
    Copyright (C) Microsoft Corporation. All rights reserved.

    Inspecting system...

    C:\Windows\System32\en-US\sconfig.vbs(235, 2) (null): 0x80041010


    C:\Windows\System32>

    I have tried another reboot, still no change.  I have searched log files and have found no reference to any errors.  The Server Core and Hyper-V all seem to be working correctly.  No issues with any of the servers residing on this box.  They are all function as normal.

     

Toutes les réponses

  • mercredi 16 juin 2010 08:28
    Modérateur
     
     Traitée
    Connectez-vous pour voter
    0

    Hi,

     

    Can you start the sconfig.vbs manually?

     

    If the issue continues, I would like to suggest that you contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. Because we find it seems to be application crash issue and we need to analyze the crash dump file to narrow down the root cause of the issue. Unfortunately, it is not effective for us to debug the crash dump file here in the forum.

     

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

     

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

     

    Hope the issue will be resolved soon.

     

    Best Regards,

    Vincent Hu

     

     
  • jeudi 1 juillet 2010 16:21
     
     
    Connectez-vous pour voter
    0

    I have the same problem. 

    sconfig.vbs.... 0x80041010

    Your resolution to call support does not help.  Please let me know if there is a patch for this error.  The error does not get in the way, since the server is still functioning.

     
  • vendredi 20 août 2010 13:02
     
     Réponse proposée A du code
    Connectez-vous pour voter
    1
    I also had same issue.
    Without apparent reason Microsoft scripting guys forgot to include default name space in the almost all calls to wmi GetObject in the sconfig.vbs scripts. So if your default namespace for scripting setting was somehow reset to something other than default value of "root\cimv2" you will not be able to run sconfig.cmd
    To fix this you need to change default namespace for scripting setting back to "root\cimv2" either remotely through Server Manager WMI configuration, or by running this command: 
    reg add "HKLM\SOFTWARE\Microsoft\WBEM\Scripting" /v "Default Namespace" /d "root\cimv2"

    In fact in my case I have changed %SystemRoot%\System32\En-US\sconfig.vbs by replacing strings:

    GetObject("winmgmts:Win32_NetworkAdapterConfiguration=" & MgmtNIC)

    to

    GetObject("winmgmts:root\cimv2:Win32_NetworkAdapterConfiguration=" & MgmtNIC)

    to remove dependence of wmi settings.


    Regards,

    Konstantin Salavatov

    • Proposé comme réponse David_SE mercredi 23 mai 2012 12:30
    •  
     
  • mercredi 23 mai 2012 12:35
     
     
    Connectez-vous pour voter
    0

    Hello Konstantin,

    after configuring a Hyper-V Server 2008 R2 I had the same error that sconfig won't start (0x80041010).

    First I checked the default namespace, but this was already set correct.

    Then I changed all the "GetObject"-Lines in the sconfig.vbs script and sconfig is working fine!

    Thank you!

    Kind Regards, David