SqlException after upgrade

Just upgraded to the latest. Now every time we run a build, we get the following exception:

System.Data.SqlClient.SqlException: Transaction (Process ID 54) 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 Inedo.Data.DatabaseFactory.Inedo.Data.IDatabaseExecuter.ExecuteNonQuery(String storedProcName, DbParameter[] parameters)
at Inedo.Data.WrappedStoredProcedure.ExecuteNonQuery()
at Inedo.BuildMaster.Windows.ServiceApplication.SlimPlanActionExecuter.Action_LogReceived(Object sender, LogReceivedEventArgs e)

Stack trace:

at System.Environment.get_StackTrace()
at Inedo.BuildMaster.Diagnostics.Logger.DatabaseErrorMessenger.Inedo.BuildMaster.Diagnostics.IMessenger.Message(MessageLevels messageLevel, String messageOrFormat, Object[] args)
at Inedo.BuildMaster.Diagnostics.Logger.Message(MessageLevels messageLevel, String messageOrFormat, Object[] args)
at Inedo.BuildMaster.Windows.ServiceApplication.SlimPlanActionExecuter.Action_LogReceived(Object sender, LogReceivedEventArgs e)
at Inedo.BuildMaster.Extensibility.Actions.ActionBase.OnLogReceived(LogReceivedEventArgs e)
at Inedo.BuildMaster.Extensibility.Actions.ActionBase.Log(MessageLevels logLevel, String message)
at Inedo.BuildMaster.Extensibility.Actions.CommandLineActionBase.LogProcessOutputData(String data)
at Inedo.BuildMaster.Extensibility.Agents.Local.LocalAgent.StandardProcess.OnOutputDataReceived(ProcessDataReceivedEventArgs e)
at System.Diagnostics.AsyncStreamReader.FlushMessageQueue()
at System.Diagnostics.AsyncStreamReader.GetLinesFromStringBuilder()
at System.Diagnostics.AsyncStreamReader.ReadBuffer(IAsyncResult ar)
at System.Runtime.Remoting.Messaging.AsyncResult.SyncProcessMessage(IMessage msg)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
at System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.ThreadPoolCallBack(Object o)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)

Hi Chris,

Can you go into Admin > Advanced Configuration, set "UseSlimPlanExecuter" to "False", restart the service, and try again?

Chris -- another thing to try, I just emailed you a SQL Script patch that may help. We will be putting this patch in BuildMaster 3.5.4 as well.

Neither had any affect.

Wait, I lied. Setting the flag did have an affect. I didn't restart the service.

We're at a bit of a loss at debugging, and have had no issues w/ this in our testing.

Could you try one other thing -- set the flag back to True, then restart service again, and try again?

We're wondering if it has nothing to do with the PlanExecutor used at all, and more to do with a state the service was in...

One other question... how big is your BuildMaster Error Log? Admin > View Errors that have occured

So, i just upgraded to your latest build and set that flag back. No errors showed up. As far as the size of the error log. I regularly clear it out if there is anything. This error showed up once for every build.

Well, I guess it wasn't meant to be. I just ran a build and that error came back. I set that flag back to false, ran another build and the error went away.