The third step of this job "Erase Phantom System Health Records" is configured to run under the SQL Server Agent Account but it is connecting to the instance under the agent account of a different instance. I'm unclear what this job step *actually* executes - i.e. where is the EraseSystemHealthPhantomRecords() module - and why it would be connecting to the instance under the wrong account.
Anyone got any ideas?