MindLink WebPart Troubleshooting
MindLink WebPart (Server 16.6.2)
MindLink WebPart Feature Section
Figure 24: SharePoint Feature Settings
1 - SharePoint API Port: The port on which to listen for incoming SharePoint server MTLS connections required only when configuring for Single Sign-On.
2 - Certificate: The server certificate to use for incoming SharePoint MTLS connections. This authenticates the Connector Service to the SharePoint server required only when configuring for Single Sign-On.
3 - Authorized Hosts: The authorized hosts collection should contain the FQDN of all SharePoint hosts that will connect to the Connector Service instance being configured required only when configuring for Single Sign-On.
If a SharePoint host attempts to connect to the Connector Service and is not in the Authorized Host collection, an error indicating that the host is not authorized will be returned.
The WebPart writes diagnostic messages to the SharePoint ULS log, which generally writes to files in: %ProgramFiles%\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS
If you experience any issues with the application, in the first instance contact your local IT support team. If you have subscribed to Support and Maintenance and require additional assistance from the Formicary Collaboration, please email the Support Team at email@example.com stating the nature of the problem and including your contact details.
The MindLink Server writes log messages to a text-based log file. The location of this file is configurable via the Management Center.
Each log is written at one of the log levels:
- Verbose - Detailed information about each action being processed, for diagnostics and troubleshooting.
- Info - Post-mortem information about significant completed operations, for usage reporting.
- Warning - Notifications of environmental, configuration, or operation abnormalities that may indicate problems - immediate, or in the future - for health monitoring.
- Error - Information about erroneous application behaviour for troubleshooting and health monitoring.
The minimum log level - as ordered above - of logs that will be written to the log file is configurable in the Management Center. All logs below this level will be discarded.
Logging at Info is recommended for production.
Skype For Business Logging
The MindLink Server uses the Microsoft UCMA SDK and Persistent Chat SDKs to integrate with Skype for Business. Each of these SDKs emit Event Tracing for Windows (ETW) logs that can be captured by the SFB Centralized Logging Service or Debugging Tools (OCS Logger) etc. The SfB core component or debugging tools must be installed on the MindLink host server, respectively.
For OCS 2007 R2 integration, MindLink uses the Group Chat SDK. This does not emit ETW logs but instead can be enabled to write to a text-based log file, distinct from the standard MindLink log file. The Management Center can be used to configure whether logging from the SDK is enabled and to what location.
These logs can be used to diagnose and troubleshoot integration problems between SfB and MindLink.
The MindLink Server runs as a Windows Service. Any environmental or configuration problems encountered during startup will cause the service to abort startup and stop immediately. Once started, further errors - environmental or otherwise - will not cause the service to stop.
The MindLink Server exposes an HTTP health-check Info Service that can be used by external monitoring systems or load balancers to verify that the service is started, healthy and operation.
By default, this service is available at http://:9081/infoservice/status. Making a GET request to that request will return an HTTP status code of 200.
When the MindLink Mobile Server is deployed in a pool, each node must be configured to connect to a Microsoft SQL Server database layer. When a node loses connectivity to the database for any reason it will declare itself unavailable and remove itself from the pool, until database connectivity is restored. While unavailable, the node will reject new logon requests and hence should be disregarded as a candidate node by the load balancer.
The Info Service will return HTTP status code 503 while the node is disconnected from the database. This status code can be used by the load balancer to maintain the set of candidate pool members, and by any external monitoring systems to detect database connectivity failure.
User Administration (Anywhere, SharePoint, Mobile)
A MindLink session will be interrupted if any of the following administration changes is made to the user account:
- The SIP address of the user is changed.
- The user is moved to a different pool.
- The user is removed from SfB.
The user will be notified that their session has ended and they will be required to re-logon