SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Failed to Login to SQL Server - when using Litespeed Restore Wizard


Failed to Login to SQL Server - when using Litespeed Restore Wizard

Author
Message
Techboy-427295
Techboy-427295
SSC Journeyman
SSC Journeyman (99 reputation)SSC Journeyman (99 reputation)SSC Journeyman (99 reputation)SSC Journeyman (99 reputation)SSC Journeyman (99 reputation)SSC Journeyman (99 reputation)SSC Journeyman (99 reputation)SSC Journeyman (99 reputation)

Group: General Forum Members
Points: 99 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.


Pall A. Gudmundsson
Pall A. Gudmundsson
SSC Rookie
SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)

Group: General Forum Members
Points: 31 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


jose pizano
jose pizano
SSC Rookie
SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)

Group: General Forum Members
Points: 29 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.


oliver jen
oliver jen
Grasshopper
Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)

Group: General Forum Members
Points: 17 Visits: 38
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.
DatabaseDave
DatabaseDave
Grasshopper
Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)

Group: General Forum Members
Points: 14 Visits: 183
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
Ty_Stewart
Ty_Stewart
Grasshopper
Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)

Group: General Forum Members
Points: 20 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.
srd8580
srd8580
SSC Rookie
SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)

Group: General Forum Members
Points: 25 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.
Lempster
Lempster
SSCertifiable
SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)

Group: General Forum Members
Points: 5103 Visits: 1657
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.
lav28
lav28
Grasshopper
Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)

Group: General Forum Members
Points: 15 Visits: 108
We had the exact same issue and creating an Alias on the server worked for us!
harryucf5
harryucf5
Grasshopper
Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)

Group: General Forum Members
Points: 14 Visits: 116
Creating Alias worked for me.


-SQLHarry
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search