Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Failed to Login to SQL Server - when using Litespeed Restore Wizard Expand / Collapse
Author
Message
Posted Sunday, April 08, 2007 5:12 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, April 08, 2009 2:22 PM
Points: 7, Visits: 47

I am trying to restore a DB using the Litespeed restore wizard, but after I click on 'Start' it gives the error 'Failed to Login to SQL Server'.

I have full admin rights on the server and the DB.

Any ideas?

Thanks.

Post #356816
Posted Tuesday, May 15, 2007 7:13 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, February 04, 2011 1:51 AM
Points: 3, Visits: 36

Hi,

I had the same error when performing a log backup with Litespeed on an sql instance other than the default instance. I was using the sp  xp_backup_log, but not the GUI.  When I used the parameter @servername = 'somename' I got the following error if somename is something else than the actual instance i.e. server\instance if I omit this parameter it also works fine.  Hope this helps.

Msg 49999, Level 19, State 1, Line 1
Failed to login to SQL Server

Pall A. Gudmundsson

Post #365935
Posted Tuesday, June 19, 2007 5:02 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Saturday, April 03, 2010 2:38 PM
Points: 1, Visits: 23

I hit this error today ... in my case, someone changed the admin account which starts up sql server so that : a) it was a user in a the database I was trying to backup, and b) the permissions for that user added was less than DBO (reader, ddl-admin)

 

Once I deleted the user account everything worked.

Post #375126
Posted Tuesday, October 23, 2007 11:04 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: 2 days ago @ 2:27 PM
Points: 1, Visits: 36
I got this error today too. I logged on as the service account and the default database for the service account was for a database that was deleted, so it had a logon error. I changed the default DB to master and everything worked.
Post #414033
Posted Wednesday, February 20, 2008 7:50 PM


Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, September 26, 2013 4:05 AM
Points: 4, Visits: 170
Getting the same error on a SQL 2005 (9.00.3042 - Developer Edition) server. Was working fine a few weeks ago. Nothing I know of has changed, and now getting the failed to login error:

Msg 49999, Level 19, State 1, Line 0
Failed to login to SQL Server


Have tried reinstalling litespeed and re-running the instance configuration, etc.

Haven't changed the SQL service account, and it doesnt matter who I run the restore command as (i.e. sa, my domain admin account, etc).



Cheers,
Dave
Post #458323
Posted Monday, July 07, 2008 10:50 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, August 11, 2009 2:20 PM
Points: 2, Visits: 9
This might be a unique situation but, we did found the cause to our situation with regards to this error.

Our SQL sever 2005 environment is running in a active/passive cluster environment. The AD account used for the cluster service was mistakenly setup with out checking the password never expires. Hence, the password had expired which generated this error when Litespeed was invoked to backup the databases. Only by rebooting the passive node did we realize this as it could not join the cluster. After setting the service account to have the password never to expire did the error go away.
Post #529754
Posted Tuesday, February 03, 2009 1:47 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, April 28, 2009 9:29 AM
Points: 1, Visits: 2
This happened to me today and I fixed it by changing the SQL Server service to run as Local System instead of Network Service.
Post #649315
Posted Wednesday, April 08, 2009 2:12 PM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, April 17, 2014 9:12 AM
Points: 1,887, Visits: 1,179
Running SQL Server under the Local System account is dangerous as the account has far more privileges than it needs. Try to avoid this if at all possible and check the Microsoft recommended best practices - SQL Server Service should run under a purposefully created Domain Account.
Post #693552
Posted Thursday, December 02, 2010 4:34 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, January 23, 2014 7:55 AM
Points: 1, Visits: 95
We had the exact same issue and creating an Alias on the server worked for us!
Post #1029588
Posted Wednesday, January 19, 2011 1:31 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, September 26, 2012 1:03 PM
Points: 6, Visits: 116
Creating Alias worked for me.


-SQLHarry
Post #1050346
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse