SYMPTOM:
Users see the the following error in the DSSErrors.log in Strategy Intelligence Server 9.x and 10.x:
CDSSServerMessage::InitAfterLoad(): Failover candidate: MsgID=###, LocalServer=### ExecutingNode=###, RqstStatus=13, LastErrorCode=0x0
The DSSErrors.log will contain a value for the MsgID, the LocalServer,and ExecutingNode fields:
MsgID = ID for a History List Message (One which has failed to execute)
Local Server = Local Server name
Executing Node = Node which is re-executing the error message.
Note: You do not have to be in a clustered environment to receive this Error Message. This message relates to History List failover. Shown below is an example message:
[Kernel][Warning] CDSSServerMessage::InitAfterLoad(): Failover candidate: MsgID=36F5A5F211E250DE33E300802FA785CE, LocalServer=Strategy.example.com ExecutingNode=Strategy.example.com, RqstStatus=13, LastErrorCode=0x0
CAUSE:
This is simply an informative message. This message is logged when a certain user logs into the Intelligence Server, and the Server checks this user`s History List, and finds that a message did not complete executing. At this point, the History List fail-over functionality comes into effect, and starts re-executing the message again. The error message is then logged to the DSSErrors.log file. These messages are expected to be logged to the DSSErrors.log whenever a user logs in, and the Intelligence Server finds that a certain History List message did not complete properly.
ACTION:
This is working as designed. History fail over is designed to re-execute a History List Message that failed to execute upon user login.
