Why do I get exceptions while using Job Manager Service since upgrade from MonitorWare Console 1.x to 2.x?
Created 2004-07-09 by Tamsila-Q-Siddique.
We have been using MonitorWare Console 1.1 and upgrade to MonitorWare Console 2.0. Every
time we schedule a report we get the error quoted below. Why do I get exceptions while using Job Manager
Service?
System.FormatException: Could not determine the order of year, month, and date from m/d/aaaa.
at System.DateTimeParse.GetYearMonthDayOrder(String datePattern, DateTimeFormatInfo dtfi)
at System.DateTimeParse.GetDayOfNNY(DateTimeResult result, DateTimeRawInfo raw, DateTimeFormatInfo dtfi)
at System.DateTimeParse.ProcessTerminaltState(Int32 dps, DateTimeResult result, DateTimeRawInfo raw,
DateTimeFormatInfo dtfi)
at System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles styles)
at System.DateTime.Parse(String s, IFormatProvider provider, DateTimeStyles styles)
at System.DateTime.Parse(String s, IFormatProvider provider)
at System.DateTime.Parse(String s)
at Adiscon.MonitorWare.JobManager.MWCJobManager.isReportTimeValid(String reportName)
at Adiscon.MonitorWare.JobManager.MWCJobManager.OnTimer(Object source, ElapsedEventArgs e)
In MonitoWare Conosle 1.x (i.e. 1.0 and 1.1) the format in which the values are written in database by Job Manager is different from the format used in MonitorWare Console 2.x. And this is the reason why Job Manager gives exception. Please do the following to solve the problem:
- Start Console and then click on Options then choose Job Manager Settings.
- A message box is displayed stating that your previous settings would be deleted (form "JMSettings" Table).
- Press Ok.
- Define your report settings again.
- Save the values.
- Re-start Job Manager.
|