I am using pentaho bi server 4.5 version, I have huge data for the particular tenant. When I am trying to generate report for particular period .. It is giving error as "Read Timeout" . And displaying as below :
ERROR
The requested URL could not be retrieved
While trying to retrieve the URL: http://xx.xxx.xx.xxx:8081/pentaho/ViewAction?
The following error was encountered:
Read Timeout
The system returned:
[No Error]
A Timeout occurred while waiting to read data from the network. The network or server may be down or congested. Please retry your request.
Please help me out.
And also need help on how to increase the read time on bi server.
Thanks in advance,
Mounesh
We can control the query timeout for PRPTs as follows.
Master Report > Attributes > query > timeout
Here you can define the how many seconds the report times out.
Master Report > Attributes > query > limit
Here you can define how many rows are returned to the report.
If using the Manage Data Sources Perspective in PUC you can add an extra property to set the query timeout.
This socketTimeout is valid for PostgreSQL and MySQL if you use any other DB let me know.
For further knowledge:
/biserver-ee/pentaho-solutions/system/mondrian/mondrian.properties
mondrian.rolap.queryTimeout=300
This accounts for Analyzer/ Mondrian timeouts.
Related
I'm using the SQL Connector in Azure Logic Apps to connect to our Azure SQL Database to perform queries, update tables, and execute stored procedures. After several months of developing logic apps, I'm seeing the below error message when using the SQL Connector "Execute Stored Procedure (V2)". I'm only encountering this error with this specific connector. All the other connectors work just fine. Has anyone encountered this error before and had success troubleshooting?
Error:
Could not retrieve values. Error code: 'BadRequest', Message: 'The value's length for key 'application name' exceeds it's limit of '128'.
clientRequestId: 'XXXXX'. More diagnostic information: x-ms-client-request-id is 'XXXXX'.
Just had a call with Microsoft Support and got confirmation: this is the global issue in the SQL connector of LogicApp. They are working on this to fix, no ETA for now.
Update: should be fixed from around 29.03.2022 03:00 CET
I have a bit a funny situation. Our Azure SQL instance maxes out at 100 DTU for a certain query and the query returns a timeout:
SqlException (0x80131904): Timeout expired. The timeout period
elapsed prior to completion of the operation or the server is not
responding. This failure occurred while attempting to connect to the
routing destination.
If I run exactly the same query (with the parameters hardcoded) in SQL Server Management Studio it still takes the DTU up to 25%, but that's still far away from 100%. Nothing else runs on that server. There are a few other queries that run before/after. But if we just run them, nothing spikes out.
Any ideas?
My analysis of the issue goes like this..
First when DTU's are maxed out and if a query fails due to that,you will not get time out..Below is the error message you will get..
Resource ID: %d. The %s limit for the database is %d and has been reached. For more information
You can try testing that by opening multiple resource intensive queries
Secondly when you get time out's as indicated in your question,this is mostly due to query waiting for resources like say some database IO,memory..
we faced similar time out's ,but most of them are fixed by updating stats and rebuilding indexes,rest of them we optimized
I'm currently unable to email out time based subscription reports from SSRS on a new SQL Server 2012 installation on Server 2012.
I receive the following error in the SSRS LogFiles
schedule!WindowsService_5!dc4!10/14/2013-10:01:09:: i INFO: Handling Event TimedSubscription with data 1a762da1-75ab-4c46-b989-471185553304.
library!WindowsService_5!dc4!10/14/2013-10:01:09:: 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.;
library!WindowsService_5!dc4!10/14/2013-10:01:09:: w WARN: Transaction rollback was not executed connection is invalid
schedule!WindowsService_5!dc4!10/14/2013-10:01:09:: i INFO: Error processing event 'TimedSubscription', data = 1a762da1-75ab-4c46-b989-471185553304, 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: Invalid object name 'ReportServerTempDB.dbo.ExecutionCache'.
Databases were migrated from SQL 2008, this was done by a third party and I'm unsure if something was overlooked.
Any assistance would be greatly appreciated.
Thank you.
Dane
This thread seems to address your issue.
http://www.sqlservercentral.com/Forums/Topic553765-147-1.aspx
Please do a modicum of research before posting error messages.
From the Link
"
After much consternation, I have found a trigger referencing the invalid object. Trigger [Schedule_UpdateExpiration] on ReportServer table Schedule has the offending reference in it. In test, I altered this trigger to reference the correct report server tempdb and now subscriptions appear to be working properly. So far I have found nothing else broken."
AND
"If anyone is looking for a quick answer then here is what I did to solve my problem:
Updated trigger on dbo.schedule to reference the correct tempdb.
Scripted all stored procedures with their permissions onto a new query then "find and replaced" all instances of the old tempdb with the new one. "
After a while searching for a solution to fix this issue, I found that this is caused by the jobs definition of SQL Server Agent was not fully migrated to the new service. For every subscription created in SSRS, there is an associated job defined in SQL Server Agent. For services reply heavily on report delivery via subscriptions, it's best to export those jobs definition and import them into the new server.
Daniel E. answer is Correct.
I have spend a lot of time to find it and the error I am getting while updating the existing subscriptions
“An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. (rsReportServerDatabaseError)”
when i search online with the above error, i couldn't manage to fix it. after a long time i found the tigger is pointing to old database.
Temp database in the below: [ReportServerTempDB]
after updating to correct tempDB all started working fine.
ALTER TRIGGER [dbo].[Schedule_UpdateExpiration] ON [dbo].[Schedule]
AFTER UPDATE
AS
UPDATE
EC
SET
AbsoluteExpiration = I.NextRunTime
FROM
[ReportServerTempDB].dbo.ExecutionCache AS EC
INNER JOIN ReportSchedule AS RS ON EC.ReportID = RS.ReportID
INNER JOIN inserted AS I ON RS.ScheduleID = I.ScheduleID AND RS.ReportAction = 3
First of all thank you on advance for taking the time to access my question here.
I'm using Report Builder 2.0 for TFS Reporting with the TFS OLAP Cube as the main datasource.
I need to calculate the time taken between the start and end (completion) of a workitem as filled in in the appopriate TFS form.
When I use the following formula:
DATEDIFF(DAY; Microsoft_VSTS_Scheduling_StartDate_Date_(Date); Microsoft_VSTS_Scheduling_EndDate_Date_(Date))
I get the following error when running the report in the browser:
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for data set 'dataSet'. (rsErrorExecutingCommand)
Semantic query execution failed. (rsSemanticQueryEngineError)
A grouping expression must be either a scalar field or an entity.
I have been around this for days and haven't found an answer anywhere.
Any ideas?
Thanks in advance!
I have a report that runs a stored procedure that takes about an hour to run.
After about 30 minutes I get this error message on the report body:
An error has occurred during report processing.
Query execution failed for data set 'DEV'.
A severe error occurred on the current command. The results, if any, should be discarded. Operation cancelled by user.
The same stored procedure runs fine when I run it from SQL Server management studio (with the same login credentials the report runs under).
Any ideas what could be causing this? I tried increasing the timeout value on the report but that didn't help.
This just sounds like a timeout. May I suggest you don't base a SSRS report on a stored proc that takes so long to run. You could schedule a daily job to populate a table (or tables) containing this report data and point the report at this table. That way it doesn't have to recalculate the data every time.
You can find the logs in your SQL Server installation directory. example: C:\Program Files\Microsoft SQL Server\MSRS10.REPORTING\Reporting Services\LogFiles
This might help.
http://blogs.msdn.com/b/jgalla/archive/2006/10/11/session-timeout-during-execution.aspx
Check your connection string for the report. I got this error when I had used a malformed connection string. i.e. I had "Server=" when I should have had "Data Source=".