- Community Home
- >
- Networking
- >
- IMC
- >
- DMA Slave cannot connect to Master after 7.3 upgra...
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
тАО02-13-2017 09:41 AM
тАО02-13-2017 09:41 AM
Hello,
I have started to upgrade my IMC environment (1 Master and 1 Slave) on 7.3
As recommend I have downloaded and installed all modules with 7.3 compatible versions.
The upgrade on the Master (IMC-Plat and NTA) went well. However on the Salve side when I start the DMA it automatically download the COMMON services from the master and silently shutdown without any Warning or Error.
The dma logfile (which is attached) says "Can not find the JRE included with the installation disk" !!! and suggest to perform the upgrade manually using:
[C:\Program Files\iMC\deploy\jdk\bin\javaw.exe, -Xmx256m, -cp, C:\Program Files\iMC\deploy\components\common\deploy\deploy.jar, com.h3c.imc.deploy.CommonComponentUpdateLauncher, autoStart]
When I do it I'm getting a PopUp window saying that it could not fing the main class (see attached file; sorry for the rendering quality:|).
I'm not familiar at all with JAVA, but it looks like a PATH is missing or a VARIABLE not defined somewhere.
Has someone alread gone through this, or suggest any clue to troubleshoot it further.
Thanks
Ray
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-02-2017 02:55 AM
тАО03-02-2017 02:55 AM
Re: DMA Slave cannot connect to Master after 7.3 upgrade
Hello Ray - i have had the same problem - this was my solution:
On the slave - have a look into : windows/IMC-Reserved/log -> there should be a file like this: update_xxxxxxxxxxxx.txt which is the logfile of your latest installation. xxxxxxxx means Date and time . Open the file -> do you see such like this:
2017-03-01 10:14:27 [ERROR] [main] [com.h3c.imc.deploy.CommonComponentUpdateLauncher::checkEnv(140)] Can not find file: F:\Program Files\iMC\deploy\components\common\deploy\jdk_windows64.zip
If this is your message - then do the following:
Go to: $imc-install -drive/Programm Files/iMC/deploy/components/common/deploy
In this directory - search for a zip file - jdk_windows.zip -> rename this file into jdk_windows64.zip
Now your deploymemt on the slave should work well.
HTH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2017 04:24 AM
тАО03-04-2017 04:24 AM
SolutionThank you for this detailled information. IMC has so many log files that I was not aware the Windows\IMC-Reserved\log.
Nevertheless I have scanned all the files in there and could not find the error you described.
As I was on time pressure I was ready to sacrify the slave server and reconfigure it (it is a test system after all).
So after lot of sweat and some increase in my blood pressure I have run the installslave script from the IMC installation directory.
Fortunatelly the script has detected there was already an installation and has started the upgrade process (miracles sometimes still happen) and the upgrade finally completed.
Caution: IMC has tried to kill me a second time when it asked me for the "sa" password that I have never provided in my first installation !!!
Thanks to a very usefull blog I have tried "iMC-Install2008" and it worked...
So the problem is solved, but I never knew the root cause.