Common Task Scheduler Event IDs

Here is a list of the most common Event IDs in the History tab for Windows Scheduled Tasks.

Event ID Description
100 Task Started
101 Task Start Failed
102 Task completed
103 Action start failed
106 Task registered
107 Task triggered on scheduler
108 Task triggered on event
110 Task triggered by user
111 Task terminated
118 Task triggered by computer startup
119 Task triggered on logon
129 Created Task Process
135 Launch condition not met, machine not idle
140 Task registration updated
141 Task registration deleted
142 Task disabled
200 Action started
201 Action completed
203 Action failed to start
301 Task engine properly shut down
310 Task Engine started
311 Task Engine failed to start
314 Task Engine idle
317 Task Engine started
318 Task engine properly shut down
319 Task Engine received message to start task
322 Launch request ignored, instance already running
329 Task stopping due to timeout reached
332 Launch condition not met, user not logged-on
400 Service started
411 Service signaled time change
700 Compatibility module started


Common Task Scheduler Operational Codes

Here are some hard to find Operational Codes that you find in the History tab in Windows Task Scheduler. Very useful for trying to figure out why your scheduled task isn’t working.

Op Codes Description
0 or 0x0 The operation completed successfully.
1 or 0x1 Incorrect function called or unknown function called.
2 or 0x2 File not found.
10 or 0xa The environment is incorrect.
0x41300 Task is ready to run at its next scheduled time.
0x41301 Task is currently running.
0x41302 Task is disabled.
0x41303 Task has not yet run.
0x41304 There are no more runs scheduled for this task.
0x41306 Task is terminated.
0x8004131F An instance of this task is already running.
0x800704DD The service is not available (is ‘Run only when a user is logged on’ checked?)
0xC000013A The application terminated as a result of a CTRL+C.
0xC06D007E Unknown software exception.


How To Add Apps to Windows Startup Folder

When a computer reboots, there may be certain applications that need to be started. This was easy to do in Windows XP. All that you need to do is drag a shortcut to the app into the Startup folder through the Start menu -> All Programs -> Startup. However, in later versions of Windows (i.e. 2012, Windows 10) this option isn’t available in the Start menus.

You can open the Startup folder and add programs to run with the following steps:

  • open the Run command with Windows Key + R
  • type shell:common startup
    This is for opening the Startup folder for all users. If you just want to open the folder for the logged in user, type shell:startup.
  • Add shortcuts to the applications you want to run in the open Startup folder.

Then the next time that you reboot the computer, the applications in the Startup folder will .


Installing MS SQL Server on Ubuntu

At Microsoft Connect(); 2016, it was announced that MS SQL Server was available for Linux (Ubuntu and RedHat) and MacOS. This was a real surprise and I’m not sure if its free or not. It was an easy installation on Ubuntu 16 running on HyperV on a Windows 2012 server.

The installation procedure for MSSQL and SQL Server Tools are at:

After you install the software, a brief tutorial on using it from the command line is here, but I prefer using SQL Server Management Studio (see below).



A Better Error Page on the Canada Immigration Site

Tonight during the historic US election, the Canadian Immigration site ( was down. I’m sure it had nothing to do with Americans trying to leave their country and move to Canada in light of the imminent Trump victory. The following ASP.NET error page was displayed:

Screen Shot 2016 11 08 at 10.59.59 PM

This is a default error page that gets displayed for ASP.NET sites. This is ok, but I prefer something more friendly than this type of page which doesn’t mean much for most people. A custom error page should have information about your website and contact info for the user to let you know the site failed.

The code to redirect errors to a custom page is added to the web.config file (located in the root of the website folder). The following settings refers to Error.aspx in the /ErrorPages folder.

        <customErrors mode="RemoteOnly" defaultRedirect="~/ErrorPages/Error.aspx" />