I am having a problem with some CRM Reports as they are not being rendered with the error
Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException: The fetch data set query timed out after 307.9435095 seconds. Increase the query timeout, and try again.
I dont know where to change that limit , but I changed the following limits in both CRM Application servers.
OLEDBTimeout , ExtendedTimeout , NormalTimeout
Do not time out ( through ReportManager for the whole report manager and for the report itself)
executed SessionTimeout.rss script against the report manager
executiontime and maxrequestlength in web.config for CRM website
But I am still getting the error as I cant optimize the query , the report is huge and takes 5 minutes of processing but it keeps showing an error after exactly 319 seconds.
This problem applies to CRM out of the box reports and also for reports developed in BIDS
Reports works fine if the data is not huge.
Joe CRM at Power Objects has a little guide that might help.
Hope that helps.
Related
I am pretty experienced in SSRS, I have been doing it for quite some time so I know when I see the error:
"An error has occurred during report processing. (rsProcessingAborted)
An attempt was made to set a data set parameter '#SiteId' that is not defined in this data set. (rsUnknownDataSetParameter)"
I know what causes this error and can fix it. However, this error randomly happens every so often. What I end up doing is simply rebuilding the project and redeploying it and all is well for a few days, then suddenly again this same error will pop up again.
I know there is no issue with the parameter as I have a #SiteId parameter as shown:
So when I get an email from a user that "The Report Is Down" I just go to my report and rebuild and republish and the error vanishes without ANY other changes. A few days later when they want to run the report again this same error happens. What is causing this issue to come back over and over. We are running SQL Server 2016 with SSRS. It happens to ANY one of my reports on the report server. Its not a specific project it randomly happens on any project.
EDIT
What I did notice does happen is when a user reports this issue I go to the "Manage" of a report on the report server url. This area is where you find the properties, data sources, and parameters. When I click parameters I see this error:
So obviously something is destroying the parameters - that is where I am confused what is causing that. This is probably why I am getting the error message. So to reiterate a report is published works...suddenly the parameters go missing. User reports "the report no longer works" I rebuild and redeploy the report...it then works again for a day or so maybe more than a day I never investigated how long it takes for it to break again (as these are not urgent reports). Days later user says report is dead again...if I go to the report server using the report server url and click "Manage" and then click "Parameters" for some reason the parameters have disappeared...causing me to yet again redeploy. This happens over and over and over. It never ends...
The short of it is you cannot have the same shared dataset name across different SSRS Projects that are on the same SSRS server.
So within our SSRS "repository" we have several different SSRS projects. Both projects are very specific to certain functionality. What I noticed is everytime I deployed one of these SSRS projects the reports on the other project would stop working.
When the email would come from the user stating Application A's reports werent working I'd go to Application A's SSRS project and redeploy it and it would fix the issue. Days later a different user said Application B's reports weren't working so I would redeploy application B's. Not knowing that when I deployed A's reports B's would break, and vice versa deploying B's broke A's.
Come to find out....both projects had a shared dataset with the SAME NAME (dsEmployees). Same name however these datasets pointed to different sprocs with different parameters. Well when you deploy and look at the back end db the Catalog table only has one entry for dsEmployees. Everytime I redeployed this would overwrite with the other dataset since the names were the same.
Lesson learned across different SSRS projects be careful with the shared dataset name, they must be different. I was able to spot the difference by running the following query:
SELECT
c.Name,
c2.*,
c2.Parameter
FROM
DataSets d
INNER JOIN
[Catalog] c
ON
c.ItemID = d.ItemID
INNER JOIN
[Catalog] c2
ON
c2.ItemID = d.LinkID
WHERE
--one specific report for now
d.ItemID='C3008EF4-E544-48F3-92C1-2222C6148B13'
When the report was stated not to work. Then I would redeploy the report and rerun that sql statement I wrote and dumped the rows to an excel sheet to compare. One of those columns is Parameters and I noticed the parameters were slightly different. Immediately I was onto something and this ended up being it. Thanks to comment posted it helped me relook at this! This has bugged me for years!
I'm having issues with one of my reports timing out when certain parameters are passed to it. This seems to happen when the execution of the stored procedure (that builds the dataset for the report) runs over 2 mins.
I have ran the query within SSMS and the query runs and finishes in 2 mins 5 seconds.
I have read up on numerous ways on trying to increase this time out value:
Updating the report on the web portal to run indefinitely.
Updating the remote query timeout for the db instance (set to 600s)
Updating DatabaseQueryTimeout in rsreportserver.config (set to 360s)
Updated Httpruntime, executionTimeout property in web.config (set to 9000s)
Moving back through the chain I have found that the issue persists when running the report directly from the SSRS web portal.
When you inspect the console on the site, I get the following:
Funnily enough if i hit view report again after hitting this error the report is correctly generated. guessing this is because the query data was cached?
Was wondering if anyone has experienced this and would be able to give me guidance on a setting / configuration which would stop the timeout.
The version of SSRS is 2016
I have query it contains 45,611 rows which executes in SSMS (Sql Server Management Studio) 2008 R2 in 2 sec.
In SSRS ,When i preview the report it will takes 6 sec,
After i deployed the same report and configure ASP.Net application here also it will takes same as 6 sec.
Next I published report in Test Server (same no of records),here it will takes more time like 30 sec .
See Here My Report is DrilDown in Chart Reports
How will i do to improve the performance ?
Because, While you browse Report from SSRS, SSRS Reports needs to be Fetched into HTML that why it is taking extra time.
What i want to Suggest you is that : [Im supposing you are using ASP.NET]
You can Request the Report from Report Server.
Then, You can give the Output as an PDF Document.
Which will save the Time for Record Fetching (a Huge Table) as an HTML Table.
Hope You understand.
I have some users intermittently receiving this error 'Unable to read data from the transport connection—The connection was closed' when viewing an ssrs report through the ReportViewer control.
The user can access the SSRS via web browser and not replicate the error
On multiple pages reports the first page loads and where it states 'Page 1 of totalPages' this totalPages counts up as the rest of the pages are loaded. Half the time it doesn't display an error but not all pages are loaded.
We are running SSRS express within a windows application.
SQL Express installation is a named instance
When it happens the screen hangs for around 2 minutes
It occurs on a couple of reports but not others different reports. It's not data amount related, sometimes 50 page reports come through OK and sometimes 2 page reports fail.
If it fails the user can run the report again and it usually works the next time. Sometimes it takes 3-4 goes.
Nothing has changed recently, I'm told this was always the case but they never reported it.
I tried giving the single shared ssrs datasource sa user credentials - no change
Some reports appear to load OK everytime while others error out or only load a couple of pages.
What I have tried so far:
I cannot replicate this error from our remote client, I just ran 20 successful reports no dramas from within another client installed on the same network. But I can replicate it from the users computer with both my account and their account.
I cannot see anything relevant in 'C:\Program Files\Microsoft SQL Server\MSRS10_50.MyInstance\Reporting Services\LogFiles'.
Thanks in advance for tips on where to look for clues and ways to resolve this issue..
I have resolved this by removing the ReportViewer UI control and we are now creating a pdf of the report using ReportViewer.ServerReport.Render() and opening with Process.Start(). The client only wants a pdf or a print out so we don't need the report viewer as such.
I'm not sure why the connection was closed at times, maybe it's network related as I couldn't replicate on a machine located physically next to the server. Either way this is resolved, onto the next project!
Our company has a huge nasty report that takes about 50-60 minutes to run (it's for a university and lists all sorts of payment information for all students registered in courses). While it has been running each morning at 5am as a subscription, it recently stopped working and displays "An error has occurred during report processing." in the properties window for the subscription.
If I manually run the report from inside Visual Studio it will work every time, but the subscription will now always fail. I had our DBA turn on trace logging and it gave us no helpful information whatsoever. I've also set the subscription to run at different times throughout the day, with no success. The report is supposed to put an Excel file on a file share and it works for the other 5 subscriptions to this report (I have 6 subscriptions, only 1 of the 6 has a parameter set that returns values from a larger dataset). So this means that it has permission to write to the file share. Any ideas?
Could it be trying to write more than 65536 rows to the Excel file? If so it will just fail.
Also you might check the configuration for IIS to see if the report is causing a timeout.