Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

Login failed for user 'sa'. [CLIENT: 10.0.0.3]

Posted on 2011-05-11
61
Medium Priority
?
837 Views
Last Modified: 2012-06-27
I have a Backup Module which is part of a SQL DB system written by a company called Digita.  Whenever I launch this backup module, I get the following event appear in my application log -

Event Type:	Failure Audit
Event Source:	MSSQLSERVER
Event Category:	(4)
Event ID:	18456
Date:		10/05/2011
Time:		21:00:02
User:		N/A
Computer:	BENCOMMS
Description:
Login failed for user 'sa'. [CLIENT: 10.0.0.3]

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 18 48 00 00 0e 00 00 00   .H......
0008: 09 00 00 00 42 00 45 00   ....B.E.
0010: 4e 00 43 00 4f 00 4d 00   N.C.O.M.
0018: 4d 00 53 00 00 00 07 00   M.S.....
0020: 00 00 6d 00 61 00 73 00   ..m.a.s.
0028: 74 00 65 00 72 00 00 00   t.e.r...

I have spoken with Digita and they do not know what is causing it.  I know my sa password and this system is using the default instance in mixed mode - any idea where I need to look to resolve this issue?
0
Comment
Question by:fuzzyfreak
  • 28
  • 23
  • 8
  • +1
60 Comments
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 35736367
Seems like someone changed your sa password.
Try connecting to SQL Server with the sa password you have and if it works, just change the password in your Backup module to get it work..
Also check whether your Backup module is pointing your Server name correctly..
0
 
LVL 4

Author Comment

by:fuzzyfreak
ID: 35736418
Thanks very much for your response, help me out here, I know very little SQL - how would I connect to SQL Server with the sa account?

Did I mention the backup module works fine?
0
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 35736442
>> how would I connect to SQL Server with the sa account?

Just Open SQL Server Management Studio and connect to your SQL Server instance using sa credentials
If it works fine, then your sa password is latest else someone changed it.

>> Did I mention the backup module works fine?

Ok, Kindly let me know more about your backup module.
Is it a scheduled Agent job running in SQL Server or using a third party tool.
Whatever it is, check whether the backup module is using your sa credential correctly.
0
Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

 
LVL 4

Author Comment

by:fuzzyfreak
ID: 35736527
Thanks, OK, so logging in under sa with the password I have on file is not working, so I have gone back to Digita to enquire as to why.
0
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 35736644
Yes, If I understand correctly, Digita is a third party company who wrote your Backup application.
First contact with your SQL Server DBA internally and check with Digita later..
0
 
LVL 4

Author Comment

by:fuzzyfreak
ID: 35736663
Yes, Digita wrote the application and the Backup module.  Having SQL skills in-house is not an option for such a small company so we rely on the companies who write their apps to use SQL to provide us with support, thus with this particular issue, I am having to call upon the likes of yourself.  Digita regard it as a low priority because it isn't stopping the module from working but for me as an Admin, I do not wish to see this event glaring at me every morning in my reports.
0
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 35736714
Ok, then check with Digita..

And one more suggestion:

SQL Server by itself has Scheduled Backup options available ( Except Express edition)

So, you can also explore additional options
0
 
LVL 20

Expert Comment

by:Marten Rune
ID: 35736922
It's a 3'rd party backup solution.

Maybe it's trying to use a database thats not there anymore. I e, the application wants to check something within the database, and keeps it's own list over databases. Now if you drop a database this error could occur.

It's not a invalid password, thats state 8 I belive. But another idea is that you enforce pwd policies, and SA account has a pwd thats not compliant with the AD pwd restriction rules. Then you could get a peculiar error, the pwd matches, but its not ok, so the account should be disabled, but SA can't be disabled. This might giva errors that match your description.

If you use SSMS (SQL Server Management Studio), you could take a look at the errorlog to see if there are any corresponding errors/messages that might shed some light. (its under Management in the object explorer window).

As a last idea, create a SQL account, not SA, and assign the db_backupoperator role to this account. Now this should have the rights nessessary to backup and restore databases.

Regards Marten
0
 
LVL 4

Author Comment

by:fuzzyfreak
ID: 35768329
From the SQL Log -

2011-05-11 10:19:06.37 Logon       Error: 18456, Severity: 14, State: 8.
2011-05-11 10:19:06.37 Logon       Login failed for user 'sa'. [CLIENT: 10.0.0.3]
2011-05-11 10:19:06.98 spid51      Using 'xpstar90.dll' version '2005.90.4035' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.

Digita could not work out why this was happening.  I pointed out that the password does not work so they reset it so I can now login under sa but this has not resolved the problem.
0
 
LVL 20

Expert Comment

by:Marten Rune
ID: 35768581
Well, this is a classic password missmatch.

They need to tell you where they store the SA password, and how to change it.

Regards //Marten
0
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 35768700
>> I pointed out that the password does not work so they reset it so I can now login under sa but this has not resolved the problem.

As martenrune already pointed out, you need to check with Digita and find out where they have stored / configured your sa password and change it accordingly..
0
 
LVL 4

Author Comment

by:fuzzyfreak
ID: 35814991
Thanks guys, I have now e-mailed Digita, though judging by their previous response to this issue, I am not holding my breath.
0
 
LVL 4

Author Comment

by:fuzzyfreak
ID: 35879083
Still no response from them, unfortunately this issue is in their hands.
0
 
LVL 4

Author Comment

by:fuzzyfreak
ID: 36025039
I had to chase them for an answer and this was it -

"We simply do not have an answer for this. The backup tool does not store the SA password, it uses windows authentication to connect to the database, the fact that the database backup tool can be accessed shows this is the case.

From the call history I can see a colleague has noted that the same error message appears in your event viewer for other instances of SQL proving it is more likely an issue with the SQL installations or with the server itself. It is also noted that you have performed system restores which can cause problems with registry entries relating to SQL Server.

Assuming this is not affecting the running of any of our products unfortunately this is not something we are going to look into further."
0
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 36025890
>> The backup tool does not store the SA password, it uses windows authentication

If it uses Windows Authentication, then you would not receive sa login failure for sure..
So I suspect that some other thing is using your sa login and you need to find it to resolve your issue better..
0
 
LVL 4

Author Comment

by:fuzzyfreak
ID: 36025952
But the event is generated as soon as their backup tool is launched!
0
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 36027800
Then I suspect that there is some bug in their tool
0
 
LVL 4

Author Comment

by:fuzzyfreak
ID: 36033054
Hmmm, unfortunately, I feel I am a little stuck.  If there was a bug in their tool, given the tone of their e-mail, they would never admit to this, nor do anything about it.  I suppose you have to see it from their point of view, if I am the only customer reporting this, then why would they do anything about it?

I wonder if there are any experts here I could send it to for analysis.
0
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 36038182
>> If there was a bug in their tool, given the tone of their e-mail, they would never admit to this, nor do anything about it.

I suspected that there is a bug in their tool with the information you have mentioned earlier:

1. It's invoked or used by their program only
2. It uses Windows Authentication

In that case, it should not use sa credentials and lock it frequently..

Or else check what other applications are connected to your SQL Server causing this event..
0
 
LVL 20

Expert Comment

by:Marten Rune
ID: 36038776
This client 10.0.0.3
is the one where the backuptool is installed on, as an adminserver for this product? Right?

//Marten
0
 
LVL 4

Author Comment

by:fuzzyfreak
ID: 36039019
Correct Marten.

So to clarify, the backup app is on my SBS2003 server, same place as SQL and the DB itself.  I am launching the backup app using a batch file and a scheduled task, however even when I launch manually it still generates the error.  The app itself still connects to the DB and works perfectly fine.
0
 
LVL 20

Expert Comment

by:Marten Rune
ID: 36039106
Is the SBS server 10.0.0.3?

//Marten
0
 
LVL 4

Author Comment

by:fuzzyfreak
ID: 36042789
Correct
0
 
LVL 20

Expert Comment

by:Marten Rune
ID: 36146548
Does the backup software use Jobs in SQL Server?

If so I have seen similar errors, open the jobs, if its owned by SQL Server change owner to yourself, now close and open again and change to SA as owner. This might resolve you problem (given these jobs I assume exists really exists). Sorry for the late respons.

Please provide feedback for this!

//Marten
0
 
LVL 4

Author Comment

by:fuzzyfreak
ID: 36165045
Sorry, I do not understand the question - how do I know if it uses Jobs? - how do I open the Jobs?
0
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 36165653
Hitting back at the older spot..
As I mentioned earlier, you seem to have some of your jobs configured using sa credentials and you can list the jobs configured in your server using the query below:

select name, description, enabled
FROM msdb.dbo.sysjobs

Either one of those jobs are configured using older password of sa credential or sa credential might have expired / changed after the job is scheduled..
0
 
LVL 4

Author Comment

by:fuzzyfreak
ID: 36166019
ran that query but no result - (0 row(s) affected)

Are you sure I was supposed to run it on msdb.dbo?
0
 
LVL 20

Expert Comment

by:Marten Rune
ID: 36167588
This means you don't have any jobs scheduled. That's okay, just a longshot.
I'll get back to this thread if I think of anything that matches the error description.
Right now I'm out of ideas. I would like to get my hands on this to examine myself,
but I guess it's resident is not in Stockholm :-)

Regards Marten
0
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 36167749
>> ran that query but no result - (0 row(s) affected)

Forgot to mention about this..
It will return records only if you have sysadmin privileges else it wouldn't display anything..

I think you need to check with digita for any jobs running or scheduled under old sa credentials and ask them to change it to get it work..
0
 
LVL 4

Author Comment

by:fuzzyfreak
ID: 36186527
Naturally I ran that query as the domain administrator.  Not quite sure what I am supposed to ask Digita, as you can see from their previous response, they no longer want responsibility.
0
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 36186673
Got it..
Can you kindly confirm whether your domain administrator is granted sysadmin rights on SQL Server..
If not, then you can't see that and as you are not getting help from Digita, I would recommend you to get your sa password so that you can start controlling your SQL Server..
0
 
LVL 4

Author Comment

by:fuzzyfreak
ID: 36186691
Hi, I am the domain admin and the domain admin has sysadmin rights on the SQL server.  I also have the sa password.
0
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 36189394
>>  I also have the sa password.

Can you login using sa credentials and try running the query which I have provided earlier. Provided again for reference

select name, description, enabled
FROM msdb.dbo.sysjobs
0
 
LVL 4

Author Comment

by:fuzzyfreak
ID: 36193950
(0 row(s) affected)

Same again.
0
 
LVL 20

Expert Comment

by:Marten Rune
ID: 36194152
Then we know for sure that it,s not at job thing.

//Marten
0
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 36200618
Also check for any jobs scheduled in your Windows Task scheduler..
0
 
LVL 4

Author Comment

by:fuzzyfreak
ID: 36213665
The backup module is launching as a scheduled task, but the message is also generated when launching the module manually.
0
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 36213926
Then at least one of the step in that task is provided with wrong sa credentials and the rest of the task are working fine..
0
 
LVL 4

Author Comment

by:fuzzyfreak
ID: 36214087
I'm confused.
0
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 36214126
Ok, can you kindly open up the Scheduled task and find out how many steps are present in that..
What I meant is that at least one of the step is configured using wrong sa credential so that you are receiving Login failed for sa..
Can you also confirm whether your Scheduled task executed successfully or not..
0
 
LVL 4

Author Comment

by:fuzzyfreak
ID: 36214135
But, as I say, the same problem occurs when launching the backup module manually i.e. not as a scheduled task.
0
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 36214194
Oh, ok..
In that case, then the job is scheduled to run automatically as a scheduled task using a login( Windows) who have sysadmin privilege in SQL Server.
But when you start the Scheduled task manually, you don't have the rights to either impersonate sa login or have sysadmin rights and hence the job is failing on the server.
0
 
LVL 4

Author Comment

by:fuzzyfreak
ID: 36214279
Let me explain again as your last comment suggest I haven't been clear enough.

A program which backs up a SQL database created by a company named Digita causes the "Login failed for user 'sa'. [CLIENT: 10.0.0.3] " error in the Application Log of the server it is running on.  (regardless of whether the program is launched manually or as a scheduled task)

Everything is on the one server and all is using Domain Admin rights.
0
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 36214301
Ok, then try this one..

Delete the existing job and reconfigure the job again which might help out..
0
 
LVL 4

Author Comment

by:fuzzyfreak
ID: 36214307
To which 'job' are you referring?
0
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 36214338
I meant job as the one present in Scheduled tasks from Digita..
0
 
LVL 4

Author Comment

by:fuzzyfreak
ID: 36214363
Forget the scheduled task - it is irrelevant.
0
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 36214381
If it is the one generating errors in your Application log, I think we need to worry about that..
Kindly let me know why you feel it as irrelevant..
0
 
LVL 4

Author Comment

by:fuzzyfreak
ID: 36214400
Because when I run the backup program manually the error is still generated  - when running manually, I am launching the backup program from it's shortcut under the start menu - I am going nowhere near scheduled tasks.
0
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 36214484
So, you obtain the error from Digita into your application log under 2 cases:

1. When run through Scheduled tasks
2. When run manually

Does this conclude that Digita is the one causing issues.
Without having knowledge and access to Digita, we can't really suggest on the measures to resolve it..
Can you kindly check it with Digita Support ( I don't think we have any more choices)
0
 
LVL 4

Author Comment

by:fuzzyfreak
ID: 36214564
Hi, I really appreciate your input but I feel I am going round in circles and as mentioned previously, Digita will help no further.

Thanks
0
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 36214699
Then I feel, you are stuck..
If you have any documentations available from Digita, then you can try reconfiguring the Backup job once again.
Else you can post those documents here so that we can try helping it out..
0
 
LVL 4

Author Comment

by:fuzzyfreak
ID: 36214792
This is all I can give you, a screen shot of the module - it has no customisable options - I am assuming that it does something to interrogate the SQL DB on launching, because the message is generated in the event log when I launch it.

 Digita-Backup.doc
0
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 36214916
Wondering there should be some settings related screen for your Digita where you will save your connection credentials and option to configure the required databases alone.
0
 
LVL 4

Author Comment

by:fuzzyfreak
ID: 36215236
No, because the app is specifically written by Digita for Digita, therefore the "Use Windows Authentication" will be written into the app.

Do you now see the difficulty I am having here?
0
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 36215604
>> No, because the app is specifically written by Digita for Digita, therefore the "Use Windows Authentication" will be written into the app

If Digita uses Windows Authentication, then Digita should not use sa credentials..
However it uses sa login somewhere which you wouldn't be able to change..

Yes, your condition is really pathetic..
And the only thing which you can do is ignore the error message in Application logs..
0
 
LVL 20

Expert Comment

by:Marten Rune
ID: 36315403
Can you test things on this server?
If so what happends if you switch authentication mode to windows only. Does anything in the application fail? When you try backups?

What about installing on a test system to figure out if the error exists after a normal next-next-next installation?

If so, you have some leverage when communicating with Digita.

//Marten
0
 
LVL 4

Accepted Solution

by:
fuzzyfreak earned 0 total points
ID: 36315453
I have requested abandoning this issue because I have done it to death.  I think reinstalling SQL would fix it but I will not do that on a system that runs two essential SQL DBs.  I am getting no help from Digita so there isn't much I can do.
0
 
LVL 22

Expert Comment

by:Larry Struckmeyer MVP
ID: 36315716
Skim read the thread so this may have already been suggested or ruled out.  If your issue is a specific application that is not working, and you actually do know the SA password, can you remove tha application and reinstall it without breaking anything else.  That should reset the password it uses to the known good SA password, or, if it asks for a password you can make it match or leave it blank?
0
 
LVL 4

Author Closing Comment

by:fuzzyfreak
ID: 37123848
Not sure why this has not been adandoned yet but forcing this by accepting my own comment.
0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article we will get to know that how can we recover deleted data if it happens accidently. We really can recover deleted rows if we know the time when data is deleted by using the transaction log.
There are literally thousands of Exchange recovery applications out there. So how do you end up picking one that’s ideal for your business & purpose? By carefully scouting the product’s features, the benefits it offers you, & reading ample reviews f…
The Relationships Diagram is a good way to get an overall view of what a database is keeping track of. It is also where relationships are defined. A relationship specifies how two tables connect to each other. As you build tables in Microsoft Ac…
Kernel Data Recovery is a renowned Data Recovery solution provider which offers wide range of softwares for both enterprise and home users with its cost-effective solutions. Let's have a quick overview of the journey and data recovery tools range he…

580 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question