Invoking the diagnostic tool on a running system will return the following: MicroStrategy installations provide a command line diagnostic tool for troubleshooting Collaboration server connection issues.Ĭhange the current working directory to \nodejs. Verify that the certificates specified in the Collaboration server config.json file are the same used to create the keystore file used with Tomcat.ĭiagnose Collaboration Server Connection Issues.Unable to connect to the Authentication Server. Error: unable to verify the first certificate. Unable to invoke Authentication Server method.Error indicating a problem with the certificate, such as:.In short, you cannot open a secure connection to a machine if you don't have the certificate for that same machine and the certificate is not signed by a trusted certificate authority. Verify that the "authorizationServerUrl" uses the same machine name as the "Common Name" associated with your certificate.Error: connect ECONNREFUSED 127.0.0.1:8443 (code=ECONNREFUSED) Unable to connect to the Authentication Server. Unable to invoke Authentication Server Method.Error indicating that the connection is refused, such as:.If you don't see any requests even after refreshing, the communication between the Library Web and Collaboration server in your environment is through HTTP polling instead of a Web Socket due to an environment limitation.It is possible that the browser debugging tool started capturing network calls after the Web Socket connection is established. If you don't see any request, refresh the page.This will display the requests and responses in JSON format. Within the request info window, open the Frames tab.Filter the request type by "WS" (WebSockets).When Collaboration server features within the Library fail without a detailed error message, monitor the error message directly from Web Socket messages using the web browser debugging tool. Click the icon and use the error message dialog to contact your administrator. If the Notification Icon is available but disabled, the Collaboration server is not connected.Ensure you have the Use Collaboration Services privilege (see Privileges in Library Web).Go to the Library Administration Control Panel and configure the Collaboration server.If the Notification Icon is not available: Issue: Collaboration Server is Unavailable Ensure you have the Use Library privilege for all projects (see Privileges in Library Web), so you can access dossiers within all projects.Review the MicroStrategyLibrary error logs and look for any console errors in the browser debugging tool.If you are looking for API errors only, click the XHR option so that the network tab displays all http(s) calls including the APIs. Look for any network requests that are red, as this indicates that the REST API request may have failed.This will display the response in JSON format. Within the request info window, open the Preview tab.Click a network request that you are interested in.Check that all of the requests are captured.When the Library Web application behaves unexpectedly without any error message, monitor the error messages being returned from the MicroStrategy REST API using the web browser debugging tool. No content has been added to your Library.Open the Library Administration Control Panel and check that Intelligence server is configured and running.To fix this issue, upgrade your IIS to a later version, such as IIS 10.0 RS3, when it is available.Troubleshooting Your MicroStrategy Library Installation Issue: My Library is Empty HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\InetInfo\Parameters\ThreadPoolUseIdealCpu Resolution To do this, update the value of the following registry from 1 to 0: To work around this issue, disable IIS Thread Pool Ideal CPU Optimization on a NUMA server if you want to specify processor affinity. However, this setting conflict with the specified processor affinity. The feature optimizes IIS performance by evenly distributing loads across all CPUs of all NUMA nodes. The issue occurs because a new feature, IIS Thread Pool Ideal CPU Optimization for NUMA hardware, is enabled in IIS 10.0.īy default, this feature is enabled. You can check the processor affinity of each worker process from the Task Manager.The issue does not apply to non-NUMA hardware.
0 Comments
Leave a Reply. |