Microsoft distributes Microsoft SQL Server 2012 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release.
Symptoms
Consider the following scenario:
-
You have an instance of Microsoft SQL Server Reporting Services (SSRS) that is configured to run in Microsoft SharePoint integrated mode.
-
There are multiple data-driven subscriptions on the SSRS instance.
-
You upgrade the SSRS instance to SSRS 2012.
-
You try to view the data-driven subscriptions in a SharePoint site.
In this scenario, you receive the following error message:
Value cannot be null. Parameter name: obj Troubleshoot issues with Microsoft SharePoint Foundation. Correlation ID: NumberDate and Time: Date Time
Cause
This issue occurs because the following tags are missing from the DataSettings column of the dbo.Subscriptions table in the existing data-driven subscriptions after you upgrade SSRS:
-
CaseSensitivity
-
AccentSensitivity
-
KanatypeSensitivity
-
WidthSensitivity
Resolution
Cumulative update information
Cumulative Update 2 for SQL Server 2012 SP1
The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2012 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
2790947 Cumulative update package 2 for SQL Server 2012 Service Pack 1Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 SP1 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released
Cumulative update 5 for SQL Server 2012
The fix for this issue was first released in Cumulative Update 5. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:
2777772 Cumulative update package 5 for SQL Server 2012Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released
Workaround
To work around this issue, manually add the missing tags to the DataSettings column. For more information about how to add tags, refer to the "More information" section.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
To add the tags to the DataSettings column, run the following script:DECLARE @subid as uniqueidentifierDECLARE @orig_string nvarchar(max)DECLARE @new_string nvarchar (max)SET @subid = '<SubscriptionID>' // You input your SubscriptionID here.SET @orig_string = CAST((SELECT DataSettings FROM dbo.Subscriptions where SubscriptionID = @subid) AS nvarchar(max))SET @new_string = STUFF(@orig_string, len(@orig_string) - 9, 0, '<CaseSensitivity>True</CaseSensitivity><AccentSensitivity>True</AccentSensitivity><KanatypeSensitivity>True</KanatypeSensitivity><WidthSensitivity>True</WidthSensitivity>')UPDATE dbo.Subscriptions SET DataSettings = @new_string where SubscriptionID = @subid
