topic Windows 2003 Command fails with exit code 255 in Server Management - Systems Insight Manager

Windows 2003 Command fails with exit code 255

Michael Sheehan — Wed, 07 Apr 2004 13:00:33 GMT

I'm trying to run a custom command (I've tried everything from simply bat files that create a local dir to the integrated windows 'dir') - all exit as sucessful with a code of 255. I even wrote a simple bat that did nothing but exit with a code of 10 - it still reported it ran 'sucessfully' with a code of 255. They are not sucessful. Nothing has ever happened, it is quite obvious they are not running.

I've reproduced on 3 different servers (DL380G3, DL360G2, BL20PG2).

I've logged into the ssh server:
ssh administrator@servername
and all looks good.

I've run mxagentconfig -a -u -p and it registers sucessfully.

I'm running under the same account (administrator) that installed SIM. I've tried various configs with SQL or the MSDE - all the same.

Any help is greatly appreciated.
Thanks,
Mike

Re: Windows 2003 Command fails with exit code 255

David Claypool — Wed, 07 Apr 2004 15:02:35 GMT

To be clear, if you have created this with the 'Custom Commands' menu options, the only place this is executing is on the hpSIM central management server (CMS) itself. The effect of naming one or more non-CMS targets is to get the task to iterate for each target while substituting the name of the target into the DEVICENAME variable.

mxagentconfig distributes keys to instances of SSH; as your target is not being used to run anything, this has no effect. If OpenSSH on the CMS was not properly trusted (hopefully you followed the directions in the README) then you would be getting

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

SQL Server/MSDE have nothing to do with this functionality.

Do any of the out-of-box supplied custom commands work, like

Tools --> Command Line Tools --> Windows --> netstat

work properly when executed against the CMS? What if your .bat file contained the statement

echo test >c:\test

...would it write the file (evidence that it is executing)?

Re: Windows 2003 Command fails with exit code 255

Michael Sheehan — Thu, 08 Apr 2004 07:43:50 GMT

All of the commands (dir, netstat) exit with 255 and no stdout or stderr.

test.bat has consisted of various commands:

exit 10
or
md test
or
echo >test.txt

Overall, I've had LOTS of problems with the installation. I'm running about 6 instances right now (windows 2000 / windows 2003), most of which have been formatted 3 or 4 times. I've found (reproducible) that uninstalling and reinstalling causes problems when creating the database (after uninstalling everything including SQL/MSDE).

Is there some DB configuration I need to do?

All servers were built with RDP 1.50 / SS7.0

-Mike