Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SSRS Error Expand / Collapse
Author
Message
Posted Monday, July 27, 2009 7:25 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, November 27, 2013 7:22 AM
Points: 133, Visits: 283
I get the following error in BIDS when trying to open a report:

Deserialization failed: The report definition element 'ConnectionProperties' is empty at line 9, position 8. It is missing a mandatory child element of type 'DataProvider'.
Line 9, position 8. 9 0

The report works fine, it was deployed previously but now I get this error in BIDS and I can't get into it to try and see what it's problem is, it's configured the same way as all my other reports that work fine as well, I don't want to have to recreate the report which I did last time I got this error.

Has anyone come accross this before or does anyone know how to fix it?


Thanks
Post #760034
Posted Monday, July 27, 2009 10:29 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 11:21 AM
Points: 10,196, Visits: 13,126
Have you tried re-downloading the report from the Report Server?

You can also open the RDL in a text editor and manually add the missing attribute.




Jack Corbett

Applications Developer

Don't let the good be the enemy of the best. -- Paul Fleming

Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
How to Post Performance Problems
Crosstabs and Pivots or How to turn rows into columns Part 1
Crosstabs and Pivots or How to turn rows into columns Part 2
Post #760231
Posted Tuesday, July 28, 2009 1:19 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, November 27, 2013 7:22 AM
Points: 133, Visits: 283
Thanks, I looked at the code and it the data collection was slightly different from a report that works so I copied the code and replaced it and it now works.

Thanks
Post #760563
Posted Tuesday, October 8, 2013 3:41 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, August 6, 2014 3:45 PM
Points: 3, Visits: 17
I ran into this problem today. I had an .rdl file in a Visual Studio Project that had a problem with it. This is a development area where no security is needed on the data sources. Since I had a deployed version of it out on the Report Server, I figured I would just edit the report definition there to create a new rdl file, delete the problem file out of my project, then use Reports > Add > Existing Item... in the Solution Explorer to bring a working copy of the report back in.

It seems to work at first, until I made any kind of change to the report in the VS design tab. Then I'd get the error quoted at the top of this thread. What was going on?

I can't speak to why the <Connection String> tag was automatically being inserted into the rdl code, but deleting it AND changing the value of the <rd:SecurityType> tag inside a <Datasource> tag did the trick:

<rd:SecurityType>Value</rd:SecurityType>



"Value" was changed from >Windows< back to >None< . It was all too easy to forget that the security settings on a deployed report get modified and can cause problems when brought back into your development environment.

Hopefully this helps someone else trying to puzzle out this particular error and how to fix it.
Post #1502848
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse