Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

Reply
New Contributor
Posts: 3
Registered: ‎12-17-2008
My Device: Not Specified

BlackBerry Messaging Agent, Event ID 10000 & requires Server restart

Has anyone experienced this before, or have a fix/advice etc

 

Our Blackberry server is generating thousands of Errors in the Event Log ( about 7000 per second). CPU on the server is at about 80%, Bes Service eventually fails and server requires a full restart.

 

Software Versions :

Windows server 2003 SP2

Domino Version : Lotus Domino (r) Server (Release 8.0.2 for Windows/32)

Blackberry Enterprise Version : Version 4.1.6.15

 

Event Viewer errors ( Application Log )  reads :

 

BlackBerry Messaging Agent  EventID 10000

[DIAG]Error telling the debug trace position. Illegal byte sequence (error42)

Retired
Posts: 79
Registered: ‎04-01-2008
My Device: Not Specified

Re: BlackBerry Messaging Agent, Event ID 10000 & requires Server restart

Does the BES currently have the permissions to write to the folder that the debug logs are collected in? There was an issue previously related to the BlackBerry Controller, where that appeared to be a catalyst for similar error messages to be logged superflously. We released a change that addressed that activity but this may be a similar issue in another area?
New Contributor
Posts: 3
Registered: ‎12-17-2008
My Device: Not Specified

Re: BlackBerry Messaging Agent, Event ID 10000 & requires Server restart

I thinks so ( we are seeing numerous  logs appearing with todays date etc) Under the logs folder under Blackberry Enterprise server directory. But I will check tomorrow when I am back in the office

 

Thanks for the pointer,

John

Highlighted
New Contributor
Posts: 3
Registered: ‎12-17-2008
My Device: Not Specified

Re: BlackBerry Messaging Agent, Event ID 10000 & requires Server restart

Just an update.

 

Issue was resolved by ...

Disabling Rich Text initially, (Doc ID : KB15931 )

 

then applying a maintenance release,( Now Up to Version 4.1.6.19) before re-enabling Rich Text Content