DPR-ERR-2056 The Report Server is not responding - inconsisten error

[franciepants]

Hi all
I have recently moved my BI Server to production and have received the error: DPR-ERR-2056 The Report Server is not responding. I have 13 reports that are scheduled, they all output Excel, the error occurs on 1 or 2 reports (not necessarily the same report each time) during the scheduled run. This doesn't happen daily but about 50% of the time.The pogo log as well as the cogserver log gives the error:
DPR-ERR-2102 The dispatcher was unable to communicate with the Report Server. Diagnostic files may have been generated, please check the "bin" directory.
When I check the dump file in the bin directory, it gives this error:
Access violation - code c0000005 (first/second chance not available)
Have searched high and low trying to solve this problem. While others have had it, their problem seems to be with a specific report whereas my error occurs on various reports. Plus, the error doesn't happen every time the schedule is run. Am running on Windows 2003 server using IIS.
Any thoughts or feedback would be greatly appreciated!

[incognito]

Did you check if the datasouce of your report has changed ?

I got this problem when running an analysis studio saved report against a cube that has changed the name of a level.

The datasource structure has change.

[franciepants]

Thanks incognito. My datasource has not changed but I suspect the problem may lie in my Oracle Client. My Client is 9i but my database is 10g. I have since upgraded my client to 10g and so far everything seems OK. I should also note that I was getting and intermittant communication in my ETL using Data Manager and this seems to have also gone away with the 10g Clinet. I shall re-post if the problem has not been fixed.

[fasi]

if you are saving reports on network.

if you have distributed servers you need to use fully qualified server location on primary app

in Cognos configuration > action > edit global config > general > archive location file://\\server name\c$\Reports


it resolved my issue.