Dears,

I have faced related scenarios in that context for which I have managed to find a workaround, however until recently process started giving me a hard time.

My flow consists of...

As per your advise, I created a new report based on the same dataset query and design. Nevertheless, upon attempting to preview the report the warnings would still appear and...

Please advise how did you get this to work... Im having the same problem but no effective solution so far.

Thanks,

Sam

Try to substitute the derived column transformation by adding the column in the OLE DB Source form the start and set the required conditions using Case statement.

Regards,

Samer

Check if your machine is synchronized with server time and that you are running the job using an admin user,

otherwise check if admin credentials have been lately changed and if...

alright, thanks for the feedback.

Regards,

Sam

well I almost downloaded it until I read the following:

WARNING This hotfix has not undergone full testing.

If you decide to install this hotfix, please note the following...

Note that I have just downloaded the Service Pack 1 in vain... problem persists!

Once you open the SSIS in 2008 it is automatically updated and you can't revert back...

Regarding the connection manager, check if there are any variables assigned in an expression relating...

seems that this issue was a bug and has been resolved by a hotfix. However it is better recommended to download the SQL 2008 R2 SP1 for that purpose.

I usually have 1 XML Config file for each package which includes all variables that I might need to edit... try doing that and avoid having multiple configurations per SSIS...

obviously there's a case which cannot be converted to integer, use the following query to detect the anomaly:

Select *

From TableName

Where IsNumeric(ColumnName) = 0

Just tried to manually design the SSIS package, consists of OLEDB Source and a flat file destination... however the package won't save either generating the following error: An invalid character...

make sure that no expressions are assigned to the flat file connection manager as that will make the path of the file read the at runtime, thus at design time...

After creating the xml config, try opening it with ie just to see if it is corrupt or valid... also in SSIS design mode assign the config to the package...