Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
MikeM
Starting Member
6 Posts |
Posted - 2008-11-12 : 18:24:55
|
After having scheduled a SRS Report, the report tried to run but I got the following error in the server event log: ===Event Type: ErrorEvent Source: MSCRMReportingEvent Category: NoneEvent ID: 19969Date: 11/12/2008Time: 4:10:44 PMUser: N/AComputer: WEB1Description:Web service request GetDataSources to Report Server http://web1/reportserver failed with SoapException. Error: The path of the item '/Solutions_MSCRM/4.0/' is not valid. If the report server is in native mode, the path must start with slash. (rsInvalidItemPath)For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.===The application that is using SRS report is Microsoft CRM. When I attempted to view the Report Snapshot I get the following error:===Event Source: MSCRMReportingEvent Category: NoneEvent ID: 19970Date: 11/12/2008Time: 4:49:07 PMUser: N/AComputer: WEB1Description:Report render failure. Error: The selected report is not ready for viewing. The report is still being rendered or a report snapshot is not available. (rsReportNotReady)For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.====I am thinking this has to be something simple because the application and the Reporting Services configuration are a very standard install. Any help or suggestions of things I might try would appreciate. I'm getting cross-eyed from trying to debug the problem.Thanks in advanceMike |
|
jesperw
Starting Member
1 Post |
Posted - 2009-12-03 : 10:59:03
|
UrgentDid you ever solve this? I seem to have the very same problem.. Pretty much out of the box installation, and still scheduled reports fail to open with the exact same errors as described by you...Any help would be very much appreciated! |
|
|
MikeM
Starting Member
6 Posts |
Posted - 2009-12-03 : 11:26:40
|
The problem that I was having turned out to be the application itself, Microsoft CRM 4.0. They have since fixed it with one of the patches. |
|
|
|
|
|