SQL job fails when user is not logged into the server

Question

I have currently one issue with a SQL job that always fails when the user is not logged in into the server.

The job is configured to run with a specific service account that has rights on the server our sql-server is in.

When i remote connect to the server and run the job I get no error and the job doesn't fail but when I'm not remote connected with the service account the job always fails.

The job type is "SQL Server Integration Services Package"

Is this normal behaviour? Is there a way to fix this? Sorry for the vague question. Hope this is enough information.

Answer 1

Sometimes it can be as simple as deleting and remaking the scheduled task/job. It could be related to:

• A stored/network password has changed since making the job
• A corrupted password
• Something just fat fingered, and round 2 gets it right
• A windows update has changed how security works