[technickel]

I guess I will be the first to open this up. I just upgraded to 4.1.7 in GW BES and my event viewer is nothing but these notifications. RIM says that they are working on it.

[noname]

I admire your courage deciding going forward with BESG 4.1.7 upgrade. It is released with nothing but troubles. There are red-coded remarks on expected issues that you will expect when you are at their Download site.

Service Pack 7
Please Note: In some instances, after upgrading to BlackBerry® Enterprise Server v4.1.7, incomplete SOAP events can be generated by the Novell® GroupWise® Post Office Agent which may cause some users to stop receiving email and notifications. See BlackBerry® Knowledge Base Article# KB22581 for more information.

Please Note: In some instances, after upgrading to BlackBerry® Enterprise Server v4.1.7, if a large amount of SOAP events are processed at one time on a Novell® GroupWise® 8.0.0 - 8.0.2 Post Office Agent, some users may stop receiving email on their BlackBerry® smartphone. See BlackBerry® Knowledge Base Article# KB24352 for more information.

SOAP mode Issues
KB22581-No events are processed following a "SLAP" in the Novell GroupWise SOAP Connector when the exception 'Object must be of type UInt32' is logged
KB24352-Redirection of new data and updates from Novell GroupWise stops after a large number of events are processed

OAPI mode Issues
KB24634-Messages filed in the Novell GroupWise email application are automatically moved back to the application mailbox

Additional Information
You may also want to know that upgrading to BESG 5.0SP1 is packaged with even more problems.

KB24504-BlackBerry Enterprise Server running on Windows Server 2003 or 2008 may stop responding due to a BlackBerry Messaging Agent memory leak
KB24579-Environmental considerations when upgrading to or installing BlackBerry Enterprise Server 5.0 SP1 for Novell GroupWise
KB24114-Recommended version of Novell GroupWise components for BlackBerry Enterprise Server 5.0.1
KB20798-Supported upgrade paths to BlackBerry Enterprise Server 5.0 SP1 for Novell GroupWise

[svandamme]

simply backrev to SP6 + MR's.. It's possible:

1 Stop BES
2 uninstall BES 4.1.7
3 reboot
4 reinstall BES 4.1.6 1/2 , point to the original DB
5 reboot
6 BES 4.1.6 2/2 uncheck "start services"
7 install the latest MR
8 reboot

Waiting for the semaphore is gone , BES works fine again.
I've done it in a live enviroment , it works.

RIM won't even comment on this workaround/resolution. They won't commit to a fix for the SP7 issue.. I was quoted " it may be in MR1, but it could also be MR2. Mr1 could be up to 6 months out, MR2 even longer.. No you aren't supposed to Backrev like that.. No we cannot recommend it, no it probably will not work..

I hear that, and i interpret it as "we don't care enough about this issue".
At that point with hundres of BB's down i have 3 options

1 wait for RIM ( as if)
2 Scratch reinstall, wipe and reactivate every device
3 Try to back rev, hope for the best.

At that point #3 doesn't sound that scary anymore

[technickel]

I hear ya ! I just called the other day to get an update and was told to hold my breath, turn blue and pass out.