AnsweredAssumed Answered

VM host failed-over, Secondary sever went into standalone and out of sync

Question asked by Sagarakunso on Oct 31, 2016
Latest reply on Oct 31, 2016 by jru



Recently the physical host of our PI server (hosted in VMware) has some issue and caused the virtual host to reboot and run on another physical host within the VM farm. After PI has started, both on Primary PI and Secondary PI, Primary PI is running as normal but Secondary PI refused client connections. The PI logs mentions of below:


Deleting connection:  SMTHost.exe(4344), Connection Refused. PI Server in Standalone mode., ID: 20   :0


Despite several PI stops & starts and virtual host reboot, issue still persists. Finally a Re-initialization of the Secondary PI fixed it. Is there a way to mitigate this?