Task Scheduler Last Run Result (0x1) but task partially completes

Question

Task Scheduler Last Run Result (0x1) but task partially completes

Michael Mariaskin 20

I'm having an odd issue. I have a scheduled task that runs as a service account nightly. The service account has the appropriate permissions in SQL and AD to execute Powershell and execute the stored procedures in the database. This task runs on the SQL server itself. The powershell, creates some files and executes a main stored procedure that launches other stored procedures. When the task is scheduled to run, it successfully creates the files and executes the main stored procedure. It appears it made it through about half of the first stored procedure in the main stored procedure that called it. Some of these stored procedures take several minutes to run (the entire routine takes about 10 minutes). It seems 0x1 is a permissions error, but the permissions are the same for every stored procedure and table involved in this routine. If I run it manually as the service account it completes successfully. It almost appears like it is timing out. Any ideas?

Accepted answer

0 additional answers

Your answer

Answer 1

MotoX80 36,401

As with any computer program, you need to have error handling and logging in your code so that when something bad happens, you will know what statement failed, and what error code you got. That is especially important for an unattended processes like a scheduled task where there is no interactive user who could see the command window and the script output.

Start by adding a transcript to the script.

https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.host/start-transcript?view=powershell-5.1

Add try/catch blocks and display key variables (processing steps) so that you know what the script is doing, and you don't have to guess.

Michael Mariaskin 20 Reputation points

2023-06-20T15:17:35.5166667+00:00

Thanks for your response. I have error handling in the script, though admittedly it was rather minimal as this was being run manually previously. I'll go ahead an add more robust error handling in the script as suggested and see what that uncovers. Thanks again.
Michael Mariaskin 20 Reputation points

2023-06-21T09:48:13.45+00:00

I just wanted to follow-up on the solution. I didnt' realize I wasn't sending my error log to the log directory, as such I checked the wrong location initially for my error log. I still think the logging could be more robust as you suggested, but the log did actually contain the issue, It was a timeout after in powershell. I raised the timeout and the job completed successfully last night. Thanks again for had you not suggested the logging, I might not have checked the log and would still be trying to figure out what went wrong.
Michael Mariaskin 20 Reputation points

2023-06-21T09:50:17.1766667+00:00

.....
MotoX80 36,401 Reputation points

2023-06-21T12:48:14.7366667+00:00

I have found that on occasions when I was struggling with some problem, I would pull a coworker over and ask them to "hey look at this for me", and as I was explaining what it was doing, I would have an "ah-ha moment" and realize what I was doing wrong. Just trying to explain the problem to someone else was the spark that helped me solve it.

Share via

Task Scheduler Last Run Result (0x1) but task partially completes

0 additional answers

Your answer