Potential problems with event log?

[Catherine Schumann]

Hi Jeroen
 
We are having a real crisis with those nasty symptoms - workflows just sit,=
 either waiting in a background step or not started even though the event h=
as fired and the receiver has been successfully found.
 
More puzzling, when users log out of MAPI connections from outlook, this oc=
casionally seems to restart everything that was waiting.  Then the whole sy=
stem waits again.  Deliberately teminating user's rfc connections has worke=
d once, but never again, so I think that we are on the wrong track there.
 
I have spoken to basis, but the system has been quiet during these times, a=
nd monitoring jobs have been minimal.  They even changed the mix of dialog =
and batch sessions for us - to the nighttime mix - for an afternoon, and no=
thing changed.
 
Does anybody know how to diagnose/fix this problem?  I have logged it on th=
e OSS, but have had no reply yet.
 
Thanks
Catherine
 
PS: 46C support pack 27, and Gui version 6.20 patch 26...
 
-----Original Message-----
From: Van der Burg, Jeroen JA SITI-ITPSEE
[mailto:jeroen.vanderburg at shell.com]
Sent: 17 March 2003 15:34
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Potential problems with event log?
 
 
Tony,
 
Experienced a similar issue when we did not have enough background processe=
s free on the system which runs the workflow stuff. In our case we had over=
cautious basis people running monitoring programs which reserved background=
 processes completly.
 
Result is that workflow rfc's can't run anymore as there is no space availa=
ble and, after they are stored for too long while there is no room for them=
 to run, time out with a 'system busy'. Really nasty as workflows tend to g=
et stuck in mid process without error status.
 
You can monitor this by looking at transaction SM50 but of course the syste=
m load changes constantly. If your system does not seem heavily loaded now =
check the job log for monitoring jobs run during the period where you exper=
ienced issues.
 
Solutions are normally to define more background processes for the system t=
o use, schedule less monitoring programs or make sure the other background =
progams are not all scheduled at the same time leaving a bit of space for o=
ther users of the system.
 
Hope this helps,
 
 
Jeroen
 
-----Original Message-----
From: Hoodak, Anthony J. [mailto:AHoodak at Gleason.com]
Sent: 17 March 2003 15:50
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Potential problems with event log?
 
 
Greetings -
 
Over the weekend, we seem to be experiencing some problems related to the
event log. The Basis admin just stopped by and said that he has a number of
errors that were raised, and the errors would appear (at least on the
surface) to be linked back to the event log. The transaction he showed me is
SM58. A typical entry in this log points to SWE_EVENT_LOG_WRITE and the
status text (in red) says "System busy".
 
Has any one out there experienced a similar problem and equally as
important, what should I be look at to determine the root of the problem? Is
this a problem with the event log filling up? If so, how do I purge the log?
Our event log has only been turned on for a week or so, so I am leaning in
this direction (unless someone advises me otherwise).
 
Thanks,
 
Tony
 
 
BBCi at http://www.bbc.co.uk/
 
This e-mail (and any attachments) is confidential and may contain=20
personal views which are not the views of the BBC unless specifically=20
stated.
If you have received it in error, please delete it from your system, do=20
not use, copy or disclose the information in any way nor act in=20
reliance on it and notify the sender immediately. Please note that the=20
BBC monitors e-mails sent or received. Further communication will=20
signify your consent to this.