DEEP Deep TROUBLE!!! MSSQL Services not starting and TCP Actively Denying connection errors. PLEASE HELP

  • Hello Masters of SQL,

    I have a very bad issue here and I don't know what to make of it.

    Backstory:

    Last week, we had a a Hyper V Host fail and with it also the Hyper-V Clients on the raid that was attached(Raid 5 came back as a RAW Drive instead of NTFS).

    so my next option was to recover the vms from the latest backup exec full and diff i had on hand.

    SQL started up fine, it seemed no issues were present.

    I attempt to start the 2008 R2 SQL Management Studio where we have some databases(Primavera P6, WSUS and some TFS Stuff)

    When I attempt to login from Management studio into the server name/or local I receive an error stating that the tcp connection is actively being refused

    then i check into the services and the MSSQL Database Engine will not start

    then I go into the SQL Server Configuration Manager > SQL Server Services > and there is an error "The Remote Procedure Call failed [0x800706be]"

    Please help I am just at a point of crying!!!

    \

    Thanks in advance

  • mataleao87 (5/28/2015)


    Hello Masters of SQL,

    I have a very bad issue here and I don't know what to make of it.

    Backstory:

    Last week, we had a a Hyper V Host fail and with it also the Hyper-V Clients on the raid that was attached(Raid 5 came back as a RAW Drive instead of NTFS).

    so my next option was to recover the vms from the latest backup exec full and diff i had on hand.

    SQL started up fine, it seemed no issues were present.

    I attempt to start the 2008 R2 SQL Management Studio where we have some databases(Primavera P6, WSUS and some TFS Stuff)

    When I attempt to login from Management studio into the server name/or local I receive an error stating that the tcp connection is actively being refused

    then i check into the services and the MSSQL Database Engine will not start

    then I go into the SQL Server Configuration Manager > SQL Server Services > and there is an error "The Remote Procedure Call failed [0x800706be]"

    Please help I am just at a point of crying!!!

    Thanks in advance

    Using google produces a pretty good list of people who have experienced this before. They all pretty much say the same thing to fix it. &ie=utf-8&oe=utf-8]https://www.google.com/search?q=The+Remote+Procedure+Call+failed+[0x800706be]&ie=utf-8&oe=utf-8

    _______________________________________________________________

    Need help? Help us help you.

    Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

    Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

    Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
    Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
    Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
    Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/

  • Using google produces a pretty good list of people who have experienced this before. They all pretty much say the same thing to fix it. &ie=utf-8&oe=utf-8]https://www.google.com/search?q=The+Remote+Procedure+Call+failed+[0x800706be]&ie=utf-8&oe=utf-8

    I tried to re-register the dll's and to recompile to Mof files. I also Ran winmgmt /verifyrepository and received a response that the WMI Repository is consistent

  • mataleao87 (5/28/2015)


    Using google produces a pretty good list of people who have experienced this before. They all pretty much say the same thing to fix it. &ie=utf-8&oe=utf-8]https://www.google.com/search?q=The+Remote+Procedure+Call+failed+[0x800706be]&ie=utf-8&oe=utf-8

    I tried to re-register the dll's and to recompile to Mof files. I also Ran winmgmt /verifyrepository and received a response that the WMI Repository is consistent

    So I fixed the Remote Procedure Call Failed error by installing SQL 2008 R2 sp3. now I receive 3 errors

    FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf for file number 1. OS error: 5(Access is denied.).

    FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf for file number 2. OS error: 5(Access is denied.).

    Unknown SQL Exception 2 occured. Additional error information from SQL Server is included below.

    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

  • mataleao87 (5/28/2015)


    mataleao87 (5/28/2015)


    Using google produces a pretty good list of people who have experienced this before. They all pretty much say the same thing to fix it. &ie=utf-8&oe=utf-8]https://www.google.com/search?q=The+Remote+Procedure+Call+failed+[0x800706be]&ie=utf-8&oe=utf-8

    I tried to re-register the dll's and to recompile to Mof files. I also Ran winmgmt /verifyrepository and received a response that the WMI Repository is consistent

    So I fixed the Remote Procedure Call Failed error by installing SQL 2008 R2 sp3. now I receive 3 errors

    FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf for file number 1. OS error: 5(Access is denied.).

    FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf for file number 2. OS error: 5(Access is denied.).

    Unknown SQL Exception 2 occured. Additional error information from SQL Server is included below.

    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

    Check that the sql server service account has access to the path and also check the path exists

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • Check that the sql server service account has access to the path and also check the path exists

    I have verified that the path exists, but Im not sure how to check that the sql service account has access to the path.

    ( I am a noob at this if you haven't noticed yet)

  • open explorer and find the data folder then right click and select properties. On the security tab you'll see details of permissions applied

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • Perry Whittle (5/29/2015)


    open explorer and find the data folder then right click and select properties. On the security tab you'll see details of permissions applied

    for the master.mdf permissions are as follows

    everyone- full control

    system-full control

    service administrator-full control

    SQLServerMSSQLUser$SQL$MSSQLSERVER- Full Control

    Administrators[servername\Administrators]-Full Control

    Same Permissions are applied to the mastlog.ldf

  • I think it's the folder permission you need to check, not the files within the folder.

  • homebrew01 (5/30/2015)


    I think it's the folder permission you need to check, not the files withing the folder.

    That was it. Have many more new issues but seems like some progress is being made. I will mark your answer correct as it was the solution.

    Love to avatar btw.

  • mataleao87 (5/30/2015)


    homebrew01 (5/30/2015)


    I think it's the folder permission you need to check, not the files withing the folder.

    That was it. Have many more new issues but seems like some progress is being made. I will mark your answer correct as it was the solution.

    Love to avatar btw.

    Mr. Whittle should get credit. I just repeated what he said.

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply