Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.
With Strategy Library 10.9+, users can communicate and share comments with other users in Strategy Dossiers. However, certain circumstances will cause the Strategy Collaboration Services icons not to load on the interface. Keep reading to learn all of the troubleshooting steps to complete when the Collaboration Service notification icon (bell icon) in the Library or the Comment icon on the dossier page is missing in Strategy 10.9+. Let's get your Library Collaboration Services up and running!
Before diving into the troubleshooting steps, note the locations of the icons.
Look to the top of the Library homepage.

Look to the top right hand corner of a dossier in Library.

Before looking to anything else, ensure that the user(s) have privileges to access Collaboration. If users do not have the correct access privileges, collaboration icon may be hidden in the Library. To find out what privileges the user may or may not have, check with your administrator. If the user does indeed have the correct privileges, move on to the next troubleshooting step.
Look to Service Availability

https://<web server>:<port>/StrategyLibrary/admin


If there are any errors, the "collabsvc" name will appear in the list. Clicking on it, will display any relevant errors. View below:
{code: "ERR001", message: "Cannot find trust store file ""."}
{code: "ERR004", message: "Service not enabled"}
Check for Missing Identity Token
Start by analyzing the Network requests using the Developer tools without any filters. This can sometimes highlight specific errors.
For instance, errors can appear for the identityToken parameter:

{code: "ERR001", message: "Required properties for token generation not configure"}
?EIO
If Strategy Library has been deployed on a JSP server other than the Apache Tomcat server that is shipped with Strategy 10.9, the identity token might be missing which will prevent the collaboration server to identify the commenting user and therefore disable the comment functionality. In order to resolve the issue, follow the steps below:
<tomcat_home>\webapps\StrategyLibrary\WEB-INF\classes\config
<Strategy Library Home>/WEB-INF/classes/config
services.collaboration.baseURL = http://<Strategy Library server name>:3000

Note that if changes need to be made to the files, restart the Strategy Library server for the changes to take effect.
identityToken.secretKey=secretTokenhere
The end user machine will connect directly to Collaboration server on the port configured in config.json (default 3000). Therefore, ensure that the end user machine can access Collaboration server by connecting to http(s)://servermachine:3000/. Follow the process for these steps below:
C:\Program Files (x86)\Strategy\Collaboration Server
"authorizationServerUrl": "http://localhost:8080/StrategyLibrary/api", "port": 3000,
Note that if changes need to be made to the files, restart the Strategy Collaboration Server machine for the changes to take effect. On a windows machine, this can be achieved from the services console, as shown below.

If Strategy Library is configured for access through SSL, Collaboration Server must be configured for SSL as well. Refer to Strategy Installation guide for further information on how to set up Collaboration server with SSL and review Considerations and certificate trust requirements when enabling HTTPS (SSL/TLS) for MicroStrategy Library and Collaboration Server .
Still have questions? We have you covered! Visit the Learning Center on Community!
Feel free to start a discussion on Community or reach out to your Support liaison to create a case.
Looking to upgrade to a newer version of Strategy? Visit the corporate website for more information!