These crazy-looking dates are caused by a clash between what the MID server thinks the right date format is and what your Service-now instance is actually using. Fortunately there's an easy solution for this...
All you have to do is to tell your MID servers about the date format that you're using on your Service-now instance. You do this by adding a particular parameter to your MID server's configuration file: the instance.date.format parameter, with a value equal to the Java SimpleDateFormat date and time pattern (tutorial here) that matches the date format on your instance.
For example, suppose your Service-now instance was configured to use dates/times like "6-12-2009 9:34 am" or "11-2-2009 11:03 pm". The SimpleDateFormat time and date pattern that matches that format is M-d-yyyy K:mm a. To add this as a parameter to your MID server, just edit the config.xml file (in the directory where you've installed your MID server) to add this line:
You can put that line just before or after any other parameter line; the order of the lines doesn't matter. Then restart your MID server and voila! — your date clashes are a thing of the past!
