Solved

Fixing permissions for SQL Jobs

Posted on 2009-05-08
4
307 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.
0
Comment
Question by:ticgums
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
4 Comments
 
LVL 31

Accepted Solution

by:
RiteshShah earned 500 total points
ID: 24337323
0
 

Author Comment

by:ticgums
ID: 24337518
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.
0
 

Author Closing Comment

by:ticgums
ID: 31579499
Will post a comment explaining why I said partially.
0
 

Author Comment

by:ticgums
ID: 24338632
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.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

Introduction: When running hybrid database environments, you often need to query some data from a remote db of any type, while being connected to your MS SQL Server database. Problems start when you try to combine that with some "user input" pass…
INTRODUCTION: While tying your database objects into builds and your enterprise source control system takes a third-party product (like Visual Studio Database Edition or Red-Gate's SQL Source Control), you can achieve some protection using a sing…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

739 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