Task Scheduler Event IDs

Event ID	Task Category
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

SCOM Action Account changed- Getting Event ID 31551 and 31561 on Management Server

Cause
========
Still old sccount

Solution
==========

1.Log onto the SQL server that the OperationsManagerDW db is located on. Go to the dbo.ManagementGroup table.
2.Right Click and go to Edit Top 200 Rows.
3.Go to the WriterLoginName check out whether the old account is associated with this.
4.If it is, then change it to the new account

DPM 2016 Agent install fails with Error 347: An error occurred when the agent operation attempted to create the DPM Agent Coordinator service

Symptoms
=============
When you try to protect Windows Server 2008 or Windows Server 2008 R2 by installing the Microsoft System Center 2016 Data Protection Manager (DPM) Agent, the installation fails, and you receive one of the following error messages:

• When you try to install the agent from the DPM console:

Install protection agent on %servername% failed:
Error 347: An error occurred when the agent operation attempted to create the DPM Agent Coordinator service on %servername%.
Error details: The service did not respond to the start or control request in a timely fashion
Recommended action: Verify that the Agent Coordinator service on %servername% is responding, if it is present. Review the error details, take the appropriate action, and then retry the agent operation.

• When you try to install the agent manually on the protected server:

The program can’t start because mi.dll is missing from your computer. Try reinstalling the program to fix this problem.

Cause
=============
This issue typically occurs because a prerequisite is not installed. Most frequently, Windows Management Framework (WMF) needs to be updated.

Workaround
=============
To work around this issue, follow these steps:

1. Upgrade Windows Management Framework (WMF) on the production server to version 4.0.
2. Make sure all other prerequisites are installed.
3. Again try to install the DPM Agent.