HI, Rebecca: Have you attempted to reformat the date as mentioned in the message to 01/02/2014 00:00:00?
2014/02/21 15:36:17 - Convert Dates.0 - ERROR (version 4.1.0, build 1 from 2012-11-06 13<tel:2012-11-06%2013>.20.53) : Reported Date String : couldn't convert string [2014/01/02 00:00:00.000] to a date using format [MM/dd/yyyy HH:mm:ss] Michelle From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Boyd, Rebecca Sent: Friday, February 21, 2014 3:36 PM To: [email protected] Subject: Re: DMT and extra Zeros ** Thanks, Roger. I tried deleting the first row of data. The new first row generated the same error message. Then I tried loading the spreadsheet with a single row of data. Same error. I've seen variations of this before. For example, when loading people, the Corporate IDs all had a ".0" appended to them. That didn't cause an error so we didn't catch it until it got into the people form. The corporate IDs on the spreadsheet definitely didn't have ".0" at the end. On Fri, Feb 21, 2014 at 4:16 PM, Roger Justice <[email protected]<mailto:[email protected]>> wrote: ** Since the error message includes the Pentaho application it could be that Pentaho is causing the error. You could attempt to import a single entry directly to the DMT form to isolate the error. -----Original Message----- From: Boyd, Rebecca <[email protected]<mailto:[email protected]>> To: arslist <[email protected]<mailto:[email protected]>> Sent: Fri, Feb 21, 2014 4:12 pm Subject: DMT and extra Zeros ** Hello everyone, I am trying to load incidents using the HPD_LoadHelpDesk tab of the Transactional_Incident spreadsheet. The job is erroring out on the Load step because it can't convert a date. The date looks correct on the spreadsheet, but when Remedy reports the error, it always reports an extra zero for the seconds. 2014/01/02 00:00:00.00 - Spreadsheet data 2014/01/02 00:00:00.000 - Remedy error I have typed the date in fresh. I've changed the date & time. I've re-formatted the cell. I've created new jobs every time only to get the same 'ol error message. 8.1 Clean Install, Oracle 11g Here's a truncated version of the error message: 2014/02/21 15:36:17 - Transactional_Incident - Start of job execution 2014/02/21 15:36:17 - Convert Dates.0 - ERROR (version 4.1.0, build 1 from 2012-11-06 13<tel:2012-11-06%2013>.20.53) : Unexpected error : 2014/02/21 15:36:17 - Convert Dates.0 - ERROR (version 4.1.0, build 1 from 2012-11-06 13<tel:2012-11-06%2013>.20.53) : org.pentaho.di.core.exception.KettleValueException: 2014/02/21 15:36:17 - Convert Dates.0 - ERROR (version 4.1.0, build 1 from 2012-11-06 13<tel:2012-11-06%2013>.20.53) : Reported Date String : couldn't convert string [2014/01/02 00:00:00.000] to a date using format [MM/dd/yyyy HH:mm:ss] 2014/02/21 15:36:17 - Transactional_Incident - Transactional_Incident 2014/02/21 15:36:17 - Transactional_Incident - ERROR (version 4.1.0, build 1 from 2012-11-06 13<tel:2012-11-06%2013>.20.53) : Errors detected! 2014/02/21 15:36:18 - Transactional_Incident - Job execution finished -- Rebecca Boyd Application Administrator Wake Forest University _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ -- Rebecca Boyd Application Administrator Wake Forest University _ARSlist: "Where the Answers Are" and have been for 20 years_ ---------------------------------------------------------------------- This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.bankofamerica.com/emaildisclaimer. If you are not the intended recipient, please delete this message. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
