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.

 All Forums
 SQL Server 2008 Forums
 Analysis Server and Reporting Services (2008)
 Empty ConnectionProperties in Upgraded 2008 Rpts

Author  Topic 

dbradish
Starting Member

24 Posts

Posted - 2009-07-27 : 13:15:28
I keep getting the following error on reports that I've upgraded to SSRS 2008 from SSRS 2005. Why do the upgraded reports keep reverting back to an empty <ConnectionProperties> <ConnectString>?

*This does not happen on new reports.
*This happens on any DataSource that a 2005 package referenced
*This happens sporadically in all SSRS 2008 report packages
*All my reports use a shared data source that in turn uses Windows Authentication.

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

DATASOURCE CODE THAT PRODUCES ERROR:
<DataSources>
<DataSource Name="Job">
<DataSourceReference>Job</DataSourceReference>
<rd:DataSourceID>42020407-a69e-46fc-b976-84fd0cc637bc</rd:DataSourceID>
<rd:SecurityType>None</rd:SecurityType>
</DataSource>
<DataSource Name="Pulse">
<ConnectionProperties>
<ConnectString />

<IntegratedSecurity>true</IntegratedSecurity>
</ConnectionProperties>
<DataSourceReference>Pulse</DataSourceReference>
<rd:DataSourceID>70e1013c-755f-45d6-80ff-b2c540008b91</rd:DataSourceID>
<rd:SecurityType>Windows</rd:SecurityType>
</DataSource>
</DataSources>

DATASOURCE CODE THAT CORRECTS THE PROBLEM, but it keeps being over-written:
<DataSources>
<DataSource Name="Job">
<DataSourceReference>Job</DataSourceReference>
<rd:DataSourceID>42020407-a69e-46fc-b976-84fd0cc637bc</rd:DataSourceID>
<rd:SecurityType>None</rd:SecurityType>
</DataSource>
<DataSource Name="Pulse">
<DataSourceReference>Pulse</DataSourceReference>
<rd:DataSourceID>70e1013c-755f-45d6-80ff-b2c540008b91</rd:DataSourceID>
<rd:SecurityType>Windows</rd:SecurityType>
</DataSource>
</DataSources>
<DataSets>

Although this problem is easily corrected, it gets very annoying to continually have to remind SSRS what DataSource it should be using.
   

- Advertisement -