Anyone come across exceptions like these before? It's currently causing significant issues in a v7 project that is having a new API added to it to support a mobile application.
2020-02-12 10:51:14,498 [7] ERROR Umbraco.Core.Persistence.UmbracoDatabase - Exception (d7efd9fe).
System.Data.SqlClient.SqlException (0x80131904): New request is not allowed to start because it should come with valid transaction descriptor.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at Umbraco.Core.Persistence.PetaPocoCommandExtensions.<>c__DisplayClass5_0.<ExecuteReaderWithRetry>b__0()
at Umbraco.Core.Persistence.FaultHandling.RetryPolicy.ExecuteAction[TResult](Func`1 func)
at Umbraco.Core.Persistence.Database.<Query>d__74`1.MoveNext()
at System.Linq.Enumerable.SingleOrDefault[TSource](IEnumerable`1 source)
at UmbracoAuthTokens.Data.UserAuthTokenDbHelper.GetAuthToken(Int32 identityId, String deviceId) in UmbracoAuthTokenDbHelper.cs:line 19
at UmbracoAuthTokens.Data.UserAuthTokenDbHelper.IsTokenValid(UmbracoAuthRefreshTokenWithDeviceId authToken) in UmbracoAuthTokenDbHelper.cs:line 104
at JWTAuthTokenAttribute.Authenticate(HttpRequestMessage request) in JWTAuthTokenAttribute.cs:line 86
at JWTAuthTokenAttribute.OnActionExecuting(HttpActionContext actionContext) in JWTAuthTokenAttribute.cs:line 28
New request is not allowed to start because it should come with valid transaction descriptor
Anyone come across exceptions like these before? It's currently causing significant issues in a v7 project that is having a new API added to it to support a mobile application.
is working on a reply...