FIX: SQL Server 2008 Reporting Services does not deliver a report that contains a line chart of the Stepped Line chart type at the scheduled time

Article translations Article translations
Article ID: 972521 - View products that this article applies to.
Microsoft distributes Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release.
Expand all | Collapse all

SYMPTOMS

Consider the following scenario.
  • You have a Microsoft SQL Server 2008 Reporting Services report that contains a line chart of the Stepped Line chart type.
  • The line chart has three or more stepped lines.
  • You configure a subscription for this report and then you schedule a time to deliver the report.
When Reporting Services tries to deliver the report at the scheduled time, the delivery may fail. When this occurs, the following error message is logged into the Report Server log:
processing!WindowsService_0!b74!05/08/2009-14:00:15:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: An unexpected error occurred in Report Processing., ;
 Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: An unexpected error occurred in Report Processing. ---> System.Threading.ThreadAbortException: Thread was being aborted.
   at Microsoft.ReportingServices.OnDemandReportRendering.DynamicImageInstance.GetImage(ImageType type, ActionInfoWithDynamicImageMapCollection& actionImageMaps)
   at Microsoft.ReportingServices.OnDemandReportRendering.ChartInstance.GetImage(ImageType type, ActionInfoWithDynamicImageMapCollection& actionImageMaps)
   at Microsoft.ReportingServices.Rendering.HPBProcessing.DynamicImage.LoadDynamicImage(ActionInfoWithDynamicImageMapCollection& actionImageMaps, PageContext pageContext)
   at Microsoft.ReportingServices.Rendering.HPBProcessing.DynamicImage.WriteCustomNonSharedItemProps(RPLElementProps nonSharedProps, PageContext pageContext)
   at Microsoft.ReportingServices.Rendering.HPBProcessing.PageItem.WriteNonSharedItemProps(RPLElementProps elemProps, PageContext pageContext)
   at Microsoft.ReportingServices.Rendering.HPBProcessing.PageItem.WriteElementProps(RPLElementProps elemProps, PageContext pageContext)
   at Microsoft.ReportingServices.Rendering.HPBProcessing.Chart.WriteStartItemToStream(RPLWriter rplWriter, PageContext pageContext)
   at Microsoft.ReportingServices.Rendering.HPBProcessing.PageItem.AddToPage(RPLWriter rplWriter, PageContext pageContext, Double pageLeft, Double pageTop, Double pageRight, Double pageBottom, RepeatState repeatState)
   at Microsoft.ReportingServices.Rendering.HPBProcessing.PageItemContainer.AddToPage(RPLWriter rplWriter, PageContext pageContext, Double pageLeft, Double pageTop, Double pageRight, Double pageBottom, RepeatState repeatState)
   at Microsoft.ReportingServices.Rendering.HPBProcessing.Report.NextPage(RPLWriter rplWriter, Int32 page, Int32 totalPages)
   at Microsoft.ReportingServices.Rendering.HPBProcessing.HPBProcessing.GetNextPage(RPLReport& rplReport)
   at Microsoft.ReportingServices.Rendering.ImageRenderer.PDFRenderer.Render(Report report, NameValueCollection deviceInfo, Hashtable renderProperties, CreateAndRegisterStream createAndRegisterStream)
   at Microsoft.ReportingServices.Rendering.ImageRenderer.RendererBase.Render(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo, NameValueCollection clientCapabilities, Hashtable& renderProperties, CreateAndRegisterStream createAndRegisterStream)
   at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderReport(IRenderingExtension newRenderer, DateTime executionTimeStamp, ProcessingContext pc, RenderingContext rc, IChunkFactory cacheDataChunkFactory, IChunkFactory yukonCompiledDefinition, Boolean& dataCached)
   --- End of inner exception stack trace ---
chunks!WindowsService_0!b74!05/08/2009-14:00:15:: w WARN: Rolling back shared chunk transaction for snapshot '99476482-275a-4b0b-9783-1065f001153c', Permanent=False.
library!WindowsService_0!b74!05/08/2009-14:00:15:: w WARN: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: An unexpected error occurred in Report Processing. ---> System.Threading.ThreadAbortException: Thread was being aborted.
   at Microsoft.ReportingServices.OnDemandReportRendering.DynamicImageInstance.GetImage(ImageType type, ActionInfoWithDynamicImageMapCollection& actionImageMaps)
   at Microsoft.ReportingServices.OnDemandReportRendering.ChartInstance.GetImage(ImageType type, ActionInfoWithDynamicImageMapCollection& actionImageMaps)
   at Microsoft.ReportingServices.Rendering.HPBProcessing.DynamicImage.LoadDynamicImage(ActionInfoWithDynamicImageMapCollection& actionImageMaps, PageContext pageContext)
   at Microsoft.ReportingServices.Rendering.HPBProcessing.DynamicImage.WriteCustomNonSharedItemProps(RPLElementProps nonSharedProps, PageContext pageContext)
   at Microsoft.ReportingServices.Rendering.HPBProcessing.PageItem.WriteNonSharedItemProps(RPLElementProps elemProps, PageContext pageContext)
   at Microsoft.ReportingServices.Rendering.HPBProcessing.PageItem.WriteElementProps(RPLElementProps elemProps, PageContext pageContext)
   at Microsoft.ReportingServices.Rendering.HPBProcessing.Chart.WriteStartItemToStream(RPLWriter rplWriter, PageContext pageContext)
   at Microsoft.ReportingServices.Rendering.HPBProcessing.PageItem.AddToPage(RPLWriter rplWriter, PageContext pageContext, Double pageLeft, Double pageTop, Double pageRight, Double pageBottom, RepeatState repeatState)
   at Microsoft.ReportingServices.Rendering.HPBProcessing.PageItemContainer.AddToPage(RPLWriter rplWriter, PageContext pageContext, Double pageLeft, Double pageTop, Double pageRight, Double pageBottom, RepeatState repeatState)
   at Microsoft.ReportingServices.Rendering.HPBProcessing.Report.NextPage(RPLWriter rplWriter, Int32 page, Int32 totalPages)
   at Microsoft.ReportingServices.Rendering.HPBProcessing.HPBProcessing.GetNextPage(RPLReport& rplReport)
   at Microsoft.ReportingServices.Rendering.ImageRenderer.PDFRenderer.Render(Report report, NameValueCollection deviceInfo, Hashtable renderProperties, CreateAndRegisterStream createAndRegisterStream)
   at Microsoft.ReportingServices.Rendering.ImageRenderer.RendererBase.Render(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo, NameValueCollection clientCapabilities, Hashtable& renderProperties, CreateAndRegisterStream createAndRegisterStream)
   at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderReport(IRenderingExtension newRenderer, DateTime executionTimeStamp, ProcessingContext pc, RenderingContext rc, IChunkFactory cacheDataChunkFactory, IChunkFactory yukonCompiledDefinition, Boolean& dataCached)
   --- End of inner exception stack trace ---
   at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderReport(IRenderingExtension newRenderer, DateTime executionTimeStamp, ProcessingContext pc, RenderingContext rc, IChunkFactory cacheDataChunkFactory, IChunkFactory yukonCompiledDefinition, Boolean& dataCached)
   at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderReport(DateTime executionTimeStamp, ProcessingContext pc, RenderingContext rc, IChunkFactory yukonCompiledDefinition)
   at Microsoft.ReportingServices.Library.RenderLive.CallProcessingAndRendering(ProcessingContext pc, RenderingContext rc, OnDemandProcessingResult& result)
   at Microsoft.ReportingServices.Library.RenderStrategyBase.ExecuteStrategy(OnDemandProcessingResult& processingResult)
runningjobs!WindowsService_0!b74!05/08/2009-14:00:15:: i INFO: CancelableJobExecution.Execute caught some other thread abort exception
library!WindowsService_0!b74!05/08/2009-14:00:15:: i INFO: Initializing EnableExecutionLogging to 'True'  as specified in Server system properties.
library!WindowsService_0!b74!05/08/2009-14:00:15:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details., ;
 Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. ---> System.Threading.ThreadAbortException: Thread was being aborted.
   at Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
   at Microsoft.ReportingServices.Library.ExecutionDisposerProxy.ExecuteReport()
   at Microsoft.ReportingServices.Library.RenderReportAction.PerformExecution()
   at Microsoft.ReportingServices.Library.RenderReportAction.Render()

RESOLUTION

The fix for this issue was first released in Cumulative Update 3 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
971491 Cumulative update package 3 for SQL Server 2008 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

WORKAROUND

To work around this issue, change the chart type to another chart type. For example, you can change from the Stepped Line chart type to the Line with Markers chart type.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

REFERENCES

For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems


For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages


For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 972521 - Last Review: July 21, 2009 - Revision: 1.0
APPLIES TO
  • Microsoft SQL Server 2008 Reporting Services
Keywords: 
kbsurveynew kbfix kbqfe kbexpertiseadvanced KB972521

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com