Troubleshooting Management Session Channel Status errors

  • Last update on April 23rd, 2025

Overview

This article provides guidance for resolving common issues when Management session channels show an error status in the app. These channels connect CoreView to Microsoft 365 services for management tasks. When a channel status is in error, use the table below to identify the problem and recommended remediation steps. 

If you do not have Tenant Admin rights, contact your tenant admin to complete the required actions.

 

Common Channel errors and remediation steps

Channel Typical Issue(s) Resolution / Action
Exchange, Microsoft Teams
  • Management user login fails due to Conditional Access policies
  • Advanced management user password has expired
  • Check Microsoft Entra ID sign-in logs for error details for the management user. If you’ve configured the advanced management type, check the sign-ins for the account named: 4ward365.admin@yourdomain.onmicrosoft.com
  • If the issue is due to password expiration of the advanced management user, do not reset or update it manually. Instead, check if there is any conditional access policy enforcing the expiration and remove the user from it. Then, execute the management action "Password never expires" to set the service account password to never expire directly from our portal. Finally, restart the management session.
  • If a conditional access policy is blocking the management user login, remove the management user from any conditional access policies that could block access. You can use the what-if analysis to assist with this.
Microsoft Graph
  • Client secret for Graph app has expired
  • Renew the client secret following the instructions in Graph Management.
  • Update the secret in CoreView configuration
SharePoint
  • Errors depend on returned messages
  • Contact CoreView's Support Team for more details regarding errors in the SharePoint management channel.
Exchange On-Premises, Active Directory On-Premises
  • Diagnostic tool needs to be run
  • CoreView agent or Docker not running; Health check outdated
  • Run the diagnostic tool in CoreView
  • Check Organization settings > On-premises for Windows service agent active status
  • Restart the CoreView Agent and Docker if needed

Additional notes

  • Error codes: when available, error codes returned by Microsoft services can provide more context for resolution steps. You can view these codes in the sign-in logs or advanced diagnostic tools.
  • Advise for operators: if you are not a Tenant Admin, forward the error and this article to your admin. They can review the sign-ins logs and conditional access policies, or update app secrets as needed.
  • For more contextual errors: we are working to show targeted error messages in the app interface in the future. For now, use this article as your troubleshooting guide.

Still need help?

If you continue to experience issues after following the above steps, please reach out to CoreView Support or consult your IT administrator.