Symptom:
When a user attempts to connect to a Strategy Intelligence Server through the Strategy Web Admin.asp page, they may notice that two Strategy Intelligence Servers will appear. This issue can occur when the following exists:
When a user connects from Strategy Web to the Intelligence Server using this link's IP address, Strategy Web will connect to both the link's IP address and the Strategy Intelligence Server's machine. This means that when the user accesses the projects page, the same projects are listed twice; one with the link's IP address and one with the Strategy Intelligence Server name.
Cause:
Strategy Web will connect to the same Strategy Intelligence Server twice as a result of an Application Programming Interface (API) cluster feature. When a user attempts to connect to Strategy Intelligence Server through the Strategy Web Admin.asp page, Strategy Web asks the Strategy Intelligence Server for its cluster information. In this case, Strategy Web will use the dedicated network link's IP address to connect to the Strategy Intelligence Server.
However, the Strategy Intelligence Server will respond to Strategy Web with its information using its own IP address. Since the IP address for the dedicated network link and the IP address for the Strategy Intelligence Server are different, Strategy Web will think that the server is registered as part of a cluster. As a result of this, Strategy Web will connect to the Strategy Intelligence Server using the machine name without realizing that they are the same.
Action:
To resolve this issue, the user needs to map the Strategy Intelligence Server name to the IP address of the dedicated network link on the web server machine, using the Data Source Name (DSN) Host file. After this, the user can utilize the Strategy Intelligence Server's machine name to connect.
8764
