Basic Troubleshooting Steps (Enterprise Console)

When an issue is encountered while using the Identity Finder Enterprise Console, it is necessary to gather sufficient logging and diagnostic information to resolve the issue or request assistance from the support team. 

• If this issue is a general usage or configuration question, please request the appropriate assistance.

Troubleshooting Steps

To obtain the necessary information to diagnose and resolve the issue, perform the following steps:

1. Please read the article, Getting Started with the Enterprise Suite, to ensure that the console has been set up properly, that the client(s) have been installed with the endpoint service, and that the appropriate settings have been installed on the endpoint(s) to ensure successful communication between the clients and the console.
2. Ensure that the client and console software are the latest release versions as the issue may have already been resolved. 
3. 1. Using the latest version of the software makes it much easier for the support team to diagnose issues.
3. Ensure that the console server is configured with the necessary IIS Roles and Role Services.
4. If the issue is related to the client (for example: communication between the client and console):
5. 1. Check the Client log for errors. 
   2. 1. Windows: To review the logs on Windows, select the Configuration tab, click the down-arrow on the Logging button and select View Current Log. 
      2. Mac: For Identity Finder for Mac, use Finder to navigate to the user folder:
         /Users/USERNAME/Library/Application Support/Identity Finder/Identity Finder Mac Edition/logs
         
         where USERNAME is the name of the currently logged on user. 
      3. To ensure that logging is enabled and configured properly, please perform the basic troubleshooting steps for the client.
   2. Follow the steps detailed in the KB article entitled, "Endpoints Fail to be Displayed in the Console".
5. If the problem remains unresolved, please gather the following information:
6. 1. Relevant screen captures that show the issue. 
   2. 1. This provides exact wording of error messages and an indication of the error, setting, or other configuration option, enabling the support team to quickly identify the specific issue.
   2. A list of resources consulted (for example: documents, kb articles). 
   3. 1. This enables the support team to understand the steps taken to resolve the issue and eliminates any unnecessary instructions. 
      2. Additionally, this enables the support team to update any relevant documentation after the issue is resolved to make it easier for other customers to get help.
   3. Client log(s).
   4. 1. As noted in Step 3 above, there should be a detailed log from the run where the undesirable/unexpected behavior occurred. 
      2. Providing this log enables the support team to get a better understanding of the search execution. 
      3. Use the Gather Data function to obtain the relevant information.
   4. Endpoint Service logs. 
   5. 1. On Windows: "endpointservice.log" and is located in the installation directory of the Identity Finder Client, which by default is as follows:
         C:\Program Files\Identity Finder 4. 
      2. On Mac: The logs are located in the following folder:
         /Users/USERNAME/Library/Application Support/Identity Finder/Identity Finder Mac Edition/logs,
         where USERNAME is the name of the currently logged on user. 
      3. These logs provide technical information related to communication, scheduling, and policies.
   5. Server logs. 
   6. 1. The logs from the enterprise console assist the support team in diagnosing configuration and application errors on the server.  
      2. Use the Gather Data function of the console administrator tool to obtain the relevant information.
   6. A detailed description of the steps taken, the behavior observed, and an explanation of the issue to be resolved. 
   7. 1. This enables the support team to attempt to replicate the issue and provide as detailed a resolution as possible.
6. Once all of the documentation is gathered, open a support ticket and include everything in the Description field of the ticket or as attachments, as appropriate. 
7. To submit attachments, it is necessary to first register with the support portal.