Here is a block of it, I'm looking in the alert log, maybe I should be
looking at another?
[30000] (10/30 00:07:07.353):{0x554} Alarm::ThreadProc: Received an
alarm message
[30000] (10/30 00:07:12.197):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 02:54:19.752):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 03:56:25.590):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 03:56:30.793):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 04:15:48.784):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 04:15:53.784):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 07:56:30.582):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 07:56:35.598):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 08:36:02.882):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 08:36:07.882):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 09:08:11.403):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 09:08:11.403):{0x754} [Alarm::ActivateAlarm] Queuing
alarm: <N/A> | BlackBerry Messaging Agent HDHSRV153 Agent 1 (Application
Event Log on HDHSRV153) | 10/30/2009 09:08:11 (AFFF4E9E) ->
RIM_HrGWResolveProxy - Exception handled
[30000] (10/30 09:08:11.403):{0x554} Alarm::ThreadProc: Received an
alarm message
[30000] (10/30 09:08:16.419):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 09:08:16.419):{0x754} [Alarm::ActivateAlarm] Queuing
alarm: <N/A> | BlackBerry Messaging Agent HDHSRV153 Agent 1 (Application
Event Log on HDHSRV153) | 10/30/2009 09:08:11 (AFFF4E9E) ->
RIM_HrGWResolveProxy - Exception handled
[30000] (10/30 09:08:16.419):{0x554} Alarm::ThreadProc: Received an
alarm message
[30000] (10/30 09:09:33.500):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 09:09:33.500):{0x754} [Alarm::ActivateAlarm] Queuing
alarm: <N/A> | BlackBerry Messaging Agent HDHSRV153 Agent 1 (Application
Event Log on HDHSRV153) | 10/30/2009 09:09:33 (AFFF4E9E) ->
RIM_HrGWResolveProxy - Exception handled
[30000] (10/30 09:09:33.500):{0x554} Alarm::ThreadProc: Received an
alarm message
[30000] (10/30 10:09:45.725):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 10:09:45.725):{0x754} [Alarm::ActivateAlarm] Queuing
alarm: <N/A> | BlackBerry Messaging Agent HDHSRV153 Agent 1 (Application
Event Log on HDHSRV153) | 10/30/2009 10:09:45 (AFFF4F29) ->
{[email protected]} MAPIMailbox::Send(ppMAPIMessage) - SubmitMessage
(0x80004005) failed
[30000] (10/30 10:09:45.725):{0x554} Alarm::ThreadProc: Received an
alarm message
[30000] (10/30 10:09:54.178):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 10:09:54.178):{0x754} [Alarm::ActivateAlarm] Queuing
alarm: <N/A> | BlackBerry Messaging Agent HDHSRV153 Agent 1 (Application
Event Log on HDHSRV153) | 10/30/2009 10:09:49 (AFFF4E20) ->
{[email protected]} Send() failed: ERR_MAILBOX_FULL, Tag=366205
[30000] (10/30 10:09:54.178):{0x554} Alarm::ThreadProc: Received an
alarm message
[30000] (10/30 11:12:51.893):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 11:20:45.986):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 11:22:04.176):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 11:55:53.272):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 11:55:58.428):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 11:56:12.398):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 11:56:20.398):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 12:26:49.285):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 12:28:53.320):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 12:30:22.323):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 13:32:32.379):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 13:32:32.379):{0x754} [Alarm::ActivateAlarm] Queuing
alarm: <N/A> | BlackBerry Messaging Agent HDHSRV153 Agent 1 (Application
Event Log on HDHSRV153) | 10/30/2009 13:32:32 (AFFF4E9E) ->
RIM_HrGWResolveProxy - Exception handled
[30000] (10/30 13:32:32.379):{0x554} Alarm::ThreadProc: Received an
alarm message
[30000] (10/30 14:18:05.373):{0x754} EventLog::ThreadProc: Received
notification, processing...
[30000] (10/30 14:18:05.373):{0x754} [Alarm::ActivateAlarm] Queuing
alarm: <N/A> | BlackBerry Messaging Agent HDHSRV153 Agent 1 (Application
Event Log on HDHSRV153) | 10/30/2009 14:18:05 (AFFF4E9E) ->
RIM_HrGWResolveProxy - Exception handled
[30000] (10/30 14:18:05.373):{0x554} Alarm::ThreadProc: Received an
alarm message
From: [email protected]
[mailto:[email protected]] On Behalf Of
[email protected]
Sent: Friday, October 30, 2009 3:19 PM
To: [email protected]
Subject: Re: [Bes-admins] Error from BES
OK, that makes it easy. Please open the agent log and see what the agent
is trying to do immediately before and after this line. This alarm is a
truncated version of the full occurrence and does not say much. The
encouraging part is "Exception Handled" - this really means that BES was
expecting to get an exception in a given code block and therefore knows
how to deal with it.
From: [email protected]
[mailto:[email protected]] On Behalf Of Page, John
Sent: Friday, October 30, 2009 3:15 PM
To: A list for BES Admin's to discuss issues, etc.
Subject: Re: [Bes-admins] Error from BES
Yes
From: [email protected]
[mailto:[email protected]] On Behalf Of
[email protected]
Sent: Friday, October 30, 2009 3:13 PM
To: [email protected]
Subject: Re: [Bes-admins] Error from BES
OK, so by the look of it, you have a single BES and single mail server.
Correct?
From: [email protected]
[mailto:[email protected]] On Behalf Of Page, John
Sent: Friday, October 30, 2009 3:10 PM
To: A list for BES Admin's to discuss issues, etc.
Subject: Re: [Bes-admins] Error from BES
No, I have it setup to email me errors, and that's what I got. This is
from the actual log file
[30000] (10/30 09:08:11.403):{0x754} [Alarm::ActivateAlarm] Queuing
alarm: <N/A> | BlackBerry Messaging Agent Mybes Agent 1 (Application
Event Log on Mybes) | 10/30/2009 09:08:11 (AFFF4E9E) ->
RIM_HrGWResolveProxy - Exception handled
From: [email protected]
[mailto:[email protected]] On Behalf Of
[email protected]
Sent: Friday, October 30, 2009 3:06 PM
To: [email protected]
Subject: Re: [Bes-admins] Error from BES
I think this has more to do with MAPI connection to the mail server. Was
there a "tail" portion of the message that you truncated?
See
http://supportforums.blackberry.com/t5/BlackBerry-Enterprise-Solution/Ha
ndhelds-cannot-send-receive-email/m-p/134763
From: [email protected]
[mailto:[email protected]] On Behalf Of Page, John
Sent: Friday, October 30, 2009 3:00 PM
To: A list for BES Admin's to discuss issues, etc.
Subject: [Bes-admins] Error from BES
Hey guys we are having issues with Blackberry messenger and it being
slow, sometimes you can message someone instantly, and other times it
seems to hang, for quite a few minutes before sending. I always thought
that the BES had nothing to do with Blackberry Messenger, and that it
use my provider and Rim's servers, so I have been writing it off as an
issue on their end, but then I noticed this error that keeps popping up,
and wondering if it's related.
"<N/A> | BlackBerry Messaging Agent MyBES Agent 1 (Application Event Log
on Mybes) | 10/30/2009 13:32:32 (AFFF4E9E) -> RIM_HrGWResolveProxy -
Exception handled"
Any ideas? I have not tried restarting any services or reboots
_______________________________________________
Bes-Admins mailing list
[email protected]
http://www.dataoutages.com/mailman/listinfo/bes-admins
http://www.dataoutages.com
http://www.dataoutagenews.com
RSS Feed: http://feeds.feedburner.com/Bes-admins
---------------------------------
