SYMPTOM:
The following error message is received during both manual and scheduled Strategy Enterprise Manager 9.x data loads configured to monitor projects that are part of an asymmetrical Strategy Intelligence Server 9.x cluster:
Login to project unsuccessful.
The connection failed. Possible causes are a) Server is not running, b) Server is loading project, c) Network problem, or d) Server reached maximum connection limit.
CAUSE:
This error occurs because at the time of data load, the project in the error (in this case 'Strategy Tutorial') is not loaded on any of the nodes in the cluster.
In a clustered environment, a project is failed over to the surviving node(s) based on the 'Project fail over latency' duration specified in the Strategy Intelligence Server 9.x configuration, under the 'Projects - Advanced' section. The default value for this setting is 30 minutes.
Projects only loaded on the failed node will not be loaded on any surviving node until after the fail over latency has passed and the failed node has not come back online.
If a data load is performed during this latency period the error will occur.
ACTION:
For the data load to take place successfully, all of the projects monitored by Strategy Enterprise Manager 9.x should be loaded on at least one node in the cluster.
By decreasing the project fail over latency duration to zero, when a node fails, the project will be immediately failed over to the surviving node(s). This will ensure that when the data load runs, all projects will be available on at least one node in the cluster.
If a node fails, but the project has been successfully failed over to a surviving node, entries similar to the following will be in the MSTRMigration log file:
12/17/2007 12:32:59 PM Login to server Strategy Tutorial unsuccessful.
12/17/2007 12:32:59 PM Reconnecting to server Node-1.
12/17/2007 12:33:05 PM Login to server Node-1 unsuccessful.
12/17/2007 12:33:05 PM Reconnecting to server Node-2.
12/17/2007 12:33:10 PM Reviewing cluster member loads.
12/17/2007 12:33:10 PM Login to server Node-2 successful.
