- Community Home
- >
- Networking
- >
- IMC
- >
- Re: iMC PLAT 7.3 (E0605P06) enviroment tab not wor...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2021 03:34 AM - last edited on тАО08-25-2021 05:53 AM by support_s
тАО08-25-2021 03:34 AM - last edited on тАО08-25-2021 05:53 AM by support_s
Hello!
After deploy updates iMC PLAT 7.3 (E0605P06) is working good, but the enviroment of monitorimg agent is not working. And backup/restore DB function not working too.
In dbman_debug.log of iMC and msSQL servers have not errors.
In logs:
c:\Program Files\iMC\deploy\log\dmalog.txt
2021-08-25 12:24:21 [INFO ] [iMC-Database-Connect-Check] [com.h3c.imc.deploy.dma.monitor.DatabaseConnectMonitor::run(84)] DatabaseConfig{type=SQLServer, address=10.0.0.14, port=1436, name=aclm_db, userName=imc_aclm, password=, instanceName=sql2k8}
2021-08-25 12:24:21 [INFO ] [iMC-Database-Connect-Check] [com.h3c.imc.deploy.dma.monitor.DatabaseConnectMonitor::run(84)] DatabaseConfig{type=SQLServer, address=10.0.0.14, port=1436, name=config_db, userName=imc_config, password=, instanceName=sql2k8}
2021-08-25 12:24:21 [INFO ] [iMC-Database-Connect-Check] [com.h3c.imc.deploy.dma.monitor.DatabaseConnectMonitor::run(84)] DatabaseConfig{type=SQLServer, address=10.0.0.14, port=1436, name=icc_db, userName=imc_icc, password=, instanceName=sql2k8}
2021-08-25 12:24:21 [INFO ] [iMC-Database-Connect-Check] [com.h3c.imc.deploy.dma.monitor.DatabaseConnectMonitor::run(84)] DatabaseConfig{type=SQLServer, address=10.0.0.14, port=1436, name=invent_db, userName=imc_inventory, password=, instanceName=sql2k8}
2021-08-25 12:24:21 [INFO ] [iMC-Database-Connect-Check] [com.h3c.imc.deploy.dma.monitor.DatabaseConnectMonitor::run(84)] DatabaseConfig{type=SQLServer, address=10.0.0.14, port=1436, name=monitor_db, userName=imc_monitor, password=, instanceName=sql2k8}
2021-08-25 12:24:21 [INFO ] [iMC-Database-Connect-Check] [com.h3c.imc.deploy.dma.monitor.DatabaseConnectMonitor::run(84)] DatabaseConfig{type=SQLServer, address=10.0.0.14, port=1436, name=perf_db, userName=imc_perf, password=, instanceName=sql2k8}
2021-08-25 12:24:21 [INFO ] [iMC-Database-Connect-Check] [com.h3c.imc.deploy.dma.monitor.DatabaseConnectMonitor::run(84)] DatabaseConfig{type=SQLServer, address=10.0.0.14, port=1436, name=reportplat_db, userName=reportplat, password=, instanceName=sql2k8}
2021-08-25 12:24:21 [INFO ] [iMC-Database-Connect-Check] [com.h3c.imc.deploy.dma.monitor.DatabaseConnectMonitor::run(84)] DatabaseConfig{type=SQLServer, address=10.0.0.14, port=1436, name=report_db, userName=report, password=, instanceName=sql2k8}
2021-08-25 12:24:21 [INFO ] [iMC-Database-Connect-Check] [com.h3c.imc.deploy.dma.monitor.DatabaseConnectMonitor::run(84)] DatabaseConfig{type=SQLServer, address=10.0.0.14, port=1436, name=syslog_db, userName=imc_syslog, password=, instanceName=sql2k8}
2021-08-25 12:24:21 [INFO ] [iMC-Database-Connect-Check] [com.h3c.imc.deploy.dma.monitor.DatabaseConnectMonitor::run(84)] DatabaseConfig{type=SQLServer, address=10.0.0.14, port=1436, name=vlanm_db, userName=vlan, password=, instanceName=sql2k8}
2021-08-25 12:24:21 [INFO ] [iMC-Database-Connect-Check] [com.h3c.imc.deploy.dma.monitor.DatabaseConnectMonitor::run(84)] DatabaseConfig{type=SQLServer, address=10.0.0.14, port=1436, name=vnm_db, userName=imc_vnm, password=, instanceName=sql2k8}
2021-08-25 12:24:21 [INFO ] [iMC-Database-Connect-Check] [com.h3c.imc.deploy.dma.monitor.DatabaseConnectMonitor::run(86)] checkDatabaseVersion
2021-08-25 12:24:36 [ERROR] [iMC-Database-Connect-Check] [com.h3c.imc.deploy.dma.monitor.DatabaseConnectMonitor::run(86)] Connect to database error
com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host 169.254.0.14, port 1436 has failed. Error: "Network is unreachable: 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.".
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:190)
at com.microsoft.sqlserver.jdbc.SQLServerException.ConvertConnectExceptionToSQLServerException(SQLServerException.java:241)
at com.microsoft.sqlserver.jdbc.SocketFinder.findSocket(IOBuffer.java:2243)
at com.microsoft.sqlserver.jdbc.TDSChannel.open(IOBuffer.java:491)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:1309)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:991)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:827)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:1012)
at java.sql.DriverManager.getConnection(DriverManager.java:582)
at java.sql.DriverManager.getConnection(DriverManager.java:154)
at com.h3c.imc.deploy.dma.monitor.DatabaseConnectMonitor.run(DatabaseConnectMonitor.java:86)
2021-08-25 12:54:06 [INFO ] [iMC-Stack-Trace-Printer] [com.h3c.imc.deploy.StackTracePrinter::run(43)] thread id: 32, name: Thread-11, TIMED_WAITING
java.lang.Thread.sleep(Native Method)
The TCP/IP connection to the host 169.254.0.14, port 1436 has failed.
169.254.0.14 - is old ip address of mssql server, it whose renamed to 10.0.0.14 many years ago...
Searching in configuration files do not have result...
Search text "169.254.0.14" in all files on drive c: not give result. The string is finded in older log files
May be in database saved it old connection string?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2021 05:01 AM
тАО08-25-2021 05:01 AM
Re: iMC PLAT 7.3 (E0605P06) enviroment tab not working
Hello,
DB address is stored in server.addr.xml file , path: -:\Program Files\iMC\common\conf.
Do you mean this heppened after installing Windows updates or you upgraded the iMC server with another iMC version?
You can use the osql command to check the connection to db server from iMC server cmd . This is osql -S (ip aaddress of the db server) -U sa -P (password for sa user).
Kind regards,
I work for HPE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2021 05:06 AM
тАО08-25-2021 05:06 AM
SolutionHello,
There are two files you can check for the old IP address, which would need adjusting manually if the DB IP changes:
* iMC\common\conf\server-addr.xml - which is used by the processes to locate the DB (among other things) when starting up
* Windows\iMC-Reserved\instinfo.txt - which is encrypted and contains important details about the iMC installation like 'sa' username and password for the DB... this is probably what is causing your issue.
instinfo.txt cannot be read or modified directly. You will need to open an Admin CMD prompt on the server, navigate to iMC\deploy folder, and then run the instInfoMgr.bat -query command to check the DB address stored in this file. If it's incorrect, you can modify it with -modify option instead, like instInfoMgr.bat -modify dbAddr=10.0.0.14 which will set the address to the new one you are using. Remember to restart iMC afterwards for the change to take effect.
Justin
Working @ HPE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2021 05:45 AM
тАО08-25-2021 05:45 AM
Re: iMC PLAT 7.3 (E0605P06) enviroment tab not working
In configuration files, as is server-addr.xml ip addres is correct 10.0.0.14
Used the instInfoMgr.bat - is resolve my problem! Thx you!
c:\Program Files\iMC\deploy>instInfoMgr.bat -query
Database Address : 169.254.0.14
Database Admin Username : hpimc
Database Admin Password : user
Database Port : 1436
Database Instance Name : sql2k8
c:\Program Files\iMC\deploy>instInfoMgr.bat -modify dbAddr=10.0.0.14
The following is the properties modification information, Press 'Enter' to confirm!
dbAddr : 10.0.0.14
Change install info successfully!Please restart Intelligent Management Server and iMC.
c:\Program Files\iMC\deploy>instInfoMgr.bat -query
Database Address : 10.0.0.14
Database Admin Username : user
Database Admin Password :
Database Port : 1436
Database Instance Name : sql2k8
Run backup and database backed up succesfully!
Next step need for migrate msSQL and Windows server form 2008 to 2016.
I have IMC Windows Migration Guide.pdf ))