Forum Discussion

Laura's avatar
Laura
Level 3
7 years ago

Server Migration Wizard not responding

I am moving from EV11.0.1 to EV12.3 (and from Server 2008R2 to Server 2016).

Export from the source worked fine. Copied all files from source to target.

Started the server migration wizard on the target server. Import to the target server completely stalls out after DNS resolution check has passed and I press the "Next" button to proceed. The DNS resolution screen is still showing and the application says "Not Responding" and task manager shows that there's absolutely nothing going on with it. The "Back", "Cancel" and "Help" buttons are active, but don't respond. The log file shows that the last thing done was to successfully create two DSNs.

I waited for as long as an hour just to make sure that I wasn't prematurely pulling the plug.

Any ideas what might be happening?

Thanks,

Laura.

  • GertjanA's avatar
    GertjanA
    7 years ago

    Hello Laura,

    I'm not sure it is in a document somewhere, but in a production environment you should definitely not run SQL and EV on the same server. I have no idea on what to look for next. I'm even not sure a logfile is created during runtime of the wizard. Perhaps logging can be enabled, or perhaps even dtrace has an option to log from the wizard, I don't know.

    To be sure, you are using the 12.3 migration wizard right?

    https://www.veritas.com/support/en_US/article.100038733.html

    You might want to check in with support, to see if they can assist somehow.

  • Laura's avatar
    Laura
    7 years ago

    Just popped in to let everyone know what the issue was -- because I was also testing moving to a new SQL Server, I had moved the database files from the source machine. To do this, I needed to stop the SQL services.

    I used Sysinternals Process Monitor to find out that when the wizard was totally stalled, it was looking to communicate with the old SQL Server via a named pipe. By simply starting the SQL services on the old SQL server, the wizard proceeded forward.

    Simple thing, but it might be a gotcha that someone else runs across.

  • VirgilDobos's avatar
    VirgilDobos
    Moderator
    7 years ago

    Hi Laura,

    Have you checked if you can communicate with the SQL server on the configured port?

    • Laura's avatar
      Laura
      Level 3
      7 years ago

      Hi Virgil -

      I can connect with SQL Management Studio from the server itself (EV and SQL Server are on the same server).

      I can also, from a remote computer, connect via ODBC (using port 1433) with the enterprise vault admin user, which is the user ID being used for the server migration.

      Are there other SQL connectivity tests that I should attempt?

      Thanks,

      Laura.

      • GertjanA's avatar
        GertjanA
        Moderator
        7 years ago

        Hello Laura,

        I hope this is a test environment :-). EV and SQL are not supported on the same server in production...

        On your new server, I assume you have run the Deployment Scanner. If you did, did you have any issues reported? Did you check SQL permissions? It might be the wizard is competing with SQL for resources and it takes ages before it can complete. Did you leave it running overnight?

        I'm not sure you can reboot the server, and restart, but if it is a test environment, that would be my next try. Make sure after restart that all necessary services (especially SQL) are indeed started.