Hi,

I am getting the following errors in my reporting server log. Can anyone help me?

ReportingServicesService!processing!11!8/22/2006-01:04:04:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: There is no data for the field at position 10., ;
Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: There is no data for the field at position 10.
ReportingServicesService!processing!11!8/22/2006-01:04:04:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: There is no data for the field at position 14., ;
Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: There is no data for the field at position 14.
ReportingServicesService!processing!11!8/22/2006-01:04:04:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: There is no data for the field at position 18., ;
Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: There is no data for the field at position 18.
ReportingServicesService!processing!11!8/22/2006-01:04:04:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: There is no data for the field at position 22., ;
Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: There is no data for the field at position 22.

This error message is usually caused by a missing field in the dataset (it is defined in the dataset, but the query does not return it). It is OK if you don't use the field in your report. But if you do, then you'd get a "#error" in the textbox, or the report fails if it's used in a group/sort/filter expression.

Fang,

I have tested your response to this error but it doesn't apply to my case. I am having the exact same error message that the other user was having.

We are getting an overwhelming number of these errors and my SA is concerned that it is affecting performance of the report. He wants me to find out how to reduce the number of these errors.

Is there anything else that could cause these problems? I am in despirate need here. We are obviously using the report at a much higher level than most of the SSRS users.

Please help!!!!

Thanks,

Jim Evans

Microsoft Certified Application Developer

Has any1 fig out a real solution to this problem-

I have a report that has an emmbeded subreport- there is only 1 parameter value.
And there is only 4 fields in the query.
Yet i keep getting the same error saying there is no data in field 6..... 9:

Snippet of log file:

library!ReportServer_0-133!3bf4!02/04/2010-07:49:58:: i INFO: RenderForNewSession('/ApplicantsM')

processing!ReportServer_0-133!4544!02/04/2010-07:49:58:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: There is no data for the field at position 6., ;

 Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: There is no data for the field at position 6.

processing!ReportServer_0-133!4544!02/04/2010-07:49:58:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: There is no data for the field at position 7., ;

 Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: There is no data for the field at position 7.

processing!ReportServer_0-133!4544!02/04/2010-07:49:58:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: There is no data for the field at position 8., ;

 Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: There is no data for the field at position 8.

webserver!ReportServer_0-133!3bf4!02/04/2010-07:49:58:: i INFO: Processed report. Report='/ApplicantsM', Stream=''

library!ReportServer_0-133!3bf4!02/04/2010-07:50:03:: i INFO: RenderForNewSession('/ApplicantsM')

webserver!ReportServer_0-133!3bf4!02/04/2010-07:50:03:: i INFO: Processed report. Report='/ApplicantsM', Stream=''

library!WindowsService_100!4cec!02/04/2010-07:50:37:: i INFO: Call to CleanBatch()

Thank you.

After verifying that the field in question was indeed in my data-set (and named the same, character for character) by running the stored procedure manually in SSRS, I tried creating a new dataset from scratch, from the same exact stored procedure. Upon successfully doing this, refreshing the fields, and attaching my report tablix to this new dataset, I found that these errors stopped occurring. I was then able to delete the old dataset with no impact.

• Proposed as answer by happyscapula Monday, June 25, 2012 3:43 PM

For me the problem was setting a Date Parameter with a Default value.

=CDate("31/1/2015")

SSRS expects it in US Date Format MM/DD/YYYY or an Australian Date Format DD/MMM/YYYY and setting the default value like this fixed it: 

=CDate("31/Jan/2015")