Uploaded image for project: 'Migration Platform'
  1. Migration Platform
  2. MIG-829

Confluence Cloud Migration Assistant versions 3.2.4 and 3.2.5 are not running on MSSQL database

    XMLWordPrintable

Details

    • 43
    • Severity 2 - Major

    Description

      Issue Summary

      When trying to open Confluence Cloud Migration Assistant versions 3.2.4 and 3.2.5 running a MSSQL database, it throws the following error stack:

      Cause
      
      org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getInitialState' in class com.atlassian.migration.agent.web.AppAction threw exception com.atlassian.util.concurrent.LazyReference$InitializationException: org.hibernate.exception.GenericJDBCException: Error accessing table metadata at /templates/app.vm[line 21, column 44]
      at org.apache.velocity.runtime.parser.node.ASTIdentifier.execute(ASTIdentifier.java:223)
      
      caused by: com.atlassian.util.concurrent.LazyReference$InitializationException: org.hibernate.exception.GenericJDBCException: Error accessing table metadata
      at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:149)
      
      caused by: org.hibernate.exception.GenericJDBCException: Error accessing table metadata
      at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:47)
      
      caused by: java.sql.SQLException: The database name component of the object qualifier must be the name of the current database.
      at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:372)
      

      Users who have followed below document and confirmed that the DB name is the same as in SQL still run into the same problem:

      "The component of the database name of the object qualifier must be the name of the current database" error on upgrade to Confluence 6.1+

      Steps to Reproduce

      1. Install Confluence Cloud Migration Assistant 3.2.4 or higher on a Confluence running MSSQL.
      2. Open Confluence Cloud Migration Assistant
      3. It will throw the error above.

      Expected Results

      Confluence Cloud Migration Assistant should be running.

      Actual Results

      Confluence Cloud Migration Assistant errors out and cannot be executed.

      Workaround

      Revert back to Confluence Cloud Migration Assistant 3.2.3:

      1. Uninstall previous version of Confluence Cloud Migration Assistant.
      2. Go to <confluence-base-url>/admin/darkfeatures.action
      3. Add the following dark feature:
        migration-assistant.disable.app-outdated-check
      4. Download the Jar file for version 3.2.3 on your workstation by browsing to the following URL:
        https://marketplace.atlassian.com/download/apps/1219672/version/300100311
        
      5. Navigate to General Configuration > Manage apps
      6. Choose Upload app
      7. Locate the file then click Upload
      8. Try to migrate again using Confluence Cloud Migration Assistant
        • If you see a "We can't communicate with your server" message after installing the older CCMA JAR, you may need to restart Confluence to reload the CCMA JAR

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              52216d0810b0 Felipe Zanettini (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              27 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: