Question : Error in Data Driven Subscription

We are encountering errors on SQL Server Reporting Services.  To make sure that the reports are rendered fast, we have taken advantage of SQL Server's data-driven subscription facility.  However, running the subscriptions always resulted to deadlock errors.  Please see sample below:

ReportingServicesService!­library!24!09/02/2008-14:41:­21:: 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: Transaction (Process ID 190) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
   at System.Data.SqlClient.­SqlConnection.OnError(­SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.­TdsParser.­ThrowExceptionAndWarning(­TdsParserStateObject stateObj)
   at System.Data.SqlClient.­TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.­SqlCommand.­FinishExecuteReader(­SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.­SqlCommand.­RunExecuteReaderTds(­CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.­SqlCommand.RunExecuteReader(­CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.­SqlCommand.­InternalExecuteNonQuery(­DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.­SqlCommand.ExecuteNonQuery()
   at Microsoft.ReportingServices.­Library.­InstrumentedSqlCommand.­ExecuteNonQuery()
   at Microsoft.ReportingServices.­Library.DBInterface.­AddReportToExecutionCache(Guid reportId, ReportSnapshot snapshotData, DateTime executionDateTime, DateTime& expirationDateTime)
   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 ---

We have seen this similar case on the web and the solution suggested was to change the RS Configuration file setting for maxqueuethreads = 1 instead of 0.   (http://www.sqlmonster.com/Uwe/Forum.aspx/sql-server-reporting/4622/bug-data-driven-subscription-generates-deadlock-in)

When we changed to 1, the errors disappeared but it also have disallowed us to do any sort of parallel processing of the subscription affecting service levels. Is there a way to get around this problem?  Is this a bug as suggested in the link? Please help asap.

Answer : Error in Data Driven Subscription

This has been declared by Microsoft as a bug.