April 6, 2008 at 5:21 am
Hi
I've got a problem with a procedure that fail when running as a sql-task in an SSIS package. When I run the procedure directly on the server no errors are displayed.
The error I get in the SSIS run says:
Error: 0x0 at sp_MTM_OrdreOppfolging_underlag_Spider: The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value
Why does this procedure only fail in SSIS and not when I start it directly?
(run procedure on server) It should be refering to the same tables and views in both cases....
Best regards
Magne
April 6, 2008 at 8:01 am
Sounds like your code is converting a char to a datetime and SSIS does not like it. Can you post the code?
April 7, 2008 at 5:10 am
Thank you for your answer, but I've figured it out. In my sql I was using a convert function without a type spesification at the end Convert(datetime, date, type). When type is empty it uses the systems default value, and in this case when I ran it locally it was the right one, but when it ran on the server, it created an error. Problem solved by specifying the right type in the SQL.
April 7, 2008 at 6:34 am
I am glad to here you got everything sorted. Thanks for posting the solution.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply