Post reply

How do I recover from a failed attempt to install SP2?

  • April 18, 2007 at 8:41 am

    #177705

    I downloaded service pack 2 for SQL Server 2005, and was applying it to our test SQL Server 2005 database, on our test server.  What I didn't know, until it was too late, was that the server we were given to use for test purposes, has a pitifully low amount of disk space.  Bottom line: SP2 ran out of space in which to work, and failed.  Now I cannot connect to that server via SQL Server Management Studio, nor by any application that tries to make a connection to it.  When I do, I get an error that says something to the effect that the default settings under SQL Server does not allow remote connections.  However, I am getting that error even when I'm on the server itself, running SQL Server Management Studio, so I don't believe that is the error.

    Bottom line: how do we recover from this problem?

    Kindest Regards, Rod Connect with me on LinkedIn.

  • April 24, 2007 at 4:47 am

    #702105

    The following points needs to be kept in mind before install SP2.

    1. Keep enough space on C$ drive. (like 1GB)

    2. Keep the TempDB to grow as well (keep maxsize in unlimited or enough size), the drive which Tempdb resides have not enough space, create new data and log files on another drive then proceed the sp2.

    good luck...

    Thanks
    Jay
    http://www.sqldbops.com

  • May 24, 2007 at 10:10 am

    #708706

    Have you attempted to connect to MSSQL in single user mode? i.e. sqlservr -smssqlserver -c -f -m -T3608

    You can then get an ADM connection via SQLCmd and shrink/move data files to another drive to free up space.

    Tommy

    Tommy

    Follow @sqlscribe

  • June 4, 2007 at 5:46 am

    #710566

    1. Check if remote connection is enabled or not.
     
    Steps:
     
    SQL Server surface area configuration --> Surface area configuration for services and connections
    Database Engine --> Remote connection --> Check the local and remote connections --> Select TCP/IP only
     
    2. Check if SQL Server browser service is running.
     
    3. If above options are there and still you are facing the issue. Callup MS support.
     
     
     
     
    Minaz
     

    "More Green More Oxygen !! Plant a tree today"

  • July 3, 2007 at 6:25 am

    #716852

    hi

    sql 2005 has dedicated administrator connections (DAC). try that to connect to your sql instance. refer BOL on how to do this.

    "Keep Trying"

  • July 3, 2007 at 9:58 am

    #716948

    We've finally got it to work.

     

    Kindest Regards, Rod Connect with me on LinkedIn.

Viewing 6 posts - 1 through 5 (of 5 total)

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