January 4, 2016 at 9:05 pm
Looking for a direction on solving an issue I am experiencing with running a SQL Agent job. Running the package in visual studios works, of course.
The package uses a Process Task to use the command line and run a NET USE command to map an UNC path to a drive letter. I chose this path, as it was the only way to pass credentials, which are required. I am not able to add permissions for the user account under the which the package is running.
So again, this works when running it manually in visual studios, but when executed from the job, I get this error:
System error 2242 has occurred. The password of this user has expired.
Having trouble tracking down the root cause. Do I need to set-up a proxy or...?
January 6, 2016 at 9:51 pm
Check the SQL Job owner. If it is set to a login that is a member of the sysadmin role, then the job will run as the SQL Agent Service Account.
If the job owner is not a sysadmin, then you need a proxy to run a cmd.
The password expired is probably on your SQL Agent Service Account.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply