We are using FSM SmartClient Release: 6 Update 29 Build: 8961to send scheduling tasks (activities) to PSO 6.13.0.62. FSM sends tasks to field ops via FSM Mobile. We have multiple datasets in PSO. We also use appointment booking in FSM. Things have been working relatively OK for some time now, however several days ago we suddenly lost visibility to the PSO Scheduling Resources Gantt view for one dataset and see that the FSM schedule nightly process PSO DAILY INITIALIZE has errored out for that dataset since this past Saturday. We’ve tried to do the initialize manually through Maintain Dataset but that doesn’t work either.
At this point FSM is no longer able to generate the overnight LOAD file for that dataset to synch FSM and PSO. For that dataset we get this error on the Gantt screen (you can see that when we select that particular dataset from the Dataset drop down, the result displays as “No dataset”):
That dataset is configured correctly in both Modelling and Scheduling Datasets configs in PSO. No PSO configs have been changed in recent times. Appropriate configs are in FSM and no known changes in FSM in recent times that would potentially affect the tasks. Again, this has been working, and all is still working for our other datasets. Here is the error in Event log from PSO:
Message:
Error processing schedule input. Details: The supplied DateTime represents an invalid time. For example, when the clock is adjusted forward, any time in the period that .
Details:
System.ArgumentException: The supplied DateTime represents an invalid time. For example, when the clock is adjusted forward, any time in the period that is skipped is invalid. (Parameter 'dateTime') at System.TimeZoneInfo.ConvertTime(DateTime dateTime, TimeZoneInfo sourceTimeZone, TimeZoneInfo destinationTimeZone, TimeZoneInfoOptions flags, CachedData cachedData) at ThreeSixty.Shared_Classes.DatasetFunctions.GetDateTimesForPattern(String strDayPattern, DateTime dtPeriodStart, DateTime dtPeriodEnd, TimeSpan tsOpenTime, TimeSpan tsDuration, String strTimeZone, TimeZoneInfo tziCurrentTimeZone) at ThreeSixty.Schema.dsScheduleData.Availability_PatternRow.GetAvailableTimes(TimeZoneInfo tziCurrentTimeZone, DateTime dtCheckStart, DateTime dtCheckEnd) at SchedulingOptimiserClient.DataConverter.CreateAvailabilityPatternPeriodSet(Availability_PatternRow drAvailabilityPattern, DateTime dtScheduleStart, DateTime dtScheduleEnd) at SchedulingOptimiserClient.DataConverter.CreateAv
We do have activities with time commits/SLAs that cross the daylight savings time date coming up, but no other datasets out of 9 have had this issue. We’ve also checked that all places in FSM have valid time zones.
We’ve turned on high details in FSM logging, tried to run the LOAD scheduled process, can’t pinpoint the issue causing the error.
Since our field ops can’t get their schedules for that one dataset at this point, we need some sort of workaround to maybe manually generate an appropriate LOAD file from FSM to pass to PSO to at least get things back in synch? We wouldn’t know what to include/exclude to manually created that particular LOAD file. Thoughts, suggestions appreciated. If anyone else has come across this problem and knows where we can look for the solution that would be a huge help. We’ve reached out to IFS for a solution, but hoping this has some known cause and can be resolved quickly. Thanks!
