This is really a question for MS. We have hundreds of subscriptions that happen on shared and timed schedules. One particular case we found that when we change the parameter from a internal list to a list populated from a stored procedure we get this error. So we are not sure how to deal with the failed subscriptions after we update a report. Is there a solution for these kind of errors that does not involve my customers to redo their subscriptions each time we make an update to a report. What is the definitive solution to fixing these kinda errors.

Hi aleroux, According to your description, when you change the parameter from an internal list to a list populated from a stored procedure, then you could get the error “The subscription contains parameter values that are not valid”, through my in-depth investigation, I suspect that the stored procedure doesn’t return any parameter sometimes, or maybe return null as a parameter. If in this case, I suggest that you could use a Data-driven Subscription to filter out the invalid parameter. In general, the subscription will not run when the parameter is not valid. Please refer to the following steps for your reference. 1. Put the parameters which are populated from the stored procedure into a table in your database. 2. Configure the subscription query, type in the T-SQL accordingly. For example: Select * from table where parameter is not null The Data-driven Subscription allows filtering parameter according to conditions based on your requirement. If I misunderstand, could you please supply more information about this issue, then we could help you more effectively. For more information about it, please see: How to create a data-driven subscription http://msdn.microsoft.com/en-us/library/ms169673.aspx Thanks, Eileen Zhao