[jamjoen]

Problem:
=======
We had similar problem with APB messages being sent overnight.

Cause:
=======
After spending time troubleshooting it was due to users having provate ToDo's - the Update ToDo agent runs at approx 1am each morning causing outstanding ToDos to move from one day to the next. Since they are provate todos the Blackberry server cant move the messages and generates the APB message.

HTH.james

[wbenge@bacardi.com]

looks like there are a lot of reasons this occurs. I had confirmation from a number of our users that after changing the 'Format preference for incoming mail' in the person doc that they have stopped recieving the System Attendant messages.

We also get them when there are netwrok connectivity issues between the BES and home mail servers on remote sites. So far we have avoided the 'overnight' torrent that others are reporting.

[kdtjlamb]

Originally Posted by MarvinK

The published reg hack to disable notifications is the "DisableFailedNotify" key. Apparently you also need to set a limit with the "MaxSkippedNotificationsPerDay", since disabling it doesn't actually disable it. I would set both hacks.

In any case, one has to wonder why there isn't a SP2-only update document--and an option in the software to disable notifications (and apparently set the limit to 0). Pretty lousy implementation on RIMs part.

There is documentation. Take a look at the admin guide for SP2. Page 21. It specifically speaks to the modifying the registry to turn off notification messages.

There is also a KB article on the RIM site which speaks to the same thing...
http://www.blackberry.com/knowledgec...44503&vernum=0

The DisableFailedNotify reg hack is for BES 2.2. It wont work on a 4.0 server.

The MaxSkippedNotificationsPerDay reg hack is for BES4.0 (w\SP2). Set the value to 0.

Been running with the hack for a 1 1/2 weeks and have had no APBs....

[MarvinK]

Originally Posted by kdtjlamb

There is documentation. Take a look at the admin guide for SP2. Page 21. It specifically speaks to the modifying the registry to turn off notification messages....

The DisableFailedNotify reg hack is for BES 2.2. It wont work on a 4.0 server.

The MaxSkippedNotificationsPerDay reg hack is for BES4.0 (w\SP2). Set the value to 0.

Been running with the hack for a 1 1/2 weeks and have had no APBs....

ADMIN.PDF is a full rewrite of the entire manual--they need to release something specific to SP2 changes and instructions. I already read the 300+ pages of PDFs for the original BES 4.0, and shouldn't have to compare those pages with the 350 pages of PDFs that may or may not have some changes (with no indication of whether they are SP2 specific).

As far as DisableFailedNotify---it is on the EXACT SAME PAGE (21) on the BES 4.0 SP2 admin.pdf as the new hack!!!

In any case, we still get APBs from time to time (with both hacks in place), but dramatically fewer than before.

I still think this should be a checkbox--not a registry hack.

[mahoward]

Woo hoo! After our 9/17 upgrade to SP2 it seems to actually be doing what it is supposed to do:

U:\>grep -c "Sending APB" KENOTESBES4_MAGT_01_200509*
KENOTESBES4_MAGT_01_20050901_0001.txt:13
KENOTESBES4_MAGT_01_20050902_0001.txt:14
KENOTESBES4_MAGT_01_20050903_0001.txt:6
KENOTESBES4_MAGT_01_20050904_0001.txt:10
KENOTESBES4_MAGT_01_20050905_0001.txt:7
KENOTESBES4_MAGT_01_20050906_0001.txt:14
KENOTESBES4_MAGT_01_20050907_0001.txt:10
KENOTESBES4_MAGT_01_20050908_0001.txt:15
KENOTESBES4_MAGT_01_20050909_0001.txt:15
KENOTESBES4_MAGT_01_20050910_0001.txt:15
KENOTESBES4_MAGT_01_20050911_0001.txt:22
KENOTESBES4_MAGT_01_20050912_0001.txt:20
KENOTESBES4_MAGT_01_20050913_0001.txt:18
KENOTESBES4_MAGT_01_20050914_0001.txt:68
KENOTESBES4_MAGT_01_20050915_0001.txt:18
KENOTESBES4_MAGT_01_20050916_0001.txt:5
KENOTESBES4_MAGT_01_20050917_0001.txt:25
KENOTESBES4_MAGT_01_20050918_0001.txt:0
KENOTESBES4_MAGT_01_20050919_0001.txt:0

U:\>

[BesDominoAdmin]

OK Everybody I think we finally have it...I have been promised by RIM for the past 5 months that the APB fix will be in the next ServicePack or Hotfix...but never came..
Now finally we have it in SP2..

Please note that RIM in no way have found a fix for the root cause. However we have a workaround for the issue with BES in a Domino Environment (Sorry guys...I have'nt researched on Exchange).

Instead of stopping the APB's to be generated, RIM has found a way we can "limit" these messages to be sent to the Users. ie..we "limit" it to "0"...so no APB's

This fix is available after deploying BES4.0 SP2

The article is in their Knowledge Base:
- Title:
Known Issues - Cannot limit APB notifications in BlackBerry Enterprise Server 4.0.2
- Article Number: KB-04291 (Last Updated: 15 August 2005)

We have tested it on 2 domino servers. I haven't yet seen a single APB even after design templete changes on User Mailfiles.

So is this a fix ???....Donno....will have to wait & see...

[BesDominoAdmin]

After 4-5 months of research..troubleshooting with RIM & IBM (for Domino) it was identified that whenever there is a Mail-Templete design change on the user's Mailfile database "*.nsf" , the BES is recognizing this as an "e-mail message", then, when it tries to process this so called "message" it fails & generates an APB.....

But here is the Official reason given by RIM (Article Number: KB-03281) updated 17th-Sep, 2 days ago:

An APB can be sent to the handheld for the following reasons:

- mail database corruption
- unreadable message format
- incompatible compression technique

(Now the following 2 are classic "I DODN'T KNOW WHAT'S CAUSING THIS" answer)

- a network issue
- an unforeseen factor

[amukhey]

It works on SP2 for Domino

[topher145]

Doesn't fix it for me:

> tell bes about
09/27/2005 11:36:20 AM BlackBerry Enterprise Server, Version 4.0.2.12
09/27/2005 11:36:20 AM c 1997-2004 Research In Motion Limited

I loaded SP2 over a week ago. After a couple of days I made the registry change and did TELL BES QUIT and LOAD BES. The APB's still got generated. So I came back here to find the registry setting again to make sure. I still had it right in:

HKEYLM > SOFTWARE > Research In Motion > Blackberry Enterprise Server > Agents
New DWORD MaxSkippedNotificationsPerDay with value 0

Should it be hexadecimal or decimal? The default id hex and that hasn't worked for me. I deleted and re-created it per the RIM documentation (which just says to change to 0). I have made it a decimal data type instead of hex.

Will see if it works. I rebooted yesterday after seeing that it wasn't working and I got 32 APBs sent, so we'll see how this does for today!

[topher145]

That didn't work either - since the last post, I've had 16 more "Sending APB" messages...

[mkb]

Can you verify that the APB messages are actually being delivered to the devices? Also, can you tell if the messages are the type generated for template changes or of the type generated for undelivered messages? It seems that the latter are still delivered. So, if a message was sent to 16 of your users at one time that the BlackBerry server could not deliver, you could potentially generate 16 APBs. Just a thought...

The service pack did seem to resolve the APB problems for us.

[topher145]

How can I verify that it was an undelivered message? I just replaced my design twice and nothing sent to me...

[mkb]

I'm not sure exactly what the message would be in the log for an undelivered message, but the body of the APB (just look on one of the BlackBerries that received the APB) will indicate that a message was not delivered. The message in the log that says "skipping now" are the APBs generated from template changes and should be blocked by the MaxSkippedNotificationsPerDay. I'm not 100% sure if the same registry setting disables ALL APBs. I have a feeling that it does not.

[TheBerryGuru]

Any one still getting messages after applying SP2 and the reg key might want to delete the APBData folder on the BES and also delete the reg key for the APBData folder as cached APB's can get stuck here and will get sent eveytime you restart the server.

[amarcord]

Why is there a delay(30 minutes) in receiving and deleting my messages with my imbox?
How I can resolve it
I have a Bes Exchange 4.0, Win 2003 sp1 , Firmware 4.0.0.215
Exchange 2003 sp1.

Thanks

[DZUCCONI]

this should resolve the issue for version 4.x and 2.2

As this will not let me post a url, becuase I need to post 10 items.

Go to the blackberry tech support website
Search for: 04245

[DZUCCONI]

Originally Posted by alpayne

I have just recently started seeing this messages in my test BES environment. (4.0/Domino) 3 of my test users received btwn 1-5 of these msgs "overnite" and i received almost 30. While the message: "The BlackBerry Enterprise Server was unable to process a message. You can still view this message in your desktop email program. Your system administrator has been notified." was displayed on my bb, there were not 30 corresponding msgs in my inbox.

Would like to hear from others experiencing this same issue.

this should resolve the issue for version 4.x and 2.2

As this will not let me post a url, becuase I need to post 10 items.

Go to the blackberry tech support website
Search for: 04245

[MarvinK]

Hopefully people aren't still struggling with this, unless they're new to BES!! In any case, here's the link dzucconi was referring to:


http://www.blackberry.com/knowledgec...44503&vernum=5

[perpetualsmile]

For those of you still looking...here's how we fixed the problem. Removed Design from running at startup by removing it from the Notes.ini of the mail server. Then cleared the accumulated messages on the BES server.

Good luck

[Sharezer]

We are using 4.0.4.7 on Domino 6.5.5 and we have no such APB problem