How To: Enable debug logging for the CMN FreeBusy Connector (4291940)

Chat now with support

Get Live Help
Complete Registration

Sign In

Request Pricing

Contact Sales

Return

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title

How To: Enable debug logging for the CMN FreeBusy Connector
Description

How can we debug FreeBusy information when trying to troubleshoot CMN's FreeBusy Connector?.
Resolution

To enable debug logging for the CMN FreeBusy Connector:
1.- Open the FreeBusy Connector folder:
Before v3.8:
C:\Program Files (x86)\Dell\Coexistence Manager for Notes\Free Busy Connector\DominoFreeBusyService\
C:\Program Files (x86)\Dell\Coexistence Manager for Notes\Free Busy Connector\ExchangeFreeBusyService\
From v3.8:
C:\Program Files (x86)\Quest\Coexistence Manager for Notes\Free Busy Connector\DominoFreeBusyService\
C:\Program Files (x86)\Quest\Coexistence Manager for Notes\Free Busy Connector\ExchangeFreeBusyService\
2.- Make a copy of log42net.config and call it log42net.config.normal.
3.- Edit the log42.net.config file.
4.- Where it says <threshold value="INFO" /> change the INFO to DEBUG.
5.- Where it says <root> <level value="INFO" /> change the INFO to DEBUG
6.- Reproduce the issue.
7.- Provide the following wlog files if the issue occurs with FreeBusy requests from Domino to Exchange:
Before v3.8:
C:\Program Files (x86)\Dell\Coexistence Manager for Notes\Free BusyConnector\ExchangeFreeBusyService\Logs\ExchangeFreeBusyService.wlog
C:\Program Files (x86)\Dell\Coexistence Manager for Notes\Free Busy Connector\Autodiscover\Logs\Autodiscover.wlog
C:\Program Files (x86)\Dell\Coexistence Manager for Notes\Free Busy Connector\EWS\Logs\EWS.wlog
From v3.8:
C:\Program Files (x86)\Quest\Coexistence Manager for Notes\Free BusyConnector\ExchangeFreeBusyService\Logs\ExchangeFreeBusyService.wlog
C:\Program Files (x86)\Quest\Coexistence Manager for Notes\Free Busy Connector\Autodiscover\Logs\Autodiscover.wlog
C:\Program Files (x86)\Quest\Coexistence Manager for Notes\Free Busy Connector\EWS\Logs\EWS.wlog
8.- Provide the following wlog files if the issue occurs with FreeBusy requests from Exchange to Domino:
Before v3.8:
C:\Program Files (x86)\Dell\Coexistence Manager for Notes\Free BusyConnector\ExchangeFreeBusyService\Logs\DominoFreeBusyService.wlog
From v3.8:
C:\Program Files (x86)\Quest\Coexistence Manager for Notes\Free BusyConnector\ExchangeFreeBusyService\Logs\DominoFreeBusyService.wlog

Once troubleshooting has been completed, disable debug logging:
1.- Rename log42net.config to log42net.config.debug.
2.- Rename log42net.config.normal to log42net.config (no service restart is required).
Additional Information

Support might also need QCalCon Debugging details to further investigate Exchange FreeBusy issues (From Domino to Exchange FB requests): 1.- Edit file log42net.config found within the following folder in Domino: C:\Program Files\IBM\Domino\ or C:\Program Files\IBM\Lotus\Domino 2.- Find the following section: " " and change INFO to DEBUG as shown below: " " 3.- Save the changes and reproduce the issue. 4.- Provide the following wlog file: C:\Program Files\IBM\Domino\QCalCon.wlog or C:\Program Files\IBM\Lotus\Domino\QCalCon.wlog Finally, support might request to enable Debug for QCalCon FB lookups in Domino to get further details when the FreeBusy arrives into Domino (from Exchange to Domino): 1.- Open the Domino Console. 2.- Run the following command: Set conf debug_Sched_all=1 Note: Set it to 0 when debugging is complete.

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Request a KB Article

Please select your product:

To serve you better, please complete the Purpose of your Chat:

Recommended Solutions for Your Problem

How To: Enable debug logging for the CMN FreeBusy Connector (4291940)

Title

Description

Resolution

Additional Information

Leave a Comment