The Delta Resource Membership update schedule fails to run: Error retrieving Collection Last Run Date or it has an invalid format


Article ID: 158174


Updated On:


Management Platform (Formerly known as Notification Server)


When the Delta Resource Membership update schedule is run it quickly fails and aborts. An error similar to the following (excerpt) is found in the NS logs.

Module: w3wp.exe

Source: Altiris.NS.StandardItems.Collection.DeltaCollectionUpdateSchedule
Description: Error occurred during delta collection updating: Altiris.NS.Exceptions.AeXException: Error retrieving Collection Last Run Date or it has an invalid format. Value '1434-08-14 09:59:19.000', Format 'yyyy'-'MM'-'dd HH':'mm':'ss' ---> System.FormatException: String was not recognized as a valid DateTime.
   at System.DateTimeParse.ParseExact(String s, String format, DateTimeFormatInfo dtfi, DateTimeStyles style)
   at Altiris.NS.StandardItems.Collection.DeltaCollectionUpdateSchedule.get_LastRunDate()
   --- End of inner exception stack trace ---
   at Altiris.NS.StandardItems.Collection.DeltaCollectionUpdateSchedule.get_LastRunDate()
   at Altiris.NS.StandardItems.Collection.DeltaCollectionUpdateSchedule.OnSchedule_Impl()
**CEDUrlStart** :**CEDUrlEnd**




When the process is initiated the stored procedure “spDeltaCollectionUpdate” is run and passed the date and time that the last update had been run via the paramter @LastRunDate. In this case the stored procedure was passed in a data that it could not use:
EXECUTE spDeltaCollectionUpdate @LastRunDate='1434-08-14 09:59:19.000', @DependantDataClassHint=N'dependant_dataclass'
As a result the process aborts. The value passed into the @LastRunDate parameter is found in C:\ProgramData\Symantec\SMP\Settings\CoreSettings.config
In this case the value set was as follows:

<customSetting key="DeltaCollectionUpdateLastRunDate" type="local" value="1434-08-14 09:59:19.000" />




Change the bogus date to a valid date and time then save the file:
<customSetting key="DeltaCollectionUpdateLastRunDate" type="local" value="2013-07-04 10:54:17" />  
Also verify that the setting PolicyChangeCollectionUpdateLastRunDate has a valid date as well, or the error may still occur.

Applies To

Symantec Management Platform 7.1 SP2 MP1.1