on 04-16-2007 10:40 AM
Hi Friends,
I have installed the Netweaver Full ABAP Preview edition in a WinXP system and trying to setup CCMS locally. Currently I don't see any data under the Alert Monitor(RZ20). I just see the tree elements but no monitors under them. What do I need to do to get data in the tree. Below are some of the steps that I have tried after reading some documentation
1. Created CSMREG user
2. Created CSMCONF file
3. Tried to register the CCMS agent by executing sapccmsr.exe -R. But after I provide the password for CSMREG user the process quits with the below error
ERROR: Registration failed: Can't get version of NSP.C_CALL_FAILED. RFC Error Info for SALS_MS_GET_LOCAL_MS_INFO
Even tried with the command sapccmsr.exe -R pf=<path to the profile file> but it quits at once with the error Cannot open Monioting Segment 99 MoniSegmentSize too small
I believe the Netweaver Preview edition has all the CCMS agent installed.
Can someone please help me with setting up the Alert Monitor.
Regards,
Jagannath
Hi Jagannath,
So I take it the Windows platform is 32-bit ?
Gary
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Everyone,
Let me just briefly explain what I have done so far so that you can give me some more suggestions on how to configure the alert monitor
1. Installed a NetWeaver 2004s ABAP Trial version from SDN download page on a Windows XP 32-bit system
2. Activated Background and Central System Dispatching.
RZ21>Technical Infrastructure>Local Method Execution-->Activate Background Dispatching
RZ21>Technical Infrastructure>Configure Central System-->Activate Central System Dispatching
3. Created the CSMREG user
4. Created CSMCONF Start File
5. Created 2 RFC destinations for data collection and analysis. Not sure if this step is needed as mine is just a single system.
6. Trying to register CCMS Agent SAPCCM4X.
Copied the CSMCONF to SYSID/<inst dir>/log/sapccm4x directory
Executing sapccm4x -R pf=<profile path>
Here is where I get the error as mentioned in my previous post.
Is there something else I need to do.
Regards,
Jagannath
Hello Jagannath,
after your summary I'm not sure what wxactly you want to do...
> 5. Created 2 RFC destinations for data collection and
> analysis. Not sure if this step is needed as mine is
> just a single system.
> 6. Trying to register CCMS Agent SAPCCM4X.
IMHO "just a single system" is the main point. You will not be able to realize central autoreaction with a single system! the RFC connections are not neccessary because The the CCMS should be activated locally, i.e. a single system is already able to monitor itself. Therefore you also won't be able to register the sapccm4x because the agent cannot be registered against the system it is monitoring.
So the main point should be: why you don't see any data in rz20? I know two possible reasons for this:
1. parameter alert/MONI_SEGM_SIZE is set to 0. This would cause the CCMS shared memory not to be created.
2. parameter rdisp/autoabaptime is set to 0. This would cause the data collectors not to be started and the monitoring objects not to be created.
Regards, Michael
Hello Jagannath,
you're welcome.
Indeed you won't have to change any of the mentioned settings on a "real" system, it will run out of the box (except for the background and central dispatching jobs). I suppose the monitoring was switched off in the test drive to keep the system slim.
Regards, Michael
Hello Michael,
We got a similar problem trying to register the sapccmsr agent with the -J2EE option in a double-stack installation. We want to display and monitor data from the J2EE Engine in the CCMS monitoring system of the ABAP part.
I executed the following command:
sapccmsr -r -j2ee -f /usr/sap/tmp/csmconf pf=/usr/sap/<SID>/SYS/profile/<SID>_DVEBMGS<nn>_<host>
I found the following error in the sapccmsr.install.log file:
...
ERROR: Cannot open Monitoring Segment 20 rtc = 245
Last reported error: [249] CCMS monitoring segment has wrong EYE CATCH. It seems to be created as unicode segment.
This program runs as non-unicode. Please use unicode version
-
sapccmsr and dispwork are NON-UNICODE since the ABAP is non-unicode, and the Java stack is unicode. In your reply posted on Apr 19, 2007 2:52 PM you say "Please ensure that sapccm4x and dispwork of the instance to be monitored are the same version..."
My question is: Is it possible to monitor the J2EE Engine in a non-unicode central CCMS monitoring system?
Thanks.
Hugo
Hello Hugo,
we have to differ between
a) the monitored system/instance (this is where the agent is running)
b) the monitoring system (CEN, where the agent is registered to).
Agent and monitored system/instance should be the same (Unicode/Non-Unicode), i.e. in your case you should use the Unicode sapccmsr. You can really believe the error message
The 'unicodeness' of the CEN doesn't matter. Both Unicode and Non-Unicode agents can be registered against the CEN.
Regards, Michael
Hi Jagannath,
Issue commands <b>sapccm4x -v</b> and <b>disp_work -v</b> and compare the results as below:
sapccm4x -v
CCMS version 20040229, <b>64 bit</b>, multithreaded, <b>Unicode</b>
compiled at Nov 11 2006
systemid 370 (Solaris on SPARCV9 CPU)
relno 6400
patch text patch collection 2006/5, OSS note 914721
patchno 157
intno 20020600
running on hcip2 SunOS 5.9 Generic_118558-10 sun4u
disp+work -v|more
-
disp+work information
-
kernel release 640
kernel make variant 640_REL
DBMS client library OCI_920
DBSL shared library version 640.00
compiled on SunOS 5.8 Generic_108528-16 sun4u
compiled for <b>64 BIT</b>
compilation mode <b>UNICODE</b>
compile time Aug 21 2005 21:06:33
update level 0
patch number 87
source id 0.087
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Gary,
Here's mine
C:\SAP\NSP\SYS\exe\run>sapccm4x.exe -v
CCMS version 20040229, 32 bit, multithreaded, Non-Unicode
compiled at Jul 12 2006
systemid 560 (PC with Windows NT)
relno 7000
patch text patch collection 2006/3, OSS note 914721
patchno 68
intno 20050900
running on APP-XP3 Windows NT 5.1 2600 Service Pack 2 Intel 801586 (Mod
2 Step 4)
C:\SAP\NSP\SYS\exe\run>"disp+work.exe" -v|more
-
disp+work information
-
kernel release 700
kernel make variant 700_COR
DBMS client library
compiled on NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10
compilation mode Non-Unicode
compile time Jul 12 2006 23:00:08
update level 0
patch number 68
source id 0.068
-
supported environment
-
database (SAP, table SVERS) 700
operating system
Windows NT 5.0
Windows NT 5.1
Windows NT 5.2
Regards,
Jagannath
Hi,
The message "CCMS monitoring segment has wrong EYE CATCH" occurs when the agent version doesn't match the SAP system version. Please check if both are 32 bit or 64 bit versions and both are unicode or non-unicode. A non-unicode agent cannot connect to a unicode system, for example. I had this same problem and resolved it by matching the versions of sapccm4x.
Gary
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am using the Netweaver 2004s ABAP Trial version and I am using a license file generated from minisap. If I view the System-->Status from the SAP GUI I see that the expiration date is 1/7/07. So the license is applied properly.
By profile file do you mean the text file present under <SAPHome>/SID/SYS/profile directory. Can you please tell me the exact steps to check.
Regards,
Jagannath
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Gary, Michael,
Thanks for your response.
As I have mentioned before I am using the Netweaver 2004s ABAP Trial version as it is. That is I am using everything that is bundled in the software and have not installed anything separately. This includes the CCMS agents too. So I believe the version incompatibility should not be there.
Anyway, based on your response I verified that both the SAP instance and CCMS agent are non-unicode. For CCMS agent version I executed sapccm4x.exe -v. For SAP version I am seeing System-->Status from the SAP GUI. Can you let me know what values to compare.
Regards,
Jagannath
Hi,
Below is the message that fills most of the dev_w0 log. Do I need to check for any specific message
ERROR => likey_check_product_no_limit: The license key library has not been initialized yet. [sliclikey.c 1269]
Also I only need to configure the Alert Monitor locally that is just one system and no central system. What are the steps to do this.
Regards,
Jagannath
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Mantosh,
Since I am very new to SAP can you please explain in a bit more detail what you mean. Sorry. Which process do I need to start. I have started sapccmsr.exe using sapccmsr.exe -DCCMS
Rajat,
Please let me know where I can find that log
Regards,
Jagannath
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Paste the dev_w0 trace of a work process.It would be helpfull to arrive to a solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
You need to activate the backgroud process First.
Try registering id through visual admin. under monitoring service for dispatcher. and try registering it using CSMREG user.
try and scroll what error do you get.
REgards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
10 | |
9 | |
9 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.