locked
Event ID: 4001 RRS feed

  • Question

  • Hi all,

    can anyone help me solving this event? I found it on a Server 2003 R2 x86 Microsoft SQL Server 2005

    Source: Health Service Script
    Id: 4001
    Description:

    DiscoverSQL2005DBEngineDiscovery.vbs : Error while reading registry value [\\d****.**.com\HKLM\Software\Microsoft\Microsoft SQL Server\\Setup\PatchLevel]. Cannot start a new logon session with an ID that is already in use.

    Tuesday, July 1, 2014 1:14 PM

Answers

All replies

  • Is that all the description?

    Do you get same error if you execute the script yourself?

    Try this hotfix: http://support.microsoft.com/kb/2283089


    www.coretech.dk - blog.coretech.dk

    Tuesday, July 1, 2014 1:31 PM
  • Hi,

    The issue may be caused by that many services do not start successfully on DC, and so that the domain controller cannot authenticate user requests.

    I would like to suggest you try below hotfix:

    http://support.microsoft.com/kb/2581130/en-US

    Hope this helps.

    Regards,

    Yan Li


    Regards, Yan Li


    • Edited by Yan Li_ Wednesday, July 2, 2014 6:04 AM edit
    Wednesday, July 2, 2014 6:04 AM
  • Thanks for the reply Michael.

    here is our complete problem:

    we have installed SCOM agent in the mentioned SQL server and it is reporting healthy in the OpsMgr console.

    But we are unable to find the server under SQL agent state in the console.

    In the Operations event log there is an error : 4001 with the description:

    DiscoverSQL2005DBEngineDiscovery.vbs : Error while reading registry value [\\d****.**.com\HKLM\Software\Microsoft\Microsoft SQL Server\\Setup\PatchLevel]. Cannot start a new logon session with an ID that is already in use.

    followed by the warning:1103 with the description:

    Summary: 1 rule(s)/monitor(s) failed and got unloaded, 1 of them reached the failure limit that prevents automatic reload. Management group "H***8". This is summary only event, please see other events with descriptions of unloaded rule(s)/monitor(s).

    followed by the warning  with the description:

    The process started at 11:12:16 PM failed to create System.Discovery.Data. Errors found in output:

    C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\2738\Win2K3DfsNamespaceDiscovery.vbs(231, 9) SWbemObjectEx: Cannot start a new logon session with an ID that is already in use.

    Command executed: "C:\WINDOWS\system32\cscript.exe" /nologo "Win2K3DfsNamespaceDiscovery.vbs" 0 {7E68C86C-2F2A-A527-C602-1709FFB75F79} {D3030797-391A-C50D-6421-978E83342300} d***.**.com d**** d***.***.com "C:\Program Files\Support Tools" Denver

    Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\2738\

    Wednesday, July 2, 2014 7:17 AM
  • Ok,

    Do you get same error if you execute the script yourself?

    Try this hotfix: http://support.microsoft.com/kb/2283089


    www.coretech.dk - blog.coretech.dk

    • Marked as answer by Deepthidurai Thursday, July 3, 2014 2:16 PM
    Wednesday, July 2, 2014 8:50 AM
  • Thank you Michael.

    After installing the hotfix the issue got resolved.

    Thank you once again..!

    Thursday, July 3, 2014 2:18 PM