SIM and Initial ProLiant Support Pack Install

[Doug Wogan]

I'm getting the error "could not execute the tool: Initial ProLiant Support Pack Install. No value was supplied for required argument with promt: Enter drive letter for setupc.exe"

Any ideas? This is a bit different from the SupportPack install in IM7.

[Jadrice Toussaint]

Daug -

This is a known issue that HP is aware of. A way around this is to just schedule the job to run at alter time (meaning) a minute or two later. This workaround worked for me pretty well during my testing.

Let me know how you make out.

[Jadrice Toussaint]

Oh by the way, make sure you have openssh installed on the remote machine that you are trying to dispatch the management agents to.

[Rob Buxton]

In the softpaq, Setupc.exe is the command line version of the deployment tool and expects parameters to be passed, setup.exe runs the Remote Deployment GUI.

[Doug Wogan]

I've tried the work-around of scheduling and get the error

"EXCEPTION CLASS: com.hp.mx.exceptions.MxFailedAuthenticationException
EXCEPTION: Authentication failed."

I know it's not from the userid and password I'm providing. Does it have anything to do with having openssh installed on the remote client?

[David Claypool]

Correcting one misconception...

OpenSSH needs to be installed and running only on the hpSIM central management server (CMS), NOT on the remote device.

hpSIM calls 'setupc' on the CMS through SSH and passes the remote node's name, login and password to it. 'setupc' then executes against that remote station using Windows security, not through SSH.

[Doug Wogan]

That's a relief. I was afraid I was going to have to go back to IM7. I wasn't about to go install openSSH to all my clients. I do still have the issue of "EXCEPTION CLASS: com.hp.mx.exceptions.MxFailedAuthenticationException
EXCEPTION: Authentication failed."
Any thoughts? I've tried both local admin accounts and domain admin accounts. I also re-exported the certificate from the CIM server and copied it back into the Support Pack configuration settings.

[David Claypool]

Your exception error indicates that the hpSIM application was not able to authenticate to OpenSSH.

Did you follow the post-install instructions regarding OpenSSH in the hpSIM release notes?

[Doug Wogan]

Of course I did! (not really) So I ran through the ssh setup to no avail. I think it's worse now. Not one of the commands givin in the instructions for setup worked. I tried "type passwd" from the etc dir and it fails. (cannot find the file specified) There is no passwd file. I tried the mkpasswd command and nothing happens. When I use the -l switch for a local account it tells me I need to specify a domain account when using the -d switch. When I use the -d switch it tells me nothing at all and the passwd file is not created in the etc dir. I tried reinstalling openSSH and have the same problem. Please don't make me go back to IM7! I just tore it down so I could use SIM!

[Jadrice Toussaint]

My apologies on the the openssh client install. David is correct, you do not need openssh installed on each client.

[Jadrice Toussaint]

Quick question for you, aer you running this on windows 2003 by any chance?

[Doug Wogan]

Yes. 2003 Advanced server on a DL360G1 w/ SQL 2000 Ent.

[Jadrice Toussaint]

ah ok I'ev attached an article to fix your openssh issue. Read it and follow the instructions.

Let me know how you make out.

[Doug Wogan]

I just went through the steps. When trying to restart the openssh service I get the following error in the system log..

Event ID 7000 The OpenSSH Server service failed to start due to the following error:
OpenSSH Server is not a valid Win32 application.

[Jadrice Toussaint]

did you delete the log file in \program files\OpenSSH\var\log ?

[Doug Wogan]

Yes I did. I've also rebuilt the server from scratch. I'll fight with it one more day and if it still doesn't work I'll go back to IM7. Do you guys have any more "work around" documents? This is truley frustrating.
Doug.

[Jadrice Toussaint]

Doug -

Don't give up on SIM, It is truely a superior product to IM7 once setup properly. I'll do my very best here to help you out.

[Doug Wogan]

Too late. I need a working system. Maybe once all the bugs are worked out I'll try again. We're going back to IM7. Thanks for all your time.
Doug.

[Juan Mares]

/*

EDIT

*/

[David Claypool]

The previous posting has been superseded by the document "Secure Shell (SSH) in HP Systems Insight Manager" from http://www.hp.com/servers/manage --> HP SIM --> Information Library

See Appendix A: Troubleshooting.

[Russell Teague]

I too am having the same error with com.hp.mx.exceptions.MxFailedAuthenticationException when trying to deploy Support Packs. I've gone through the troubleshooting guides listed here and am still having trouble getting OpenSSH configured properly. I downloaded HP SIM 4.1 the first week of September and ran the full install on Windows 2003 Server with all patches current to date. Hardware is an ML530. Any additional assistance getting this running would be greatly appreciated. Thanks.

[Chad Taggart]

Do you have the Openssh service starting under local system or the same acocunt that was used to install SIM?

To set this up you need to read the "SSH in HP SIM" white paper, appendix A Pg16 - regarding 2003. Even though i am running SIM on windows 2000 i had to complete this process for it to work.

[COOPERCAV]

I have been pulling my hair out with the same problems. I get the setupc.exe error if I run manually or MxFailedAuthenticationException errors in the scheduled task log if I schedule a task. I am running W2K with SIM, OpenSSH, Version Repository Manager etc all on this same server. I have tried the WS2K3 services workaround anyway but can seem to create a connection. If I try to connect via the GUI MXAGENTCONFIG I get 'could not connect to server'. I have also tried the netstat tool suggested, however, I get the same MxFailedAuthenticationException error. I can deploy the Proliant Support pack remotely manually without a problem and the updates are downloading fine so I really want to complete the circle. I do have an administrator account so named, but I have also looked at the proliant-msa-tools.xml file but can't see where to make the change(s). Thanks.

[COOPERCAV]

I have had some good fortune. Having removed SIM4.0, SSH and VCRM etc etc, I did a clean install of SIM4.1 and all of the above apps on the same server as before. Strange thing was this time the repository was not populated despite selecting 2 PSP's. This was not a problems before and also the VCRM did not show up in the servers managment page. I therefore installed VCRM and SSH on 2 seperate servers. The first failed to populate the repository folder but did show the VCRM in the servers managment page. The second did populate this directory as well so I selected this from SIM and sucessfully deployed my first PSP (at last). I cannot say conclusively why it is now working but it seems very hit and miss but maybe down to having VCRM and SSH on a seperate server (same server should be simpler you would think). Anyway, its working now and to be honest I've spend to much time already to try to pin the problem/cause down any further. Fingers crossed. Ta all.

[Thorsten Schmitt]

Hi,

I have got the same problem and error.
I already tried the suggested solutions, but nothing helps.
Maybe it might be a problem, that our local "administrator" acount is renamed.???

When I try to execute a initial Support Pack install via setupc.exe it works fine. But when I execute the task in the website i get the same error.
Is there already a solution in between?

My SIM version 4.2 is installed on a new Windows 2003 DL 360 G3 with SQL 2000. I've created 2 local useraccounts with admin rights, one for the openSSH service and one for the rest of sim. But as mentioned, "the adminsitrator" does not exist.

Thanks for hints
Regards
Thorsten