none
Having major problems with Windows Server 2012 running SQL Server 2012

    Question

  • So, I've set this server up 5 time in the last week, documenting everything and making small changes.  The problem is, once I get SQL Server installed then configure Report Server when I re-boot the server, I can never log back in.  The computer accepts the Ctrl+Alt+Del, but never shows the dialog to accept my login credentials.

    If I re-boot in Safe mode and then disable all non-essential services, I can get back in, but I really need this SQL server, and eventually SharePoint 2013 to all work on the same computer.

    I am not using Hyper-V or any other Virtual Setup.

    When I remote into the Event Viewer I get the following:

    - System
    - Provider
    [
    Name]
    Microsoft-Windows-Winlogon
    [
    Guid]
    {DBE9B383-7CF3-4331-91CC-A3CB16A3B538}
    [
    EventSourceName]
    Wlclntfy
    - EventID 6006
    [
    Qualifiers]
    32768
    Version 0
    Level 3
    Task 0
    Opcode 0
    Keywords 0x80000000000000
    - TimeCreated
    [
    SystemTime]
    2013-06-14T20:03:18.000000000Z
    EventRecordID 7992
    Correlation
    - Execution
    [
    ProcessID]
    0
    [
    ThreadID]
    0
    Channel Application
    Security
    - EventData
    GPClient
    3598
    CreateSession
    04000000

    Has anyone seen this before?  What can I do to fix this?

    I am at my wits end on this one.

    Friday, June 14, 2013 8:50 PM

Answers

All replies

  • Hello,


    That error is related to the shutdown process.

    Could you please share with us how much memory you have assigned to that server?


    Thank you in advance.

    Regards,

    Alberto Morillo
    SQLCoffee.com

    Friday, June 14, 2013 10:43 PM
  • Also even though Alberto is helping You can get better solution by posting this error in Windows Server 2012 Community/Forum...

    I suppose moderators will move it ,its just matter of time how long


    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

    Saturday, June 15, 2013 6:06 AM
  • We were able to get everything working as long as we change all the SQL process to Delay Start. Considering this issue closed.
    Monday, August 04, 2014 4:15 PM