Issue

The Snow Update Service fails logging a timeout error:

2017-03-13 19:17:53,076 [InstallationWorker] ERROR SnowSoftware.Update.ProductUpdate [(null)] - An error occurred while executing instructions of v 8.0.09 for Snow License Manager Service Provider Edition (UR# 291). Beginning rollback. 2017-03-13 19:17:53,076 [InstallationWorker] ERROR SnowSoftware.Update.ProductUpdate [(null)] - The exception was: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. 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.RunExecuteNonQueryTds(String methodName, Boolean async) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at SnowSoftware.Update.Installation.UpdateDatabaseInstruction.ExecuteStatement(String statement) at SnowSoftware.Update.Installation.UpdateDatabaseInstruction.ExecuteSqlFromFile(String filePath, Encoding encoding) at SnowSoftware.Update.Installation.UpdateDatabaseInstruction.Execute(ProductUpdate update) at SnowSoftware.Update.ProductUpdate.Install() 2017-03-13 19:17:53,076 [InstallationWorker] DEBUG SnowSoftware.Update.Installation.UpdateDatabaseInstruction [(null)] - Beginning rollback of

Environment

This problem happens when running the update service for Snow License Manager

Resolution

There are two ways to get around this problem:

• Change the timeout setting in SQL server so the script can run for a long time without timeouts.
• Run the sql script part directly in sql management studio prior to running the update service.

Cause 

The environments effected by this problem tend to be large. The problem is because the sql script in that's part of the update takes longer than the timeout setting in SQL server permits for external query's.