Hi.
Am running into an interesting problem with a SQL Server 2012 Reporting Services instance that I'm running. For reference it's Reporting Services 2012 on a Windows Server 2012 R2 box, but the ReportServer and TempDB's are being hosted on a Windows Server 2008 R2 server running SQL Server 2008 R2.
Basically everything works, as it should - with the exception of saving reports in Report Builder, that already exist on the server (so overwriting them).
So I can open any report, work on it, and save it as a new name and it saves fine. If I then attempt to save that report with the same name as any other report, the ReportBuilder window freezes for 120 seconds before throwing the following error:
Failed to save report 'https://myreportserver......'
An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database.
---> 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.Exception: For more information about this error navigate to the report server on the local server machine, or enable remote errors
The strange thing is, I'm pretty sure it's none of these problems. Neither the Reporting Services or the SQL Server where the databases are kept are having any performance problems of any kind, and there's no unusual load on the servers at the time I attempt to save the file. I can't find any other error logs on either server to indicate there's an issue. Most interestingly is that whilst waiting for this error to occur I can see on the SQL Server that the database (or at least a number of tables) become locked and for the entire 120 seconds the report server becomes unusable as every other task ends up queued until the timeout happens.
It doesn't seem to be a permissions problem from what I can see either on Reporting Services, or within the database as I can see that the service account used to access the databases has the correct 'RSExecRole' permission on all the right databases, and dbo on the ReportServer and ReportServerTempDB databases.
I'm a little stumped. Have Googled (um, sorry, Binged) this problem for hours and can't find a similar problem. Anybody seen this before? Thanks.