Symptoms
When you install Microsoft SQL Server 2014 with default preferences, the language property is English (United States) us_english, and the default order for date is mdy. If the date order of the operating system differs from this, when you set up Managed Backup to Windows Azure, you receive the following error messages after backup is complete:
Error:
Note
SqlError, Code = 242, Stage = Undefined, Message = The conversion of a varchar data type to a datetime data type resulted in an out-of-range value. The statement has been terminated.
Stack:
Note
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.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.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.SqlServer.SmartAdmin.SmartBackupAgent.FileService.InsertOneRowForHelperTable(SmartBackupFilesTableRow row, SqlConnection conn, Boolean& isDuplicate)
at Microsoft.SqlServer.SmartAdmin.SmartBackupAgent.FileService.GetLastLSNAndInsertToHelperTable(System.String, System.String, System.Guid, System.Nullable`1<System.Guid>, System.String, System.Nullable`1<System.Decimal> ByRef, System.Nullable`1<System.Decimal> ByRef, System.Nullable`1<System.Guid> ByRef, System.Nullable`1<System.Decimal> ByRef)
at Microsoft.SqlServer.SmartAdmin.SmartBackupAgent.SmartBackup.DoJobOutcomeVerification(Microsoft.SqlServer.SmartAdmin.SmartBackupAgent.AutoBackupDBData)
at Microsoft.SqlServer.SmartAdmin.SmartBackupAgent.SmartBackup.DoWork()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at System.Threading.ThreadHelper.ThreadStart()
Resolution
This issue was first fixed in the following cumulative update of SQL Server.
Cumulative Update 5 for SQL Server 2014 /en-us/help/3011055
About cumulative updates for SQL Server
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.