Login failed for user 'sa'. Reason: Server is in single user mode.

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • aj
    #1

    Login failed for user 'sa'. Reason: Server is in single user mode.

    SQL Server 2005 SP2 2005.090.3054.0 0

    I'm trying to move master/model/msdb to a new spot. I restart SQL
    Server in single user mode with the "-c;-m;-T3608" startup params.

    When I try to connect to do the detach, I get:
    Login failed for user 'sa'. Reason: Server is in single user mode. Only
    one administrator can connect at this time. (Microsoft SQL Server,
    Error: 18461)

    But no one else is trying to connect....????

    I have stopped all other services other than the main MSSQLSERVER server
    instance.. same result..

    Any ideas appreciated..

    aj
    Tags: None
    • aj
      #2
      Re: Login failed for user 'sa'. Reason: Server is in single usermode.

      I found a workaround. I simply used SQLCMD rather than Mgmt Studio. I
      guess Mgmt Studio must be trying to make a 2nd connection somehow, but
      I don't know why. I scripted this out on my test server beforehand, and
      Mgmt Studio connected just fine.... <scratching head>...

      aj

      aj wrote:
      SQL Server 2005 SP2 2005.090.3054.0 0
      >
      I'm trying to move master/model/msdb to a new spot. I restart SQL
      Server in single user mode with the "-c;-m;-T3608" startup params.
      >
      When I try to connect to do the detach, I get:
      Login failed for user 'sa'. Reason: Server is in single user mode. Only
      one administrator can connect at this time. (Microsoft SQL Server,
      Error: 18461)
      >
      But no one else is trying to connect....????
      >
      I have stopped all other services other than the main MSSQLSERVER server
      instance.. same result..
      >
      Any ideas appreciated..
      >
      aj

        Comment

        • Erland Sommarskog
          #3
          Re: Login failed for user 'sa'. Reason: Server is in single user mode.

          aj (ronald@mcdonal ds.com) writes:
          I found a workaround. I simply used SQLCMD rather than Mgmt Studio. I
          guess Mgmt Studio must be trying to make a 2nd connection somehow, but
          I don't know why. I scripted this out on my test server beforehand, and
          Mgmt Studio connected just fine.... <scratching head>...
          If you have set up Mgmt Studio to open both a query window and an
          Object Explorer when you startup, there will be two connections.

          Not talking how funny this will be in SQL 2008 with intellisense,
          which opens a second connection behind your back.


          --
          Erland Sommarskog, SQL Server MVP, esquel@sommarsk og.se

          Books Online for SQL Server 2005 at
          http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx

          Books Online for SQL Server 2000 at
          http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

            Comment

            Previous template Next
            Working...