October 3, 2008 at 10:31 am
First off, let me apologize for my ignorance as I'm not a DBA and there's not one at my company so as a developer this issue has fallen into my hands.
We are running SSRS 2005 and have decided to migrate to a new server in hopes of a performance increase. The existing environment runs smooth as silk.
In testing the new environment, I'm running 2 test subscriptions to ensure our new environment's stability at various timed intervals.
One subscription which uses a report with a SQL datasource hums along without issue. A few others which use reports with an Oracle datasource will run for a few hours then mysteriously fail with general "An error has occurred during report processing" message.
Can anyone point me in the right direction as to where I can find further information on the route cause of failure or a solution if anyone has experienced a similar problem? Thanks.
November 3, 2008 at 3:16 pm
I have experienced a similar problem with one of the project teams that uses the leveraged installation of SSRS that I support - their subscriptions are for reports that use oracle as the datasource. Many times there are issues with long-running reports and no way to cancel them out of the system. I hope someone answers for you so I can see what they say.
November 4, 2008 at 1:05 pm
Well, after spending some time on the phone with Microsoft the solution was discovered.
SSRS is installed across a cluster however SSRS isn't cluster aware. So in certain instances SSRS was generating the reports on one instance then trying to send them from the other where the report session was null. The problem was resolved by removing the secondary instance from the configuration manager.
November 4, 2008 at 2:17 pm
in my case - SSRS is configured as a webfarm. There are 3 instances in the farm and they all appear on the initialization tab of the configuration. They all have the same machine key too. So mine are clustered together.
November 4, 2008 at 2:40 pm
Well, that sounds like our configuration. When I removed the second initialization per Microsoft advice, the issue resolved.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply