Mirroring. Error message: Failed InstanceLookup (agent probably not running): instance not found
Hello everyone!
Maybe someone will tell me what could be the reason for such messages in the message.log file
05/03/23-06:46:27:155 (6584) 0 [Utility.Event] [SYSTEM MONITOR] Mirror state: Member type = Failover, Status = Transition
05/03/23-06:46:27:350 (1620) 1 [Utility.Event] Failed InstanceLookup (agent probably not running): instance not found
05/03/23-06:46:27:351 (1620) 2 [Utility.Event] Failed to become either Primary or Backup at startup
05/03/23-06:46:27:725 (1620) 1 [Utility.Event] Failed InstanceLookup (agent probably not running): instance not found
ISCAgent service is running.
Comments
Have not seen such errors, but how defined the mirror members, by hostname or by IP?
By hostname, arbiter - by ip.
ISCAgent is running on primary, alternate and arbiter? It has to be running on all 3. IRIS Windows installation by default will install ISCAgent but will not enable it for auto-start.
You can check the ISCAgent service status from the Windows Services screen:
.png)
Confirm that if it's started automatically (sorry for the language of the image).
Thanks for the answer. But the ISCAgent service is installed and running. The ISCAgent service was the first thing I checked. Restarting the service does nothing.
>> [Utility.Event] Failed InstanceLookup (agent probably not running): instance not found
The WRC says that this error indicates a problem with the locally installed agent.
We were able to resolve the issue. The WRC noticed an error in the configuration. As it turned out, the agent's address was incorrectly specified on this server. Instead of a locally installed agent, there was an arbiter address causing this error. In the mirror configuration, I changed the agent address for this server and everything worked fine.