Home Dashboard Directory Help
Search

SSRS: System.Data.SqlClient.SqlException: The specified @category_id ('100') does not exist. by Tomasz Piekos


Status: 

Closed


1
0
Sign in
to vote
Type: Bug
ID: 795110
Opened: 7/26/2013 8:09:38 AM
Access Restriction: Public
1
Workaround(s)
view
0
User(s) can reproduce this bug

Description

Hello
during creation of e-mail subscription in SSRS I'm receiving this error:
ERROR: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. ---> System.Data.SqlClient.SqlException: The specified @category_id ('100') does not exist.

I found this: http://www.sqlservercentral.com/Forums/Topic392091-162-1.aspx#bm1323298 as a solution but I need to know if it is supported by MS.

Could you tell where SSRS is holdig category_id number? Is it hardcoded in application? I couldn't find it in any of ReportServer tables nor configuration files and even in registry.

My server:
Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64) Jun 28 2012 08:36:30 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
Details
Sign in to post a comment.
Posted by Microsoft on 10/24/2013 at 5:30 PM
Hello,
Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SQL Server. The reasons for closing these bugs are following:
1.     The fix is risky to implement in the current version of the product (service packs)
2.     Scenarios reported in the bug are not common enough
3.     A viable workaround is available
Thanks again for reporting the product issue and continued support in improving our product.

I have also provided workarounds for this issues.

Regards,
Mariusz Cichomski
Sign in to post a workaround.
Posted by Microsoft on 10/24/2013 at 5:29 PM
there are several workarounds:

1) make the service account sysadmin

2) callow only local connections to teh SQL server (disable TCP, named Pipes)

3) revert to using a domain account for the ReportServer. and give proper permissions to the login.