Cloud Migration Assistant for Confluence - Error accessing table metadata

[Ilya Petrov]

When I start migration assistant, ServerBaseURL/admin/migration.action, I get "Oops - an error has occurred"
The text that appears several times next after the "Cause": Error accessing table metadata

We are using MSSQL 2014, and there is no table named "metadata" in the "confluence" database.

We have checked searched result for the text "Error accessing table metadata" - it tells that uppercase letters is database name "Confluence" can be the possible cause  - but that is not our case, we have a lowercase "confluence" either as database name or in file "confluence.cfg.xml"

Should we create new table named "metadata"? Do we need add some columns and lines to this table?

Do we need to update environment first? Windows Server 2003? x86 to x64? jre1.8.0_121 to some later java? Confluence 5.10.8 to some lates version? MSSQL 2014? Any ideas?

[Alexis Robert · Accepted solution]

Hi @Ilya Petrov , 

Confluence 5.10 is quite an old version - I would suggest (if possible for you) to upgrade to at least Confluence 7.4 or 7.13 as these are Long Term version, and better supported.

I have myself done a few migration with the assistant, using Confluence and MS SQL Server and never had an issue like the one you described.

Did you also make sure that the migration assistant was updated to the latest version ? 

Let me know if this helps, 

--Alexis

[Ilya Petrov]

Migration Assistant version 3.2.4 and does not show "update" button, so I suppose its the latest.

As for Confluence Server, it is expired, but I can get trial key to upgrade it, right? And it will consume significant time to upgrade, since Confluence 6 and 7 are x64-only, so I guess we need to upgrade Windows Server first. I was hoping we could skip this step and migrate directly from 5.10.8 - Migration Assistant says it is compatible with Confluence starting with 5.10.

[Ilya Petrov]

At first I tried to udpate 5.10 to 6.6 (to the nearest LTS) - but failed, because I cannot get Confluence Server trial key, and Confluence data center trial key did not work with Confluence server.

Then I tried to set up Confluence Server 7.4 (using trial key for Confluence Data Center) - update did not show any errors, but pages showed no information about users - just "Unknown User", perhaps 7.4 works with LDAP in some different way, not similar to 5.10.

Since we were going to do Cloud migration without Access, we have to replace LDAP users with users in Internal directory anyway. I hoped that migration assistant will help me with users somehow, but as I see that user information lost during the upgrade (not the migration) I decided to move users into internal directory manually, before upgrading.

So I restored 5.10, re-created users in internal directory (using login names matching the old ones from LDAP), turned off LDAP, and then upgraded to 7.4. Success! There were some "Anonymous" user records for users who were deleted from LDAP, we are ok with that.

The final step, Cloud migration from 7.4, turned out surprisingly easy: assistant showed a warning about 10 users limit for Free plan - but less than 10 were active, no problem. Cloud migration successful!