BlackBerry Forums Support Community - View Single Post

noname · 05-21-2011, 03:15 AM

Arkanian, no MR is gonna resolved your issue. RIM has issued a Critical Advisory for DT 1216175 which DarthBBerry has given you in KB26461.

You should not have upgraded your BES to 5.0 SP3 if you still have stuck pending internal events.

Source: http://docs.blackberry.com/en/admin/...1-5.0.3-US.pdf

Internal events are stucked due to environmental issues causing communications between the BAS instances to failed. The many BAS instances you have in your setup, the higher the chances of getting stuck jobs. I don't under why one needs to install so many BAS instances in a setup. For BAS pooling, just setup 2 in a pool and preferably all located in the same LAN and avoid using TCPPing communication mode. A BAS instance is like a web-server, and with the web admin console URL, you can access it for administration from 100 workstation's IE browsers if you like. So for redudancy, just install 2 instances, one to standby in case the other is not working.

One can still function with 1 BAS instance for a domain of 10 BES servers with many people access from multiple workstation to the web admin console address using IE browsers to admin these servers remotely.

05-21-2011, 03:15 AM	#14
noname BlackBerry Extraordinaire Join Date: Sep 2005 Location: Congested Islet of "Foreign Talents" (> 45% of workforce) - Singapore. Model: Z10 OS: 10.0.0 PIN: NUKE(PAP) Carrier: Singtel Posts: 1,504	Re: Stuck "Pending internal event processes" Arkanian, no MR is gonna resolved your issue. RIM has issued a Critical Advisory for DT 1216175 which DarthBBerry has given you in KB26461. You should not have upgraded your BES to 5.0 SP3 if you still have stuck pending internal events. Source: http://docs.blackberry.com/en/admin/...1-5.0.3-US.pdf Internal events are stucked due to environmental issues causing communications between the BAS instances to failed. The many BAS instances you have in your setup, the higher the chances of getting stuck jobs. I don't under why one needs to install so many BAS instances in a setup. For BAS pooling, just setup 2 in a pool and preferably all located in the same LAN and avoid using TCPPing communication mode. A BAS instance is like a web-server, and with the web admin console URL, you can access it for administration from 100 workstation's IE browsers if you like. So for redudancy, just install 2 instances, one to standby in case the other is not working. One can still function with 1 BAS instance for a domain of 10 BES servers with many people access from multiple workstation to the web admin console address using IE browsers to admin these servers remotely. __________________ Native but 4th class citizen of a nation governed by idiots who import congestions & contention. Last edited by noname; 05-21-2011 at 03:17 AM..
Offline