Problem with CHECK_SAP_CONS

[Novak, Mark]

Hello Everyone,
 
I am trying to make the SAP CCMS plugins work with my systems.  I have
successfully installed and configured ./check_sap.sh, and it works fine.
 
When setting up check_sap_cons, I set up an agent.cfg and login.cfg in
/etc/sapmon.  For the login.cfg, I used my userid and password (SAP_ALL
and SAP_NEW).
 
When I execute "./check_sap_cons 00 SM1", I receive the following error:
 
<==  RfcLastError
 
FUNCTION: SXMI_LOGON
RFC operation/code SYSTEM_FAILURE
ERROR/EXCEPTION
key     :
status  :
message : Name or password is incorrect (repeat logon)
internal:
 
<==  RfcClose
 
I have googled for this error and checked the newsgroups. I followed
Wolfgang Barth's excellent book for the setup.
 
I am not sure why I would get an incorrect username/password error.  I
can log in fine through SAPGUI with the same username/password combo.
 
Any and all assistance is much appreciated!
 
agent.cfg ->
[TEMPLATE_00]
DESCRIPTION=Dialog response time
MONI_SET_NAME=SAP CCMS Monitor Templates
MONI_NAME=DIALOG Overview
PATTERN_0=*
 
login.cfg ->
[LOGIN_SM1]
LOGIN=-d SM1 -u user -p password -c 001 -h myhostname -s 00
 
Command that I am running ->
./check_sap_cons 00 SM1
 
 
Thanks,
 

Mark Novak
EDS SAP Practice
Office: 972-605-2817
Cell:    214-725-5295
Email: mark.novak at eds.com 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20080518/0235d946/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null