BES 4.0 SP1 HF3 (Exchange) - removed from downloads?
Anyone know why RIM removed this from the Service Pack Downloads page? I had downloaded when it was released and installed within our Test environment, but now its removed. Odd...
Wirelessly posted (BlackBerry7250/4.0.0 Profile/MIDP-2.0 Configuration/CLDC-1.1)
I know, spent 10 days figuring what tore my bes up, that's why its gone. Any that have it, OTA activate probably will fail.
I haven't really seen any issues in our Test environment, to be honest. I even went through a database migration during that time. Not a lot of users tho, but I'm definitely glad that I didn't install it to Production :-)
Well I'm not sure exactly when RIM figured out it was a problem. After 8 days giving them a chance to figure it out, I decided to start over with 4.0 to rebuild the database as some of the errors I saw reflected the fact that the database was not functioning correctly.
The problem would only be seen with new users or if you removed a user, readded them, then tried a wireless activation, the activation would hang every time with no less than Handheld Agent, Memos, Tasks, and Address book still initializing.
Once I worked my way up to 4.0 HF3 I stopped, it's rocking now and having little or no issues at this time.
Be very glad you didn't install it, was a ***** to figure out, especially when even they didn't know.
Just found this...
My symptoms are different...same symptoms we've had since we installed BES 4/Exchange, but much, much worse since HF3. Unfortunately, HF3 was when we also doubled the number of users (to 35), so I don't know if it's the HF or the new load.
Our symptoms: BES server is also a file server. Pretty stout machine; 2x P4 3GHz, 4GB RAM, WS2003. Was a dedicated file server; machine ran flawlessly until BES installed.
File server performance degrades noticeably over a period of (originally) a few weeks and now, a few days, characterized by very slow IO and errors citing "inadequate system resources" when copying/moving/deleting large numbers of files. Has to be restarted to get performance back.
Just before it's about to get really bad, app log fills with 1000s of BES events...different each time. Last time it was
Event Type: Error
Event Source: BlackBerry Synchronization Service
Event Category: None
Event ID: 10000
Time: 11:40:57 AM
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot insert duplicate key row in object 'SyncRequest' with unique index 'idx_SyncRequest2'.[SqlState 23000][ODBCRecord::DoSetValue]DATA: Locked UserConfigID Locked Operation Operation.
This time it was
Event Type: Warning
Event Source: BlackBerry Messaging Agent SERVER1 Agent 1
Event Category: None
Event ID: 20539
Time: 3:21:59 PM
text email address removed} RescanPIMItems(3) failed: ERR_NETWORK_PROBLEM
I can stop the errors by restarting the BES services, but I have to restart the computer before its performance returns to normal.
Something is REALLY wrong with this software.
Does anyone have instructions on removing HotFix 3?
As per the article, we have to call our provider. When I e-mailed ours, this was his reply:
I can schedule time with you to go through this uninstall process which will include the two of us conferencing with Nextel's tier three tech support who will be able to patch us into RIM's Tech Support.I wish they'd just document the removal in the KB. I haven't gone through it yet...I will not have an opportunity until at least late this week, and will have to keep restarting this server every day or two until I do.
I'll see how involved it is; I imagine there are more steps than I could record for documentation purposes and perform at the same time with a degree of confidence that I'd want others relying upon my instructions. This was a 15MB patch, remember! And there may be different removal scenarios depending on configuration, so it's probably best to do it RIM's way.
I'll tell you what I did, whether you want to or not is up to you.
I reinstalled BES 4.0
Reinstalled BES 4.0 SP1
Reinstalled BES 4.0 SP1 HF1
Reinstalled BES 4.0 SP1 HF2
Who knows; that may be what RIM will tell me! But I'm hoping for a surgical hotfix-ectomy, though. As much of a headache as it was to get BES working in the first place, I'm not anxious to do it again.
If I end up reinstalling, I'll probably put it on a dedicated server or a VM where it can't screw anything up but itself.
|All times are GMT -5. The time now is 10:50 AM.|
Powered by vBulletin® Version 3.6.12
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.