LKBEN10586: Troubleshooting the windows scheduler (AT job) with an interactive command.


This article has not been checked!

LKB | Created: 02/04/2020 | Version: 0 | Language: EN | Rating: 0 | Outdated: False | Marked for deletion: False

Author: Wim Peeters - Keskon GmbH & Co. KG


Symptom

Your scheduled job does not run as expected.

Cause

This can have lots of causes.

Solution

You can set the switch so interaction with the desktop is possible in services.msc. (Schedule or Taskplaner) Then you check the time on your system, ad 2 minutes to it and execute the following command:

at 16:39 /interactive c:windowssystem32cmd.exe /k c: emp est.cmd

The test.cmd file has the following contents:

echo off
echo troubleshooting
echo troubleshooting > c: emp rouble.txt

You do not need to add the cmd file, just cmd.exe /k will do. I just prefer to be noticed which commandline is opened by the scheduler since I always have a few command lines on the screen. The one opened by the job is the one with "troubleshooting" in it.
If you do not see your commandline, you can check for the file c: emp rouble.txt. It should be there. If not, your job did not run. If it is but you do not see anything, you should check the interactive setting for the service.

About the Author

Wim Peeters is electronics engineer with an additional master in IT and over 30 years of experience including time spent in support, development, consulting, training and database administration. Wim has worked with SQL Server since version 6.5. He has developed in C/C++, Java and C# on Windows and Linux in different European countries and different European languages. He writes knowledge base articles to solve IT problems and publishes them on the Lubby Knowledge Platform where he is one of the most important contributors and the main developer.

Disclaimer:

The information provided in this document is intended for your information only. Lubby makes no claims to the validity of this information. Use of this information is at own risk!