April 8, 2007 at 5:12 pm
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.
May 15, 2007 at 7:13 am
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
June 19, 2007 at 5:02 pm
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.
October 23, 2007 at 11:04 am
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.
February 20, 2008 at 7:50 pm
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
July 7, 2008 at 10:50 pm
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.
February 3, 2009 at 1:47 pm
This happened to me today and I fixed it by changing the SQL Server service to run as Local System instead of Network Service.
April 8, 2009 at 2:12 pm
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.
December 2, 2010 at 4:34 pm
We had the exact same issue and creating an Alias on the server worked for us!
January 19, 2011 at 1:31 pm
Creating Alias worked for me.
-SQLHarry
January 9, 2012 at 7:25 am
I had the same problem except that one database out of job with 12 restores and multiple other jobs with a total around 250 restores would fail.
While the job is owned by SA (helps avoids windows authentication issues) the Service account was a login on the server but not part of the SysAdmin role except through Administrators group permission.
I gave the service account SysAdmin role, and hopefully this will work from now on.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply