one our client which they are using CA SDM 12.7 on windows server 2012 R2. Now want to Migrate 12.7 to 17.1. While we migrating 17.1 but getting some error.
following screen shot & logs file
Good Morning Dinesh.
Please check on the log file you attached for the lines with 'ERROR'.
And you'll find the possible cause of the error?
Should you not manage to resolve this, then I want to advise on the following: Please check on the following, somewhat formal kind of statement:This 'Community' functionality is meant for relatively simple questions&(quick)answers for CA Service Catalog.Looking into this one, it seems/appears that a 'quick answer' can not be made available within this community thread.More likely, 'investigation' and/or 'debugging' is needed to find a possible cause and solution for this.Therefor I need to ask you to consider to open a 'standard' case.Through which you can get 'standard' and 'full-service' follow-up by our Support Teams. Thanks in advance for your understanding and kind regards, Louis.
These error are serious
2018/08/08 184.108.40.206 INFO [AWT-EventQueue-0] [DatabasePersister] Unable to obtain Database Connection for user : mdbadmin May be a fresh installation.The TCP/IP connection to the host URJA-9323-SDM, port 1433 has failed. Error: "Connection refused: connect. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.".
2018/08/08 220.127.116.113 ERROR [AWT-EventQueue-0] [ConfigureSQLServer] The TCP/IP connection to the hostcom.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host URJA-9323-SDM, port 1433 has failed. Error: "Connection refused: connect. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.".
On sql database server side, verify you have "SQL Server Browser" service running and "UDP port 1434" open
Check the basics, as the SQL error message suggests. Can you connect to the SQL host with 'sqlcmd' from the command line on the new SDM host, using the credentials that you have been given for 'sa' (or equivalent login with SA authority)? If not, then is the new MDB listening on port 1433? If it's on a non-default (named) instance it will not be on 1433 and you must get a fixed port configured. Get that sorted and things should start to work.
Are you still having difficulties with the SDM upgrade to 17.1?