Actions

Information

2 responses

24 05 2013
Brian

I recently fought through this issue as well. In my case, one of the stored procedure parameters A) was unused and B) had a default value, so I removed that parameter from the stored procedure invocation. I suspect that SQL Server did something behind my back to “optimize” the call by removing the unused parameter.

17 12 2012
Richard

I had a similar problem a while back:

http://sqlprogramming.wordpress.com/2012/04/26/ssrs-report-throws-an-error-that-says-a-parameter-doesnt-exist-when-the-report-designer-clearly-shows-the-parameter-exists/

Things can look good at design time and fall apart at run time, it seems. Anyway, I had to edit the XML code to get the evaluation to happen in the correct order.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s




Follow

Get every new post delivered to your Inbox.

Join 258 other followers

%d bloggers like this: