mossmis
asked on
SQL Report Server Error. Connection failure, timeout...
I had to perform a database shrink and log file shrink to clean up space on our SQL Server. Now when I try to manage my subscriptions on the reporting services, I get the following:
An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. (rsReportServerDatabaseErr
This happens when I want to modify an existing schedule on a report and try to save it. Any Suggestions?
An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. (rsReportServerDatabaseErr
This happens when I want to modify an existing schedule on a report and try to save it. Any Suggestions?
Last Comment
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
good you found it
ASKER
Upon searching for solutions, I came I decided to create a new subscription. This time a new error surfaced and I was able to google it and find an answer:
http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=127765
http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=127765
Microsoft SQL Server
Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.
171K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
And what part of your database was getting to big
- data (.mdf or .ndf) then maybe index maintenance could solve something
- log (.ldf) look at the recovery model and if a better frequency of transaction log backups can keep them small
Shrinking database will internaly fragment database and while it normaly will grow again (from first actions) also fragment the files on disk.
For the error, no direct indication, but could be caused by not having transactionlog backup and now just crossed the timeout line.