BlackBerry Forums Support Community

BlackBerry Forums Support Community (http://www.blackberryforums.com/)
-   BES Admin Corner (http://www.blackberryforums.com/bes-admin-corner/)
-   -   BES 4.0 SP3 for Exchange available for Download (http://www.blackberryforums.com/bes-admin-corner/17902-bes-4-0-sp3-exchange-available-download.html)

jnelson2000 10-25-2005 04:15 PM

BES 4.0 SP3 for Exchange available for Download
 
https://www.blackberry.com/Downloads...93E4F3BB068C22

jibi 10-25-2005 07:42 PM

good looking out, j. i will post up the release notes when i get a free moment tonight. odd that they would remove SP2 from download.

jibi 10-25-2005 08:55 PM

Functional changes
automatic time zone mappings
The BlackBerry Enterprise Server now automatically maps time zones not supported by CDO. (SDR 54867)

Microsoft PowerPoint® slide support
The BlackBerry Attachment Service now enables users to view files in slide show format on the BlackBerry device. Viewing Microsoft PowerPoint slide show files requires BlackBerry Device Software 4.1 and BlackBerry Enterprise Server 4.0 SP3.

Fixed issues
BlackBerry Attachment Service
SDR 65573
Previously, if users attempted to use the Retrieve Info command on a Corel® WordPerfect® attachment on their BlackBerry device, it resulted in the BlackBerry Enterprise Server using an increased percentage of system resources, and did not produce an error message.

BlackBerry Handheld Configuration Tool
SDR 54570
Previously, if you provisioned a BlackBerry device at the administration computer using the BlackBerry Handheld Configuration Tool and configured message prepopulation in the BlackBerry Manager, all messages, instead of the number of messages that you configured, prepopulated to the BlackBerry device.

BlackBerry Manager
SDR 55763
Previously, if you had an environment with multiple BlackBerry Enterprise Servers, and added a user on one BlackBerry Enterprise Server, the BlackBerry Manager caused the configuration databases on all BlackBerry Enterprise Servers to reload.

SDR 50393
Previously, if you configured the BlackBerry Manager to refresh the user list automatically, and a user property window was open when an automatic refresh occurred, the BlackBerry Manager closed unexpectedly.

SDR 46334
Previously, if you added three 5-user small business edition (SBE) licenses to the BlackBerry Manager and applied a 5-user SBE upgrader license, the upgrader did not upgrade the licenses and an error message appeared in the BlackBerry Manager.

BlackBerry Messaging Agent
SDR 60531
Previously, if users created a contact in Microsoft Outlook® with an email type other than SMTP, synchronized the BlackBerry device and desktop computer using the BlackBerry Desktop Software and then performed a wireless synchronization, the contact in Outlook changed to SMTP.

SDR 53433
Previously, if a user set the desktop computer to one of several specific time zones, the BlackBerry Enterprise Server did not send the time zone index to the BlackBerry device.

SDR 959
Previously, if a user forwarded a message from the BlackBerry device to the desktop computer, the message received on the desktop computer contained the sender address instead of the display name in the message header.

BlackBerry Mobile Data Service
SDR 61758
Previously, the BlackBerry Mobile Data Service misinterpreted the PGP key creation date format when retrieving the PGP key status for a BlackBerry device. As a result, in certain circumstances, when a user tried to view the PGP key status on the BlackBerry device a warning indicated that the PGP key creation date was set to a date in the future and that the BlackBerry device date and time setting might be incorrect.

SDR 60482
Previously, in certain circumstances, when a user tried to retrieve the status of a certificate using the certificate revocation list (CRL) method, an internal proxy provider error appeared on the BlackBerry device and the updated certificate status was not retrieved.

SDR 55798
Previously, in the BlackBerry Manager, you configured the Push Server Connection Listen Port as the port that the Mobile Data Service listened on to receive push requests. Push requests now route through the Web Server Listen Port. The Push Server Connection Listen Port setting is no longer in the BlackBerry Manager.

BlackBerry Policy Service
SDR 65058
Previously, if the connection to the Configuration Database was lost, the BlackBerry Policy Server might have stopped responding.

SDR 62840
Previously, if you upgraded to BlackBerry Enterprise Server 4.0 and had an environment with multiple instances of BlackBerry Enterprise Server 3.6 and an IT Policy restricting the use of other messaging services, the users were no longer able to send messages from the BlackBerry device.

BlackBerry Router
SDR 42551
Previously, in certain circumstances, the BlackBerry Router did not start correctly after it was restarted.

BlackBerry Synchronization Service
SDR 58902, SDR 58900
Previously, in certain circumstances, if the configuration database stopped responding, certain configuration database errors might have caused the BlackBerry Synchronization Service to incorrectly add contacts on or remove contacts from the BlackBerry device.

SDR 57470
Previously, when you added a user to the BlackBerry Manager, and then activated the user wirelessly, the initial synchronization of PIM data to the BlackBerry device did not complete successfully until you restarted the Synchronization Service.

SDR 56240
Previously, if the Synchronization Service was turned off, the SRP connection to the BlackBerry Dispatcher was not stopped. Users started up incorrectly and user threads might have become non-responsive when you restarted the Synchronization Service.

SDR 49239
Previously, if you created a calendar appointment in Microsoft Outlook and performed a wireless synchronization with the BlackBerry device, and after synchronization, you deleted the appointment on your device, the appointment did not delete in Outlook.

Configuration database
SDR 66711
Previously, when you tried to update a user PIN to 0 and it coincided with an update of another user to 0 the configuration database would not accept the update.

Setup program
SDR 62121
Previously, in certain circumstances, when you upgraded from BlackBerry Enterprise Server 4.0 to SP2, the setup program did not create BlackBerry Messaging Agents.

SDR 61394
Previously, when you performed any upgrade to the BlackBerry Enterprise Server, the BlackBerry Mobile Data Service statistics and status web page did not display and the Mobile Data Service log file did not properly show the resource string. The upgrade did not remove the Tomcat library files from the previous BlackBerry Enterprise Server installation.

SDR 55259
Previously, when you upgraded the BlackBerry Enterprise Server 4.0 SP1 to 4.0 SP2 on a computer running Windows 2003 SP1, the upgrade did not complete successfully and an error message appeared.

SDR 54868
Previously, if you upgraded the BlackBerry Enterprise Server from version 4.0 or earlier, users could not view Microsoft PowerPoint attachments on the BlackBerry device.

SDR 37643
Previously, if you ran the setup program using an account that contained accented characters, after you provided the Windows login information, the setup program stopped responding.

Wireless calendar synchronization
SDR 67423
Previously, in certain circumstances, when you upgraded from BlackBerry Enterprise Server 3.6 SP 3 or later to 4.0, the BlackBerry Enterprise Server could have sent duplicates of exceptions to recurring appointments to a user BlackBerry device.

SDR 57219
Previously, on certain BlackBerry Connect™ devices, when a meeting organizer sent an updated meeting request from the BlackBerry device, and the attendee accepted the meeting request, the attendee status did not synchronize to the meeting organizer’s desktop computer correctly.

SDR 55928
Previously, in certain circumstances, when a user tentatively accepted a meeting request, the status of the meeting displayed as Busy.

SDR 55112
Previously, in certain circumstances, if a user declined a recurring appointment, the BlackBerry device displayed the incorrect date that the user declined the appointment.

SDR 45992
Previously, in certain circumstances, when an organizer sent a meeting request from the desktop computer to a BlackBerry device, the status of the meeting request always displayed a Busy status as Tentative on the BlackBerry device.

SDR 42689
Previously, when a user updated an occurrence of a recurring all day appointment from one time zone to another time zone on the BlackBerry device, the appointment did not update correctly in Outlook if the BlackBerry device and user desktop computer were situated in different time zones.

Wireless enterprise activation
SDR 61643
Previously, if a user had an encryption key and attempted to perform a wireless enterprise activation, the password might have reset with an expiry time set to 1970.

Wireless message reconciliation
SDR 57467
Previously, in certain circumstances, if you added a disclaimer text message in the BlackBerry Manager, then attempted to delete the disclaimer, the text still displayed in messages that were sent from BlackBerry devices.

Wireless PIM synchronization
SDR 65992
Previously, if a user created a contact with no first or last name on the BlackBerry device when the wireless transceiver was off, and then the user turned the wireless transceiver on, the contact might have appeared with a blank name in Microsoft Outlook.

SDR 64271
Previously, if a user created a contact on the BlackBerry device, and tried to use that contact in Microsoft Outlook to send a message, an Operation failed error message appeared in Outlook.

SDR 57257
Previously, after applying BlackBerry Enterprise Server 4.0 SP1 hotfix 3,an increase in nonresponsive threads might have occurred.

SDR 57254
Previously, if a user created a task on the BlackBerry device, the owner property field contained the SMTP address rather than the display name of the owner.

SDR 54899
Previously, during wireless enterprise activation, the initial synchronization process failed to complete successfully.

SDR 46252
Previously, when you changed a user device using the BlackBerry Desktop Software, the initial load of BlackBerry device data was not loaded on the BlackBerry device when the user used the serial connection.

Known issues
Key issue
SDR 62174
When you upgrade the BlackBerry Enterprise Server from 4.0 SP1 to 4.0 SP2 the setup program does not back up the configuration database when the Backup Database check box is selected.

Workaround: You must manually backup the configuration database before beginning the upgrade.

BlackBerry Attachment Service
SDR 56666
In certain circumstances, Acrobat version 1.3 PDF attachments that third-party applications generate might not display correctly
on the BlackBerry device.

SDR 51971
Attachments that contain Czech characters might not display correctly on the BlackBerry device.

SDR 44322
If the registry key (located in HKLM\SYSTEM\CurrentControlSet\Services\BBAttachSer ver\Parameters\EnableLog) is not set to 5, the BlackBerry Attachment Service and Attachment Conversion logs do not generate.

BlackBerry Handheld Configuration Tool
SDR 55224
In certain circumstances, the BlackBerry Handheld Configuration Tool does not correctly display branch information on the configuration tab.

Workaround: Re-index the BlackBerry device software that does not display correctly on the configuration tab. See the BlackBerry Enterprise Server Handheld Management Guide for more information.

SDR 52705
If you turn off TCP/IP on the BlackBerry Configuration Database or connect to a port other than the default port (1433), you cannot open the Handheld Configuration Tool.

SDR 52601
If the For fast searching, allowing Indexing Service to index this folder check box is not selected in the PackageCache folder properties on the BlackBerry Enterprise Server, third-party applications might not be delivered wirelessly to BlackBerry devices successfully.

Workaround:
1. On the computer on which the BlackBerry Enterprise Server is installed, browse to C:\Program Files\Research In Motion\BlackBerry Enterprise Server\.
2. Right-click the PackageCache folder
3. Click Properties.
4. Click Advanced.
5. Select the For fast searching, allowing Indexing Service to index this folder check box.

BlackBerry Manager
SDR 61515
If you move users from one BlackBerry Enterprise Server to another in the BlackBerry Manager, and then you check the list of users on the target BlackBerry Enterprise Server, the list might show only the users that you moved.

Workaround: Manually refresh the list.

SDR 58927
In certain circumstances, if you remove users in the Active Directory in Microsoft Exchange and then in the BlackBerry Manager, additional users removed are also removed from the BlackBerry Manager.

SDR 57440
In certain circumstances, if you add a user, and then you refresh the BlackBerry Manager, the user creation time statistic displays as Not Available.

SDR 55528
If you view users in the BlackBerry Manager on BlackBerry Enterprise Server 3.6, the user IT policy statistics do not display.

Workaround: Open the Properties window for the user to view the IT policy statistics.

SDR 52033
If you open the BlackBerry Manager in an environment with a BlackBerry Enterprise Server 3.6 and a BlackBerry Enterprise Server 4.0 configuration database, and you do not have administrative permissions on all the Microsoft Exchange Servers that contain BlackBerry users, the BlackBerry Manager might close.

SDR 42694
If, in the BlackBerry Manager you turn off S/MIME encryption for signed and weakly encrypted messages, you must restart the BlackBerry Enterprise Server for the changes to take effect.

BlackBerry Messaging Agent
SDR 64054
In certain circumstances, the BlackBerry Messaging Agent might stop responding when it attempts to decode too large a message.

SDR 61523
In certain circumstances, setting a mailbox name to null can cause the BlackBerry Enterprise Server to stop responding.

SDR 61010
If messages generate a network error during BlackBerry Enterprise Server prepopulation of the message queue, the messages that generated an error might not be queued during a rescan and might not be sent to the BlackBerry device.

SDR 60316
If problems occur with the connection to the SQL database, the BlackBerry Messaging Agent might stop responding.

SDR 58886
If a user has 0 or null for a PIN an unnecessary error message might be logged in the BlackBerry Enterprise Server policy logs.

SDR 56128
In certain circumstances, if the Microsoft SQL Server computer on the which the configuration database exists stops responding, the Messaging Agents might also stop responding.

Workaround: Restore operation to the Microsoft SQL Server computer and restart the BlackBerry Controller.

SDR 53669
When a user sends a message with foreign characters from a BlackBerry device, the characters do not display correctly on web mail accounts.

SDR 53494
If you restart the BlackBerry Enterprise Server, the TimerHealth thread might not start correctly for a user, and the user cannot send messages from or receive messages on the BlackBerry device.

Workaround: Restart the BlackBerry Controller.

SDR 50786
In certain circumstances, if a user copies a message in Microsoft Outlook to a folder that is redirected to the BlackBerry device, the message might not be delivered to the BlackBerry device.

BlackBerry Mobile Data Service
SDR 69404
The BlackBerry Mobile Data Service might stop responding if the connection to the configuration database is lost.

SDR 67424
The version number of the BlackBerry Mobile Data Service does not display in the logs.

SDR 33227
SNMP traps for the Mobile Data Service do not appear correctly in a SNMP trap viewer.

BlackBerry Policy Service
SDR 70023
When you apply an IT policy, it immediately displays as Applied successfully, regardless of the actual status.

Workaround: View the Time received field to see when the user’s BlackBerry device received the IT policy.

SDR 61943
After you upgrade to BlackBerry Enterprise Server 4.0 or later, an error message appears indicating that you cannot delete the existing IT policy because users are still assigned to the policy, even when there are no users assigned to the policy.

Workaround: Delete the user manually from the PolicyUsers table using the following script:
Delete FROM PolicyUsers
Where UserMailboxDN=’mailboxDN’

SDR 61608
If you set a policy in the Smart Dialing IT policy group, the BlackBerry Policy Service does not retain the settings when you close the window.

SDR 61188
The BlackBerry Policy Service provides an extraneous log line for all users after already producing a log line for a specific user when polling them for missing applications.

Configuration database
SDR 49638
When you turn on peer-to-peer encryption on BlackBerry Enterprise Server 4.0, users on BlackBerry Enterprise Server 3.6 who are connected to the same 4.0 configuration database cannot send PIN messages to users on BlackBerry Enterprise Server 4.0.

SDR 48851
If multiple BlackBerry Enterprise Servers connect to a single configuration database and multiple BlackBerry Routers, the BlackBerry Enterprise Server might send incorrect BlackBerry Router information to BlackBerry devices.

Setup program
SDR 59427
If you upgrade the BlackBerry Enterprise Server while logged on using a different account than the account that you used to create the existing configuration database, the upgrade does not complete successfully and an error message appears.

SDR 58916
When you install the BlackBerry Enterprise Server, if XML Core Services (MSXML) 4.0 is not installed on the computer, the Policy Service fails to start and displays an error message.

SDR 58204
If you upgrade a BlackBerry Enterprise Server that uses a remote BlackBerry Router from 4.0 SP1 to 4.0 SP2, the Router Host field changes to localhost from the remote BlackBerry Router.

SDR 54329
When you install or upgrade the BlackBerry Enterprise Server, if the BlackBerry Enterprise Server name contains one or more spaces, the BlackBerry Enterprise Server cannot connect to the Messaging Agent, and messages do not redirect to BlackBerry devices.

SDR 43010
If you upgrade the BlackBerry Enterprise Server to any version of 4.0 and have the Windows Services window open during the upgrade, the BlackBerry Controller and BlackBerry Dispatcher are removed.

Workaround: Close the Windows Services window before the upgrade.

SDR 40956
When you upgrade the BlackBerry Enterprise Server, user-defined log levels are not preserved during the upgrade.

Workaround: Redefine the log levels manually.

Wireless calendar synchronization
SDR 65168
In certain circumstances, if a user creates a non-recurring appointment in Microsoft Outlook and the appointment information is synchronized wirelessly to the BlackBerry device, the time zone information in the appointment on the BlackBerry device might be incorrect.

SDR 64327
If a meeting invitee prints a meeting request with the location, time, and day of the meeting in the Notes field, the list of attendees does not print.

SDR 64139
When a BlackBerry device and desktop computer are set to the following time zones, appointments that users create on the BlackBerry device display one hour early in Microsoft Outlook:
• Beijing, Hong Kong (UTC +8)
• Irkutsk (UTC +8)
• Kuala Lampour (UTC +8)

Workaround: Downgrade to BlackBerry Enterprise Server 4.0 SP1.

SDR 58220
In certain circumstances, when a meeting organizer receives accepted meeting requests, the When field does not display correctly.

SDR 55785
If, in Microsoft Outlook, an attendee declines or tentatively accepts an appointment occurrence in a recurring set of appointments after accepting the recurring set of appointments, the meeting request status does not update in the organizer’s calendar.

Workaround: Turn off wireless message redirection for the organizer, and the calendar updates as expected.

Wireless enterprise activation
SDR 60780
Expired wireless enterprise activation passwords might be copied to the Configuration Database and overwrite newer passwords, which might result in passwords being used more than once.

SDR 37897
In certain circumstances, if you assign and activate two different users that both use the same configuration database on separate BlackBerry Enterprise Servers, the PIN for the users might not synchronize correctly between the desktop computer and the configuration database.

Wireless PIM synchronization
SDR 60975
MAPI errors might cause problems in constructing a user folder list on the BlackBerry device and might result in other PIM synchronization issues.

Workaround: Restart the BlackBerry Controller.

HaTaX 10-25-2005 11:13 PM

Great post jibi! I actually downloaded this at the office and had it applied by 4pm.. Will be great to see the 7100i come up in handheld manager and also be able to use desktop bluetooth sync now for our users..

lenemery 10-26-2005 05:21 AM

2003 exch sp2 working ok so far w bes sp3

exiled 10-26-2005 09:30 AM

Does anyone forsee any issues going from 4.0.1 right to SP3? Or should i install SP2 first, bring it up succesfully, then install SP3.

Thoughts?

LAW 10-26-2005 09:43 AM

My assumption is that the Service Packs are cumulative. They seem to represent a full installation, not just a change file, and the documentation for each "service pack" is simply the basic server installation guide.

I am shifting gears to skip SP2 and go straight to SP3, so if this is wrong, I need to find out soon.

Also, if the assumptions are correct, does anyone have a feel for whether we should be uninstalling SP2 first or entirely rebuilding the server, or is simply installing over the top of SP2 adequate?

We cannot have any chance of experiencing the problem reported in this article:
http://www.infomaticsonline.co.uk/vn...hes-blackberry

jibi 10-26-2005 10:51 AM

SP3 will contain the fixes and updates found in SP1 and SP2 and the hotfixes in between. The download you get off their general Service Packs download site is the upgrade only (besxU_4.0.3.exe). Just run setup.exe and it upgrades your installation (not to be confused with upgrade.exe). If you look at the SQL scripts included, you'll see that it includes things such as 'SchemaTweak40x.sql' where 'x' is the number for each of the service packs (just an example, as I'm sure there is more to it than one SQL script for the cumulative upgrades).

If you want the full version, you can contact TSupport and request it - they should respond with temporary access to the full version (besx_4.0.3.exe). The latter can be installed without the requirement of BES 4.0 being installed already; otherwise, you will be prompted during installation that 4.0 needs to be installed before applying the upgrade.

LAW, I think that one-in-how-many-ever-thousands of installations of BESX 4.0 is nothing to be worried about, to be honest. The odds are on your side (unless you're a Murphy's Law kind of company, in which case...). :-)

LAW 10-26-2005 11:16 AM

Thanks for the detailed reply, Jibi! Very helpful.

BlackBerry definitely has some egg on their faces from this one, but you are right (as I pointed out in a different thread), no need to think the sky is falling.

I'm not worried that we will have the problem, but I am going to have to defend my decision on how to handle the patching given the nature of the BBC issue.

We aren't a Murphy's Law kind of place, but we definitely what I will call a LAW's law kind of place: "If anything bad can happen, no matter how unlikely, you'd better have a long list of reasons why it won't happen to us, and 2 backout plans in case you're wrong."

Makes for fun meetings.

Natrone 10-26-2005 12:57 PM

FYI, SP2 was removed from their site because of a huge flaw in which unintended recipients were receiving mail on their blackberry's from their coworkers.
http://networks.silicon.com/mobile/0...9153677,00.htm

jibi 10-26-2005 01:12 PM

Quote:

Originally Posted by Natrone
FYI, SP2 was removed from their site because of a huge flaw in which unintended recipients were receiving mail on their blackberry's from their coworkers.
http://networks.silicon.com/mobile/0...9153677,00.htm

are you speculating that is the reason SP2 was removed or does it actually say it somewhere in that article that i simply overlooked? they still have SP2 available for download on their FTP, so...

also, 'huge flaw' would mean more than probably less than 1% of 1% of 1% of their total users. it was a circumstantial issue that had only been reported ONCE, and it was due to an error thrown at the BES by their Exchange servers not the BES itself. i'm sorry, but calling that 'huge' is a bit of an exaggeration, and thats being polite.

BB Junkie 10-26-2005 01:20 PM

Which do you guys install first: Exchange 2003 SP2 then BES 4.0 SP3 or vice versa?

jibi 10-26-2005 01:50 PM

vice versa - BES 4.0 SP3 then Exchange 2003 SP2.

juwaack68 10-26-2005 02:45 PM

Quote:

Originally Posted by jibi
vice versa - BES 4.0 SP3 then Exchange 2003 SP2.

I was on the phone yesterday with RIM support and was told that they are not supporting Exchange 2003 SP2 yet...only SP1. Just a heads-up.

jibi 10-26-2005 04:47 PM

Quote:

Originally Posted by juwaack68
I was on the phone yesterday with RIM support and was told that they are not supporting Exchange 2003 SP2 yet...only SP1. Just a heads-up.

http://www.blackberry.com/knowledgec...00935&vernum=1

Quote:

This behavior will be addressed in BlackBerry Enterprise Server 3.6 Service Pack 7 and BlackBerry Enterprise Server 4.0 Service Pack 3.
i would assume that with the release of BESX 4.0 SP3 and Exchange 2003 SP2, RIM is now supporting the latter in conjunction with the prior.

sejinro 10-26-2005 04:49 PM

Thanks. The upgrade went smooth.

jibi 11-03-2005 07:41 PM

anyone else have the ALRT logs fill up to GIGS and GIGS (averaging 15-20GB/day here only on one server)...? i didn't reboot after the upgrade, but i just rebooted and the issue has disappeared.

dev 11-04-2005 06:30 AM

Funny thing happened....I upgraded BESX to BESX v4.0.3, had to redo my BES Alert config...seems to be a normal thing now.
While testing my BESAlert settings (stopped SQL server, and some other services) I generated over 300 alert messages. Never saw that many messages generated before. Also my logs were growing very quickly during that time. I attempted to purge all the pending messages, removed the BESAlert settings...but the they were still being generated....very strange I thought. I did a total shutdown and restart.
The messages stopped...I redid the BESAlert settings and it has been normal ever since.

jibi 11-04-2005 11:44 AM

Well, the odd thing is with me... I don't have alerts configured at all. We use other forms of SNMP monitoring for alerting, so no need in using the built-in solution. I'm thinking about just disabling it, but I haven't researched to see if that'd cause any issues. I had to take a file splitter and split up the entire 15GB file into 20MB parts just to see the issue.

I guess my new rule of thumb is to reboot no matter if it tells me to or not.

jrbes 11-04-2005 12:11 PM

I was just contacted by my BES Acct Manager and told NOT TO INSTALL SP3! There will be something coming out later today in regards to it, I will post what I hear.

I only installed it in test, luckily.


All times are GMT -5. The time now is 09:26 AM.

Powered by vBulletin® Version 3.6.12
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.