Empty report: displayed on server 1, error on server 2

Hello,

I'm deploying the same report on different servers, same database. For the year 2007, I have no data. When I display the report on server 1 or in VS2003 locally, I see an empty report. But on server 2, I have the "rsProcessingAborted" error.

Is there a way to configure the server so that it displays an empty report even if the dataset returned is empty?

Thanks for the answers!

Tiago

Usually the report is empty if the resultset is empty. Have you looked at the logfiles (\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\Logfiles)? If processing was aborted there is usually an error (empty resultsets do not cause errors)..
|||

Yes I did. Indeed, the error happens when the resultset is empty, but it should display an empty report, not an error.

The error is the following (LogFile):

w3wp!processing!11a0!30.05.2006-14:44:10:: e ERROR: An exception has occurred in data source 'Query'. Details: System.IndexOutOfRangeException: [Product].[Activity Code]

at System.Data.Common.FieldNameLookup.GetOrdinal(String fieldName)

at System.Data.OleDb.OleDbDataReader.GetOrdinal(String name)

at Pmi.RaDGims.ReportingServices.DataExtensions.OseDataReaderWrapper.GetOrdinal(String name)

at Microsoft.ReportingServices.DataExtensions.MappingDataReader..ctor(String dataSetName, IDataReader sourceReader, String[] aliases, String[] fieldNames)

at Microsoft.ReportingServices.ReportProcessing.h..ctor(String A_0, IDataReader A_1, String[] A_2, String[] A_3)

at Microsoft.ReportingServices.ReportProcessing.a1.v()

at Microsoft.ReportingServices.ReportProcessing.ax.c()

at Microsoft.ReportingServices.ReportProcessing.a1.a(Boolean& A_0)

at Microsoft.ReportingServices.ReportProcessing.ax.b()

at Microsoft.ReportingServices.ReportProcessing.a1.a(Object A_0)

Configuration file difference between server 1 and 2 is only "ConnectionType" (0 in first server, 1 in second one). Moreover, in first server there is:

ReportingServicesService!library....

And in second one it is:

w3wp!library...

I believe it doesn't come from the report, but from the server configuration...

|||

Ok I found out. For an empty dataset:

Connection Type = OLE DB generates an empty report.

Connection Type = Olap Secure generates an error.

Had to compare LogFiles init section to find out =)

|||ps. Olap Secure is a custom connection type