Hi Ben,

I can see you already have opened a case with Technical Support on this issue and the investigation is in progress.

Can you please verify that you are using a 'sa' account or an account with similar permissions to access the SQL Server via the MobiControl installer?

Please let me know if you have any questions.

Thanks

Yes I have the sa account. I have been onto a number of people from Soti technical support but still in the same place. I have been advised to create a new VM with the same OS and SQL version and restore a back of the database so I am just waiting for Soti to come back to me to do the upgrade now.

Thanks

Hi Ben,

Please let us know if this issue is resolved for you? 

Thanks

The upgrade didn't work as such on the architecture that we had. We needed to upgrade to SQL Server 2014 and so we built a new server with Windows Server 2016 and upgrade the database before we could upgrade to 13.4

Which we now have done so we are working and I guess this can be closed.

What you said is really interesting.   According to the official MobiControl documentation, MS-SQL 2016 is not officially supported for MobiControl v13.x.   I really don't know what level of testings have v13.x been done with this SQL version.   Hope you have already got official assurance and commitment from Soti support/professional service team that your approach is fine and supported.

Sorry, I do apologize, I got mixed up. I have amended the above post now.

SQL Server 2014

Windows Server 2016 

We know about 2016 not being fully supported but we went with it anyway. 

Hi Ben,

What versions are you getting the error between?

As the error you are receiving is being generated after the DB is backed up try doing your backup manually and unchecking this in the installer in the advance section before committing to begin the upgrade.

Also, the actual error is indicating an error with sp_rename on line 140, without access to your version of the DB I cannot confirm what that line contains but I have used a clever workaround before for issues such as these and that is to upgrade to an in between version when you are following the upgrade path.  Assuming your issue isn't that you are not following the upgrade path in the first place?? 

For example follow the upgrade path here but when you get to the last version that is upgrading successfully upgrade to a version before the one you are erroring out on.   This may help to update the procedure in question with the correct information/format and then upgrade to the version you were having difficulty upgrading to.

Hopefully you have a successful upgrade after this.

Cheers,