BES 4.1 for Exchange - Now Available to TSupport Customers
If the BlackBerry Policy Service checks to determine if the applications on a user’s BlackBerry device require an upgrade while the BlackBerry Configuration Database is unavailable, the policy service cannot retrieve the user’s configuration information and might be restarted by the BlackBerry Controller.
If a user downloads a Java™ Application Download (JAD) file using the BlackBerry Browser, in certain circumstances, the file size might display as zero bytes. The uses might not be able to see the JAD file size prior to downloading.
Workaround: Use the Wireless Application Protocol (WAP) Browser to download a JAD file.
BlackBerry Collaboration Service
If your instant messaging environment is Novell® GroupWise® Messenger, when several events occur in rapid succession, one of the events might not display correctly in the enterprise messenger (for example if a user closes a conversation in enterprise messenger while a user in the conversation changes their status, the status change does not appear).
Workaround: Log out and log in to enterprise messenger.
If your instant messaging environment is IBM® Lotus Sametime®, if you shorten the Idle Timeout value from the default, sessions might not become available when expected. If your Maximum Simultaneous Sessions value is also lowered from the default, users might not be able to log in to their enterprise messenger.
If your instant messaging environment is Microsoft® Live Communications Server, when a user invites multiple users to a group conversation, the first invitee appears to join the conversation and then immediately leave, but never receives the invitation to join and cannot participate. The second and subsequent invitees receive the invitation and can join the conversation successfully.
Workaround: When inviting users to a conversation, invite them sequentially and type a message to each user before inviting the next user.
If your instant messaging environment is Microsoft Live Communications Server, occasionally when you install or upgrade the BlackBerry Enterprise Server, the BlackBerry Instant Messaging Connector Service does not start automatically.
Workaround: Using Microsoft Windows® Services, manually start the BlackBerry Instant Messaging Connector Service.
If your instant messaging environment is Sametime, when a user adds a contact in their desktop instant messaging client whose name contains special characters, the contact name displays incorrectly. If the same user adds the same contact in the enterprise messenger, the contact name displays correctly. Both the correct and incorrect contact names are included in the user’s Buddy List.
BlackBerry Configuration Database
If your database environment is Microsoft SQL Server and you attempt to install the BlackBerry Database Notification System on a named instance, the installation complete successfully but the BlackBerry Database Notification System is not operational.
Workaround: Install the BlackBerry Database Notification System on only the default instance of Microsoft SQL Server.
BlackBerry Configuration Panel
If you attempt to use the configuration panel to create a new configuration database, an error message displays ("Database connection lost. Please test connection again with a valid User ID and Password to be able to access configuration settings from the database."). This error message should not display as the connection cannot be made to a database that does not yet exist.
Workaround: Click OK and then follow the on-screen prompts to create the new configuration database.
BlackBerry Instant Messaging for Microsoft Live Communications Server
If users copy a conversation history into an enterprise messenger conversation, an “ArrayIndexOutOfBounds” error message appears.
If users attempt to switch conversations using the message indicator, a “message queue overflow” error message appears.
If users delete a contact, a “message queue overflow” error message might appear and they are signed out of enterprise messenger.
BlackBerry Instant Messaging for Novell GroupWise Messenger
If users delete a contact that appears in multiple groups, that contact is only deleted in the group from which they deleted it. If the contact appears in other groups, users cannot modify or delete that contact. Users cannot send an instant message to that contact unless that contact sends a message to them first.
If users attempt to edit the “GroupWise” folder, a “Command Failed” error message appears.
If users are in a conversation with a contact and they delete that contact, the conversation is deleted as well.
If users are using enterprise messenger in a language other than English, the custom status option does not appear when setting a status.
If users are in a conversation with a contact who does not appear in their contact list, and they delete that conversation, but the contact continues to send instant messages, an “Uncaught exception” error message appears.
If users are using a BlackBerry device with BlackBerry Device Software version 4.1, the enterprise messenger typing indicators and message-received pop up messages might not appear.
If users type a URL into an enterprise messenger conversation, and their contact is using enterprise messenger on their
BlackBerry device, the contact receives the URL with a smiley icon in it.
BlackBerry Instant Messaging for Sametime
If users have groups that differ only by capitalization (for example, AA, aA, and aa), those groups might not display properly.
If users attempt to log in to Enterprise Messenger using a password that is greater than 100 characters, they receive a “SametimeError:80000001” error.
If a user is using the desktop client and is in two separate conversations with two contacts, and tries to invite contact 2 to join a conference with contact 1, contact 2 never receives a conference invitation. Instead the conversation between the user and contact2 were having turns into a conference.
If users log in to enterprise messenger, presence notification is turned off on their email client.
The device administrator role is not able to assign a BlackBerry device to a user.
Workaround: Start the BlackBerry Manager using the security or enterprise administrator role and assign a BlackBerry device to a user.
The junior help desk administrator role is able to assign device policies for BlackBerry MDS Studio Applications to BlackBerry devices.
If you used an earlier version of the BlackBerry Manager to set WLAN, VPN, or VoIP IT policy rules to specify user names and passwords, those IT policy rules cannot be edited or completely removed as they no longer appear in the BlackBerry Manager.
Workaround: Use the per-user IT policy rule to specify user name and password values. These settings override any earlier user name and password values.
If you set the Disclaimer Text option to automatically include a standard disclaimer that exceeds the limit of 5000 characters, no error message appears.The disclaimer text is not successfully added, and the Disclaimer Text field is empty when reopened.
Workaround: Set the disclaimer text to 5000 characters or less.
If you create a new global or user filter rule without specifying any conditions for the filter, a warning dialog box appears. If you do not close the dialog box and then close the filter screen window, the BlackBerry Manager silently stops responding.
If you create a filter in a Group template, save and close the Group template, and then re-open the Group template, the filter might not display the values that you set.
If you create multiple user groups with at least one user in each group and then move the groups to a new BlackBerry Enterprise Server that uses the same configuration database as the original BlackBerry Enterprise Server, only the user(s) in the first user group move successfully to the new BlackBerry Enterprise Server.
Workaround: Move user groups to a new BlackBerry Enterprise Server one at a time.
In certain circumstances, XML parsing removes extra spaces in data type strings entered in the BlackBerry Manager.
BlackBerry MDS Runtime
SDR 81793, SDR 81577, SDR 81180
If an error occurs in a BlackBerry MDS Studio™ Application (for example, a security violation resulting from a policy change) while the application is accessing data stored on the BlackBerry device, the application might not be able to retrieve that data again and might terminate unexpectedly.
SDR 56784, SDR 58847
If users run the BlackBerry MDS Runtime on BlackBerry Device Software version 4.0, they might experience the following issues:
• The font assigned to an editbox is ignored (for example, phone, messages).
• Edit boxes display as the same height regardless of the font.
• The font color assigned by a style is ignored on a text field with active text (for example, messages, phone, URL, etc.)
BlackBerry MDS Services
If you remove a user from the BlackBerry Enterprise Server, their BlackBerry device continues to be listed in the BlackBerry MDS Services as a registered device and BlackBerry MDS Studio Applications on their BlackBerry device continue to remain active.
The BlackBerry MDS Services URL does not include the fully-qualified domain name of the computer on which it is installed, so notifications cannot be sent to the BlackBerry MDS Services. You cannot specify this computer name during the setup program and you cannot modify the computer name in the BlackBerry Manager.
If a user deletes a BlackBerry MDS Studio Applications from the BlackBerry MDS Control Center and then restores the application to their BlackBerry device using the BlackBerry Desktop Manager, the BlackBerry MDS Service still considers the application as being deleted. You cannot administer this application in the BlackBerry Manager and users cannot send or receive information in the application.
If you specify a BlackBerry MDS Studio Application as required and push the application to users’ BlackBerry devices, the BlackBerry MDS Services delivers the application as recommended and users are prompted to agree to the installation.
If the connection to the configuration database becomes unavailable and then is restored, you cannot administer instances of the BlackBerry MDS Services from the BlackBerry Manager.
Workaround: Using Microsoft Windows Services, restart the BlackBerry MDS Services - Apache Tomcat Service.
BlackBerry Policy Service
If the connection to the configuration database becomes unavailable and then is restored while the policy service is creating XML-based service books, the policy service might be restarted by the BlackBerry Controller.
The policy service logs a common event (“Instantiated a PackageDB object”) at a higher level than necessary.
If the network connection between the BlackBerry Enterprise Server and the configuration database is unfavorable, the BlackBerry Policy Service might use increased system resources when determining whether users require upgrades to the applications on their BlackBerry Devices.
When you remove an instance of the BlackBerry MDS Services, some settings remain on the computer. If you install an instance of the BlackBerry MDS Services on the same computer, the setup program might attempt to perform an upgrade instead of an installation and the process does not complete successfully.
1. On the server where you host the BlackBerry Enterprise Server, start the Registry Editor.
2. In the left pane, browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Uninstall.
3. Right-click the BlackBerry MDS Services key.
4. Click Delete.
5. Click Yes.
SDR 81949, SDR 64753
If your database environment is Microsoft SQL Sever and you install the Microsoft SQL Server on the same computer on which you plan to install the BlackBerry Enterprise Server using a custom instance name for the database server, the setup program does not recognize the local installation and prompts you to either install MSDE or to use a remote Microsoft SQL Server.
If your database environment is Microsoft SQL Server and you attempt to install the BlackBerry Enterprise Server using the minimum required database permissions, the installation does not complete successfully.
Workaround: Give the account under which you are installing the BlackBerry Enterprise Server system administrator permissions on the database server.
If this is not possible in your environment, create the configuration database before installation with the CreateDB tool and using an account with system administrator permissions. After you create the configuration database, install the BlackBerry Enterprise Server using an account with the minimum required permissions.
If your database environment is Microsoft SQL Server and you attempt to install the BlackBerry MDS Services on a named instance, the installation does not complete successfully.
Workaround: Install the BlackBerry MDS Services databases on only the default instance of Microsoft SQL Server.
When you install the BlackBerry MDS Services, the setup program permits you to use the same name for both of the databases and does not warn that this is an error.
If you copy the BlackBerry Enterprise Server installation media to a folder that contains non-basic ansi characters, the setup program does not continue after the computer restarts.
Workaround: Copy the installation media to a folder that does not contain ansi characters.
If this is not possible in your environment, click the Setup.exe file to continue the setup program.
If your database environment is Microsoft SQL Server, the setup program provides you with the download location of the Microsoft SQL Server 2005 Java Database Connectivity (JDBC) driver regardless of the version of Microsoft SQL Server in your environment.
Workaround: See the BlackBerry Enterprise Server Version 4.1 Installation Guide for more information about the download location of the Microsoft SQL Server 2000 JDBC™ driver.
If you specify network folders for the configuration database data and log files, the BlackBerry MDS Service database installations do not complete successfully.
Workaround: Use the local folders listed by default for the database settings.
If you are installing BlackBerry Enterprise Server with BlackBerry MDS Services and you press ENTER instead of clicking Finish on the last screen of the setup program, the required post-installation tasks do not complete.
When upgrading the BlackBerry Enterprise Server with BlackBerry MDS Services, the BlackBerry MDS Services might start after the BlackBerry Enterprise Server restarts during the upgrade and the setup program cannot complete successfully.
Workaround: In Windows Services, manually stop the BlackBerry MDS Services after the BlackBerry Enterprise Server restarts.
You cannot install the BlackBerry Enterprise Server to a folder name that contain unicode characters.
If the setup program cannot update the BlackBerry Services (for example, if you install the BlackBerry Enterprise Server on a computer where the BlackBerry Enterprise Server was previously installed, or if you install a service pack or hotfix) an “Error 1923” message displays, the update process does not complete, and the BlackBerry Services cannot start.
Wireless calendar synchronization
In certain circumstances, if a meeting invitee declines an instance of a recurring meeting that occurs in a different daylight saving time status (for example, if the current date is not daylight saving time and the invitee declines a meeting that occurs during daylight saving time), the organizer receives the update on their BlackBerry device as a message instead of a meeting response and the invitee status remains “Invited”.
In certain circumstances, if your environment is configured with the messaging server over a wide area network (WAN) with the BlackBerry Enterprise Server, calls for calendar items and messages might result in hung threads that force the BlackBerry Messaging Agent to restart.
In certain circumstances, if the BlackBerry Enterprise Server starts after a large number of calendar items have been created and accepted, when the BlackBerry Enterprise Server detects the events and begins to queue the events to the BlackBerry device, the BlackBerry Enterprise Server might stop responding.
In certain circumstances, if a user creates a recurring appointment in one time zone on the BlackBerry device, and the user’s desktop email program is in another time zone, the appointment does not appear in the desktop email program.
In certain circumstances, if a user modifies the recurrence pattern of a recurring meeting, when the updated meeting requests are sent to the invitees, error messages appear in the messaging agent logs.
has to be asked...
worth going from 4.0.3 to 4.1? Looks like alot of fixes! Also would SP4 need to be installed before upgrading to 4.1 or is this cumulative like the rest?
And why doesn't this address the issue when changing the time of a calendar item in outlook sync issue?
This would be a huge improvement for me. Right now, I have no access to our BES. If I need a end-users password reset, I have to submit a NEW ticket to have another team reset it for me. If I can get added to the new Senior Help Desk role I would be able to do so much more in half the time.
Also available as a $999 "one time upgrade"
At the bottom of the page.
I'm pulling our test server from our production pool and reinstalling it as a base installation of 4.0.4, adding myself to it and verifying everything is working (post-security wipe), then documenting processes for a straight upgrade to 4.1 from there. If there are any complications, I'll be sure to add my documentation steps here.
Looks like I'm going to be alone tonight - not going to let the girlfriend come over (how horrible is that?!)... heh.
If someone is able to verify if Unity voicemails can be listened to as rumored, I'd be interested to know.
have you looked into the BlackBerry add-in for Unity 4.1? from what i've read, it sends a link to the user's handheld/email when they receive a VM. when they click on the link (connects to the server via MDS), they are asked for a callback number in which the server uses to call them to listen to the VM. kind of nifty, but requires network coverage, obviously (although, to be fair, any attachment would as well).
anyhow, i should have this up and running tonight/tomorrow.
For those who are going to order the 4.1 update or the support, once you order it takes 3-5 business days to actually get access to the software. That stinks.
I've upgraded to 4.1 a few hours ago.
I don't have the collaboration service installed which is needed to configure the LCS and enterprise messaging options I want. I don't see how to install the collaboration service either. During setup when it got to IM, the only options were groupwise or sametime, no LCS. So that is one issue for me.
The second is that I have unity send the .wav vm to users and still can't open the .wav attachment. I understand there is more integration coming out with unity but i'd rather not have to follow a link to play .wavs if I can get it working now just by opening the attachment. I see in the bes now that wav says enabled but when trying to open it says unrecognized doc format. Doesn't seem like a sampling issue.
So those are my two main issues, otherwise the upgrade went smooth and everything is running as before but I love the new interface over the legacy mmc one.
Inphektion, what handhelds are your users using for the WAV files? I believe that the Cingular OS that was issued with the 8700c did not have the ability to open WAV files. I do not think any handhelds other than the 8700c, 7130e and 7100i are capable of opening WAV files, either (ugh!). You may want to try to upgrade one of the handhelds' OS to one of the latest versions from one of the Asian or European carriers (Bharti, etc), if you have an 8700 to test with.
I'm about to do the upgrade now, so I'll write a reply here shortly. For the most part, aside from installing MDAC 2.8 and the hotfix on the SQL server, there have been little to no issues. I'm not really excited about having to install MSMQ, but whatever - it doesn't require installation media or a reboot, for those that have never installed it.
* Edit: LCS was an option for me on my installation, as was GroupWise and Sametime. Just FYI.
..i can't seem to get the client connected to the LCS server, but i'm going to take a look into that tomorrow. i'm a wee bit tired right now. flawless upgrade - no issues at all (of course, it was only in a test environment from 4.0.3 HF3 to 4.1 w/ 1 user on the server).
their documentation for the instant messaging/collaboration services (from client deployment to configuration and troubleshooting), from what i can tell unless i'm overlooking something, is piss-poor, at best.
This is going to take a lot of time getting used to... while everything 'seems' the same from an options/settings standpoint, the interface is COMPLETELY different (in a good way, though).
is 4.1 available for Exchange? I haven't been able to find it. I am a T-Support member.
Been beta testing this for a bit and am downloading the official release now to see if they've improved it at all. General impressions were that it is a huge step forward for those that need role-based administration, hated the mmc console, and think there will be MANY applications requested for the BB platform by their end-users.
MDS was a little tricky to install in Beta (I have a remote SQL server with named instances...the wizard didn't allow for that, but there was a separate MDS install after the wizard completed that allowed me to go back and change it) and I never did get web browsing through the MDS browser to work, but I can't wait to get the GA code installed and poke at it for a week or two before rolling it out (I gotta test first...2400 or so very vocal users). At least now I'll have full T-Support to help work through the little bugs. :)
Can you paste the link to this forum to download 4.1?
I'm confused. You are all saying no more MMC console...but isn't it still going to be available in this version to make the transition easier? If not, that's fine. I am very eager to see the new interface. Just downloaded all the docs and am currently downloading the install file.
I asked RIM about getting unity files played through 4.1, they responded that wav files are not supported.
I wish the Unity addin would be an option, but if it requires a call back, my users wouldn't like it. It would require too many steps for them to do.
On the left, highlight Downloads then Software Downloads Americas and choose it from the drop-down.
And FYI - fixed the LCS issue and am able to login.
User name: DOMAIN\username
|All times are GMT -5. The time now is 04:01 AM.|
Powered by vBulletin® Version 3.6.12
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.