I'm trying to upgrade my website from 8.17 to v9.
Everything is going rather smoothly (got 95% up and running), except for an annoying issue.
I have my local enviroment running in IIS and connected to the database server on Azure, this is the same database server as my live enviroment. (I know, not ideal, but for now its ok ;-))
But every ~ 3,5-4 minutes, i'm getting an error whilst developing that the connection is lost resulting in the below error.
Added clarification: The entire application stops working, and the JIT debugger from visualstudio triggers returning this error. The entire application stops and I need to restart it..
I'm currently a bit out of options as to what this issue is..
System.Data.SqlClient.SqlException
HResult=0x80131904
Message=Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
The statement has been terminated.
Source=Core .Net SqlClient Data Provider
StackTrace:
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action1 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.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource 1 completion, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite, String methodName)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at StackExchange.Profiling.Data.ProfiledDbCommand.ExecuteNonQuery() in C:\projects\dotnet\src\MiniProfiler.Shared\Data\ProfiledDbCommand.cs:line 300
at Umbraco.Cms.Infrastructure.Persistence.FaultHandling.FaultHandlingDbCommand.
Inner Exception 1:
Win32Exception: The wait operation timed out.
I dont think that would resolve the issue. That would indicate a certain query is running so long it would reach the timeout, and also trigger an entire application shutdown?
When I check the Azure logs, there are no long-running queries, or any reason this should happen, i'll add this to the main post.
To be honest it seems like the profiler is generating the error:
System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource 1 completion, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite, String methodName) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at StackExchange.Profiling.Data.ProfiledDbCommand.ExecuteNonQuery() in C:\projects\dotnet\src\MiniProfiler.Shared\Data\ProfiledDbCommand.cs:line 300 at
Umbraco.Cms.Infrastructure.Persistence.FaultHandling.FaultHandlingDbCommand.
I could be wrong but it seems like a long running query is exceeding the database timeout period.
Well I checked using profiler, and only on the startup there's an initial load of about 40seconds (which is normal as it builds the project and stuff.. every other page is around 50ms only.
Checked Azure for long queries, the longest was 0.8 second long.. So that wouldn't be it either..
Couldnt find a solution, so in the end I used Usync content edition to migrate all my content from the V8 to a clean V9 database, and it worked like a charm!
Database timeout error
I'm trying to upgrade my website from 8.17 to v9. Everything is going rather smoothly (got 95% up and running), except for an annoying issue.
I have my local enviroment running in IIS and connected to the database server on Azure, this is the same database server as my live enviroment. (I know, not ideal, but for now its ok ;-))
But every ~ 3,5-4 minutes, i'm getting an error whilst developing that the connection is lost resulting in the below error.
Added clarification: The entire application stops working, and the JIT debugger from visualstudio triggers returning this error. The entire application stops and I need to restart it..
I'm currently a bit out of options as to what this issue is..
Inner Exception 1: Win32Exception: The wait operation timed out.
You could try increase the timeout on the connection string:
Hope this helps
I dont think that would resolve the issue. That would indicate a certain query is running so long it would reach the timeout, and also trigger an entire application shutdown?
When I check the Azure logs, there are no long-running queries, or any reason this should happen, i'll add this to the main post.
Maybe try and use profiler to see what's going on:
https://our.umbraco.com/Documentation/Fundamentals/Code/Debugging/
To be honest it seems like the profiler is generating the error:
I could be wrong but it seems like a long running query is exceeding the database timeout period.
Well I checked using profiler, and only on the startup there's an initial load of about 40seconds (which is normal as it builds the project and stuff.. every other page is around 50ms only.
Checked Azure for long queries, the longest was 0.8 second long.. So that wouldn't be it either..
The error message suggests that the error comes from this line:
https://github.com/MiniProfiler/dotnet/blob/745fae4457e1429f907927aed9dcf1b9cb536d8e/src/MiniProfiler.Shared/Data/ProfiledDbCommand.cs#L300
Not sure why.
Couldnt find a solution, so in the end I used Usync content edition to migrate all my content from the V8 to a clean V9 database, and it worked like a charm!
Glad it's done :-)
is working on a reply...