I've been monitoring the forum regarding SP3 and it's hotfixes for the last three weeks. I've seen some really good and informational posts from some really skilled BES admins. I would like to read more experiences from those who have already installed SP3. I think others would also like to see more. Please reply with your experiences with installing SP3 for BES 4.0. I really appreciate your reply's and this forum. Thanks.
James
We are having 4 production BES boxes and wanted to migrate to BES 4. I have created a test environment and had 3.6 Servers installed and moved the DB to a remote SQL server and merged them. All was ok. Then the BES migration also completed succesfully. I left if for 2-3 weeks and was ok.
Yesterday i installed the BES4 SP3 and then all sorts of problem started. The moment i installed it i could see my server CPU hiked to 90-100 % always. Then after few reboots i discovered another problem. One of my user on the test server did not get any mails on his BB, looking at the server i found that the Router service did not start..... trying to start i found that the service did not start bcoz it said the port 4101cud be use by another application.... The setup has been the same for BES 4 and the problem happend only after SP3..... i did install the hotfix but that did not help either.. now am fighting to solve the problem
TCPView from sysinternals is great to find whats running on what port.
What process is using all your CPU time. BESAlert has been known in Sp3 to dominate that. If you do not use BlackBerry Alert service stop it and see if the CPU time returns to your baseline.
I would recommend that SP3 is not a good option... I have checked the Port usage and that is ok... To resolve that i uninstalled and reinstalled the Router service on the problem machine and that solved the problem... However the CPU Utlisation did not come down..... The System Process uses 70 % of the CPU and then remaining chokes the CPU to go to 90% always.. I have see few threads talking about this and stopping the BES Alert etc did not help. Even the hotfix did not work..... I have restored the BES 4 to the basic version and all is ok now so i am sure that it is not a system problem.. and also the port locking did not happen when i reinstalled bes 4 again so its something to do with the BES 4 SP3......
I have been told that there is a new release of the SP so we need to wait and i would be speaking with the technical consultant from RIM and will let you know any important information.....
BES 4 SP3 is not a good option according to me.....
Everyone keeps saying that they are putting out a new release of SP3, but I was on the phone with T-support several times and they never mentioned anything of that sort. I'll wait for either another release of the SP or a hotfix to fix all the new issues.
Sure wish I'd seen these messages before applying SP3 + Hotfix 1. All services are started, but no mail is flowing through the BBs and also none of them show up in the BB MGR. Configuration DB looks in tact (SQL 2000) and licensing info and other info look good.
Do I need to uninstall SP3 + Hotfix 1 and go back to stock 4.0?? That was working...
Well, not sure that would have been the best route for us to take although I did take al ook at removing SP3 and the hotfix but there were no entries in Add/Remove Programs for them.
Anyways, the resolution for our issue was we had a schema corruption issue on our Configuration Database. Although the Service Pack and Hotfix installed cleanly, the SQL database did not fair as well.
We were given a script from RIM that repaired the schema issues and once the services were restarted, all of our BBs came back into the manager and e-mail started flowing again.
This is apparently a known problem that can occur with both SP2 and SP3 and is currently in development's hands to resolve for the next service pack/release.
Well, not sure that would have been the best route for us to take although I did take al ook at removing SP3 and the hotfix but there were no entries in Add/Remove Programs for them.
Anyways, the resolution for our issue was we had a schema corruption issue on our Configuration Database. Although the Service Pack and Hotfix installed cleanly, the SQL database did not fair as well.
We were given a script from RIM that repaired the schema issues and once the services were restarted, all of our BBs came back into the manager and e-mail started flowing again.
This is apparently a known problem that can occur with both SP2 and SP3 and is currently in development's hands to resolve for the next service pack/release.
Mike.
I keep checking this forum for good experience with SP3, and all I find is stuff like this. I'd really like to take a service pack to our BES server, but from what I read on here I think it is best to wait. We are still at stock 4.0.
Sure wish I'd seen these messages before applying SP3 + Hotfix 1. All services are started, but no mail is flowing through the BBs and also none of them show up in the BB MGR. Configuration DB looks in tact (SQL 2000) and licensing info and other info look good.
Do I need to uninstall SP3 + Hotfix 1 and go back to stock 4.0?? That was working...
Mike.
Contact RIM for that. I did and they guided me through some special instructions for fixing this problem.
--Sorry I didn't see your later post about a successful fix.--
Last edited by BBTechGuy; 11-30-2005 at 05:41 PM..
We are at sp2 running on Windows 2003 and will wait till we see a more positive experience for future service packs. Applying sp1 was no problem but we had to have RIM walk us through the process to apply sp2.
We do have to recycle services/server from time to time still because of hung threads.
First SP 2, now this. Is this a common occurrence when RIM releases a service pack? It's not very trust inspiring. I'm afraid to even think about applying a service pack to my BES.
We are at BES 4.0 SP1 with Exchange 5.5 on Win2k SP4 and the BB Router service does not start when rebooting the server. Also having an issue with the wireless sync for the Address Book for one user that has BB 8700c. I was thinking to install SP3 with the hotfixes, but after seen these other issues, I will wait.
Running SP3 hotfix#1 and the only problem seems to be excessive logging so I stopped BES Alert. Wait... we are also having problems with users not being able to accept meeting requests and in some cases not being able to send them.
WOW... We have server 2003sp1 with Bes 4.0.3 and all current patches installed and everything seems just fine. No problems to date. (Been running it since the patch was released a few months ago.
BES for Exchange 4.0 SP3 Experiences
We have server 2003sp1 with Bes 4.0.3 and all current patches installed and everything seems just fine. No problems to date. (Been running it since the patch was released a few months ago.
