Files Deployment
Ensure that nBTCal.exe, nBTCalL.exe, nBTCalF.exe, nbtex.dll files are copied to Domino directory.
NOTES.INI Parameters
See Appendix G.
Domino Routing Configuration Modifications
Foreign Domain Document
i.e. Exchange
Mail Information
Gateway server name: BTEXCHCONN/ACME
Gateway mail file name: btexchange.box
Calendar Information
Calendar server name: BTEXCHCONN/ACME
Calendar system: btexchange.box
Foreign SMTP Domain
i.e. exchange*.binarytree.com Domain name: ExchangeDirect
Server Configuration Document
SMTP used when sending messages outside of the local internet domain = Enabled
SMTP allowed within local internet domain = Disabled
Servers within the local Notes domain are reachable via SMTP over TCPIP = Always
MIME Tab
On the MIME tab navigate to the Conversion tab and then select the Outbound sub-tab. Enter the following information.
Return receipts: Enabled
Message content = from Notes to HTML
Server Connection
Connection type = SMTP
Source server = BTMail01/BinaryTree
Connect via = Direct Connection
Destination server = CMTC Mail
Destination domain = ExchangeSMTPDirect
SMTP MTA relay host = 167.105.2.155 “
Replication task = Disabled
Routing task = SMTP Mail Routing
Route at once if = 1 messages pending
Routing cost = 1
Connection = enabled
Connect at times = 12:00 AM to 11:59 PM
Repeat interval of = 60 minutes
Files Deployment
Ensure that nBTCal.exe, nBTCalL.exe, nBTCalF.exe, nbtex.dll files are copied to Domino directory.
NOTES.INI Parameters
See Appendix G.
Domino Routing Configuration Modifications
Foreign Domain Document
i.e. Exchange
Mail Information
Gateway server name: BTEXCHCONN/ACME
Gateway mail file name: btexchange.box
Calendar Information
Calendar server name: BTEXCHCONN/ACME
Calendar system: btexchange.box
Foreign SMTP Domain
i.e. exchange*.binarytree.com Domain name: ExchangeDirect
Server Configuration Document
SMTP used when sending messages outside of the local internet domain = Enabled
SMTP allowed within local internet domain = Disabled
Servers within the local Notes domain are reachable via SMTP over TCPIP = Always
MIME Tab
On the MIME tab navigate to the Conversion tab and then select the Outbound sub-tab. Enter the following information.
Return receipts: Enabled
Message content = from Notes to HTML
Server Connection
Connection type = SMTP
Source server = BTMail01/BinaryTree
Connect via = Direct Connection
Destination server = CMTC Mail
Destination domain = ExchangeSMTPDirect
SMTP MTA relay host = 167.105.2.155 “
Replication task = Disabled
Routing task = SMTP Mail Routing
Route at once if = 1 messages pending
Routing cost = 1
Connection = enabled
Connect at times = 12:00 AM to 11:59 PM
Repeat interval of = 60 minutes
Integration for Notes includes customizable reason codes displayed for Non Delivery Reports (NDR’s) sent by BTCal. The default reason codes in the table below will be displayed as part of the message defined in the BTMULTISCHEDREPORTTEXTx Notes.ini parameter by %reason%. The only exception is BTNDR22, which completely replaces the BTMULTISCHEDREPORTTEXTx.
The table below includes the default customizable reason codes in the Notes.ini file and valid keywords that can be used in the error message.
Default Reason Code |
Explanation |
Valid Keywords |
---|---|---|
BTNDR1="Converting a single instance meeting to a recurring meeting cannot be supported between Exchange and Domino. Please cancel the meeting and recreate it as a recurring meeting." |
The Outlook user scheduled a single occurrence meeting and is now trying to convert it to a recurring meeting. |
|
BTNDR2=" Rescheduling an entire series of a recurring meeting that contains a Domino Room or Resource cannot be supported between Exchange and Domino. Please cancel and recreate the meeting." |
The Outlook user attempted to reschedule the entire series of a meeting that contains a Domino Room or Resource. |
|
BTNDR3="Canceling an entire series of a recurring meeting that contains a Domino Room or Resource after a single occurrence has been cancelled cannot be supported between Exchange and Domino. Please notify all participants that they should delete the meeting from their calendars. The Room or Resource reservation must also be manually deleted from the Resource Reservations database.” |
The Outlook user attempted to cancel the series that contains a Domino Room or Resource but had previously canceled a single occurrence of the series. |
|
BTNDR4="You have specified that this recurring meeting should occur on the “0” (zero) day of each month, which cannot be supported by Domino. Please cancel and recreate the meeting using a value between 1-28 (the 29th, 30th and 31st days of each month are also not supported as not every month contains more than 28 days).” |
The Outlook User scheduled a recurring meeting to occur on the zero day of each month. This appears to have been a bug in one or more versions of Outlook 2007. |
%RULE% |
BTNDR5="You have specified that this recurring meeting should occur on the 29th, 30th or 31st day of each month, which cannot be supported by Domino, because not every month contains more than 28 days. Please cancel and recreate the meeting using a value between 1-28” |
The Outlook User scheduled a recurring meeting to occur on either the 29th, 30th or 31st day of each month. This is not supported by Notes. |
|
BTNDR6="You have specified that this recurring meeting should occur on the 29th, 30th or 31st day of each month, which cannot be supported by Domino, because not every month contains more than 28 days. Please cancel and recreate the meeting using a value between 1-28.” |
The Outlook User scheduled a recurring meeting to occur on either the 29th, 30th or 31st day of each month. This is not supported by Notes. |
|
BTNDR7="Creating a recurring meeting with no end date cannot be supported by Domino. Please cancel and recreate the meeting specifying an end date or number of occurrences.” |
The Outlook user scheduled a recurring meeting with no end date, which cannot be supported by all versions of Domino and Notes. |
|
BTNDR8="Creating a recurring meeting that is scheduled to continue past 2037 cannot be supported by Domino. Please cancel and recreate the meeting so the series ends before the year 2037." |
The Outlook user tried to schedule a recurring meeting that will go past year 2037. |
|
BTNDR9="Creating a recurring meeting with over 1200 instances cannot be supported by Domino. Please cancel and recreate the meeting with fewer than 1200 instances." |
The Outlook user specified a recurring meeting that contains too many dates. By default, Integration for Notes will only support 1200 meetings for a recurring meeting. This is configurable via the BTRecurrenceLimit parameter. If the expanded list of individual meetings exceeds this limit, this error will be returned. |
|
BTNDR10="Rescheduling the entire series of a meeting after one or more occurrences have been rescheduled cannot be supported between Exchange and Domino. Please cancel and recreate the entire meeting series.” |
The Outlook user rescheduled a single occurrence of a recurring meeting, and is now trying to reschedule the entire series. |
|
BTNDR11="The recurring meeting contains a larger number of instances than can be supported between Exchange and Domino. Please cancel and recreate the meeting with fewer instances.” |
The Outlook user specified a recurring meeting that contains too many dates. For recurring meetings, the RRULE from the ICS file is expanded into a list of individual date/times for the meeting. These are stored in a 32K buffer. Too many dates and will overflow this buffer and this error will be returned. |
|
BTNDR12="Creating a recurring meeting with a date in the “Until” field that is before the first meeting date cannot be supported by Domino. Please cancel and recreate the meeting with valid dates.” |
The Outlook user specified an “UNTIL” date/time that preceded the first date/time of the meeting. This appears to have been a bug in one or more versions of Outlook 2007. |
|
BTNDR13="There was an internal processing issue that should be reported to IT Support as an invalid cache document. Please cancel and recreate the meeting.” |
There were problems with the cache document for the meeting, such as it could not be opened or a specific field could not be found. |
|
BTNDR14="Your meeting update could not be processed due to an uncorrectable error. Please cancel the entire meeting and recreate it.” |
This is defensive code for a scenario found in a customer's production environment. Although we had the offensive ICS file, we were not able to reproduce, or determine the root cause. |
|
BTNDR15="Your meeting update could not be processed due to an uncorrectable error. Please cancel the entire meeting and recreate it.” |
This is defensive code for a scenario found in a customer's production environment. Although we had the offensive ICS file, we were not able to reproduce, or determine the root cause. |
|
BTNDR16="Your meeting update could not be processed due to an uncorrectable error. Please cancel the entire meeting and recreate it.” |
This is defensive code for a scenario found in a customer's production environment. Although we had the offensive ICS file, we were not able to reproduce. Integration for Notes expands the RRULE for a recurring meeting into a series of RDATES, with each RDATE representing a single instance of the recurring meeting. While trying to do this, one of the parameters taken from the ICS file is invalid. |
|
BTNDR17="Your meeting update could not be processed due to an uncorrectable error. Please cancel the entire meeting and recreate it.” |
This is defensive code for a scenario found in a customer's production environment. Although we had the offensive ICS file, we were not able to reproduce, or determine the root cause. |
%RULE% |
BTNDR18="Changing the recurrence pattern of the meeting cannot be supported by Domino. Please cancel and recreate the entire series.” |
You cannot change the original definition of the meeting occurrences. For example, you cannot schedule a recurring meeting in Outlook for Monday-Friday, and then change the recurrence pattern to start on Wednesday and continue for 3 days. |
|
BTNDR19="Changing the entire series of a recurring meeting after one or more instances of that meeting have been changed cannot be supported between Exchange and Domino. Please cancel and recreate the meeting.” |
For recurring meetings between Exchange and Domino, you cannot change the entire series after an instance of the meeting has been changed. |
|
BTNDR20="The number of updates made to this meeting exceeds the limit supported between Domino and Exchange. Please cancel the meeting and recreate it.” |
In the ICS file, a VEVENT is used to define a calendar event. Integration for Notes does not support more than one VEVENT in a single ICS file. |
|
BTNDR21="Your meeting update could not be processed due to an uncorrectable error. Please cancel the (entire) meeting and recreate it.” |
The ICS file is encoded in MIME as Quoted Printable Text. This is not a supported type. This is defensive code for a scenario found in a customer's production environment. Although we had the offensive ICS file, we were not able to reproduce, or determine the root cause. |
|
BTNDR22="Dear User,\r\n\r\nThe delegation (forwarding) of your invitation is not currently supported.\r\nPlease request that the chairperson invite the intended delegate.\r\n\r\nOriginal invitation information:\r\n\r\n\tSubject: %SUBJECT%\r\n\tDate: %DATE%\r\n” |
An Exchange user is invited to a meeting and delegates (forwards) that meeting to a Domino user. Meeting delegation functions differently between Domino and Exchange and cannot be supported. |
%SUBJECT%, %DATE% |
BTNDR23="Creating a recurring meeting with the option to move it if it occurs on a non-workday can only be supported if the meeting is a daily meeting. Please cancel and recreate the meeting specifying Don’t Move if the meeting occurs on a non-workday.” |
The Notes user specified to move the meeting if it occurs on weekend for a non-daily recurring meeting. The Notes user can only choose “Don’t move”. |
|
BTNDR24="Adding an Exchange user to an existing meeting cannot be supported between Domino and Exchange. Please cancel and recreate the meeting with the appropriate invitees.” |
The Domino user added an Exchange user(s) to an existing meeting. This can only be supported if GRIP is configured in the coexistent environment. |
|
BTNDR25="Creating a meeting that occurs monthly by date, and selecting more than one date per month cannot be supported by Exchange. Please cancel and recreate the meeting using one date per month, or use an alternative recurring pattern.” |
The Notes user specified more than one date when choosing the Monthly by Date option. The Notes user can only choose one date. |
|
BTNDR26="Creating a meeting that occurs monthly by day, and selecting more than one day per month cannot be supported by Exchange. Please cancel and recreate the meeting using one day per month, or use an alternative recurrence pattern.” |
The Notes user specified more than one day when choosing the Monthly by Date option. The Notes user can only choose one day. |
|
BTNDR27="Rescheduling an instance of a meeting to occur after another scheduled instance of the series cannot be supported between Domino and Exchange. Please cancel and recreate the meeting series.” |
The Domino user tried to reschedule an instance of a recurring meeting after another scheduled occurrence. |
|
BTNDR28="Rescheduling an instance of a meeting to occur before another scheduled instance of the series cannot be supported between Domino and Exchange. Please cancel and recreate the meeting series.” |
The Notes user tried to reschedule an instance of a recurring meeting before another scheduled occurrence. |
|
BTNDR29="Exchange Rooms and Resource must be placed in the “To:” field to ensure proper functionality.” |
The Domino user tried to schedule a meeting and specified an Exchange resource in the Resource field. Exchange resources must be added in the “To:” field. |
%RESOURCENAME% |
BTNDR30="Exchange Rooms and Resource must be placed in the “To:” field to ensure proper functionality.” |
The Domino user tried to schedule a meeting and specified an Exchange room in the Room field. Exchange resources must be added in the “To:” field. |
%ROOMNAME% |
BTNDR31="Rescheduling a recurring meeting and specifying that the reschedule applies to “This instance and all previous instances” or “This instance and all future instances” cannot be supported between Domino and Exchange. Please cancel and recreate the meeting.” |
The Domino user specified either “This instance and all previous instances” or “This instance and all future instances” when rescheduling a meeting. This is not supported. The Notes user can only reschedule the entire series or just a single occurrence. |
|
BTNDR32="Creating a recurring meeting using a custom recurrence pattern cannot be supported by Exchange. Please cancel and recreate the meeting using a non-custom recurrence pattern.” |
The Notes user specified a recurring meeting using custom dates. |
|
BTNDR33="This email cannot be processed by the system that manages coexistence between Domino and Exchange, because the domain (@domain.com) is not configured. Please report this to your technical support organization.” |
The Domino user attempted to send a mail item to a Foreign Domain that is not configured for BTExchangeDomain or BTAltExchangeDomains. |
%DOMAINNAME% |
BTNDR34="Rescheduling the entire series of a meeting after one or more occurrences have been rescheduled cannot be supported between Domino and Exchange. Please cancel and recreate the entire series.” |
The Domino user rescheduled one or more individual occurrences of a recurring meeting, and is now trying to reschedule the entire series. |
|
BTNDR35="Rescheduling a recurring meeting using the Monthly by Day recurrence pattern cannot be supported between Domino and Exchange. Please cancel and recreate the meeting using an alternative recurrence pattern.” |
The Domino user attempted to reschedule a meeting using the Month by Day option. |
|
BTNDR36="Adding an Exchange user to this meeting cannot be supported, because there have been too many changes to the meeting. Please cancel and recreate the meeting.” |
The Domino user attempted to add Exchange users to an existing meeting and the number of exceptions exceeds BTAddUserExceptionsMax. This required GRIP to be configured. |
|
BTNDR37="Your attempt to add an Exchange user to this meeting could not be processed at this time. Please cancel and create the meeting with the appropriate invitees.” |
The Domino user attempted to add Exchange users to an existing meeting and BTCal could not get the original invitation information before BTAddUserDelayMax has expired. This could be due to network or server issues. This required GRIP to be configured. |
|
BTNDR38="Adding an Exchange user to this meeting cannot be supported, because there have been too many changes to the meeting. Please cancel and recreate the meeting.” |
The Domino user attempted to add Exchange users to an existing meeting that had exceptions and exceptions are not allowed. This requires GRIP to be configured. |
%EXCEPTIONCOUNT% |
BTNDR39="This meeting reschedule cannot be properly processed between Domino and Exchange. Please cancel and recreate the meeting.” |
The Domino user attempted to reschedule a meeting, and BTCal could not find the meeting in the cache database. Cache.nsf may be corrupt, or the document may not be in the expected cache folder. This is the same as BTNDR41, but in a different place in the code. |
|
BTNDR40="This meeting reschedule cannot be properly processed between Domino and Exchange. Please cancel and recreate the meeting.” |
The Domino user attempted to reschedule a meeting, and BTCal could not open the meeting in the cache database. Cache.nsf may be corrupt. |
|
BTNDR41="This meeting reschedule cannot be properly processed between Domino and Exchange. Please cancel and recreate the meeting.” |
The Domino user attempted to reschedule a meeting, and BTCal could not find the meeting in the cache database. Cache.nsf may be corrupt, or the document may not be in the expected cache folder. This is the same as BTNDR39, but in a different place in the code. |
|
BTNDR47=" This meeting change cannot be supported between Outlook and Notes. Please cancel and recreate the meeting to ensure that the Notes invitees are properly updated." |
The meeting between Outlook and Notes cannot be opened in BTCache. |
|
BTNDR49= "An encrypted copy of the message could not be delivered to the following Domino Group(s): %GROUPLIST%.\r\nPlease re - send the message using individual recipients." |
An encrypted copy of the message could not be delivered to the listed Domino Groups. |
|
BTNDR50= "An encrypted copy of the message could not be created for the following Notes recipient(s): %RECIPIENTS%.\r\nPlease contact the HelpDesk." |
An encrypted copy of the message could not be created for the listed Notes recipients because there was not a Public Key in their Person Document. |
|
BTNDR51= "An encrypted copy of the message could not be delivered to the following Notes recipient(s) : %RECIPIENTS%.\r\nPlease contact the HelpDesk." |
An encrypted copy of the message could not be delivered to the listed Notes recipients because the Public Key was not valid. |
|
BTNDR52= "This meeting contains more text than BTCal can process for Domino users.\r\nPlease recreate it using less than 25K of text." |
The meeting contains more than 25K of text. |
|
To customize the text of a reason code add BTNDR##= to the Notes.ini followed by your custom text
Examples:
BTNDR30=This is a custom reason code, using the keyword for a room %ROOMNAME%
For reason codes requiring more than one line of text, append “.#” to the notes.ini parameter. As with BTMULTISCHEDREPORTTEXTx, \n and \t must be used to insert the end on the line of text and a tab (respectively). For example:
BTNDR29.1=first line of the reason code text\n
BTNDR29.2=the second line of the reason code text\n
BTNDR29.3=the third line of the reason code text\n
BTNDR29.4=the fourth line of the reason code text\n
There is no limit on the number of lines a message may span; however, there is a 64K size limit for all lines of text combined.
This section describes how calendar delegation behaves between Domino and Exchange, as well as what remediation options are available in CMTC.
There are two types of delegation; delegating a meeting to another person, and delegating calendar privileges to another person.
In Domino, you may delegate a meeting to another person by selecting Delegate under the Participant Actions dropdown menu. Although there is an option to be kept informed of updates, the act of delegating in this scenario general means that the original invitee is no longer invited to the meeting.
In Exchange, a similar result is achieved by forwarding a meeting to another person. In this scenario, the original invitee continues to be a full participant of the meeting.
Despite the similarities of these actions, the internal processing is quite different and it is not possible to achieve fully transparent functionality across platforms. The below table outlines the expected behavior of delegating/forwarding meetings in a Coexistent environment.
There are six different general scenarios for cross-platform delegation:
Notes Chairperson invites Notes User who delegates to an Outlook User
Notes Chairperson invites Outlook User who delegates to a Notes User
Notes Chairperson invites Outlook User who delegates to an Outlook User
Outlook Chairperson invites Outlook User who delegates to a Notes User
Outlook Chairperson invites Notes User who delegates to an Outlook User
Outlook Chairperson invites Notes User who delegates to a Notes User
For purposes of this document, the following terms will be used:
Delegator - the person who delegates a meeting to another user
Delegate - the person to whom the meeting is delegated
Integration for Notes can be configured to detect forwarded invitations from Exchange to Domino, and to return an NDR when found. This is the recommended behavior. This feature is enabled via the BTDelegateNDR parameter. The parameter accepts a value of Y or N, with Y being the default. Therefore, by default, this feature is enabled.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center