Exe file by Task schedule couldn't run after server reboot by schedule

If you are not familiar with the Task Scheduler, you can also try creating a simple batch file that runs the second application and configure it to run at startup using other methods such as adding it to the Startup folder or using Group Policy. This can be a quick workaround while you troubleshoot the Task Scheduler issue. 

Remember to test the batch file to ensure it runs correctly and launches the second application when the server restarts. If the batch file runs successfully, you can use this as a temporary solution until you are able to resolve the Task Scheduler issue.

Hello

All u mentioned I set it before. Please refer to my previous email. But the problem still remian. 

Really hope to get the solution from this webwite. 

Thanks

Hello Jayraj Chhaya

1. Ensure that the Task Scheduler service is set to start automatically. ==> Set it early
2. Check the security context under which the task is running. It should have the necessary permissions to execute the application. ==> Set it early
3. Modify the task to run with the highest privileges. ==> Set it early
4. Configure the task to run whether the user is logged on or not. ==>Set it early
5. Test the task by manually running it to check for any errors or prompts that require user interaction. By following these steps, you can troubleshoot and resolve the issue of Task Scheduler failing to run an application after a server reboot. ==>  Task can ran only after Windows login followed by server manager. But manually run it failed. I noticed the Task Scheduler failed due to access the wrong folder  "%APPDATA%\Microsoft\Windows\Start" , actually startup folder %APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup (keep shortcut) which  I added into user variable. How to make sure to access the right folder when at system startup?

Thank you

Hello Jayraj Chhaya

The following 4 items you mentioed are all set correctly. Refer to the attached. 

But application didn't start automatilly after server restarted. 

Until, login the Windows server and server manger console appear, then followed by application windows appear.I need application windows run automatically without login to the server. 

1. Ensure that the path specified in the task action is correct.
2. Check the permissions of the file or application being executed by the task.
3. Verify that the task is configured to run with the highest privileges.
4. Consider using full paths instead of environment variables like %APPDATA%.

The error code 2147942402 indicates "The system cannot find the file specified." This error commonly occurs when the Task Scheduler is unable to locate the file path specified in the task action.

To resolve this issue:

1. Ensure that the path specified in the task action is correct.
2. Check the permissions of the file or application being executed by the task.
3. Verify that the task is configured to run with the highest privileges.
4. Consider using full paths instead of environment variables like %APPDATA%.

By following these steps and ensuring the correct configuration of the Task Scheduler task, you should be able to run the application automatically after a server reboot without the need for manual login.

Hello Jayraj Chhaya

Thank you for your help. 

All you mentioned have been included. Here found the error message. 

Task Scheduler failed to launch action "%APPDATA%\Microsoft\Windows\Start" i
n instance "{c3278866-ee05-414e-95be-c64fd51b0044}" of task "\CCNFTP". 
Additional Data: Error Value: 2147942402.

Using domain administrator to setup.

Please advise. Thanks

When Task Scheduler fails to run an application after a server reboot, it might be due to the application requiring user interaction or specific permissions that are not available during system startup. To resolve this issue, you can try the following steps:

1. Ensure that the Task Scheduler service is set to start automatically.
2. Check the security context under which the task is running. It should have the necessary permissions to execute the application.
3. Modify the task to run with the highest privileges.
4. Configure the task to run whether the user is logged on or not.
5. Test the task by manually running it to check for any errors or prompts that require user interaction. By following these steps, you can troubleshoot and resolve the issue of Task Scheduler failing to run an application after a server reboot.

Hello Makwana

Thank you for your post. 

Your step on 1, 3, 4, 5, I set it before . But, it doesn't make sense. 

Step 2 I just make it and tested. the applicatin didn't startup until I login to the server. 

Kindly advise. 

It sounds like you’re having trouble getting an application to start automatically after a server restart on Windows Server 2019. This is a common issue and can often be resolved by adjusting the settings of the Task Scheduler or the application itself.

Here are a few steps you can take:

1. Check the Task Scheduler settings: Make sure the task is set to run whether the user is logged in or not. You can find this setting in the “General” tab of the task properties.

2. Run with highest privileges: In the same “General” tab, check the box that says “Run with highest privileges”. This allows the task to run with administrative privileges, which some applications require to start properly.

3. Check the application settings: Some applications have settings that control whether they start when the system starts. Check the documentation for your application to see if this is the case.

4. Use the “Startup” folder: If the application doesn’t need to start at a specific time, but just needs to start when the server starts, you could add a shortcut to the application in the “Startup” folder. This folder is located at C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp.

5. Check for application errors: If the application is still not starting, it may be encountering an error. Check the Event Viewer for any related error messages.

Thanks