1 Reply Latest reply on Aug 29, 2016 1:42 AM by sandstrand

    IPAM moved to another server, problems...

    sandstrand

      While waiting for support, maybe someone here can help...

      Tried moving IPAM from an old server to a new. Installed IPAM with the same version on the new server.  The old server had ip address x.x.9.99 and the new x.x.9.199.  Changed ip on the old to x.x.9.198 and change ip on the new to x.x.9.99.

      The hostnames where also changed, so that the new server was given the same hostname as the old and the old was given a new name.  The old server is no longer in production.

      So the only server up and running now is the new IPAM server. This has the same hostname and ip address as the old one.

      Deactivated the license on the old and activated it on the new.  The database is running on a another databaseserver, running MSSQL.

      Installed the new server and ran config wizzard.  Staring the config wizzard again shows first:

      "Please ensure the primary Orion server is updated first and all the services on the primary Orion are running before continuing.

      Detected engines:

      IPAM001 (x.x.9.99)

      IPAM-PROD-001 (x.x.9.99)

      IPAM002 (x.x.9.198)

      "

      IPAM001 and x.x.9.99 was the old hostname and ip address, and has been given to the new server.  The new server had ipam-prod-001 before hostname was changed.

      IPAM002 was the old server running IPAM.

      When config wizzard is almost finished I get:

      Website configuration failed:

      •  •  Connection to SolarWinds® Information Service did not succeed.

      Last error: The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:01:00'.

       

      What can I do to fix this?

       

      Geir