After our SQL Server Reporing Services instance was rebuilt (for reasons unrelated to EdgeSight), I am unable to load the EdgeSight reports. When I attempt to load the reports, I receive the following error: "Error publishing reports: The item '/Citrix/EdgeSight/E6B1E9E3-D1E8-4B01-93B8-085284F6D5DB/edgesight' cannot be found. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/Citrix/EdgeSight/E6B1E9E3-D1E8-4B01-93B8-085284F6D5DB/edgesight' cannot be found.I have confirmed that Report Server Credentials have the Content Manager role in the root folder of the report server.When I navigate to "Home > Citrix > EdgeSight > E6B1E9E3-D1E8-4B01-93B8-085284F6D5DB > Default" through Report Manager, I find an alerts report with the following text: "The report server cannot process the report. The data source connection information has been deleted. (rsInvalidDataSourceReference)".Outside of reporting, all other aspects of EdgeSight remain functional. We are running EdgeSight Server 5.2 on Win2k8x64. The SQL Server Reporting Services instance is 2008 running on Win2k8x64. The EdgeSight database is hosted on a clustered SQL 2005 instance.
Re-applying the Report Server Configuration through EdgeSight's web console fixed it. It rebuilt the missing Data Source. I could have sworn I had to do this after the Reporting server was rebuilt but probably somehow wiped out the DataSource entry while troubleshooting the fallout.
Hi David,
You've checked everything in the EdgeSight console, in Configure | Server Configuraton | Reporting Services | Report Server, such as Report Server URL, user, etc?
Regards,Mark
Mark,
Yes. Everything is configured correcly under the Report Server (configuration tab) page (or I would likely have an error on the page). When I attempt to load the reports, it creates all of the appropriate folders in the Report Server URL, just not the reports.
And the only thing that's changed is the SQL Server Reporing Services reinstall?
As far as I know. Our SQL Reporting server was corrupted when a different product was set up to use it. It was rebuilt (same name, same service accounts, same URL, etc...). Once it came back up, I configured security on it for the EdgeSight service account and was able to connect (EdgeSight stopped complaining about the URL being unavailable) and run the load reports procedure (it just doesn't work). Not sure if something was overlooked when it was rebuilt (I, thankfully, didn't have the privilege of rebuilding it). But, it appears to be healthy and isn't throwing any errors.
Odd one this. I must admit I was reckoning on something in the Report Services config being amiss. I had problems and that's there the issue was. I can check with a couple of people who may be able to help but I guess they may not respond for a couple of days now.
I would appreciate any help you can offer. EdgeSight was working fine before SQL Reporting was rebuilt so my guess is that SQL Reporting is where the problem lies. Unfortunately, it isn't generating any errors in the logs so this might require a little more in-depth troubleshooting than I am familiar with (when it comes to SQL Reporting Services).
Thanks for the assistance.