i observed a strange behavior of SQL Server Reporting Services (SSRS) 2016 on different machines with different reports and different data source types (SQL and OLAP).
In the table [ReportServer].[dbo].[ExecutionLogStorage] are ca. 100 entries per month with ([TimeProcessing] / 1000) = 240 and [Status] = 'rsProcessingAborted'. The ReportServer logfile has for each row the entry:
ERROR: Throwing
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.;
Since there is enough space and the connection works in other cases it might be a timeout inside SSRS and i guess in the connection to the ReportServer database, but i don't know which one. The reports have specific configured timeouts (over 1 hour), so it's not the Report Server default timeout.
Which timeout is the cause of these report errors?
Related
I have migrated SQL Server 2008 R2 based SSRS to SQL Server 2016 SSRS. I am getting the following error every 10 minutes in the logs. Schedules are not updating Next Run time after Job execution.
library!WindowsService_3!28c4!01/31/2020-00:02:08:: i INFO: Call to CleanBatch()
library!WindowsService_3!28c4!01/31/2020-00:02:08:: e ERROR: Throwing 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.;
dbcleanup!WindowsService_3!28c4!01/31/2020-00:02:08:: e ERROR: Error in CleanExpiredContentCache: 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: Invalid object name 'ReportServerTempDB.dbo.ContentCache'.
runningjobs!WindowsService_3!28c4!01/31/2020-00:02:08:: e ERROR: Error in timer Database Cleanup (NT Service) : 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: Invalid object name 'ReportServerTempDB.dbo.ContentCache'.
We have a powerbuilder application which connects to SQL Server 2008 database. We have some reports which run around 3-4 hours. This is via a procedure invoked from the application code. when this long report runs, the application is getting disconnected from the database after 1 hour 40 minutes.
We have the below timeout parameters set in the connection string from application:
Connect timeout = 6000, TimeOut = 6000,CommandTimeOut = 6000
When we increased the CommandTimeOut Parameter to a higher value, the reports were completed with out database disconnect. But the performance was reduced. ie the reports are taking more time when we increased the value of CommandTimeout parameter in the connection string.
Could you please let me know what is the best solution for this issue.
I've had an SSAS tabular model deployed to a server running SQL Server 2016 for about a month and it has been running fine. All of a sudden, today it is throwing random errors when I try to query it. I just tried to run the same query 8 times and got the following 8 error messages:
1) An unexpected error occurred (file 'xmvsquery.cpp', line 3184, function 'XMVSColumn::Bind').
2) An unexpected exception occurred.
3) Query (7, 46) A date column containing duplicate dates was specified in the call to function 'DATESYTD'. This is not supported.
4) Memory error: Allocation failure . If using a 32-bit version of the product, consider upgrading to the 64-bit version or increasing the amount of memory available on the machine.
5) Column 'RowNumber-2662979B-1795-4F74-8F37-6A1BA8059B61' in table 'table name' cannot be found or may not be used in this expression.
6) An unexpected error occurred (file 'tmmdmodeltm.cpp', line 2404, function 'MDModelTM::ResolveIMBIColumnId').
7) MdxScript(Model) (1, 66) Calculation error in measure 'measure name': A date column containing duplicate dates was specified in the call to function 'DATESYTD'. This is not supported.
8) Column 'RowNumber-2662979B-1795-4F74-8F37-6A1BA8059B61' in table 'table name' cannot be found or may not be used in this expression.
Looking in the application log on the server yields no further information - The description for Event ID 22 from source MSSQLServerOLAPService cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
A couple of things that are interesting. The errors only happen if I try to run an MDX query against the model. If I try to run an equivalent DAX query, it runs fine. If I clear the SSAS cache, I can run the MDX and DAX queries against the model for a short period of time before this starts happening again.
This model is currently deployed to Microsoft SQL Server 2016 (SP1-GDR) (KB3207512) - 13.0.4199.0 (X64) and the server is running Windows Server 2016.
I've tried the following so far, and after doing each it will work for a short period of time and then it starts up again
Redeploy the model
Delete the database completely and redploy the model
Do a full process of the model
Clear the SSAS cache
Any tips would be greatly appreciated!!!
It sounds to be like your are experiencing the same defect I ran into with 2016 SP1-RTM - a seemingly random pattern of unexpected exceptions, queries that would sometimes run, sometimes not, or even render the database unprocessed(!).
SP1-CU2 resolves a number of defects which can cause symptoms like you are seeing (see link for full list), so if you've now got the latest update you are probably OK.
The only defect I have seen which SP1-CU2 does not resolve is that SELECTCOLUMNS() does not play nicely with UNION().
Thanks in advance for any assistance.
When I use the SSRS "My Subscriptions" link in the Report Manager, the browser waits for several minutes and often times out.
When checking the list of locks in SQL Activity Monitor there are a large number of locks on the Reportserver database with type ASYNC_NETWORK_IO querying the Subscription table.
The ReportServer service and database are on the same SQL Instance.
I also cannot at that time open the Subscription Table, its locked.
I have checked there are no duplicate users (linked to reports or subscriptions).
There is plenty of disk space allocated to the ReportServer and ReportServerTempDB datbases.
The report database has in the past been moved off an old server to the current one (backup & restored).
The error in the SSRS logfile at the time is:
library!WindowsService_6!7780!01/18/2016-12:11:37:: e ERROR: Throwing
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:
dbpolling!WindowsService_6!7780!01/18/2016-12:11:37:: e
ERROR: PollingMaintenance: Restarting maintenance thread for the
following exception:
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: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding..
The reports and subscriptions are working fine, its just the subscription management interface that is not loading a lot of the time.
Thanks
Vaughn
I'm attempting to populate a DB on my local SQL2008 Server using a Data Generation Plan. However, when I run it I get:
Data generation failed because of the following exception: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.. occurred 1 time(s).
I've tried setting the Connection timeout setting in the Advanced connection properties to 120 instead of 15, but I still get the error.
How do I fix this problem?
There are roughly 40 tables involved and about 20 of those are getting 100 rows inserted while, 10 tables ~1000 rows and the rest less than 100 rows. Also, when I exclude the trouble table the script completes successfully.
Thanks!
Go to Tools menu > Options > Database Tools > Data Generator > SQL Timeout
You may have to restart Visual Studio for the change to take effect, at least I had to.
There are also other timeout values that can be configured via the Registry (QueryTimeoutSeconds, LongRunningQueryTimeoutSeoncds, LockTimeoutSeconds) though I don't understand the difference. See here.