During the Specified Schedule, a couple of the AD Import Rules tried to run but these were not able to finish. The progress status stays at 0% and there is not a way to stop the AD Import after it has started.
When the AD Import is forced to stop, the following error appears in the logs:
Date: 9/29/2006 8:42:05 AM
Tick Count: 411380093
Host Name: NSSERVER
Process: w3wp.exe (356)
Thread ID: 4608
Description: While stopping import rule 588ad124-1f27-4152-afcf-9d92dfa85281 System.Exception caught in StopImport. Reason: Failed to stop task ID 588ad124-1f27-4152-afcf-9d92dfa85281. Error: Invalid task id: 588ad124-1f27-4152-afcf-9d92dfa85281 ( Unhandled exception. Type=System.Exception Msg=Failed to stop task ID 588ad124-1f27-4152-afcf-9d92dfa85281. Error: Invalid task id: 588ad124-1f27-4152-afcf-9d92dfa85281 Src=Altiris.NS
Server stack trace:
at Altiris.NS.TaskManagement.TaskManagerService.Stop(String taskID)
at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(MethodBase mb, Object args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)
Exception rethrown at :
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Altiris.NS.TaskManagement.ITaskManager.Stop(String taskID)
at Altiris.NS.TaskManagement.TaskManager.Stop(String taskID)
at Altiris.DirectoryServices.UI.DirectoryConnectorWebService.StopImport(String strImportId) )
As well, there are some warnings that comes before and after the error above occurs. In this case the Schedule used for the AD Import is Half-Hour:
Date: 9/29/2006 7:50:56 AM
Tick Count: 408311031
Host Name: NSSERVER
Process: aexsvc.exe (964)
Thread ID: 5320
Description: Directory import schedule will not run. Directory Import task Half-Hour is already running.
Unknown. Possibly default schedules for these AD Import rules were overlapping. Corrupted AD Import Rules.
1. Check if the AD Import is running an update schedule for his AD information too frequently. There is the chance that it is overlapping the same update schedule. For the warning message mentioned in the Problem section, the Half-Hour Schedule was still running when the next run started. Try to change the schedule to be run every 2hrs or more.
2. You may need to delete one of the AD import rules with problems and recreate it. After the AD Import Rule has been created, run it and test the results.
Notification Server 6.0.6074 sp3
AD Connector 6.1.842