Post reply

Error while running xp_readerrorlog

  • February 18, 2010 at 12:41 pm

    #215863

    I can run xp_readerrorlog when server is not in single user mode. I get ''Failed to open loopback connection'' error while running xp_readerrorlog once I start my standalone sql 2005 instance in sigle user mode(using ;-m in start up parameters in config. mgr.).

    Why am I getting this error?

    Thanks,

    MJ

  • February 19, 2010 at 1:09 am

    #1121602

    try sp_readerrorlog

    -------Bhuvnesh----------
    I work only to learn Sql Server...though my company pays me for getting their stuff done;-)

  • February 19, 2010 at 5:35 am

    #1121751

    Same error with sp_readerrorlog too...

  • February 19, 2010 at 5:43 am

    #1121756

    First , Are you using sql 2008 ?

    and second thing ( blind guess) use sa(administrator) account to run it

    -------Bhuvnesh----------
    I work only to learn Sql Server...though my company pays me for getting their stuff done;-)

  • February 22, 2010 at 12:01 pm

    #1123171

    Its 2005 and I am using admin account for the same.

    Mj

  • February 23, 2010 at 3:36 am

    #1123510

    sp_readerrorlog needs to open a new connection to get to the data. You are in single user mode and are already using the only connection available.

    You can always read the error log using some other tool, such as Notepad.

    Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.

    When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara

  • February 23, 2010 at 2:31 pm

    #1123897

    Thanks for the Explanation.

  • April 2, 2013 at 5:43 am

    #1602749

    hi how you got for answer this..

    same error coming in one of my server.

    i have made localhost servername entry in hostfile ..

    then restarted server ..

    it works ..

    regards,

    HEMANT..

  • April 12, 2013 at 2:22 am

    #1605880

    Had similar issue with SQL Server running with encrypted connection.

    Resolved by securing certificate includes localhost as one of the common name entries under the certificate "subject".

Viewing 9 posts - 1 through 8 (of 8 total)

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