Problem solved. It seems that a corruped encryption key may have caused this. We have restored the SSRS repository from backup and all went back to normal
Main Topics
Browse All TopicsWe run Reporting Services in Sharepoint integrated mode. We have a farm, with the report server on one server and Sharepoint (MOSS 2007) on another server. When we connect a report to a datasource (not in the same library) it works for a while,
but then the connection's lost and the datasource disabled. I really can't understand why
The error returned is: The report server cannot process the report. The data source connection information has been deleted.
(rsInvalidDataSourceRefere
To fix it we need to point the shared data source back to its location and re-enable the data source (user/password for the data source needs to be re-entered too)
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: chrismcPosted on 2009-09-02 at 09:28:44ID: 25242713
I've seen this behaviour in the design environment (BIDS/VS) and SQL 2005 SP3 fixed that but not heard of it in the deployed environment.
It may be worth making sure you are fully patched up to date.