Bes 4.1.7 Mr2
Anyone install MR2, yet, for 4.1.7?
I have not but am getting ready to from BES 4.1.6 MR7. Have you done it yet? Did you run into any issues?
Has one else, reading this thread, gone to 4.1.7 MR2, yet?
Very simple exe to run before installing SP7.
But, what I was more interested in / concerned with are the key known issues which have not been fixed yet. And, they are:
(DT 459588) When a user tries to open a message attachment, a "Cannot initialize COM library" error might display. The user
cannot open the message attachment.
(SDR 301305) If users view a Microsoft® PowerPoint® presentation on the BlackBerry® device, pictures that are included in
background graphics do not display on the first slide when a background color is set.
Workaround: Remove the background color from the first slide of the Microsoft PowerPoint presentation or set a background
color for all slides in the Microsoft PowerPoint presentation.
(SDR 153315) If you upgrade a remote BlackBerry Attachment Service, the maximum file size settings that you configured
change to the default values.
BlackBerry Configuration Database known issues
(SDR 195757) If you rename a remote Microsoft® SQL Server® and you upgrade the BlackBerry® Enterprise Server, the setup
application does not complete successfully.
(SDR 188502) The user statistics and server statistics that are explicity and implicity called might result in a heavy load on
the BlackBerry Configuration Database.
(SDR 187354) If you upgrade from BlackBerry Enterprise Server version 4.1 SP2, the setup application does not complete
successfully if the BlackBerry Configuration Database tables contain non-standard statistics.
Workaround: Run the command "DROP STATISTICS <table_name>.<statistics_name>" on the BlackBerry Configuration
Database and try the upgrade again.
(SDR 173464) If you install the BlackBerry database notification system, a certain SELECT statement might cause multiple
SQL recomputations, which could increase the CPU utilization of the Microsoft SQL Server.
(SDR 171273) If you try to install the BlackBerry database notification system, the installation fails if you have configured more
than one nondefault Microsoft SQL Server.
(SDR 146177) You cannot upgrade the BlackBerry Configuration Database if you turn on database replication.
BlackBerry Controller known issues
(SDR 194218) If the BlackBerry® Messaging Agent requests a restart during a blackout period for the BlackBerry Controller,
the MaxRestartsPerDay registry value increases even though a restart did not occur.
(SDR 192996) The BlackBerry Controller can restart the BlackBerry Messaging Agent one time more than the maximum
number of restarts that you specify using the MaxRestartsPerDay registry key.
(SDR 189482) When the BlackBerry Controller starts, it also restarts the BlackBerry® Enterprise Server and IBM® Lotus®
(SDR 181269) When you move several user accounts to a different BlackBerry Enterprise Server, the BlackBerry Enterprise
Server might report the thread as unresponsive even though it is still working. As a result, the BlackBerry Controller might
restart the BlackBerry Messaging Agent.
(SDR 170295) When the BlackBerry Controller restarts a component of the BlackBerry Enterprise Server, it might cause
debugging activities such as NSD to fail.
BlackBerry Dispatcher known issues
(SDR 356404) If you register the BlackBerry® database notification system and try to create a user account using a senior
helpdesk administrator role, the user account is not created successfully.
Workaround: Uninstall the BlackBerry database notification system and restart the BlackBerry Dispatcher. Add the user
account again using the security role or the BESAdmin account. Restart the BlackBerry Dispatcher whenever you add a new
(SDR 216155) If you upgrade to BlackBerry® Enterprise Server version 4.1 from a multi-instanced BlackBerry Enterprise Server
version 3.6 environment with multiple SRP IDs, and you install a configuration with multiple, chained BlackBerry Router
instances, and then you stop one BlackBerry Router, causing the BlackBerry Enterprise Server to fail over to a secondary
BlackBerry Router, the BlackBerry Dispatcher might process the BlackBerry Router configuration information twice, causing
an access violation error.
(SDR 211397) If more than five data packets are pending for a BlackBerry device that is out of a wireless coverage area, the
BlackBerry Dispatcher might delete any additional data packets, including cancellation packets for messages that the user
deletes from the email application. As a result, messages that have been deleted in the user's email application are delivered
to the BlackBerry device when the BlackBerry device enters a wireless coverage area again.
(SDR 207982) If the BlackBerry Dispatcher fails to write data to the data directory of the BlackBerry Messaging Agent, the
APB engine might loop. As a result, the BlackBerry Manager might stop responding.
(SDR 166533) If you restart the BlackBerry Dispatcher with no SRP connection, the dispSysHealthSRPTotalSecNotConnected
SNMP object might report an incorrect value.
BlackBerry Enterprise Server Alert Tool known issues
(SDR 181271) If the SMTP server becomes unavailable, the BlackBerry® Enterprise Server Alert Tool causes the TCP/IP stack
to run out of memory due to the number of queued alerts. As a result, the BlackBerry® Enterprise Server might stop responding.
BlackBerry MDS Integration Service known issues
(DT 351108) If the BlackBerry® MDS Integration Service tries to send a message to a BlackBerry® MDS Runtime Application
on BlackBerry devices and the message exceeds the maximum message size that you configured, the message is not delivered
successfully. In rare circumstances, the BlackBerry MDS Integration Service does not send a "Message size exceeds the
maximum size expected by BlackBerry MDS Connection Service" error message to the BlackBerry device.
(DT 255003) If you activate a user account on a new BlackBerry MDS Integration Service, the BlackBerry MDS Runtime
Applications that were associated with the user's original BlackBerry MDS Integration Service are not hidden on the user's
(DT 252825) If you assign a BlackBerry MDS Integration Service device policy to a user account with "external access"
configured to "read only", users can still add call numbers to the contact list on the BlackBerry device.
(DPI 225447) If the BlackBerry MDS Integration Service uses a proxy server, BlackBerry MDS Runtime Applications that require
user authentication might not prompt the user for authentication information.
(DPI 225077) You cannot schedule the removal of a BlackBerry MDS Runtime Application using the BlackBerry Manager.
(DPI 97174) If a user backs up the data on the BlackBerry device, upgrades the BlackBerry MDS Runtime, and then attempts
to unsubscribe from a push application subscription, a “Processor | Failed to process message. |
ErrorCode=SOAP_BACKEND_ERROR; MsgType=Unknown; ErrCause=Subscription not found” error appears on the
BlackBerry Manager known issues
(SDR 363569) If you add user accounts to a group, push rules are not applied to the user accounts.
Workaround: Apply the push rules to the group again after you add the user accounts.
(SDR 354520) If you export asset summary data for user accounts, the IT policy status column does not display any values in
the export file.
(SDR 349931) If you try to move a user account to a remote BlackBerry® Enterprise Server and you do not have Windows®
administration permissions for the computer that hosts the remote BlackBerry Enterprise Server, the BlackBerry Manager
cannot query the registry and determine the status of the remote BlackBerry Enterprise Server. You cannot move the user
account, and the following error message displays: "The status of this server cannot be determined due to the possibility of
insufficient permissions. Server may not be running. Do you want to move it anyway?"
Workaround: Get local administration rights for the computer that hosts the remote BlackBerry Enterprise Server.
(SDR 338845) If you use the Load Handheld option to load a software configuration that contains several large applications
onto a BlackBerry device that is connected to the computer that hosts the BlackBerry Manager, the BlackBerry Manager might
stop responding. The software configuration is not loaded onto the BlackBerry device.
(SDR 332562) Parentheses display after the status of the BlackBerry Policy Service.
(SDR 329532) If you try to remove a pull rule from multiple user accounts at the same time, the pull rule is only removed from
one of the selected user accounts.
(SDR 322206) If the BlackBerry Manager fails to authenticate with the BlackBerry Configuration Database because you enter
the wrong authentication credentials, and then you authenticate successfully during the same session, you might not be able
to perform certain tasks in the BlackBerry Manager. For example, you might not be able to add new users to the BlackBerry
Enterprise Server or to assign personal address books.
Workaround: If you enter the wrong authentication credentials, before attempting to authenticate the BlackBerry Manager
with the BlackBerry Configuration Database again, restart the BlackBerry Manager.
(SDR 311356) The Erase Data and Disable Handheld command does not work if the AppsVer (BlackBerry version) entry for the
user account is a null value in the BlackBerry Configuration Database.
Workaround: Change the value of the AppsVer entry for the user account to a non-null value in the BlackBerry Configuration
Database, or send the kill_handheld command using the BlackBerry Enterprise Server User Administration Tool.
(SDR 310430) If the BlackBerry Manager is installed on the same computer as the BlackBerry Enterprise Server and you rename
the BlackBerry MDS Connection Service client workstation, the BlackBerry Manager might not connect to the BlackBerry MDS
Connection Service and tries to build the BlackBerry MDS Connection Service string. As a result, a null pointer exception occurs.
(SDR 269789) The content about administrative roles in the help file contains incorrect information about security and
enterprise administrator roles.
(SDR 219787) The Disable Media Manager IT policy in the Security Policy Group should be labelled Disable Media Manager
(SDR 219487) If you create a custom IT policy and leave a space at the end of the IT policy name, when you try to edit the
properties of the BlackBerry Domain, the properties screen does not open and the following error message displays:
"Application Error - please report to support personnel if problem persists."
Workaround: Delete the custom IT policy template from the ITPolicyTemplate2 table in the BlackBerry Configuration Database.
(SDR 212895) When you assign an IT policy to a user account, the list of available IT policies is not in alphabetical order.
(SDR 212727) If you change the Maximum Stored Pushed Messages option, the following error message displays: "Unknown
Exception caught at: C:\ABS10\Components\Manager\4.1.6\LocalBuild\enter prise\Manager\UI\win\server\codebase
\main\uipropertysheet.cpp, line 391 -- details in log."
(SDR 211256) When you search for BlackBerry device users, additional search results might display in addition to the expected
(SDR 206353) After you restart the BlackBerry Messaging Agent, the server-level "pending data packets" value in the
BlackBerry Manager is reset to 0.
(SDR 191303) Relative path information appears for all organizer data settings. This information is only relevant for journal
and contact information.
(SDR 185645) When you add a user account to a group, the list of available groups is not in alphabetical order.
(SDR 184874) If you install the BlackBerry Collaboration Service, the Collaboration Service Relationship screen displays
incorrectly as "View Only" in the BlackBerry Manager, and you cannot click the Apply and OK buttons.
Workaround: To save the settings that you enter, complete the following steps:
1. On the Collaboration Service Relationship (View Only) screen, click Cancel.
2. On the Related Service screen, click OK.
3. On the Blackberry Collaboration Service screen, click OK.
(SDR 180681) If you click OK after specifying one or more new URL patterns for a pull rule, the following error message displays:
"Unknown Exception caught at C:\ABS10\Components\Manager\4.1.5\LocalBuild\entep rise\Manager\UI\win\server
\codebase\main\uipropertypage.cpp, line 1814 - details in log".
(SDR 172399) If you log into the BlackBerry Manager using the device administrator role, you cannot use the “Deploy
Applications” option when you select a single user. You can use this option when you select multiple users.
(SDR 170789) When a new user is assigned to a user group, the wireless synchronization settings for the members of the group
might be deleted.
(SDR 167355) The BlackBerry Manager displays the status of a user account as "Initializing Password Set" after the user's
activation password expires.
(SDR 163432) If your BlackBerry Enterprise Server environment includes a large number of BlackBerry Enterprise Server
instances (for example, more than 26) with a large number of users (for example, 26,000 users), you cannot delete a BlackBerry
Enterprise Server from the BlackBerry Domain using the BlackBerry Manager.
(SDR 159519) If you search for a user account, the user account might not be displayed in the preview window the first time
that you try the search.
(SDR 140695) If you turn off S/MIME message processing for a BlackBerry device using the BlackBerry Manager, S/MIME
message processing turns on for the BlackBerry device a short time later.
(SDR 139583) You cannot sort the Role Administration list.
(SDR 124825) If you add a user to the BlackBerry® Enterprise Server, the BlackBerry Manager might retrieve an incorrect email
address for that user if the user has multiple SMTP addresses. The BlackBerry Manager might retrieve the first SMTP address
for that user in alphabetical order, instead of the primary SMTP address.
Workaround: Refresh the view in the BlackBerry Manager. The primary SMTP address might display a few hours after you
add the user.
(SDR 107089) If you create a global or user message filter using the BlackBerry Manager, the BlackBerry Manager might
retrieve an incorrect SMTP address for user accounts that have multiple SMTP addresses and a primary address that was
changed at some point in Microsoft® Active Directory®.
BlackBerry Messaging Agent known issues
(DT 403549) In rare cases, if a user replies to or forwards a rich-text email from the BlackBerry® device, the message body is
blank when the recipient opens the message on the BlackBerry device. The message body displays in the email application.
(DT 358934) Users cannot reply to NNE messages received on the BlackBerry® Tour™ 9630 smartphone.
(SDR 339797) In certain rare circumstances, if a user responds to a rich-text email from the BlackBerry device, the body of
the reply does not display on the recipient's BlackBerry device.
(SDR 336770) In certain circumstances, graphics might not display in the email messages that users receive on their BlackBerry
devices, and the following error message appears in the BlackBerry Messaging Agent log file: "Assertion failed: Deleted
MEMHANDLE handle which we did not allocate".
(SDR 287464) If a user replies to a rich-text email message from an external Internet domain and attaches a contact list
contact using the Attach Address or Attach Contact option (VCF attachment) on the BlackBerry device, the message is not
delivered to the recipient.
(SDR 279712) If a user sends a message from the BlackBerry device with a large attachment, the BlackBerry Messaging Agent
private memory might spike for a short period of time.
(SDR 269826) Users cannot turn off the option to redirect sent items from the BlackBerry device.
(SDR 264758) In certain circumstances, if a user sends a message with an attachment from the BlackBerry device, the
BlackBerry Messaging Agent might not process the message attachment.
(SDR 250169) When the BlackBerry Messaging Agent reconciles file management changes over the wireless network (for
example, deleting email messages), a thread might be reported as "No Response", which results in the BlackBerry Controller
restarting the BlackBerry Messaging Agent.
(SDR 248591) Email messages that a user sends from the BlackBerry device are not saved in the user's IBM® Lotus Notes®
mail file if the user's mail file name contains the "ñ" character.
(SDR 232290) If a user forwards an email message from the BlackBerry device that contains a PDF attachment, the PDF
attachment might not be attached when the recipient receives the message, or the PDF might appear as a text file attachment,
or the PDF might display as embedded text in the email message.
(SDR 220157) The BlackBerry Enterprise Server cannot initialize user accounts on a clustered server in a foreign domain when
the primary mail server is not responding.
(SDR 209561) If the BlackBerry Messaging Agent catches an exception that occurred in the IBM Lotus Notes API, hung threads
can result and the BlackBerry Messaging Agent might stop responding.
(SDR 205736) Shutting down the BlackBerry Enterprise Server might cause multiple IBM Lotus Notes API handle leaks to occur.
(SDR 204985) In rare circumstances, if the BlackBerry Messaging Agent processes a rich-text email message that uses 8-bit
encoding, the message is not received and the BlackBerry Enterprise Server might stop responding.
(SDR 177271) If the document that an IBM Lotus Notes Link provides access to is located in a domain or on a server that the
BlackBerry Enterprise Server cannot access, the user does not receive a message indicating that the BlackBerry Enterprise
Server cannot access the IBM Lotus Notes Link.
(SDR 177229) If an extra space occurs at the end of the value for the ServerHostNames registry key, IBM Lotus Notes Links
that provide access to documents in external domains cannot be accessed from the BlackBerry device.
(SDR 171175) In rare circumstances, the BlackBerry Messaging Agent might stop responding if a user soft-deletes a message.
(SDR 169747) If a user performs a remote search for email messages, a search with the default criteria returns the error "Search
cancelled by remote service. Please try again later."
Workaround: Instruct users to change the default search criteria and search again.
(SDR 136345) If a user turns on the out of office service in IBM Lotus Notes 8.0, the user cannot turn on or turn off out of office
notifications from the BlackBerry device.
(SDR 110318) If a user sends an SSP-signed email message to a recipient with LDAP server information attached, the recipient
cannot import the LDAP server information.
BlackBerry Policy Service known issues
(SDR 334578) If you send a Set Password and Lock Handheld command to a BlackBerry® device that is out of a wireless
coverage area, and then you assign the user account a new BlackBerry device, the Set Password and Lock Handheld command
is not sent to the user's new BlackBerry device until you restart the BlackBerry Policy Service.
(SDR 317741) The BlackBerry Policy Service might resend service books to BlackBerry devices after a Microsoft® SQL Server®
(SDR 184969) In certain circumstances, if the device.xml file is not updated and you restart the BlackBerry® Policy Service
instances, user accounts might get associated with a single BlackBerry Policy Service.
Workaround: Update the device.xml file.
(SDR 175714) If you move users to a different BlackBerry® Enterprise Server, for some user accounts, the BlackBerry Policy
Service might use the source server’s SRP address or IT policy commands instead of the destination server’s SRP address. As
a result, the correct IT policy might not be applied to users until you restart the BlackBerry Enterprise Server.
(SDR 171638) In certain circumstances, the BlackBerry Policy Service sends the update service data command to a BlackBerry
device after it sends the switch service command to the BlackBerry device. As a result, the BlackBerry device might receive
incorrect SRP information.
(SDR 167837) If you move a user to a different BlackBerry Enterprise Server, the BlackBerry Enterprise Server might send an
incorrect SRP ID to the user’s BlackBerry device with the BlackBerry MDS Integration Service service book.
Logging known issues
(DT 401077) The location for tasks might be written to the log files as blank instead of reporting the user's mail file path.
(SDR 257255) When the BlackBerry® Policy Service polls BlackBerry devices for missing applications, the BlackBerry Policy
Service might write an error in the log file indicating that the device.xml file needs to be updated, when the issue is that the
device.xml file cannot be found.
(SDR 186491) Invalid log entries might display all logging levels and not the logging level that the logging is configured for.
(SDR 180186) If a user account has an address book on a different server than the users messaging account, the BlackBerry®
Enterprise Server might log failover information incorrectly.
(SDR 166284) The text of SMS messages in log files is sometimes replaced with multiple "@" characters.
(SDR 61188) The “PollForMissingApps failed” error is written to the BlackBerry® Policy Service log file after the log information
for all users on the BlackBerry Enterprise Server is written to the log file. This log line may be confusing because the information
that precedes it does not give more details.
Organizer data synchronization known issues
(DT 401884) If a user changes the email information for a contact on the BlackBerry® device, the change might not synchronize
to IBM® Lotus Notes®.
(SDR 303984) In certain circumstances, if a user updates the email addresses for a contact on the BlackBerry device, the
updated information does not synchronize to IBM Lotus Notes successfully.
Workaround: Edit email addresses for contacts using IBM Lotus Notes.
(SDR 277907) When the BlackBerry® Enterprise Server rescans a user account, the BlackBerry Enterprise Server might initiate
organizer data synchronization for the user account again.
(SDR 250861) Organizer data synchronization might take longer than expected on large IBM® Lotus® iNotes® address books.
(SDR 150752) If a user’s UserInfo document is too large, the BlackBerry Messaging Agent might enter a loop while attempting
to resolve the read and unread marks for the user’s messages, resulting in an error on the BlackBerry device.
(SDR 149614) The contact list lookup on the BlackBerry device returns unexpected results when too many matches are found
in the IBM Lotus Notes directory.
Setup application known issues
(DT 393021) After you install or upgrade to BlackBerry® Enterprise Server 4.1 SP7, the BlackBerry MDS Connection Service
might not start because the MSVCR71.dll file might not be installed in the proper location on the computer.
Workaround: Copy the MSVCR71.dll file from <drive>:\Program Files\Research In Motion\BlackBerry Enterprise Server\MDSS
\jre\bin to <drive>:\Program Files\Research In Motion\BlackBerry Enterprise Server\MDS\bin.
(DT 327711) If you modify the remote database connection information during the installation process (after the reboot) and
then you try to create the BlackBerry Configuration Database and click Back to return to the database information screen, the
Microsoft® SQL Server® name is greyed out and the BLACKBERRY instance name is added to the remote Microsoft SQL Server
Workaround: Select Local and then Remote again to edit the remote Microsoft SQL Server name.
(DT 313541) If you install the BlackBerry Enterprise Server in a location that is not the default location in the setup application,
the BlackBerry MDS key store file is not created.
Workaround: Use the default installation path in the setup application, or before installing the BlackBerry Enterprise Server,
create the path C:\Program Files\Research In Motion\BlackBerry Enterprise Server\MDS\webserver\ to contain the
BlackBerry MDS key store file.
(SDR 370652) If you run the setup application to remove a BlackBerry Attachment Service, BlackBerry Dispatcher, or BlackBerry
MDS Connection Service that has stopped running, the setup application cannot remove the service. You must restart the
computer and run the setup application again to complete the removal and install the service again.
(SDR 249701) When you install multiple BlackBerry Enterprise Server instances with multiple local BlackBerry Collaboration
Service instances, if you do not start a BlackBerry Collaboration Service instance after you install it, the next BlackBerry
Collaboration Service instance replaces the previous instance in the BlackBerry Configuration Database.
(SDR 234488) The setup application might not complete successfully due to language scripts in the errors.sql file.
(SDR 192765) If you configure your BlackBerry Enterprise Server to use "Triple DES only" or "AES only", and you run the change
database wizard to associate the BlackBerry Enterprise Server with an existing BlackBerry Configuration Database, the
encryption algorithm for the BlackBerry Enterprise Server changes to "Triple DES and AES".
(SDR 184791) If you configure settings for how BlackBerry Enterprise Server services start, the settings change to the default
settings after you upgrade the BlackBerry Enterprise Server.
(SDR 177524) If you upgrade from BlackBerry Enterprise Server 4.1 SP1 and you specify a lower-case Windows® machine name,
the BlackBerry MDS Connection Service might not start.
Workaround: Change the Windows machine name to use upper case before you perform the upgrade, or edit the MDSConfig
table in the BlackBerry Configuration Database to use the correct instance number and remove the additional entries that
reference the same machine name.
(SDR 177085) When upgrading from BlackBerry Enterprise Server 4.1 SP4, the following error might display: "Failed to check
the component GUID. Refer to the installation log for more information. Setup will now exit."
Workaround: Create a temporary registry key named Components in HKEY_LOCAL_MACHINE\Software\Wow6432Node
\Microsoft\Windows\CurrentVersion\Installer\UserDa ta\S-1-5-18. Delete this registry key after the installation process
(SDR 135348) A user with the junior help desk administrator role has the ability to modify the mapping between the BlackBerry
Enterprise Server and the environment’s instant messaging server during the installation process. If a user does not select the
appropriate mapping settings during the installation process, your instant messaging service could be disrupted.
Wireless calendar known issues
(DT 400600) If a user changes the location or reminder option of an instance of a recurring meeting in IBM® Lotus Notes®,
all instances of the recurring meeting might be updated on BlackBerry® devices.
(DT 360960) If a user adds an invitee to a existing recurring meeting in IBM Lotus Notes, only the past instances display in
the calendar on the invitee's BlackBerry device.
(DT 350980) In certain circumstances, the BlackBerry® Enterprise Server might stop responding when processing a user's
meeting decline message.
(DT 252022) If a user accepts or rejects a calendar invitation in IBM Lotus Notes while the user's BlackBerry device is off or
out of a wireless coverage area, when the user turns on the BlackBerry device or enters a wireless coverage area, the calendar
invite appears on the BlackBerry device and is not updated with the acceptance or rejection.
(SDR 363459) The BlackBerry Enterprise Server might stop responding due to inconsistencies in list fields when the BlackBerry
Enterprise Server updates recurring meeting instances on BlackBerry devices.
(SDR 357014) If a user turns on the out of office agent in IBM Lotus Notes from the BlackBerry device without first turning on
the out of office agent using IBM Lotus Notes, the user cannot configure the out of office agent using IBM Lotus Notes, and
an error message displays.
(SDR 289431) In certain circumstances, when the BlackBerry Enterprise Server iterates calendar items in a user's BlackBerry
state database, the BlackBerry Enterprise Server might run out of memory.
(SDR 257729) If a user changes the location or the reminder notice for certain instances of a recurring meeting on the
BlackBerry device, all instances of the recurring meeting are updated with the changes on the BlackBerry device. Only the
specified instances are updated with the changes in IBM Lotus Notes.
(SDR 211702) If a user accepts a meeting invite from the BlackBerry device, the meeting participants might receive duplicate
alarm notifications for the meeting.
(SDR 180345) If a user turns on their out of office agent using the BlackBerry device, the out of office profile created by the
BlackBerry Enterprise Server is not compatible with the IBM Lotus Notes format.
Workaround: Turn on the out of office agent using IBM Lotus Notes.
(SDR 171564) When a user checks the availability of meeting invitees from the BlackBerry device, if the availability information
cannot be retrieved for a single invitee, the availability information for the other meeting invitees might not be available as
well, and an "Unable to find time where all attendees are available" error message displays.
(SDR 151218) In certain circumstances, calendar invitations that users delete from IBM Lotus Notes still synchronize to users’
|All times are GMT -5. The time now is 07:38 AM.|
Powered by vBulletin® Version 3.6.12
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.