We help IT Professionals succeed at work.

Fixing permissions for SQL Jobs

348 Views
Last Modified: 2012-05-06
Below is there error message I get when trying to run a SQL Job. I have an idea of what the problem is but can seem to find the palce to change the username and password.

I am trying to run a legacy DTS package in a scheduled job but the job fails due to an invalid password. I checked the server configuration Manager and Surface Area Configuration but the account in the error message below is not listed as the SQL Server Agent account.

I'm running SQL Server 2005 and I have my SQL Agent setup to run as a domain admin account instead of the default local service. Everything worked fine until this morning when the domain admin account password expired and I had to change it. I'd like to change the domain acount that is used by SQL server but I can find where to change the account and password.





Date            5/8/2009 10:36:58 AM
Log            Job History (Job Name)

Step ID            1
Server            TIC-BAAN
Job Name            Job name
Step Name            Execute DTS
Duration            00:00:00
Sql Severity            0
Sql Message ID            0
Operator Emailed            
Operator Net sent            
Operator Paged            
Retries Attempted            0

Message
Unable to start execution of step 1 (reason: Error authenticating proxy Domain\User, system error: Logon failure: unknown user name or bad password.).  The step failed.
Comment
Watch Question

This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
Thanks for the suggestion, I tried changing the owner of the job but that didn't work. Still get the same error.

The links you included are for SQL 2000, I am running SQL 2005.

Author

Commented:
Will post a comment explaining why I said partially.

Author

Commented:
Changing the owner of the SQL Job was not what needed to be done but it made me rethink the job process and how the steps run. Each step of the job was set to "run as" a specific user (custom credential) So I changed the "run as" option for the first step and it worked. I then went in to the security credentials and update the custom credential that I created to use an AD service account that did not have an expiring password.

Thanks for getting me on the right track.

Gain unlimited access to on-demand training courses with an Experts Exchange subscription.

Get Access
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Empower Your Career
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE

Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.