March 8, 2018 at 2:54 pm
Good evening all, I have a somewhat annoying issue that I am hoping you can help with.
Due to our back office system being old and running on 2008R2,
I am forced to use BIDS for my SSIS needs which pains me greatly as I am used to using SSDT 2015 with SQL Server 2016.
The issue I have is that when entering variables in an SSIS package in BIDS, there is no option to add expressions in place of values.
I understand that you can change the setting to evaluate as expression in the properties window however this still doesn't cure my issue.
The package starts with a WMI event watcher that polls a folder every 5 seconds for a file matching a set of variables.
When run, the package immediately fails with error 'Invalid parameter'.
I am wondering if there is a step in BIDS that I am missing.
Does anyone have any suggestions for how I can identify the invalid parameter please?
Dave
March 9, 2018 at 3:36 pm
david_h_edmonds - Thursday, March 8, 2018 2:54 PMGood evening all, I have a somewhat annoying issue that I am hoping you can help with.Due to our back office system being old and running on 2008R2,I am forced to use BIDS for my SSIS needs which pains me greatly as I am used to using SSDT 2015 with SQL Server 2016.The issue I have is that when entering variables in an SSIS package in BIDS, there is no option to add expressions in place of values.I understand that you can change the setting to evaluate as expression in the properties window however this still doesn't cure my issue.The package starts with a WMI event watcher that polls a folder every 5 seconds for a file matching a set of variables.When run, the package immediately fails with error 'Invalid parameter'.I am wondering if there is a step in BIDS that I am missing.Does anyone have any suggestions for how I can identify the invalid parameter please?Dave
Enabling logging should be able to give you more information.
Sue
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply