March 17, 2009 at 10:26 am
I created a few Maintenance Plan jobs using the "sa" account for authentication. The
"sa" account password was changed since then and these jobs are now failing due to authentication failure. I do not know what the "sa" password was when these jobs were created, so I can't changed the "sa" password back to what it was. I can't delete these jobs for the same reason.
How can I get these jobs that are failing to use the current "sa" password?
Thanks
March 17, 2009 at 10:54 am
Is sqlagent connecting to sqlserver using the sa account or using its service account ?
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
March 17, 2009 at 10:57 am
Use the SQL server configuration manager on the server to update the account and password that the agent runs under.
The best advice would be to setup a domain account to run the agent, as running anything using the sa account is very bad practice and can possibly open your business to a security breach.
March 17, 2009 at 11:19 am
The "SQL Server Agent" windows service is setup to use the "Local System" Windows account.
March 17, 2009 at 11:22 am
This is the error I get.
Date03/17/2009 1:21:27 PM
LogSQL Server (Current - 03/17/2009 1:21:00 PM)
SourceLogon
Message
Login failed for user 'sa'. [CLIENT: 192.168.76.14]
March 17, 2009 at 2:25 pm
ronss (3/17/2009)
This is the error I get.Date03/17/2009 1:21:27 PM
LogSQL Server (Current - 03/17/2009 1:21:00 PM)
SourceLogon
Message
Login failed for user 'sa'. [CLIENT: 192.168.76.14]
and the client is the IP address of your sqlserver ?
Check if the job uses DTS or ISQL/OSQL commandlines that connect using the sa-user.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
March 22, 2009 at 3:38 am
first we can change the password the then ran the jobs in sql server 2000.
folowing this staps
open the notepad
copy
then save the text file at changespassord.bat in c drive
then run this
osql /U sa /P sa /Q "exec sp_password @old='sa', @new=null, @loginame='sa'"
kaushalendra Singh
March 22, 2009 at 6:16 am
Kaushalendra Singh (3/22/2009)
first we can change the password the then ran the jobs in sql server 2000.folowing this staps
open the notepad
copy
then save the text file at changespassord.bat in c drive
then run this
osql /U sa /P sa /Q "exec sp_password @old='sa', @new=null, @loginame='sa'"
I must urge you NOT to use null passwords !
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
March 22, 2009 at 11:05 am
There's no reason to use a null password. It's a horrible habit, and even if you think your system is secure, you never know. You especially never know in an environment like a company where things can change.
Set a real password and document it.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply