Post reply

Help! Logins and Default Databases Broken

  • August 29, 2007 at 12:31 pm

    #125444

    We installed a utility for BackUp Exec that seems to have messed up our SQL Server logins and default databases on our default instance of SQL Server 2005. We can login using Management Studio, but when we right click to look at any of the properties or execute any of the tasks, we are receiving an error that says:

    “Cannot show requested dialog. (SqlMgmt) Failed to receive data for the request. (Microsoft.SqlServer.SmoEnum) Failed to connect to server ServerName. (Microsoft.SqlServer.ConnectionInfo) Cannot open user default database. Login Failed. Login Failed for User Username. (Microsoft SQL Server Error: 4064)”

    We also can’t connect to the server using the sa account. We get a message that says “login failed for sa.” Any help getting this instance usable again would be greatly appreciated!

    Thanks,

    Wendy Schuman


    Wendy Schuman

  • August 29, 2007 at 12:48 pm

    #730236

    Did you try to login with DAC - Dedicated Admin Connection ?

     

  • August 29, 2007 at 12:56 pm

    #730238

    No, we are going to try that right now. We tried connecting using the osql utiltiy, but that didn't work either. Our SysAdmin and I are new to this and our database admin that we would have turned to for these kinds of problems left the company a month ago. I appreciate your help and will let you know how the DAC works.

    Thanks!


    Wendy Schuman

  • August 29, 2007 at 1:37 pm

    #730244

    We were not able to connect using DAC. We got an error that said Login Failed for sa. Does this mean that we have to reinstall or do we have any other options.

    Thanks for your help.

    Wendy


    Wendy Schuman

  • August 29, 2007 at 2:09 pm

    #730252

    Do you have a recent backup of your master database ? Try to restore it to another server first. Try to login there as sa, if it will work, restore master on your server.

     

  • August 29, 2007 at 2:19 pm

    #730254

    That's the problem. This was a new server and we haven't been using the default instance. We installed another instance on the server that we've been using for development and we've been running backups on that one. If we have to reinstall the default instance, it won't interfere with the other instance on that server, will it?


    Wendy Schuman

  • August 29, 2007 at 2:53 pm

    #730259

    If BUILTIN\Administrators is still there, add your(or any known account) to Windows Domain Admin. Then use that account to log in and reset the sa password.

    Cheers.


    * Noel

  • August 30, 2007 at 6:16 am

    #730397

    We are using Backup Exec, but with windows authentication.  Haven't tried SQL Server authentication.

  • August 30, 2007 at 7:21 am

    #730423

    When the Backup Exec utility was installed, did it create a new SQL account that you could possibly use to log into your SQL Server?

    Have a good day,

    Norene Malaney

  • August 30, 2007 at 4:32 pm

    #730625

    Don't take this as a solution- it's a thought, but I wonder what others say about this plan...

    stop sqlserver and copy the device master.mdl and masterlog.ldf file to another instance.

    attach those as a different named db (i.e. MyMaster)

    select * from MyMaster..sysxlogins

    (look at your logins [are there any sql logins with null password?)

    update the password field for sid= 1 to null

    Update MyMaster..sysxlogins

    Set password = null where sid = 1

    Detach MyMaster database

    Save a copy of the original master.mdl and masterlog.ldf

    On the broken instance

    copy files to broken instance location

    Start sql on broken instance

    Ordinarily, I don't modify system tables, but it may work for you

    Any thoughts?

    Regards;

    Ben

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

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