Select the product you need help with
FIX: SSMS freezes when you perform management operations that relate to roles to an SSRS 2008 R2 or SSRS 2012 databaseArticle ID: 2755192 - View products that this article applies to. On This PageSymptomsAssume that you try to perform management operations on a Microsoft SQL Server 2008 R2 Reporting Services (SSRS 2008 R2) or Microsoft SQL Server 2012 Reporting Services (SSRS 2012) database in Microsoft SQL Server Management Studio (SSMS). The operations relate to roles in SSRS. In this situation, SSMS may freeze. Additionally, a time out intermittently occurs. CauseThis issue occurs because a stored procedure that is used to retrieve the role data for policies returns too much duplicated data. This issue is more likely to occur if there are many complex users, roles and policies defined in an SSRS database. ResolutionCumulative update informationCumulative Update 3 for SQL Server 2012 SP1The fix for this issue was first released in Cumulative Update 3. 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:2812412 Note 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:
(http://support.microsoft.com/kb/2812412/
)
Cumulative update package 3 for SQL Server 2012 Service Pack 12772858
(http://support.microsoft.com/kb/2772858/
)
The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was releasedCumulative update 6 for SQL Server 2012The fix for this issue was first released in Cumulative Update 6. 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:2728897 Note 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:
(http://support.microsoft.com/kb/2728897/
)
Cumulative update package 6 for SQL Server 20122692828
(http://support.microsoft.com/kb/2692828 /
)
The SQL Server 2012 builds that were released after SQL Server 2012 was released Cumulative update 4 for SQL Server 2008 R2 Service Pack 2 (SP2)The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:2777358 Note 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 2008 R2 Service Pack 2 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:
(http://support.microsoft.com/kb/2777358/
)
Cumulative update package 4 for SQL Server 2008 R2 Service Pack 22730301
(http://support.microsoft.com/kb/2730301/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was releasedStatusMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. Properties | Article Translations
 |
Back to the top
