Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Looking For In-Place Upgrade Steps From Microsoft

(0) ShareShare
ReportReport
Posted on by

Rough description of what I'm trying now:

1. Uninstall 2015 email router and reporting extensions.

2. Disable 2015 Org in 2015 Deployment Manager.

3. Install 2016 reporting extensions

4. Open 2016 install media and install 2016 but don't click "upgrade organization" there as it errors out (my DB doesn't have _MSCRM after it) so I just click don't setup an organization at this time.

5. From the 2016 deployment manager I right click my Org and do "upgrade".

Upgrade fails after five or so minutes with:

08:11:44|  Error| Installer Complete: OrganizationUpgrader - Error encountered
08:11:44|  Error| Exception occured during Microsoft.Crm.Tools.Admin.OrganizationUpgrader: Error.ActionFailed Microsoft.Crm.Tools.Admin.UpgradeDatabaseAction
InnerException:
System.Data.SqlClient.SqlException (0x80131904): Database '_15to16IPMT' does not exist. Make sure that the name is entered correctly.
   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.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, 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.Crm.Setup.Database.DatabaseUtility.ExecuteSqlCommands(String sql, IDbCommand cmd)
   at Microsoft.Crm.Setup.Database.DatabaseUtility.ExecuteSql(InstallDatabase database, String sql, Int32 timeout, Boolean disablePool)
   at Microsoft.Crm.Setup.Database.SqlScriptAction.Execute(DatabaseUtility dbUtility)
   at Microsoft.Crm.Setup.Database.DatabaseInstaller.ExecuteReleases(ReleaseInfo releaseInfo, Boolean isInstall)
   at Microsoft.Crm.Setup.Database.DatabaseInstaller.Install(Int32 languageCode, String configurationFilePath, Boolean upgradeDatabase, Boolean isInstall)
   at Microsoft.Crm.Setup.Database.DatabaseInstaller.Install(Int32 languageCode, String configurationFilePath, Boolean upgradeDatabase)
   at Microsoft.Crm.Tools.Admin.InstallDatabaseAction.Do(IDictionary parameters)
   at Microsoft.Crm.Setup.Shared.CrmAction.ExecuteAction(CrmAction action, IDictionary parameters, Boolean undo)
ClientConnectionId:2f52db46-19a4-48cc-a28a-e5d89210679d
Error Number:911,State:1,Class:16

I could understand if I got something like that right away, but it seems to do the upgrade for 5-10 minutes before saying the db does not exist. It is odd that it is adding an underscore before the name, as in SQL it is just called 15to16IPMT

*This post is locked for comments

  • Verified answer
    RE: Looking For In-Place Upgrade Steps From Microsoft

    Wow Microsoft. The fix is to not have a numeral begin your CRM database's name. 15to16crm will fail on migrations or updates while crm15to16 will not...having a numeral in the front causes part of the CRM upgrade to add an underscore to the beginning of your SQL database's name.

  • RE: Looking For In-Place Upgrade Steps From Microsoft

    What's odd is this same db/org has been backed up, restored to a different server with its own sql instance, db restored to that database without a _MSCRM and it upgraded fine! Not sure what it is about an in-place upgrade that it doesn't like.

    Deleted it in Org Manager, renamed it in SQL to have _MSCRM, reimported it in Deployment Manager (2015) which worked. Grabbed the 2016 installer, told it to update during the installation but that failed at basically the exact same part

    10:00:08|Verbose| Processing custom entity exp_invitation
    10:00:08|Verbose| EntitySetName updated successfully.
    10:00:08|Verbose| EntitySetNames are succesfully updated for all custom entities
    10:00:11|Verbose| DatabaseAction execution time; Bin\Microsoft.Crm.SE.DatabaseActions.dll:Execute; 00:00:03.2968884
    10:00:11|   Info| Set Database Compatibility Level
    10:00:11|Verbose| DatabaseAction execution time; Bin\Microsoft.Crm.Setup.DiffBuilder.dll:SetDatabaseCompatibilityLevel; 00:00:00.1874966
    10:00:11|   Info| Drop the PostVegaComponents table.
    10:00:11|   Info| Did not detect single user -- not clearing pool
    10:00:11|Verbose| DatabaseAction execution time; Scripts\Drop_PostVegaComponents.sql; 00:00:00.0156230
    10:00:11|   Info| Add the SystemApplicationMetadataChild table
    10:00:11|   Info| Did not detect single user -- not clearing pool
    10:00:11|Verbose| DatabaseAction execution time; Scripts\DBUpdate_SystemApplicationMetadataChild.sql; 00:00:00.0156345
    10:00:11|   Info|
            Upgrading database version stamp
          
    10:00:11|   Info| CrmAction execution time; UpgradeDatabaseAction; 00:07:55.2822146
    10:00:11|  Error| Installer Complete: OrganizationUpgrader - Error encountered
    10:00:11|  Error| Exception occured during Microsoft.Crm.Tools.Admin.OrganizationUpgrader: Action Microsoft.Crm.Tools.Admin.UpgradeDatabaseAction failed.
    InnerException:
    System.Data.SqlClient.SqlException (0x80131904): Database '_15to16IPMT_MSCRM' does not exist. Make sure that the name is entered correctly.
       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.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, 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.Crm.Setup.Database.DatabaseUtility.ExecuteSqlCommands(String sql, IDbCommand cmd)
       at Microsoft.Crm.Setup.Database.DatabaseUtility.ExecuteSql(InstallDatabase database, String sql, Int32 timeout, Boolean disablePool)
       at Microsoft.Crm.Setup.Database.SqlScriptAction.Execute(DatabaseUtility dbUtility)
       at Microsoft.Crm.Setup.Database.DatabaseInstaller.ExecuteReleases(ReleaseInfo releaseInfo, Boolean isInstall)
       at Microsoft.Crm.Setup.Database.DatabaseInstaller.Install(Int32 languageCode, String configurationFilePath, Boolean upgradeDatabase, Boolean isInstall)
       at Microsoft.Crm.Setup.Database.DatabaseInstaller.Install(Int32 languageCode, String configurationFilePath, Boolean upgradeDatabase)
       at Microsoft.Crm.Tools.Admin.InstallDatabaseAction.Do(IDictionary parameters)
       at Microsoft.Crm.Setup.Shared.CrmAction.ExecuteAction(CrmAction action, IDictionary parameters, Boolean undo)
    ClientConnectionId:a3d44aa7-28d4-47a3-a319-4033a022e1f3
    Error Number:911,State:1,Class:16

     

    edit: Andreas Cieslik, sorry didn't mention those were the ones I was already looking at. They are a bit general and was hoping to find something more specific if MS had exact steps for an in-place upgrade.

  • Andreas Cieslik Profile Picture
    Andreas Cieslik 9,267 on at
    RE: Looking For In-Place Upgrade Steps From Microsoft

    Here is a guide but may not be complete:

    technet.microsoft.com/.../hh699716.aspx

    and this:

    blogs.msdn.microsoft.com/.../dynamics-crm-2016-upgrade-complete-guide

  • David Jennaway Profile Picture
    David Jennaway 14,063 on at
    RE: Looking For In-Place Upgrade Steps From Microsoft

    As a guess, part of the upgrade process may not be coping without the _MSCRM suffix on the database name. I suggest you rename the database so that it has an _MSCRM suffix, then run the upgrade. Given the current state, you could:

    • Delete the org in Deployment Manager
    • In SQL Management Studio, rename the database
    • Import the org in Deployment Manager. This should also upgrade the org during the import

    If you need to then remove the _MSCRM suffix, you could repeat the steps to rename it back, though if the above works, I'd be strongly tempted to keep the _MSCRM suffix in case this issue is still relevant for future versions

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Daivat Vartak – Community Spotlight

We are honored to recognize Daivat Vartak as our March 2025 Community…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Kudos to the February Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,516 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,430 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans