U4-10680 - Umbraco Migration not working properly with reference of previous Ticket -U4-10679

Created by Chetan Khule 14 Nov 2017, 09:57:37 Updated by Sebastiaan Janssen 14 Nov 2017, 10:20:31

Duplicates: U4-7339

As mentioned in reply from yours side that Error text is not visible properly so please find below error description which we faced while umbraco-Migration.

Error Description: The database failed to upgrade .ERROR: The database configuration failed with following message :Invalid object name'umbracoMigration'. Please check log file for additional information (can be found in 'App_Data/Logs/UmbracoTraceLog.txt').

I am sharing log file content as below: 2017-11-10 09:39:17,359 [P10312/D2/T1] ERROR Umbraco.Core.Persistence.UmbracoDatabase - Database exception occurred System.Data.SqlClient.SqlException (0x80131904): Invalid object name 'umbracoMigration'. 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.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) 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)

1 Attachments

Comments

Sebastiaan Janssen 14 Nov 2017, 10:20:07

You've updated the version in your web.config to the newer version, reset it to the old version (the one you're upgrading from) and you should be fine.


Priority: Normal

Type: Bug

State: Duplicate

Assignee:

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions:

Due in version:

Sprint:

Story Points:

Cycle: