Chat now with support
Chat with Support

Coexistence Manager for GroupWise 1.7.1 - User Guide

About the Coexistence Manager for GroupWise documentation suite Introduction Coexistence Manager for GroupWise Directory Connector
Directory Connector overview Installation and configuration DC Management Console Connector Creation Wizard Connector Advanced Settings Running and stopping the Directory Connector service
Coexistence Manager for GroupWise Mail Connector Coexistence Manager for GroupWise Free/Busy Connector The Log Viewer Appendix A: Known limitations Appendix B: Troubleshooting Appendix C:Configuring Coexistence Manager for GroupWise logging

Mail Connector

Verify that all CMG system requirements have been met (as documented in the most recent RTM Release Notes).

Verify that you have a valid Quest License Key installed. For more information, see About Quest license keys in chapter 1.

This problem is often caused by the iCal service being disabled in the GWIA. In the SMTP/MIME Settings tab of GWIA Properties, click the Enable iCal service checkbox.

Coexistence Manager for GroupWise processing may marginally increase or decrease the size of a message, which may rarely push a message over a receiving server’s size limit even though the original message was smaller than the server’s configured limit.

A subdomain routing method may introduce a risk that the assigned subdomain names will escape your organization’s internal communications, which in turn can cause bounce-backs on replies to those addresses.

A migrated user in Exchange is unable to accept or decline an invitation sent from GroupWise, and the attempt generates a "User not found" error. A native Exchange user (synched to GroupWise, but was never there), however, can accept or decline such invitations uneventfully.

The cause seems to be a bug with GroupWise 8.0.2 GWIA. A Novell HotFix 8.0 SP2 HP3 solves the issue, as documented in the Novell Release Notes (see #704520, D101 error when Accepting iCal Appointments).

Look through your Coexistence Manager for GroupWise Mail Connector log files for clues to help diagnose and resolve the problem. If necessary, see Appendix C: Configuring Coexistence Manager for GroupWise logging for instructions to configure the feature to suit your needs.

Free/Busy Connector

If an Outlook client repeatedly crashes during F/B lookups, and you are running an Exchange 2007 or Exchange 2010 Client Access Server, the cause may be a known issue in the combination of .NET Framerwork 3.5 SP1 and .NET Framework 2.0 SP2. For more information, see Microsoft’s KnowledgeBase article, and Microsoft Support can point you to a HotFix to resolve this problem.

If you are coexisting with Office 365, and Coexistence Manager for GroupWise’s F/B Connector works fine for a time but then suddenly and consistently fails, the most likely cause is a change in Microsoft’s Autodiscover URL.

Our configuration instructions for the F/B Connector (see Management Console screen: Exchange F/B Connector | Exchange Free/Busy) suggest that, for Office 365, you select the Autodiscover Endpoint connection method, and set the Exchange Autodiscover URL field to this Microsoft URL:

But this is a Microsoft URL that is subject to change, in which case the connection would fail and the Free/Busy Connector would fail. In that case, contact Microsoft to get the new URL, or select the Autodiscover Only method instead.

If Outlook users get certificate errors when logging into Outlook, after Coexistence Manager for GroupWise's F/B Connector has been configured, the most likely cause is a name mismatch in the certificate. Check to verify that the certificate in use on the Exchange server for port 443 is accepting all required named domains. If the error shows a name mismatch, the certificate may not have the required domain.

To troubleshoot errors retrieving free/busy information from Exchange, you can use these PowerShell cmdlets:

To get F/B info for an Exchange user via the Exchange F/B Connector Service:

Get‑CmgExchangeFreeBusy

[-UserEmailAddress] <String>
[-StartDate] <DateTime>
[-EndDate] <DateTime>

UserEmailAddress: Email address of an Exchange user.
StartDate: Starting date for the F/B search.
EndDate: Ending date for the F/B search.

To get F/B info for an Exchange user via the FreeBusyBridge Web Service:

Get‑CmgFreeBusyBridge

[-WebServerName] <String>
[-UserEmailAddress] <String>

WebServerName: Name of server where FreeBusyBridge Web Service resides.
UserEmailAddress: Email address for whom to get F/B info from Exchange.

These cmdlets retrieve free/busy information for one or more users directly from Exchange using the same code used by the Exchange F/B Connector Service or Bridge Web Service. The cmdlets can be used to narrow down whether the problem is retrieving Free/Busy information from Exchange, or the configuration of the Bridge, or of the Autodiscover service or EWS.

To troubleshoot errors retrieving Free/Busy information from GroupWise, you can use the Get-CmgGroupWiseFreeBusy cmdlet. This cmdlet will retrieve F/B information for one or more users using the Coexistence Manager for GroupWise Mail Connector service.

To get F/B info for a group of GroupWise users via the GroupWise F/B Connector Service:

Get‑CmgGroupWiseFreeBusy

[-UserEmailAddresses] <String[]>
[-StartDate] <DateTime>
[-EndDate] <DateTime>

UserEmailAddresses: List of email addresses of GroupWise users.
StartDate: Starting date for the F/B search.
EndDate: Ending date for the F/B search.

This cmdlet can be used to narrow down whether the problem is retrieving Free/Busy information from GroupWise, or the configuration of the Autodiscover or Availability web services.

An Exchange-to-GroupWise F/B query will generate this error:

... if the IIS_IUSRS user does not have List folder / read data permission. To resolve this, grant the user that List folder / read data permission.

Verify that Add-AvailabilityAddressSpace has been executed on the Exchange server. To see if the cmdlet has run, type on the Exchange Management Console: Get-AvailabilityAddressSpace
Add-AvailabilityAddressSpace -ForestName <YourDomain.com> -AccessMethod OrgWideFB -Credentials $adminCreds -UseServiceAccount $true
Add-AvailabilityAddressSpace -ForestName <YourDomain.com> -AccessMethod OrgWideFB -Credentials $adminCreds -UseServiceAccount <AccountName> -TargetAutodiscoverEpr 'https://autodiscover.<YourDomain.com>/autodiscover/autodiscover.xml'
Ensure you can ping <smtpdomain> or autodiscover.<smtpdomain> and that it resolves to the computer running the Coexistence Manager for GroupWise F/B Connector.
Open a web browser such as Internet Explorer and type https://<host>/autodiscover/autodiscover.xml (where <host> is either <smtpdomain> or autodiscover.<smtpdomain>), and ensure an .xml file appears and that you do not have any certificate errors.
If the .xml file displayed has the text "this is a placeholder file", then IIS is not properly configured with an XML Handler.
2
Ensure the Managed Pipeline mode for QuestAutodiscoverAppPool and QuestEWSAppPool are both set to Integrated.
3
Access https://<host>/autodiscover/autodiscover.xml, and ensure you do not see the error message "this is a placeholder file".
4
From the Exchange server, open a web browser such as Internet Explorer, and type https://<host>/EWS/Service.asmx (where <host> is either <smtpdomain> or autodiscover.<smtpdomain>), and ensure an .xml file appears and that you do not have any certificate errors.
Ensure that the appropriate DNS entries have been made to route <smtpdomain> or autodiscover.<smtpdomain> to the computer running the Coexistence Manager for GroupWise Free/Busy Connector.
On the computer running Coexistence Manager for GroupWise Free/Busy Connector web services, run the Get-CmgAutodiscoverConfig cmdlet, and verify that the CmgAvailabilityUrl is set to https://<host>/EWS/Service.asmx (where <host> is either <smtpdomain> or autodiscover.<smtpdomain>).
On the computer running Coexistence Manager for GroupWise Free/Busy Connector web services, ensure that Get-CmgAvailabilityConfig is configured to communicate to the correct host and port for the computer running the Coexistence Manager for GroupWise GroupWise Free/Busy Connector service.

If you see the following error message: The maximum message size quota for incoming messages (65536) has been exceeded, you must increase the quota by using the MaxReceivedMessageSize property on the appropriate binding element.

If you are using OWA or Outlook and querying Free/Busy information for a GroupWise user, edit the Web.Config file in the EWS folder on the Coexistence Manager for GroupWise Web Server:

Add the maxReceivedMessageSize property to the file and set it to a large value:
<netTcpBinding>
<binding name="Coexistence Manager for GroupWiseFreeBusyClientSettings"
openTimeout="00:01:00"
receiveTimeout="00:01:00"
sendTimeout="00:01:00"
closeTimeout="00:01:00"
maxReceivedMessageSize="655360">
<security mode="None"/>
</binding>
</netTcpBinding>

Look through your Coexistence Manager for GroupWise Free/Busy Connector log files for clues to help diagnose and resolve the problem. If the default logging settings don’t meet your diagnostic needs, see Appendix C: Configuring Coexistence Manager for GroupWise logging for instructions to change logging configuration settings.

Appendix C:Configuring Coexistence Manager for GroupWise logging

By default, Coexistence Manager for GroupWise is installed with the log42net utility to generate log files of Coexistence Manager for GroupWise components’ system activity. This information is critical to diagnosing any problems that may arise. Coexistence Manager for GroupWise log entries look like this:

Coexistence Manager for GroupWise logs are configured and saved separately, by component, in files that reside in or under each component’s subtree root folder. Coexistence Manager for GroupWise logging is enabled by default, for all Coexistence Manager for GroupWise components, and the default configurations will be suitable for almost all organizations and circumstances. The parameters that are most often edited are listed in the procedure notes below.

IMPORTANT: The Open Log File button in the Management Console’s Health screen is enabled only when the UdpAppender is defined in the log42net.config file of at least one module. During a new installation, the Log Viewer installer installs a file with the required UdpAppender. During an upgrade, however, the installer does not overwrite the log42net.config file, so the UdpAppender is not present, and this makes the Open Log File button invisible. To correct this, see To add the UdpAppender to an existing log file at the end of this Appendix.

Coexistence Manager for GroupWise actually generates multiple log files for each component, so you can track different types and levels of program activity. All Coexistence Manager for GroupWise logging-configuration files are xml-format files, which you can edit with any XML editor.

Log files for the Directory Connector

DC Log Filename

Configured in:

Coexistence Manager for GroupWise.log

Directory/File: ...\Directory Connector\log42net.config
Section: section <appender name="LogFileAppender" ...>

Coexistence Manager for GroupWise_ERROR.log

Directory/File: ...\Directory Connector\log42net.config
Section: <appender name="ErrorLogFileAppender" ...>

Log files for the Mail Connector

MC Log Filename

Configured in:

Coexistence Manager for GroupWise.log

Directory/File: ...\Mail Connector\log42net.config
Section:section <appender name="LogFileAppender" ...>

Coexistence Manager for GroupWise_ERROR.log

Directory/File: ...\Mail Connector\log42net.config
Section: section <appender name="ErrorLogFileAppender" ...>

SMTP.log

Directory/File: ...\Mail Connector\log42net.config
Section: section <logger name="SmtpFileAppender" ...>

Log files for the Free/Busy Connector

FBC Log Filename

Configured in:

FreeBusyBridge.log

EWS.log

Autodiscover.log

GroupWiseFreeBusyService.exe.log

ExchangeFreeBusyService.exe.log

QuestSoftwareFreeBusy.log

FreeBusyBridge.log.config

EWS.log.config

Autodiscover.log.confi

GroupWiseFreeBusyService.log.config

ExchangeFreeBusyService.log.config

QuestSoftwareFreeBusy.log42net.config

PowerShell log configuration file is in ...\Free Busy Connector\Powershell\

A Coexistence Manager for GroupWise configuration file will roll over to a new file (close the existing log file and create a new one) when its contents reach a particular size, or a particular time of day (e.g., midnight). Also, the log42net utility will create up to a certain number of sequential files before deleting the oldest to preserve disk space. By default the rollover method is size (default 10MB), to a default maximum of 25 sequential files, but these are configurable values, as noted in the procedure notes below.

To edit any of the configuration settings in a Coexistence Manager for GroupWise configuration file:

2
For the Mail Connector’s SMTP.log file (only): If you want to enable or disable SMTP logging altogether, find the section <logger name="Coexistence Manager for GroupWise. SmtpProtocol.logging" ...>, and then:
3
For a Directory Connector or Mail Connector log (only): Find the corresponding section in the open file (section name also appears in the right-hand column above).
<file value="[PathAndFilename]" />: Location and name of the log file that log42net will generate. The path specification can be absolute (e.g., "C:\log42net\Coexistence Manager for GroupWise.log") or relative to the installation directory (e.g., ".\log42net\Coexistence Manager for GroupWise.log").
<threshold value="INFO" />: Scope and level of detail to appear in the logs. A valid value is any of these single words:
The values are listed here in ascending order of detail, left to right, and the log will contain items at and above (to the left of) the specified value. For example, <threshold value="WARN" /> tells log42net to include WARN, ERROR and FATAL events in the log file. The level is set to INFO by default.
<rollingStyle value="Size" />: Determines what will trigger log42net’s closing of a current log file and opening of a new one: either a change in calendar date, or a log file reaching a particular size. Parameter value is set to "Size" by default, or change to "Date" for the alternative.
<maximumFileSize value="10MB" />: Maximum log file size—the size at which log42net will close the current log file and open a new one (applies only if <rollingStyle value="Size" />.
<maxSizeRollBackups value="25" />: Maximum number of log files to keep—after which log42net deletes the oldest log file to create a new one.
5
Close and Save the configuration file under the same filename.
NOTE: Any changes to the log42net.config file are immediately applied by the Coexistence Manager for GroupWise service when the configuration file is saved.

For more detailed information about the log42net utility and how its log files can be configured, see the log42net Config Examples at the Apache.org web site.

To add the UdpAppender to an existing log file

To add the UdpAppender to an existing log file

The Open Log File button in the Management Console’s Health screen is enabled only when at least one module has the UdpAppender defined in its log42net.config file. During a new installation, the Log Viewer installer installs a file with the required UdpAppender. During an upgrade, however, the installer does not overwrite the log42net.config file, so the UdpAppender is not present, and this makes the Open Log File button invisible.

For upgrades or installations prior to the current release, the log42net.config file must be modified in each module to enable live log viewing. In the <log42net> root in each module directory, add the following lines:

Related Documents