The resolution is different for each cause here are the steps needed to resolve the issue.
First, check to see if the error is happening with every import rule that exists or if it only happens with one. If it is happening for every rule, perform fix 1; if it is for a single rule, look at fix 2.
- Using SQL Query Analyzer or SQL Management Studio perform the following steps;
NOTE; It is recommended that you back up your database and/or the contents of the TaskManager table before you perform any direct modification of the database. Modifying the database in this manner could cause corruption requiring you to restore the database to its state before performing any of these modifications.
Select the proper database and run the following query;
SELECT * FROM TaskManager
This will show you the contents of the table containing the task statuses. A common occurence when seeing this problem, is that one or more tasks will have a EndDateTime value of NULL. If you see one or a few of these occurences you may choose to remove just these, which should address the problem. Alternatively you can truncate the whole table, if removing the few offending entries does not fix the problem or if you cannot easily identify the offending entries.
To remove the entries with the NULL EndDateTime value run the following query;
DELETE from TaskManager
WHERE TaskManager.[Name] like '%TASKTYPE%'
and TaskManager.[EndDateTime] is NULL
The TASKTYPE value in the query should be substituted with the proper task type as seen in the [Name] column of the offending entry/entries. If there are multiple types you can run the query each time for each type or you can run the following query that does not perform a check on the task type;
DELETE from TaskManager
WHERE TaskManager.[EndDateTime] is NULL
To remove all contents of the table run the following query;
TRUNCATE TABLE TaskManager
Run the rules again and verify that they are working correctly.
- Delete the individual rule that appears to be corrupt. There are occasional difficulties deleting rules. If the rule appears again or errors in the deletion see article 3104 for steps on deleting the rule.
Note: Before deleting any rules, make sure that there are no objects in the Notification Server database that were imported by the rules to be deleted. Notification Server associates the Active Directory import rule with the objects that it imports and deleting the rule can result in the imported objects not being able to be deleted as a result.
Should this result, see article 1815, "Cleaning up Active Directory (AD) imported computer accounts created by deleted AD import rules," to get instructions on how to remove imported computer accounts.
Applies To
Notification Server 6.0
Microsoft Active Directory Connector 6.x*