SYMPTOM:
In Strategy 9.x, in rare cases the following error message may be logged into the DSSErrors.log of the Strategy Intelligence Server machine:
2011-10-22 23:52:06.489-05:00 Network: Failure to communicate with Strategy Intelligence Server.
2011-10-22 23:52:06.536-05:00 Network: Not Connected to Strategy Intelligence Server.
2011-10-22 23:52:06.536-05:00 Network: Failure to communicate with Strategy Intelligence Server.
2011-10-22 23:52:06.567-05:00 Network: Not Connected to Strategy Intelligence Server.
The error may be logged multiple times per second and the Intelligence Server is confirmed to be running. Additionally, restarting the Intelligence Server does not remove the message.
CAUSE:
One possible cause of this message is a hung Enterprise Manager Data load process. In this case, the MAEMETL.exe process can be seen continuing to run in the background and consuming resources. Additionally, if the command "mstrctl -s Intelligence Server gs" is run it is clear the Process ID(PID) logging the errors does not come from the Intelligence Server
ACTION:
In order to resolve this issue the hung MAEMETL.exe process throwing the errors needs to be identified and killed through task manager. In order to find the process, check the DSSErrors.log and note the PID section to get the PID of the process responsible for throwing the errors. You can then sort the task manager by Process ID to kill it. Once this has been done the errors messages should stop logging.
