Hi, My question might look complicated... hope I can describe it clearly. We use SSRS2005 sp3 enterprise and data driven subscription. We don't have issues with most of our data sources - SSAS, SQL Engine..., until we adpoted SAP BW(7.0) as another data source for reporting recently. It's still fine if the data driven subscriptions run one by one, i.e. there is no overlapping on running time; the issue however arised when the second data driven subscription gets fired before the first one finishes. The symptoms are: 1. In the runningjobs table, the value of Timeout column for the 1st subscription was -1 before the second one gets fired; the value became to 3600 immediately after the second one fired. The value is -1 for the second subscription. Another changed value is for JobStatus column, the value changed from 1 to 2 at the same pointing time. 2. The second subscription doesn't add into tables notifications and activesubscriptions; only the first one got an entry in each table. 3. The second one disappeared from the runningjobs table after a couple of minutes; where the first one is just hanging forever! 4. When I tried to use the sample script(CancelRunningJobs.rss) to cancel the job for the first subscription, the rs tool returned the message that there is no running job though the job is still in the runningjob table. 5. In the reporting services log, the message - "w WARN: Previous request for Running Requests Scavengerstill executing, skipping... w WARN: Previous request for Running Requests DBstill executing, skipping..." keeps repeating. 6. Even though the maxquerythread is set to 1, the second subscription still interrupts the first one which is being processed in the runningjob table. If another type of data source job kicks off, e.g. SSAS, it doesn't get processed until the first one successfully finishes. 7. At the moment I have to restart the reporting services service to clean up the subscription queue. 8. The problem is only with subscriptions; if those reports run through Report Manager concurrently, there is no issue. Sorry, I know the question is too long.. but I just want to give all the information for debugging. Please let me know if there is anything else that helps. Thanks a lot,

After I restarted the reporting services service, the service is back to normal, and the error messages were added into the log: " ReportingServicesService!dbpolling!1b!23/03/2011-15:15:34:: i INFO: EventPolling polling service stopped ReportingServicesService!dbpolling!a!23/03/2011-15:15:34:: i INFO: EventPolling heartbeat thread exiting for stop. ReportingServicesService!dbpolling!1b!23/03/2011-15:15:34:: i INFO: NotificationPolling polling service stopped ReportingServicesService!dbpolling!b!23/03/2011-15:15:34:: i INFO: NotificationPolling heartbeat thread exiting for stop. ReportingServicesService!dbpolling!1b!23/03/2011-15:15:34:: i INFO: SchedulePolling polling service stopped ReportingServicesService!dbpolling!1b!23/03/2011-15:15:34:: i INFO: UpgradePolling polling service stopped ReportingServicesService!runningjobs!1b!23/03/2011-15:15:34:: e ERROR: Timer Running Requests Scavenger still executing, breaking... ReportingServicesService!runningjobs!1b!23/03/2011-15:15:34:: e ERROR: Timer Running Requests DB still executing, breaking... ReportingServicesService!servicecontroller!1b!23/03/2011-15:15:34:: i INFO: Service controller exiting. ReportingServicesService!runningjobs!19!23/03/2011-15:15:34:: e ERROR: Error in timer Running Requests Scavenger : System.Threading.ThreadAbortException: Thread was being aborted. at System.Threading.Monitor.Enter(Object obj) at Microsoft.ReportingServices.Diagnostics.RunningJobContext.Cancel(AbortReason reason) at Microsoft.ReportingServices.Diagnostics.RunningRequestsScavenger.DoTimerAction() at Microsoft.ReportingServices.Diagnostics.TimerActionBase.TimerAction(Object unused) ReportingServicesService!processing!4!23/03/2011-15:15:34:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for data set 'BW_BIP'., ; Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for data set 'BW_BIP'. ---> System.Threading.ThreadAbortException: Thread was being aborted. at System.Threading.WaitHandle.WaitOneNative(SafeWaitHandle waitHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext) at System.Threading.WaitHandle.WaitOne(Int64 timeout, Boolean exitContext) at System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean exitContext) at System.Net.LazyAsyncResult.WaitForCompletion(Boolean snap) at System.Net.Connection.SubmitRequest(HttpWebRequest request) at System.Net.ServicePoint.SubmitRequest(HttpWebRequest request, String connName) at System.Net.HttpWebRequest.SubmitRequest(ServicePoint servicePoint) at System.Net.HttpWebRequest.GetRequestStream() at Microsoft.ReportingServices.XmlaClient.HttpStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) at System.IO.StreamWriter.Flush() at System.Xml.XmlTextWriter.Flush() at Microsoft.ReportingServices.XmlaClient.XmlaClient.EndRequest() at Microsoft.ReportingServices.XmlaClient.XmlaClient.SendMessage(Boolean endReceivalIfException, Boolean readSession, Boolean readNamespaceCompatibility) at Microsoft.ReportingServices.XmlaClient.XmlaClient.Discover(String requestType, String requestNamespace, ListDictionary properties, IDictionary restrictions, Boolean sendNamespacesCompatibility) at Microsoft.ReportingServices.XmlaClient.XmlaClient.Discover(String requestType, ListDictionary properties, IDictionary restrictions, Boolean sendNamespacesCompatibility) at Microsoft.ReportingServices.XmlaClient.AdomdConnection.XmlaClientProvider.Microsoft.ReportingServices.XmlaClient.AdomdConnection.IXmlaClientProviderEx.Discover(String requestType, IDictionary restrictions, Boolean throwOnErrors, Boolean sendNamespaceCompatibility) at Microsoft.ReportingServices.XmlaClient.AdomdConnection.ReadDataSourceInfo() at Microsoft.ReportingServices.XmlaClient.AdomdConnection.ConnectToXMLA(Boolean createSession, Boolean isHTTP) at Microsoft.ReportingServices.XmlaClient.AdomdConnection.Open() at Microsoft.ReportingServices.DataExtensions.SapBw.SapBwCommand.ExecuteReader(CommandBehavior behavior) at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.RunDataSetQuery() --- End of inner exception stack trace --- ReportingServicesService!processing!3!23/03/2011-15:15:34:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for data set 'ParamWeeks'., ; Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for data set 'ParamWeeks'. ---> System.Threading.ThreadAbortException: Thread was being aborted. at System.Threading.WaitHandle.WaitOneNative(SafeWaitHandle waitHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext) at System.Threading.WaitHandle.WaitOne(Int64 timeout, Boolean exitContext) at System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean exitContext) at System.Net.LazyAsyncResult.WaitForCompletion(Boolean snap) at System.Net.Connection.SubmitRequest(HttpWebRequest request) at System.Net.ServicePoint.SubmitRequest(HttpWebRequest request, String connName) at System.Net.HttpWebRequest.SubmitRequest(ServicePoint servicePoint) at System.Net.HttpWebRequest.GetRequestStream() at Microsoft.ReportingServices.XmlaClient.HttpStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) at System.IO.StreamWriter.Flush() at System.Xml.XmlTextWriter.Flush() at Microsoft.ReportingServices.XmlaClient.XmlaClient.EndRequest() at Microsoft.ReportingServices.XmlaClient.XmlaClient.SendMessage(Boolean endReceivalIfException, Boolean readSession, Boolean readNamespaceCompatibility) at Microsoft.ReportingServices.XmlaClient.XmlaClient.Discover(String requestType, String requestNamespace, ListDictionary properties, IDictionary restrictions, Boolean sendNamespacesCompatibility) at Microsoft.ReportingServices.XmlaClient.XmlaClient.Discover(String requestType, ListDictionary properties, IDictionary restrictions, Boolean sendNamespacesCompatibility) at Microsoft.ReportingServices.XmlaClient.AdomdConnection.XmlaClientProvider.Microsoft.ReportingServices.XmlaClient.AdomdConnection.IXmlaClientProviderEx.Discover(String requestType, IDictionary restrictions, Boolean throwOnErrors, Boolean sendNamespaceCompatibility) at Microsoft.ReportingServices.XmlaClient.AdomdConnection.ReadDataSourceInfo() at Microsoft.ReportingServices.XmlaClient.AdomdConnection.ConnectToXMLA(Boolean createSession, Boolean isHTTP) at Microsoft.ReportingServices.XmlaClient.AdomdConnection.Open() at Microsoft.ReportingServices.DataExtensions.SapBw.SapBwCommand.ExecuteReader(CommandBehavior behavior) at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.RunDataSetQuery() --- End of inner exception stack trace --- ReportingServicesService!processing!14!23/03/2011-15:15:34:: e ERROR: Exception in abort callback. Details: System.Threading.ThreadAbortException: Thread was being aborted. at System.Threading.WaitHandle.WaitOneNative(SafeWaitHandle waitHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext) at System.Threading.WaitHandle.WaitOne(Int64 timeout, Boolean exitContext) at System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean exitContext) at System.Net.LazyAsyncResult.WaitForCompletion(Boolean snap) at System.Net.Connection.SubmitRequest(HttpWebRequest request) at System.Net.ServicePoint.SubmitRequest(HttpWebRequest request, String connName) at System.Net.HttpWebRequest.SubmitRequest(ServicePoint servicePoint) at System.Net.HttpWebRequest.GetRequestStream() at Microsoft.ReportingServices.XmlaClient.HttpStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) at System.IO.StreamWriter.Flush() at System.Xml.XmlTextWriter.Flush() at Microsoft.ReportingServices.XmlaClient.XmlaClient.EndRequest() at Microsoft.ReportingServices.XmlaClient.XmlaClient.SendExecuteAndReadResponse(Boolean skipResults, Boolean throwIfError) at Microsoft.ReportingServices.XmlaClient.XmlaClient.CancelCommand(String sessionID) at Microsoft.ReportingServices.XmlaClient.AdomdConnection.XmlaClientProvider.Microsoft.ReportingServices.XmlaClient.AdomdConnection.IXmlaClientProviderEx.CancelCommand(String sessionID) at Microsoft.ReportingServices.XmlaClient.AdomdConnection.CancelCommand(AdomdConnection originalConnection) at Microsoft.ReportingServices.XmlaClient.AdomdCommand.Cancel() at Microsoft.ReportingServices.DataExtensions.CommandWrapper.Cancel() at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.Abort() at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSourceNode.Abort() at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.Merge.AbortHandler(Object sender, EventArgs e) at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ProcessingContext.AbortHelper.Abort(Int32 reportUniqueName, ProcessingStatus status) ReportingServicesService!runningjobs!14!23/03/2011-15:15:34:: e ERROR: Error in timer Running Requests DB : System.Threading.ThreadAbortException: Thread was being aborted. at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ProcessingContext.AbortHelper.Abort(Int32 reportUniqueName, ProcessingStatus status) at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ProcessingContext.AbortHelper.Abort(ProcessingStatus status) at Microsoft.ReportingServices.Diagnostics.ThreadJobContext.Cancel(AbortReason reason) at Microsoft.ReportingServices.Diagnostics.RunningJobContext.Cancel(AbortReason reason) at Microsoft.ReportingServices.Diagnostics.RunningJobList.InternalCancel(RunningJobContext jobCtx, AbortReason reason) at Microsoft.ReportingServices.Library.RunningJobDbTimer.DoTimerAction() at Microsoft.ReportingServices.Diagnostics.TimerActionBase.TimerAction(Object unused) ReportingServicesService!processing!f!03/23/2011-15:15:34:: 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 System.Threading.WaitHandle.WaitOneNative(SafeWaitHandle waitHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext) at System.Threading.WaitHandle.WaitOne(Int64 timeout, Boolean exitContext) at System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean exitContext) at System.Threading.WaitHandle.WaitOne() at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ThreadSet.WaitForCompletion() at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.Merge.Process(ParameterInfoCollection parameters, Boolean mergeTran) at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ProcessReport(Report report, ProcessingContext pc, ProcessingContext context) at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ProcessReport(Report report, ProcessingContext pc, Boolean snapshotProcessing, Boolean processWithCachedData, GetReportChunk getChunkCallback, ErrorContext errorContext, DateTime executionTime, CreateReportChunk cacheDataCallback, ProcessingContext& context) at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderReport(IRenderingExtension renderer, DateTime executionTimeStamp, GetReportChunk getCompiledDefinitionCallback, ProcessingContext pc, RenderingContext rc, CreateReportChunk cacheDataCallback, Boolean& dataCached) --- End of inner exception stack trace --- ReportingServicesService!chunks!f!03/23/2011-15:15:34:: v VERBOSE: ### ID=e552974c-d8b8-478f-ad0a-22abedffd482, Length=0, CompressedLength=0, TimeCompressing=0, TimeUncompressing=0, Ratio=0, Buffering=0, Permanent=False ReportingServicesService!processing!4!23/03/2011-15:15:34:: e ERROR: An exception has occurred in data source 'BW_BIP'. Details: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for data set 'BW_BIP'. ---> System.Threading.ThreadAbortException: Thread was being aborted. at System.Threading.WaitHandle.WaitOneNative(SafeWaitHandle waitHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext) at System.Threading.WaitHandle.WaitOne(Int64 timeout, Boolean exitContext) at System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean exitContext) at System.Net.LazyAsyncResult.WaitForCompletion(Boolean snap) at System.Net.Connection.SubmitRequest(HttpWebRequest request) at System.Net.ServicePoint.SubmitRequest(HttpWebRequest request, String connName) at System.Net.HttpWebRequest.SubmitRequest(ServicePoint servicePoint) at System.Net.HttpWebRequest.GetRequestStream() at Microsoft.ReportingServices.XmlaClient.HttpStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) at System.IO.StreamWriter.Flush() at System.Xml.XmlTextWriter.Flush() at Microsoft.ReportingServices.XmlaClient.XmlaClient.EndRequest() at Microsoft.ReportingServices.XmlaClient.XmlaClient.SendMessage(Boolean endReceivalIfException, Boolean readSession, Boolean readNamespaceCompatibility) at Microsoft.ReportingServices.XmlaClient.XmlaClient.Discover(String requestType, String requestNamespace, ListDictionary properties, IDictionary restrictions, Boolean sendNamespacesCompatibility) at Microsoft.ReportingServices.XmlaClient.XmlaClient.Discover(String requestType, ListDictionary properties, IDictionary restrictions, Boolean sendNamespacesCompatibility) at Microsoft.ReportingServices.XmlaClient.AdomdConnection.XmlaClientProvider.Microsoft.ReportingServices.XmlaClient.AdomdConnection.IXmlaClientProviderEx.Discover(String requestType, IDictionary restrictions, Boolean throwOnErrors, Boolean sendNamespaceCompatibility) at Microsoft.ReportingServices.XmlaClient.AdomdConnection.ReadDataSourceInfo() at Microsoft.ReportingServices.XmlaClient.AdomdConnection.ConnectToXMLA(Boolean createSession, Boolean isHTTP) at Microsoft.ReportingServices.XmlaClient.AdomdConnection.Open() at Microsoft.ReportingServices.DataExtensions.SapBw.SapBwCommand.ExecuteReader(CommandBehavior behavior) at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.RunDataSetQuery() --- End of inner exception stack trace --- at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.RunDataSetQuery() at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeReportDataSetNode.FirstPassInit() at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.FirstPassProcess(Boolean& closeConnWhenFinish) at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeReportDataSetNode.Process() at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.ProcessConcurrent(Object threadSet) ReportingServicesService!processing!3!23/03/2011-15:15:34:: e ERROR: An exception has occurred in data source 'ParamWeeks'. Details: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for data set 'ParamWeeks'. ---> System.Threading.ThreadAbortException: Thread was being aborted. at System.Threading.WaitHandle.WaitOneNative(SafeWaitHandle waitHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext) at System.Threading.WaitHandle.WaitOne(Int64 timeout, Boolean exitContext) at System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean exitContext) at System.Net.LazyAsyncResult.WaitForCompletion(Boolean snap) at System.Net.Connection.SubmitRequest(HttpWebRequest request) at System.Net.ServicePoint.SubmitRequest(HttpWebRequest request, String connName) at System.Net.HttpWebRequest.SubmitRequest(ServicePoint servicePoint) at System.Net.HttpWebRequest.GetRequestStream() at Microsoft.ReportingServices.XmlaClient.HttpStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) at System.IO.StreamWriter.Flush() at System.Xml.XmlTextWriter.Flush() at Microsoft.ReportingServices.XmlaClient.XmlaClient.EndRequest() at Microsoft.ReportingServices.XmlaClient.XmlaClient.SendMessage(Boolean endReceivalIfException, Boolean readSession, Boolean readNamespaceCompatibility) at Microsoft.ReportingServices.XmlaClient.XmlaClient.Discover(String requestType, String requestNamespace, ListDictionary properties, IDictionary restrictions, Boolean sendNamespacesCompatibility) at Microsoft.ReportingServices.XmlaClient.XmlaClient.Discover(String requestType, ListDictionary properties, IDictionary restrictions, Boolean sendNamespacesCompatibility) at Microsoft.ReportingServices.XmlaClient.AdomdConnection.XmlaClientProvider.Microsoft.ReportingServices.XmlaClient.AdomdConnection.IXmlaClientProviderEx.Discover(String requestType, IDictionary restrictions, Boolean throwOnErrors, Boolean sendNamespaceCompatibility) at Microsoft.ReportingServices.XmlaClient.AdomdConnection.ReadDataSourceInfo() at Microsoft.ReportingServices.XmlaClient.AdomdConnection.ConnectToXMLA(Boolean createSession, Boolean isHTTP) at Microsoft.ReportingServices.XmlaClient.AdomdConnection.Open() at Microsoft.ReportingServices.DataExtensions.SapBw.SapBwCommand.ExecuteReader(CommandBehavior behavior) at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.RunDataSetQuery() --- End of inner exception stack trace --- at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.RunDataSetQuery() at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeReportParametersDataSetNode.FirstPassInit() at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.FirstPassProcess(Boolean& closeConnWhenFinish) at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeReportParametersDataSetNode.Process() at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.ProcessConcurrent(Object threadSet) ReportingServicesService!processing!3!23/03/2011-15:15:34:: v VERBOSE: An exception has occurred. Trying to abort processing. Details: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for data set 'ParamWeeks'. ---> System.Threading.ThreadAbortException: Thread was being aborted. at System.Threading.WaitHandle.WaitOneNative(SafeWaitHandle waitHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext) at System.Threading.WaitHandle.WaitOne(Int64 timeout, Boolean exitContext) at System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean exitContext) at System.Net.LazyAsyncResult.WaitForCompletion(Boolean snap) at System.Net.Connection.SubmitRequest(HttpWebRequest request) at System.Net.ServicePoint.SubmitRequest(HttpWebRequest request, String connName) at System.Net.HttpWebRequest.SubmitRequest(ServicePoint servicePoint) at System.Net.HttpWebRequest.GetRequestStream() at Microsoft.ReportingServices.XmlaClient.HttpStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) at System.IO.StreamWriter.Flush() at System.Xml.XmlTextWriter.Flush() at Microsoft.ReportingServices.XmlaClient.XmlaClient.EndRequest() at Microsoft.ReportingServices.XmlaClient.XmlaClient.SendMessage(Boolean endReceivalIfException, Boolean readSession, Boolean readNamespaceCompatibility) at Microsoft.ReportingServices.XmlaClient.XmlaClient.Discover(String requestType, String requestNamespace, ListDictionary properties, IDictionary restrictions, Boolean sendNamespacesCompatibility) at Microsoft.ReportingServices.XmlaClient.XmlaClient.Discover(String requestType, ListDictionary properties, IDictionary restrictions, Boolean sendNamespacesCompatibility) at Microsoft.ReportingServices.XmlaClient.AdomdConnection.XmlaClientProvider.Microsoft.ReportingServices.XmlaClient.AdomdConnection.IXmlaClientProviderEx.Discover(String requestType, IDictionary restrictions, Boolean throwOnErrors, Boolean sendNamespaceCompatibility) at Microsoft.ReportingServices.XmlaClient.AdomdConnection.ReadDataSourceInfo() at Microsoft.ReportingServices.XmlaClient.AdomdConnection.ConnectToXMLA(Boolean createSession, Boolean isHTTP) at Microsoft.ReportingServices.XmlaClient.AdomdConnection.Open() at Microsoft.ReportingServices.DataExtensions.SapBw.SapBwCommand.ExecuteReader(CommandBehavior behavior) at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.RunDataSetQuery() --- End of inner exception stack trace --- at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.RunDataSetQuery() at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeReportParametersDataSetNode.FirstPassInit() at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.FirstPassProcess(Boolean& closeConnWhenFinish) at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeReportParametersDataSetNode.Process() at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.ProcessConcurrent(Object threadSet) ReportingServicesService!processing!4!23/03/2011-15:15:34:: v VERBOSE: An exception has occurred. Trying to abort processing. Details: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for data set 'BW_BIP'. ---> System.Threading.ThreadAbortException: Thread was being aborted. at System.Threading.WaitHandle.WaitOneNative(SafeWaitHandle waitHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext) at System.Threading.WaitHandle.WaitOne(Int64 timeout, Boolean exitContext) at System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean exitContext) at System.Net.LazyAsyncResult.WaitForCompletion(Boolean snap) at System.Net.Connection.SubmitRequest(HttpWebRequest request) at System.Net.ServicePoint.SubmitRequest(HttpWebRequest request, String connName) at System.Net.HttpWebRequest.SubmitRequest(ServicePoint servicePoint) at System.Net.HttpWebRequest.GetRequestStream() at Microsoft.ReportingServices.XmlaClient.HttpStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) at System.IO.StreamWriter.Flush() at System.Xml.XmlTextWriter.Flush() at Microsoft.ReportingServices.XmlaClient.XmlaClient.EndRequest() at Microsoft.ReportingServices.XmlaClient.XmlaClient.SendMessage(Boolean endReceivalIfException, Boolean readSession, Boolean readNamespaceCompatibility) at Microsoft.ReportingServices.XmlaClient.XmlaClient.Discover(String requestType, String requestNamespace, ListDictionary properties, IDictionary restrictions, Boolean sendNamespacesCompatibility) at Microsoft.ReportingServices.XmlaClient.XmlaClient.Discover(String requestType, ListDictionary properties, IDictionary restrictions, Boolean sendNamespacesCompatibility) at Microsoft.ReportingServices.XmlaClient.AdomdConnection.XmlaClientProvider.Microsoft.ReportingServices.XmlaClient.AdomdConnection.IXmlaClientProviderEx.Discover(String requestType, IDictionary restrictions, Boolean throwOnErrors, Boolean sendNamespaceCompatibility) at Microsoft.ReportingServices.XmlaClient.AdomdConnection.ReadDataSourceInfo() at Microsoft.ReportingServices.XmlaClient.AdomdConnection.ConnectToXMLA(Boolean createSession, Boolean isHTTP) at Microsoft.ReportingServices.XmlaClient.AdomdConnection.Open() at Microsoft.ReportingServices.DataExtensions.SapBw.SapBwCommand.ExecuteReader(CommandBehavior behavior) at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.RunDataSetQuery() --- End of inner exception stack trace --- at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.RunDataSetQuery() at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeReportDataSetNode.FirstPassInit() at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.FirstPassProcess(Boolean& closeConnWhenFinish) at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeReportDataSetNode.Process() at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.ProcessConcurrent(Object threadSet) ReportingServicesService!processing!4!23/03/2011-15:15:34:: i INFO: Some other thread has already aborted processing. ReportingServicesService!processing!3!23/03/2011-15:15:34:: i INFO: Merge abort handler called. Aborting data sources ... ReportingServicesService!processing!3!23/03/2011-15:15:34:: v VERBOSE: Data source 'BW_BIP': Abort handler called. CanAbort = True. ReportingServicesService!processing!3!23/03/2011-15:15:34:: v VERBOSE: Data set 'ParamWeeks': Cancelling command. ReportingServicesService!dataextension!3!23/03/2011-15:15:34:: w WARN: CommandWrapper.Cancel not called, connection is not valid ReportingServicesService!processing!4!23/03/2011-15:15:34:: v VERBOSE: Processing of data set 'BW_BIP' completed. ReportingServicesService!processing!3!23/03/2011-15:15:34:: v VERBOSE: Abort callback successful. ReportingServicesService!processing!4!23/03/2011-15:15:34:: e ERROR: Data source 'BW_BIP': An error has occurred. Details: System.Threading.ThreadAbortException: Thread was being aborted. at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.ProcessConcurrent(Object threadSet) at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.Process() ReportingServicesService!processing!3!23/03/2011-15:15:34:: v VERBOSE: Processing of data set 'ParamWeeks' completed. ReportingServicesService!processing!3!23/03/2011-15:15:34:: e ERROR: Data source 'BW_BIP': An error has occurred. Details: System.Threading.ThreadAbortException: Thread was being aborted. at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.ProcessConcurrent(Object threadSet) at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.Process() ReportingServicesService!library!f!03/23/2011-15:15:34:: e ERROR: Transaction rollback failed. Exception thrown: System.Data.SqlClient.SqlException: A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParserStateObject.WriteSni() at System.Data.SqlClient.TdsParserStateObject.WritePacket(Byte flushMode) at System.Data.SqlClient.TdsParser.TdsExecuteTransactionManagerRequest(Byte[] buffer, TransactionManagerRequestType request, String transactionName, TransactionManagerIsolationLevel isoLevel, Int32 timeout, SqlInternalTransaction transaction, TdsParserStateObject stateObj, Boolean isDelegateControlRequest) at System.Data.SqlClient.SqlInternalConnectionTds.ExecuteTransactionYukon(TransactionRequest transactionRequest, String transactionName, IsolationLevel iso, SqlInternalTransaction internalTransaction, Boolean isDelegateControlRequest) at System.Data.SqlClient.SqlInternalConnectionTds.ExecuteTransaction(TransactionRequest transactionRequest, String name, IsolationLevel iso, SqlInternalTransaction internalTransaction, Boolean isDelegateControlRequest) at System.Data.SqlClient.SqlInternalTransaction.Rollback() at System.Data.SqlClient.SqlTransaction.Rollback() at Microsoft.ReportingServices.Library.ConnectionManager.AbortTransaction() ReportingServicesService!library!f!03/23/2011-15:15:34:: 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.Data.SqlClient.SqlException: A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParserStateObject.WriteSni() at System.Data.SqlClient.TdsParserStateObject.WritePacket(Byte flushMode) at System.Data.SqlClient.TdsParser.TdsExecuteTransactionManagerRequest(Byte[] buffer, TransactionManagerRequestType request, String transactionName, TransactionManagerIsolationLevel isoLevel, Int32 timeout, SqlInternalTransaction transaction, TdsParserStateObject stateObj, Boolean isDelegateControlRequest) at System.Data.SqlClient.SqlInternalConnectionTds.ExecuteTransactionYukon(TransactionRequest transactionRequest, String transactionName, IsolationLevel iso, SqlInternalTransaction internalTransaction, Boolean isDelegateControlRequest) at System.Data.SqlClient.SqlInternalConnectionTds.ExecuteTransaction(TransactionRequest transactionRequest, String name, IsolationLevel iso, SqlInternalTransaction internalTransaction, Boolean isDelegateControlRequest) at System.Data.SqlClient.SqlInternalTransaction.Rollback() at System.Data.SqlClient.SqlTransaction.Rollback() at Microsoft.ReportingServices.Library.ConnectionManager.AbortTransaction() at Microsoft.ReportingServices.Library.SessionReportItem.ThreadNoLongerUseThisSession() at Microsoft.ReportingServices.Library.RSService.RenderAsLiveOrSnapshot(CatalogItemContext reportContext, ClientRequest session, Warning[]& warnings, ParameterInfoCollection& effectiveParameters) at Microsoft.ReportingServices.Library.RSService.RenderFirst(CatalogItemContext reportContext, ClientRequest session, Warning[]& warnings, ParameterInfoCollection& effectiveParameters, String[]& secondaryStreamNames) --- End of inner exception stack trace --- ReportingServicesService!runningjobs!f!03/23/2011-15:15:34:: v VERBOSE: ThreadJobContext.EndCancelableState ReportingServicesService!runningjobs!f!03/23/2011-15:15:34:: i INFO: CancelableJobExecution.Execute caught some other thread abort exception ReportingServicesService!library!f!03/23/2011-15:15:34:: i INFO: Initializing EnableExecutionLogging to 'True' as specified in Server system properties. ReportingServicesService!runningjobs!f!03/23/2011-15:15:34:: v VERBOSE: RunningJobList.RemoveJob: 5n4dvyrhxbdhmr55j25soc3y was removed ReportingServicesService!subscription!f!03/23/2011-15:15:34:: i INFO: System.Threading.ThreadAbortException: Thread was being aborted. at Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper() at Microsoft.ReportingServices.Library.RenderFirstCancelableStep.RenderFirst(RSService rs, CatalogItemContext reportContext, ClientRequest session, JobType type, Warning[]& warnings, ParameterInfoCollection& effectiveParameters, String[]& secondaryStreamNames) at Microsoft.ReportingServices.Library.ReportImpl.Render(String renderFormat, String deviceInfo) at Microsoft.ReportingServices.FileShareDeliveryProvider.FileShareProvider.SaveReport(Notification notification, SubscriptionData d) at Microsoft.ReportingServices.Delivery.ReportContentDelivery.ReportContentDeliveryProvider.Deliver(Notification notification) ReportingServicesService!library!f!03/23/2011-15:15:34:: Data Driven Notification for activation id 511fd803-80db-4fda-88c7-68d907adda41 was saved. ReportingServicesService!library!f!03/23/2011-15:15:34:: Status: Failure writing file All_Item_Sales_Ewan_Jones : Thread was being aborted. ReportingServicesService!library!f!03/23/2011-15:15:34:: Data Driven Notification for activation id 511fd803-80db-4fda-88c7-68d907adda41 was saved. ReportingServicesService!library!f!03/23/2011-15:15:34:: Status: Error: Thread was being aborted. ReportingServicesService!notification!f!03/23/2011-15:15:34:: Error thrown by delivery provider: System.Threading.ThreadAbortException: Thread was being aborted. at Microsoft.ReportingServices.Delivery.ReportContentDelivery.ReportContentDeliveryProvider.Deliver(Notification notification) at Microsoft.ReportingServices.Library.NotificationQueueWorker.HandleNotification(QueueItem item) ReportingServicesService!notification!f!03/23/2011-15:15:34:: e ERROR: Error occured processing notification. Thread was being aborted. ReportingServicesService!library!f!03/23/2011-15:15:34:: Data Driven Notification for activation id 511fd803-80db-4fda-88c7-68d907adda41 was saved. ReportingServicesService!library!f!03/23/2011-15:15:34:: Status: Thread was being aborted. ReportingServicesService!library!f!03/23/2011-15:15:34:: e ERROR: Queue item has unhandled exception. System.Threading.ThreadAbortException: Thread was being aborted. at Microsoft.ReportingServices.Library.NotificationQueueWorker.HandleNotification(QueueItem item) at Microsoft.ReportingServices.Library.NotificationQueueWorker.QueueWorker(QueueItem item) at Microsoft.ReportingServices.Library.QueuePollWorker.WorkItemStart(Object state) ReportingServicesService!library!f!03/23/2011-15:15:34:: v VERBOSE: Transaction begin. ReportingServicesService!processing!4!23/03/2011-15:15:34:: e ERROR: An exception has occurred in data source 'BW_BIP'. Details: System.Threading.ThreadAbortException: Thread was being aborted. at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.Process() at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSourceNode.ProcessConcurrent(Object threadSet) ReportingServicesService!processing!4!23/03/2011-15:15:34:: v VERBOSE: Processing of data source 'BW_BIP' completed. ReportingServicesService!processing!4!23/03/2011-15:15:34:: v VERBOSE: Thread completed. 0 thread remaining. ReportingServicesService!library!f!03/23/2011-15:15:34:: v VERBOSE: Transaction commit. ReportingServicesService!runningjobs!4!23/03/2011-15:15:34:: e ERROR: error in thread function: System.Threading.ThreadAbortException: Thread was being aborted. at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSourceNode.ProcessConcurrent(Object threadSet) at Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper() at Microsoft.ReportingServices.Diagnostics.ThreadWorkItem.SafeThreadPoolCallback(Object ctx) ReportingServicesService!library!f!03/23/2011-15:15:34:: v VERBOSE: Transaction begin. ReportingServicesService!notification!f!03/23/2011-15:15:34:: Notification a1e9f9ae-87b0-4f03-8ad0-4864e32898fa completed. Success: False, Status: Thread was being aborted., DeliveryExtension: Report Server FileShare, Report: Decision Support - Base - Retail - BW, Attempt 0 ReportingServicesService!library!f!03/23/2011-15:15:34:: v VERBOSE: Transaction commit. ReportingServicesService!dbpolling!f!03/23/2011-15:15:34:: i INFO: NotificationPolling finished processing item a1e9f9ae-87b0-4f03-8ad0-4864e32898fa ReportingServicesService!dbpolling!f!03/23/2011-15:15:34:: e ERROR: Queue worker thread caught unhandled exception: System.Threading.ThreadAbortException: Thread was being aborted. at Microsoft.ReportingServices.Library.QueuePollWorker.WorkItemStart(Object state) "

Hi WII, Thank you for your question. I am trying to involve someone familiar with this topic to a further look at this issue. There might be some time delay. Appreciate your patience. Thank you for your understanding and support. Thanks, Jerry

Hi Jerry, Thanks very much for your reply. I can nearly confirm that this is not a problem of reporting services. Though I don't understand it fully, just a quick hint for the people who might run into the similar problem as mine, check the settings on BW side. I can't tell exactly which setting to check due to lack of BW administration knowledge, but it's definitely because the query request sent by the second subscription was rejected by BW due to some reason. But the reporting services does not receive that message, and because the Timeout value for data driven subscription is -1, the thread for the second subscription is just hanging around until it's explicitly killed. If you are not able to see the error message generated on BW side to find out the root cause, like me, my workaround is to use different BW credentials for concurrent RS subscriptions. This is not perfect, but working. Thanks again, WII