Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 Old Forums
 CLOSED - SQL Server 2005/Yukon
 SSIS Invalid character value for cast specificatio

Author  Topic 

2lazydba
Yak Posting Veteran

62 Posts

Posted - 2006-06-20 : 13:42:14
Hi,

I am getting the following error in the SSIS Data Flow Task
while running a simple query to fetch data


[WS_ACCOUNT_DEFECT Source [237]] Error: An OLE DB error has occurred. Error code: 0x80040E21. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "Invalid character value for cast specification".


[DTS.Pipeline] Error: component "WS_ACCOUNT_DEFECT Source" (237) failed the pre-execute phase and returned error code 0xC0202009.

How shud i solve it????

Thanks

blindman
Master Smack Fu Yak Hacker

2365 Posts

Posted - 2006-06-20 : 14:52:57
Try running your query outside of Inflagration Services (use Management Studio). Do you still get an error?
Go to Top of Page

2lazydba
Yak Posting Veteran

62 Posts

Posted - 2006-06-20 : 16:27:39
no..
tats the 1st thing i did...
Go to Top of Page

Wanderer
Master Smack Fu Yak Hacker

1168 Posts

Posted - 2006-06-21 : 04:41:27
I'm just throwing this out there:

Are the source and target destinations code pages the same?

The error message specifies issues with casting - what casting operations are you doing? I realize you said that they ran successfully outside SSIS - was it the "whole process" i.e. the select and the insert, that ran successfully outside SSIS, or only the select?

*##* *##* *##* *##*

Chaos, Disorder and Panic ... my work is done here!
Go to Top of Page

2lazydba
Yak Posting Veteran

62 Posts

Posted - 2006-06-22 : 01:19:28
problem has been solved...sorry didnt post wat exactly happened.
my sql select query was returning 2 dates ...i had declared 2 var in SSIS but of datatype string..

i changed their datatype to datetime and it solved the problem...
would have been easier if SQL Server would have pointed in a better way where is the problem...
newayz..

Go to Top of Page

blindman
Master Smack Fu Yak Hacker

2365 Posts

Posted - 2006-06-22 : 12:27:49
2005's error messages seem to set a new low for their content/verbosity index.
Go to Top of Page

Wanderer
Master Smack Fu Yak Hacker

1168 Posts

Posted - 2006-06-23 : 04:41:49
quote:
Originally posted by blindman

2005's error messages seem to set a new low for their content/verbosity index.



sadly true....

*##* *##* *##* *##*

Chaos, Disorder and Panic ... my work is done here!
Go to Top of Page
   

- Advertisement -