Messaging server down

Dear Sun, our office messaging server down without reason, webmail able to send mail to internal and external user, but unable to receive the mail, all the mail all jam at our office email gateway. After we restart the server and services, the problem is solved temporary only, after a while the email gateway unable to relay to messaging server again. How can i found out the root cause? thanks

elson.vhliu wrote:
Dear Sun, our office messaging server down without reason, webmail able to send mail to internal and external user, but unable to receive the mail, all the mail all jam at our office email gateway.It doesn't sounds like Messaging Server is "down" at all.
Are there any errors reported at the "office email gateway" end to indicate why emails are not being accepted by the Sun Messaging Server MTA?
Do you see any errors in the Sun MTA mail.log_current file?
Are you sure that all email is "jammed" at the office email gateway -- as opposed to just being processed slowly?
Also if this is a really urgent issue then you should be logging a Sun support request. The forums are not the appropriate place to rely on timely assistance.
Regards,
Shane.

Similar Messages

Http service of message Server offten core down?

our company buy the jes sysytem , when i use it . i find a error that make http service of message server often core down these days, i want to know the reason. here is the environment and the error message:
Sun Java(tm) System Messaging Server 6.1 (built Apr 28 2004)
libimta.so 6.1 (built 12:38:06, Apr 28 2004)
SunOS staff-jes1.sina.com.cn 5.9 Generic_117172-07 i86pc i386 i86pc
error message is:
Assertion failed: U_SUCCESS(err), file mee.c, line 1700

httpd problem seems to go away now. It's been up for two days without crashing.
But I got to tell you, applying patch on JES is not easy if you have customized webmail interface. And If you have multiple customized webmail interface, it's a lot of work. Mind you we only have 3 customized domains. The patch does not apply to those so you have to do it manually for each customized domains. Maybe I missed something, please tell me.
Sun should change the current implementation customized domains. For ISP like us planning to put 5000 domains on JES, that means 5000 links or directories on /opt/SUNWmsgsr/config/html to provide customized interface for each one. Again. maybe there is a different way that I don't know.

I am getting the error "We're sorry we cannot complete your request on the iTunes store at this time. Please try again later." on both my iPhone and iTunes on my computer. What is wrong with iTunes? Is the server down???

I am getting the error "We're sorry we cannot complete your request on the iTunes store at this time. Please try again later." on both my iPhone and iTunes on my computer. What is wrong with iTunes? Is the server down or what? I need to download some things and update some apps...

I've been getting the same message for like an hour now. Since everything was working fine a few hours ago, and nothing changed on my end before it stopped working, I'm guessing it's something on Apple's end. They probably already know about it by now, and are hopefully working on fixing it, so there's probably not much we can do but wait for them to fix it.

Dispatcher running but not connected to message server :( please help .

trc file: "dev_disp", trc level: 1, release: "700"
sysno 00
sid DEV
systemid 562 (PC with Windows NT)
relno 7000
patchlevel 0
patchno 144
intno 20050900
make: multithreaded, Unicode, 64 bit, optimized
pid 3744
Mon Oct 26 12:37:38 2009
kernel runs with dp version 232000(ext=109000) (@(#) DPLIB-INT-VERSION-232000-UC)
length of sys_adm_ext is 576 bytes
SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (00 3744) [dpxxdisp.c 1243]
 shared lib "dw_xml.dll" version 144 successfully loaded
 shared lib "dw_xtc.dll" version 144 successfully loaded
 shared lib "dw_stl.dll" version 144 successfully loaded
 shared lib "dw_gui.dll" version 144 successfully loaded
 shared lib "dw_mdm.dll" version 144 successfully loaded
rdisp/softcancel_sequence : -> 0,5,-1
use internal message server connection to port 3900
Mon Oct 26 12:37:50 2009
WARNING => DpNetCheck: NiHostToAddr(www.doesnotexist0211.qqq.nxst) took 12 seconds
Mon Oct 26 12:38:06 2009
WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 16 seconds
***LOG GZZ=> 2 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 5371]
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
DpIPCInit2: start server >noptqas_DEV_00 <
DpShMCreate: sizeof(wp_adm) 25168 (1480)
DpShMCreate: sizeof(tm_adm) 5652128 (28120)
DpShMCreate: sizeof(wp_ca_adm) 24000 (80)
DpShMCreate: sizeof(appc_ca_adm) 8000 (80)
DpCommTableSize: max/headSize/ftSize/tableSize=500/16/552064/552080
DpShMCreate: sizeof(comm_adm) 552080 (1088)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
DpShMCreate: sizeof(slock_adm) 0 (104)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm) 0 (72)
DpShMCreate: sizeof(vmc_adm) 0 (1864)
DpShMCreate: sizeof(wall_adm) (41664/36752/64/192)
DpShMCreate: sizeof(gw_adm) 48
DpShMCreate: SHM_DP_ADM_KEY (addr: 000000000EE70050, size: 6348592)
DpShMCreate: allocated sys_adm at 000000000EE70050
DpShMCreate: allocated wp_adm at 000000000EE72150
DpShMCreate: allocated tm_adm_list at 000000000EE783A0
DpShMCreate: allocated tm_adm at 000000000EE78400
DpShMCreate: allocated wp_ca_adm at 000000000F3DC2A0
DpShMCreate: allocated appc_ca_adm at 000000000F3E2060
DpShMCreate: allocated comm_adm at 000000000F3E3FA0
DpShMCreate: system runs without slock table
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 000000000F46AC30
DpShMCreate: allocated gw_adm at 000000000F46ACB0
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 000000000F46ACE0
DpShMCreate: allocated wall_adm at 000000000F46ACF0
MBUF state OFF
DpCommInitTable: init table for 500 entries
ThTaskStatus: rdisp/reset_online_during_debug 0
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 4096 kByte.
<ES> Info: em/initial_size_MB( 16383MB) not multiple of em/blocksize_KB( 4096KB)
<ES> Info: em/initial_size_MB rounded up to 16384MB
Using implementation view
<EsNT> Using memory model view.
<EsNT> Memory Reset disabled as NT default
<ES> 4095 blocks reserved for free list.
ES initialized.
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c 1633]
Mon Oct 26 12:38:07 2009
***LOG Q0K=> DpMsAttach, mscon ( noptqas) [dpxxdisp.c 11822]
DpStartStopMsg: send start message (myname is >noptqas_DEV_00 <)
DpStartStopMsg: start msg sent
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: start to initalize 3.X shared alert area (first segment).
DpMsgAdmin: Set release to 7000, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1050]
DpMsgAdmin: Set patchno for this platform to 144
Release check o.K.
Mon Oct 26 12:38:47 2009
ERROR => DpHdlDeadWp: W0 (pid 276) died [dpxxdisp.c 14532]
ERROR => DpHdlDeadWp: W1 (pid 5532) died [dpxxdisp.c 14532]
ERROR => DpHdlDeadWp: W2 (pid 3696) died [dpxxdisp.c 14532]
ERROR => DpHdlDeadWp: W3 (pid 4928) died [dpxxdisp.c 14532]
ERROR => DpHdlDeadWp: W4 (pid 6040) died [dpxxdisp.c 14532]
ERROR => DpHdlDeadWp: W5 (pid 3892) died [dpxxdisp.c 14532]
ERROR => DpHdlDeadWp: W6 (pid 3860) died [dpxxdisp.c 14532]
ERROR => DpHdlDeadWp: W7 (pid 4564) died [dpxxdisp.c 14532]
ERROR => DpHdlDeadWp: W8 (pid 3940) died [dpxxdisp.c 14532]
ERROR => DpHdlDeadWp: W9 (pid 3288) died [dpxxdisp.c 14532]
my types changed after wp death/restart 0xbf --> 0xbe
ERROR => DpHdlDeadWp: W10 (pid 5136) died [dpxxdisp.c 14532]
my types changed after wp death/restart 0xbe --> 0xbc
ERROR => DpHdlDeadWp: W11 (pid 5128) died [dpxxdisp.c 14532]
my types changed after wp death/restart 0xbc --> 0xb8
ERROR => DpHdlDeadWp: W12 (pid 4452) died [dpxxdisp.c 14532]
ERROR => DpHdlDeadWp: W13 (pid 4680) died [dpxxdisp.c 14532]
ERROR => DpHdlDeadWp: W14 (pid 5664) died [dpxxdisp.c 14532]
my types changed after wp death/restart 0xb8 --> 0xb0
ERROR => DpHdlDeadWp: W15 (pid 5540) died [dpxxdisp.c 14532]
my types changed after wp death/restart 0xb0 --> 0xa0
ERROR => DpHdlDeadWp: W16 (pid 4312) died [dpxxdisp.c 14532]
my types changed after wp death/restart 0xa0 --> 0x80
DP_FATAL_ERROR => DpWPCheck: no more work processes
DISPATCHER EMERGENCY SHUTDOWN ***
increase tracelevel of WPs
NiWait: sleep (10000ms) ...
NiISelect: timeout 10000ms
NiISelect: maximum fd=309
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Mon Oct 26 12:38:57 2009
NiISelect: TIMEOUT occured (10000ms)
dump system status
Workprocess Table (long) Mon Oct 26 07:08:57 2009
========================
No Ty. Pid Status Cause Start Err Sem CPU Time Program Cl User Action Table
0 DIA 276 Ended no 1 0 0
1 DIA 5532 Ended no 1 0 0
2 DIA 3696 Ended no 1 0 0
3 DIA 4928 Ended no 1 0 0
4 DIA 6040 Ended no 1 0 0
5 DIA 3892 Ended no 1 0 0
6 DIA 3860 Ended no 1 0 0
7 DIA 4564 Ended no 1 0 0
8 DIA 3940 Ended no 1 0 0
9 DIA 3288 Ended no 1 0 0
10 UPD 5136 Ended no 1 0 0
11 ENQ 5128 Ended no 1 0 0
12 BTC 4452 Ended no 1 0 0
13 BTC 4680 Ended no 1 0 0
14 BTC 5664 Ended no 1 0 0
15 SPO 5540 Ended no 1 0 0
16 UP2 4312 Ended no 1 0 0
Dispatcher Queue Statistics Mon Oct 26 07:08:57 2009
===========================
SiSelNRemove: removed sock 196 (pos=2)
SiSelNRemove: removed sock 196
NiSelIRemove: removed hdl 2
MBUF state OFF
AdGetSelfIdentRecord: > <
AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
blks_in_queue/wp_ca_blk_no/wp_max_no = 1/300/17
LOCK WP ca_blk 1
make DISP owner of wp_ca_blk 1
DpRqPutIntoQueue: put request into queue (reqtype 1, prio LOW, rq_id 15)
MBUF component DOWN
NiICloseHandle: shutdown and close hdl 2 / sock 196
NiBufIClose: clear extension for hdl 2
MsIDetach: detach MS-system
cleanup EM
EsCleanup ....
EmCleanup() -> 0
Es2Cleanup: Cleanup ES2
***LOG Q05=> DpHalt, DPStop ( 3744) [dpxxdisp.c 10421]
Good Bye .....
Thanks in advance
Shakeel.

Please check this forums subject. It is SAP Business One System Administration - dedicate to SAP Business One System only.
Close your thread and post to a proper forum. To make other members read your message easily, at least some line breaks are needed in your message.
Thanks,
Gordon

Mutiple instance for messaging server

Can I set up mutiple instance of messaging server in one physical server ? The purpose is to separate domain to use difference resource, configuration. Now we use JES verion 6.

Can I set up mutiple instance of messaging server in
one physical server ? The purpose is to separate
domain to use difference resource, configuration. Now
we use JES verion 6.While I don't know if it supported(I think it wasn't but we needed to make it work while JES is still in transition about HA strategy), I did an installation of 3 JES2004Q2 messaging instances on 3 different hosts that were all in the same Veritas Cluster. With this configuration, we were able to have any messaging instance run on any host in the cluster (and could shift them so all 3 instances were running on a single host without problem, which we did several times)
Each host had a SAN partition mounted as
/usr/iplanet-$host
such as
/usr/iplanet-host1
/usr/iplanet-host2
these partitions were able to be moved between hosts as needed by the cluster software.
On each host, I made sure it had the SAN mount in place, then installed messaging as:
/usr/iplanet-$host/msg61
(instead of /opt/SUNWmsgsrv)
and when I ran /usr/iplanet-$host/msg61/sbin/configure
I said that the data directory should be:
/usr/iplanet-$host/msg61/msg-$host
I installed the admin server as:
/usr/iplanet-$host/admin5
On each of the messaging instances, I ran the ha_ipconfig script to lock down the IP address that the server processes bound to (and also had to lock down the ens daemon using a separate configutil variable, it still listened on the wildcard address).
When I was configuring the admin servers, I made each instance's run on a seperate port number so I didn't need to worry about locking down the IP. We also had to make a slightly customized version of the VCS agent that Sun supplies to work with the model we decided on.
There are still some issues, such as with performing patches. To patch an instance, you would need to make sure it is running on the host that it was originally installed on. If you only have a single host, I don't think the technique I used would work for you (unless you are able to use Solaris 10 beta and the zones functionality, and I am not sure if the JES packages play well with it yet)

Help me! My Message Server isn't work!

My server works well before the suddenly power down.
Solaris 8, Message Server 5.1 patch 1
I can telnet my smtp server by telnet localhost 25
but when I type HELO there is no response
The POP3 and HTTP works well.
Log in the tcp_master:
pmt_tls_init failed in sslinit(-1)
Continuing normally without TLS support....
Log in the job_controller:
os_map_file:lock failed -11
Can't get the lock. Another dirsync might be running
Log in my dirsync.trc:
Cannot get the dirsync lock
Even when I reboot my server or restart the msgserver,
the problem is still.
Help me! Please!
It emergence!

If you have iMS 5.2 you can and SHOULD configure Direct LDAP, per the Appendix B from the Administration Guide:
http://docs.sun.com/source/816-6009-10/dirldap.htm
You also should download and install Patch 1, as there are hundreds of fixes there.
You also will want to open a tech support ticket to get a current hotfix (1.25), with hundreds of further fixes.
Now, for your specific problem:
21:03:49.08: os_map_file: lock failed - 11
This is not a fatal error. It only means that when one thread has tried to open a file, some other thread already has it opened. We see these all the time, and they're not a problem.
"my mail server doesn't work" really doesn't give me anything to go on. Consider Messaging Server a loosely coupled set of modules. Each module can fail, but each fails in a different way, and has a different recovery technique. "doesn't work" doesn't tell me where it failed, or what has failed. that being the case, I have a great deal of difficulty telling you what is wrong, or how to fix it.
It's like you call your auto mechanic on the phone, and say, "my car won't go". He's going to need to find out several things, before he can tell you what he will charge you to fix it. "Does the engine start? Does it stall right away? Are there any lights on the dash? Does it go into gear?" etc. A better description of the problem really is the first thing we need.

Cannot connect to message server

Hi,
I have integrate a BSP Application from a sap ERP system in my portal !
After I checked this BSP, my ICM from my SAP ERP system failed : Server Overload !
I tried to restart the SAP system and know I have this error in the mmc :
disp+work.exe Running but not connected to Message Server !
In my dev_disp file :
DpJ2eeStart: j2ee state = STARTED
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c   1617]
***LOG Q0F=> DpLoopInit, nomstry () [dpxxdisp.c   1704]
ERROR => Connection to Message Server failed - check installation [dpxxdisp.c   1705]
In my std_server0.out :
Framework started for 151840 ms.
SAP J2EE Engine Version 7.00   PatchLevel is running!
PatchLevel March 04, 2006 16:23 GMT
>
Login :
SAP J2EE Engine Version 7.00   PatchLevel is shutting down! PatchLevel March 04, 2006 16:23 GMT
Stopping services.
Service jmsconnector stopped. (0 ms)
Service sld stopped. (0 ms)
Service com.adobe~TrustManagerService stopped. (31 ms)
Service com.adobe~DocumentServicesConfiguration stopped. (16 ms)
Service tcsecwssec~service stopped. (0 ms)
Service tc.CBS.Service stopped. (0 ms)
Service com.adobe~DocumentServicesDestProtoService stopped. (15 ms)
Service pmi stopped. (47 ms)
Service tcsecvsi~service stopped. (0 ms)
Service tcsecdestinations~service stopped. (0 ms)
Service tcsecsecurestorage~service stopped. (0 ms)
Service adminadapter stopped. (0 ms)
Service monitor stopped. (20000 ms) - Timeout expired.
Service com.adobe~LicenseService stopped. (0 ms)
In my std_dispatcher.out
Framework started for 46754 ms.
SAP J2EE Engine Version 7.00   PatchLevel is running!
PatchLevel March 04, 2006 16:23 GMT
>
Login :[ParNew 159114K->11211K(557952K), 0.3431082 secs]
[Full GC[Unloading class sun.reflect.GeneratedMethodAccessor17]
[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor5]
[Unloading class sun.reflect.GeneratedMethodAccessor15]
[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor12]
[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor2]
[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor8]
[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor9]
[Unloading class sun.reflect.GeneratedMethodAccessor5]
[Unloading class sun.reflect.GeneratedMethodAccessor24]
[Unloading class sun.reflect.GeneratedMethodAccessor14]
[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor11]
[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor3]
[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor10]
[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor7]
[Unloading class sun.reflect.GeneratedMethodAccessor10]
[Unloading class sun.reflect.GeneratedMethodAccessor11]
[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor4]
[Unloading class sun.reflect.GeneratedMethodAccessor3]
[Unloading class sun.reflect.GeneratedMethodAccessor7]
[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor1]
[Unloading class sun.reflect.GeneratedMethodAccessor21]
[Unloading class sun.reflect.GeneratedMethodAccessor25]
[Unloading class sun.reflect.GeneratedMethodAccessor20]
[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor13]
[Unloading class sun.reflect.GeneratedMethodAccessor12]
[Unloading class sun.reflect.GeneratedMethodAccessor26]
[Unloading class sun.reflect.GeneratedMethodAccessor6]
[Unloading class sun.reflect.GeneratedMethodAccessor29]
[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor6]
[Unloading class sun.reflect.GeneratedMethodAccessor22]
[Unloading class sun.reflect.GeneratedMethodAccessor28]
[Unloading class sun.reflect.GeneratedMethodAccessor9]
[Unloading class sun.reflect.GeneratedMethodAccessor27]
[Unloading class sun.reflect.GeneratedMethodAccessor23]
[Unloading class sun.reflect.GeneratedMethodAccessor13]
[Unloading class sun.reflect.GeneratedMethodAccessor8]
[Unloading class sun.reflect.GeneratedMethodAccessor16]
11211K->10224K(557952K), 0.5038284 secs]

Can you help help me, please.
Thank you.
Best regards,
Mathieu

System log error message when try to connect to message server

Hello,
There is a syslog entry, " Q0X Connection to client C of msg server closed as time exceeded". Research on SAP suggested a old note 73936. I am trying to find the root cause and resuire some guidance.The entries in dev_ms file shows the message:
***LOG Q0X=> MsSConnCheck, timeout (CX) [msxxserv.c   8032]
ERROR => No MS_LOGIN within 300 seconds [msxxserv.c   8039]
ERROR => Close connection to CX (XXX.XXX.X.XX), [XXX.XXX.X.XX] [msxxserv.c   8042]
How to narrow down whether it is caused by an incorrect client program or network issue? the ip address displayed in error message in dev_ms file is not listedin /etc/hosts files. Will that be causing the issue. Any help would be appreciated?

Hi,
That timeout message occurred due to inactivity from the client side. First you need to identify what application is connected to your message server. May be it's not a problem at all and this application just doing nothing and since message server is terminating a connection between them. Then, if you want to increase the time for message server to wait for activity from the application part, increase ms/conn_timeout parameter (set to 300s by default).
Regards,
Mike

"Disaster Recovery with Messaging server"

Suggest a better solution for load balancing on Netscape Messaging Server. Also for disaster recovery - in case one server goes down.

Better solution than what? Nothing? Use a cluster for the mail store. Use more than a single server for the other components and use a load balancer as the front end for those services.

JCo destination/ SLD configuration/ message server GRANT POINTS!

Hi,
I am trying to create JCo Destination, using wizard when I get to the point 3.2 (message server) I do not have my message server listed in the drop down list, althogh it is up running on port 3601.
Here is an error message I ve got at the end.
SLD Data supplier service running and I have HTTP and RFC configuration in place
Thanks Denis
Failed to create new JCO client connection HR_Human_Resouces_Test: com.sap.lcr.api.cimclient.LcrException: CIM_ERR_ALREADY_EXISTS: Instance already exists: SAP_MsgServJCODestination.CreationClassName="SAP_MsgServJCODestination",Name="HR_Human_Resouces_Test",SystemCreationClassName="SAP_J2EEEngineCluster",SystemName="DE1.SystemHome.sbdevsqlsap2" at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.raiseExceptionOnError(SimpleResponseAnalyser.java:120) at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.getIResult(SimpleResponseAnalyser.java:53) at com.sap.lcr.api.cimclient.CIMOMClient.sendImpl(CIMOMClient.java:215) at com.sap.lcr.api.cimclient.CIMOMClient.send(CIMOMClient.java:147) at com.sap.lcr.api.cimclient.CIMOMClient.createInstanceImpl(CIMOMClient.java:660) at com.sap.lcr.api.cimclient.CIMOMClient.createInstance(CIMOMClient.java:642) at com.sap.lcr.api.cimclient.CIMClient.createInstance(CIMClient.java:730) at com.sap.lcr.api.sapmodel.JavaCIMObjectAccessor.createInstance(JavaCIMObjectAccessor.java:44) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:283) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:649) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)

Hi Denis,
The below is the Wiki which i have created, please go through the notes.
Configure SLD for JCo and Creation of JCo Destinations
To create JCo connections you need to configure SLD (System Landscape Directory) first and then create JCo destinations.
First lets see as how to configure SLD.
Start Visual Administrator.
To start it
1) Go to Server Installed path i.e. usr\sap\<systemid>\<systeminstance>\J2ee\admin
2) Choose go.bat and start it.
3) Under Global Server Configuration, choose <Serverid>.
4) Choose Services under it.
5) Find SLD Data Supplier.
6) Under System Landscape Directory select HTTP Settings.
7) Give all the required fields like Host Name, Port Number, User Name and Password.
8) Similarly choose CIM Client Generation Settings and give Host Name, Port Number, User Name and Password.
9) You can test the SLD is configured properly or not. Just click CIM Client Test.
10) Save the settings and close Visual Administrator.
Now that you have configured SLD through Visual Administrator, we can create JCo Connections. To create JCo connections
1) You will need Super Administrator permissions to create JCos.
2) Log on to the Portal.
3) Go to Content Administration  Web Dynpro
4) Since we have configured SLD, now we can see a button to Create JCo Destination. Click it
5) Now you can observe Create new JCo Destination on right side panel.
6) Give the Following Details.
a) General Data:
Name: Give the name of JCo
Client: Give the Client number to which system you want to create JCo for. Click Next.
b) J2EE Cluster: Check the Use Local J2EE engine. Click Next.
c) Connection Type: Select Dictionary Meta Data. Click Next.
d) Application Server Connection: Select the existing Message Server and Logon Group.
It might sometimes happen that Message Server and Logon Group is not configured to configure them, follow the process
For Message Server:
i. Log on to SDL through portal i.e. http://<servername>:<portnumber>/sld
ii. Choose Technical System. Click it.
iii. You will observe New Technical System button, click it.
iv. System Type: Select Web AS ABAP , if you want to connect to R/3 System and incase you are using Java application use Web AS Java
v. General: Log on to R/3 System through SAP Log on pad. Go to System  Status, check for SID, Installation Number and Database Host Name.
vi. Central Servers: Give Host Name and Port Number and Instance Number.
For Logon Group:
i. Click on Add New Logon Group, this will open a row in the table.
ii. Log on to R/3 through Logon pad and get Logon Groups ids and the transaction code is SMLG.
vii. Application Servers: Click on Add Application Server and then give Host Name and Instance Number of R/3 System.
viii. Clients: Give Client number (System id) and Logical Client Name (which we can get from SMLG code). And click finish.
7) Message Server Connection:
i. Name: Give the logon name of R/3 System
ii. Password & Confirm Password: Give appropriate password of R/3 System.
8) Click Finish.
regards
Anil

Messaging Server 4: WebMail login returns "unable to locate the server"

When I log into WebMail, the following error occurs: 

Netscape is unable to locate the server hostname.
Please check the server name and try again.

End User

First verify that you cannot reach the hostname
server by using the ping
utility (Windows NT or Unix). If
you cannot reach the host, report this problem to the appropriate system
administrator or help desk.

However, if you can reach the host with ping
, then the problem may be a minor
networking issue that you can resolve. There is also the possibility that
the network has been configured to allow users to ping
unreachable systems. You can use the
following actions to rule out possible sources of the problem: 

<OL>
<LI>Attempt to log in to WebMail again. If you can log in successfully, then
the problem with the WebMail server may have been temporary or is an
intermittent problem.

<LI>End the current browser session and then restart the browser and try to
connect to the WebMail server again. If you can log in successfully, then,
most likely, the browser had cached some old network information that was
reset when you exited the browser.

<LI>Verify the DNS configuration of your system and then restart the entire
system.
</OL>

If the above actions do not work, then you will need to contact the
system administrator or the help desk.

Mail Server Administrators

As the problem with connecting to the WebMail server is caused by configuration
or availability problems, make sure that users who report this problem have
HTTP network connectivity to the hostname. The following scenarios are
possible causes of connectivity problems: 

<UL>
<LI>Users have the wrong proxy.
<LI>Users are being blocked by firewalls.
<LI>Users are connecting from the wrong network.
<LI>Users specify the incorrect DNS servers.
</UL>

In addition, users may also report that the server is down. As the login page
for WebMail does not contain URL links that are FQDNs or absolute path names,
it is possible that users may still be able to see the login window if it was
cached or loaded before the server stopped working.

In some cases, it may be necessary to access the hostname that is used in the
WebMail links. This hostname setting is stored in the configdb
parameter
service.smtp.messagehostname.
This configuration setting is not mentioned in the Messaging Server
documentation.

The messagehostname is a
configuration value that affects many server functions. For this reason, do
not make changes to this value without first considering the effects of such a
change on other WebMail settings, such as the postmaster group and user
mailhost values. Also, please note that changing messagehostname
is not supported from Console.

For more information on messagehostname
, please see "What is messagehostname?"
at 
article 4250

You can also find documentation for configutil
in the Messaging Server Administrator's
Guide at the following URL: 

http://docs.iplanet.com/docs/manuals/messaging/nms41/ag/cmdline.htm#1003887

Note: You must stop and restart the HTTP service in order for changes to
the messagehostname to
take effect.

When I log into WebMail, the following error occurs: 

Netscape is unable to locate the server hostname.
Please check the server name and try again.

End User

First verify that you cannot reach the hostname
server by using the ping
utility (Windows NT or Unix). If
you cannot reach the host, report this problem to the appropriate system
administrator or help desk.

However, if you can reach the host with ping
, then the problem may be a minor
networking issue that you can resolve. There is also the possibility that
the network has been configured to allow users to ping
unreachable systems. You can use the
following actions to rule out possible sources of the problem: 

<OL>
<LI>Attempt to log in to WebMail again. If you can log in successfully, then
the problem with the WebMail server may have been temporary or is an
intermittent problem.

<LI>End the current browser session and then restart the browser and try to
connect to the WebMail server again. If you can log in successfully, then,
most likely, the browser had cached some old network information that was
reset when you exited the browser.

<LI>Verify the DNS configuration of your system and then restart the entire
system.
</OL>

If the above actions do not work, then you will need to contact the
system administrator or the help desk.

Mail Server Administrators

As the problem with connecting to the WebMail server is caused by configuration
or availability problems, make sure that users who report this problem have
HTTP network connectivity to the hostname. The following scenarios are
possible causes of connectivity problems: 

<UL>
<LI>Users have the wrong proxy.
<LI>Users are being blocked by firewalls.
<LI>Users are connecting from the wrong network.
<LI>Users specify the incorrect DNS servers.
</UL>

In addition, users may also report that the server is down. As the login page
for WebMail does not contain URL links that are FQDNs or absolute path names,
it is possible that users may still be able to see the login window if it was
cached or loaded before the server stopped working.

In some cases, it may be necessary to access the hostname that is used in the
WebMail links. This hostname setting is stored in the configdb
parameter
service.smtp.messagehostname.
This configuration setting is not mentioned in the Messaging Server
documentation.

The messagehostname is a
configuration value that affects many server functions. For this reason, do
not make changes to this value without first considering the effects of such a
change on other WebMail settings, such as the postmaster group and user
mailhost values. Also, please note that changing messagehostname
is not supported from Console.

For more information on messagehostname
, please see "What is messagehostname?"
at 
article 4250

You can also find documentation for configutil
in the Messaging Server Administrator's
Guide at the following URL: 

http://docs.iplanet.com/docs/manuals/messaging/nms41/ag/cmdline.htm#1003887

Note: You must stop and restart the HTTP service in order for changes to
the messagehostname to
take effect.

SUN messaging server 7.0 HA in cluster 3.2

Hi all,
I Can't start message server resource group
Please follow the link below to assist:
http://forums.sun.com/thread.jspa?threadID=5334751
Thanks!

Hi shane,
>
I had a quick look at the above, I noted the following:
Sep 26 12:26:53 ms1 Cluster.PMF.pmfd: [ID 887656 daemon.notice] Process: tag="msg-rg,msg-rs,1.svc", cmd="/bin/sh -c /opt/sun/
comms/messaging64/bin/start-msg watcher", Failed to stay up.
Are there any error messages in the watcher/default log files to indicate whether/why there was a problem?
Following is the output in the default log:
[26/Sep/2008:12:25:41 +0800] ms1 stored[2498]: Store Warning: stored: Sun Java(tm) System Messaging Server STORE 7.0-0.04 64b
it (built Jun 20 2008) starting up
[26/Sep/2008:12:25:43 +0800] ms1 impurge[2499]: General Notice: impurge started
[26/Sep/2008:12:25:47 +0800] ms1 imsched[2502]: General Notice: starting up
[26/Sep/2008:12:26:53 +0800] ms1 imsched[2502]: General Notice: shutting down
[26/Sep/2008:12:26:53 +0800] ms1 impurge[2499]: General Notice: impurge finished
[26/Sep/2008:12:26:55 +0800] ms1 stored[2498]: Store Warning: stored: Sun Java(tm) System Messaging Server STORE 7.0-0.04 64b
it (built Jun 20 2008) shutting down
[26/Sep/2008:12:31:04 +0800] ms2 stored[2245]: Store Warning: stored: Sun Java(tm) System Messaging Server STORE 7.0-0.04 64b
it (built Jun 20 2008) starting up
[26/Sep/2008:12:31:07 +0800] ms2 impurge[2246]: General Notice: impurge started
[26/Sep/2008:12:31:12 +0800] ms2 imsched[2249]: General Notice: starting up
[26/Sep/2008:12:32:17 +0800] ms2 imsched[2249]: General Notice: shutting down
[26/Sep/2008:12:32:17 +0800] ms2 impurge[2246]: General Notice: impurge finished
[26/Sep/2008:12:32:20 +0800] ms2 stored[2245]: Store Warning: stored: Sun Java(tm) System Messaging Server STORE 7.0-0.04 64b
it (built Jun 20 2008) shutting down
[26/Sep/2008:12:36:20 +0800] ms2 stored[2393]: Store Warning: stored: Sun Java(tm) System Messaging Server STORE 7.0-0.04 64b
it (built Jun 20 2008) starting up
[26/Sep/2008:12:36:22 +0800] ms2 impurge[2394]: General Notice: impurge started
[26/Sep/2008:12:36:27 +0800] ms2 imsched[2397]: General Notice: starting up
[26/Sep/2008:12:37:33 +0800] ms2 imsched[2397]: General Notice: shutting down
[26/Sep/2008:12:37:33 +0800] ms2 impurge[2394]: General Notice: impurge finished
[26/Sep/2008:12:37:35 +0800] ms2 stored[2393]: Store Warning: stored: Sun Java(tm) System Messaging Server STORE 7.0-0.04 64b
it (built Jun 20 2008) shutting down
Following is from watcher log:
watcher process 2488 started at Fri Sep 26 12:25:21 2008
watcher process 2514 started at Fri Sep 26 12:26:56 2008
watcher process 2235 started at Fri Sep 26 12:30:43 2008
watcher process 2261 started at Fri Sep 26 12:32:20 2008
watcher process 2383 started at Fri Sep 26 12:35:59 2008
watcher process 2410 started at Fri Sep 26 12:37:35 2008
Are you able to start the instance outside of cluster control?
ms2@root# /opt/sun/comms/messaging64/sbin/start-msg
Warning: a HA configuration is detected on your system,
use the HA start command to properly start the messaging server.

Messaging Server 3: Startup failure due to postmaster error

Attempting to start up Netscape Messaging Server 3.x fails. From the
Server Selector, a dialog box shows the following error message: 

"Error:
An error occurred during startup."

The following error message appears at the command line: 

# /etc/NscpMail start
19990407000633:Dispatch:Notification:Error encountered in checking for
Postmaster account. You need to have one single Postmaster account assigned
with mail or mailAlternateAddress as [email protected] with the
proper substitution for host and domain. Please verify the possible causes
of this startup problem with absence of Postmaster or existence of multiple
Postmasters in your messaging server. This problem may be caused by (among
other things) a Directory Server being down or still in the process of
starting up.
Please wait, retrying...
Startup Problem:
A required resource was not available to the Mail Server.
Netscape Messaging Server Exiting!

However, the Messaging Server log shows no errors.
Use the following steps to resolve the problem: 

<OL>
<LI>Check the Directory Server access log for a query that appears
something as follows: 

[10/Jan/2000:18:27:57 -0800] conn=15 op=1 SRCH base="o=airius.com" scope=2
filter="(|([email protected])
([email protected]))"
[10/Jan/2000:18:27:57 -0800] conn=15 op=1 RESULT err=0 tag=101 nentries=0

This log entry shows that the Messaging Server failed to find a postmaster
address (as indicated by
"nentries=0").
The postmaster mail address in the example above uses the
MessageHostName
in the /etc/netscape.mail.conf
file, 

MessageHostName=kwikimart.nasd.mcom.com

<LI>In the Administration Server 3.x, go to the "User and Group" interface.

<LI>Add the
postmaster@MessageHostName
to the group as an alternate email
address.

<LI>Verify that startup is successful. 

The Directory Server access log should contain an entry showing that the
search found one postmaster entry
(nentries=1).
For example, 

[10/Jan/2000:17:47:35 -0800] conn=617 op=1 SRCH base="o=airius.com" scope=2
filter="(&(|([email protected])
([email protected]))
(|(objectclass=mailrecipient)(objectclass=mailgroup)))"
[10/Jan/2000:17:47:35 -0800] conn=617 op=1 RESULT err=0 tag=101 nentries=1

Also, the Messaging Server log file should contain a successful startup
message, such as 

20000110174743:Dispatch:Start
</OL>

Hello,
that looks strange for me:
> sysnr=$$
Is the system-nr. of the r3-system perhaps 44 and you've accidently pressed the shift-key while typing?
Regards,
Norman

Jcontrol.exe not starting - message server error

Hello Experts,
My jcontrol.exe is not staring and showing the status as "Some of the processes running" from long time. It is not coming to the status "Running". I had restarted, but still faces the same issue. I am sure that i had not installed or configured anything on the machine prior to this issue. We are working on Netweaver 2004s sp17.
my dev_control log file shows this:
[Thr 4812] JControlICheckProcessList: process server0 started (PID:2112)
JControlStartJLaunch: program = D:\usr\sap\NSP\JC01\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NSP\JC01\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NSP\SYS\profile\NSP_JC01_NSPCLNT000
-> arg[02] = -DSAPINFO=NSP_01_sdm
-> arg[03] = -nodeId=2
-> arg[04] = -file=D:\usr\sap\NSP\JC01\SDM\program\config\sdm_jstartup.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4796
-> arg[06] = -nodeName=sdm
-> arg[07] = -jvmOutFile=D:\usr\sap\NSP\JC01\work\jvm_sdm.out
-> arg[08] = -stdOutFile=D:\usr\sap\NSP\JC01\work\std_sdm.out
-> arg[09] = -locOutFile=D:\usr\sap\NSP\JC01\work\dev_sdm
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=D:\usr\sap\NSP\SYS\profile\NSP_JC01_NSPCLNT000
-> lib path = PATH=D:\j2sdk1.4.2_09
jre\bin\server;D:\j2sdk1.4.2_09
jre\bin;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\j2sdk1.4.2_09\bin\;D:\usr\sap\NSP\SYS\exe\uc\NTI386
-> exe path = PATH=D:\j2sdk1.4.2_09
bin;D:\usr\sap\NSP\JC01\j2ee\os_libs;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\j2sdk1.4.2_09\bin\;D:\usr\sap\NSP\SYS\exe\uc\NTI386
[Thr 4812] JControlICheckProcessList: process SDM started (PID:3660)
[Thr 4812] JControlMSSendLogon: delete SDM logon information (rc=0)
[Thr 4812] Wed Nov 11 11:53:17 2009
[Thr 4812] JControlMSSendLogon: insert SDM logon information (port=50118; rc=0)
my dev_control.b00 shows below
[Thr 7316] JControlICheckProcessList: process SDM started (PID:944)
[Thr 7316] *** ERROR => MsIModState: not_attached [msxxi.c      3838]
[Thr 7316] *** ERROR => Can't modify message server state (state = 3, rc = -3) [jcntrms.c    841]
[Thr 6628] Wed Nov 11 11:48:33 2009
[Thr 6628] ***LOG Q0I=> NiPConnect2: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 2823]
[Thr 6628] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 0 / sock 1684
    (SI_ECONN_REFUSE/10061; I4; ST; 10.245.105.31:3900) [nixxi.cpp    2823]
[Thr 6628] *** ERROR => MsIAttachEx: NiBufConnect to NSPCLNT000/3900 failed (rc=NIECONN_REFUSED) [msxxi.c      652]
[Thr 6628] *** WARNING => Can't reconnect to message server (NSPCLNT000/3900) [rc = -100]-> reconnect [jcntrms.c    368]
[Thr 5636] Wed Nov 11 11:48:35 2009
[Thr 5636] JControlSigInt: signal = 2
[Thr 5636] JControlIStopInstance: shutting down (command: 0)
[Thr 5636] *** ERROR => MsIModState: not_attached [msxxi.c      3838]
[Thr 5636] *** ERROR => Can't modify message server state (state = 6, rc = -3) [jcntrms.c    841]
[Thr 5636] JControlIProcessSoftKill: soft kill of process dispatcher (pid:5536)
[Thr 5636] JControlIProcessSoftKill: soft kill of process server0 (pid:2232)
[Thr 5636] JControlIProcessSoftKill: soft kill of process SDM (pid:944)
[Thr 7316] JControlICheckProcessList: process dispatcher (pid:5536) died (STOPPING)
[Thr 7316] JControlIResetProcess: reset process dispatcher
[Thr 7316] JControlICheckProcessList: process server0 (pid:2232) died (STOPPING)
[Thr 7316] JControlIResetProcess: reset process server0
[Thr 7316] JControlICheckProcessList: process SDM (pid:944) died (STOPPING)
[Thr 7316] JControlIResetProcess: reset process SDM
[Thr 7316] *** ERROR => MsIModState: not_attached [msxxi.c      3838]
[Thr 7316] *** ERROR => Can't modify message server state (state = 7, rc = -3) [jcntrms.c    841]
[Thr 7316] JControlCloseProgram: started (exitcode = 0)
[Thr 6628] Wed Nov 11 11:48:39 2009
[Thr 6628] ***LOG Q0I=> NiPConnect2: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 2823]
[Thr 6628] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 0 / sock 1744
    (SI_ECONN_REFUSE/10061; I4; ST; 10.245.105.31:3900) [nixxi.cpp    2823]
[Thr 6628] *** ERROR => MsIAttachEx: NiBufConnect to NSPCLNT000/3900 failed (rc=NIECONN_REFUSED) [msxxi.c      652]
[Thr 6628] *** WARNING => Can't reconnect to message server (NSPCLNT000/3900) [rc = -100]-> reconnect [jcntrms.c    368]
But, here my message server settings are correct, i did not changes those.
any help will be appreciated.
Thanks in Advance
Regards
Sunil Chiluveru

hello,
Could anyone help me in solving this issue...
Unable to resolve this issue....
server0 is hanging after this below text in log file
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 6136] Wed Nov 18 10:24:05 2009
[Thr 6136] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 6136] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 6136] JLaunchISetClusterId: set cluster id 12432550
[Thr 6136] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 6136] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 5860] Wed Nov 18 10:27:45 2009
[Thr 5860] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
[Thr 6488] Wed Nov 18 10:27:49 2009
[Thr 6488] JHVM_RegisterNatives: registering methods in com.sap.security.core.server.vsi.service.jni.VirusScanInterface
[Thr 6136] Wed Nov 18 10:28:09 2009
[Thr 6136] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
Wed Nov 18 10:31:30 2009
Excluding compile: com.sap.engine.services.webservices.jaxrpc.encoding.TypeMappingImpl::initializeRelations
Regards
Sunilchiluveru

Error with message server or lgtst?

Hi,
I`m new in this, so I need your help please with SAP, we have a problem, this happened the last 2 mondays, we have the SAP R3 v4.7.c with SGeSAP B04.01 in a cluster on a HP-UX 11i V2, in a package is running the database and the central instance and in another 2 hosts is running the applications, all conected by nfs. The problem: in a moment the SAP Message Server Monitor detect
WARNING: Message server 'server1' on node 'node1' - monitor state:YELLOW,1
(msmon_monitor): lgtst:
ERROR timeout occured
TIME Mon Feb 5 16:37:48 2007
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -5
COUNTER 1
using trcfile: /dev/null
Feb 5 16:37:49 - Node "node1": (msmon_monitor): msprot: returncode=0
Feb 5 16:37:49 - Node "node1": (msmon_monitor): ERROR: Message server process not running
Node "node1": Halting package at Mon Feb 5 16:37:49 SAT 2007 ###########
Feb 5 16:37:49 - Node "node1": Halting service dbciPE1db
Feb 5 16:37:50 - Node "node1": Halting service dbciPE1ms
cmhaltserv : Service name dbciPE1ms is not running.
and the service start to going down...
This appears in the package log, but the problem is not on the net or in the nfs server, some people tell us that might be a parameter in the sapms.mon, the MSMON_RFC_TIMEOUT..but we don't be sure..it seems that the message server lost conection with something but I don't know how works the Message Server, is strange that this happen only one day in the week so I think that there is another variable that produce this error..
any idea??? Can I see another file? or log? I don't know what can we do..
Thanks a lot!
Regards, Caro.

hi
Since you are indeed working with the depreciation area for 'special reserve', the arithmatic for this derived depreciation area would be ideally tax depreciation area - book depreciation area.
kindly confirm if this the arithmatic used for your depreciation area 03.
if this is not the case please let me know the arithmatic used for the derived depreciation area 03.
thanks

Messaging server down

Similar Messages

Maybe you are looking for