[SOLUS3] - Strange Agent issue
We have a school that has about 25 devices in their SOLUS3 environment. The SOLUS3 database, service and UI are all on 3.5.20. The agents on a few devices are also working fine and on 3.5.20. However, some devices are online but still on 3.5.118 and not automatically upgrading the SOLUS3 agent, SIMS, FMS etc. Strangely, we can re-deploy SIMS and FMS to these devices to upgrade them manually without issue, but getting the updates automatically, they do nothing. When the agents are idle (ie, no deployments taking place), the online agents running with agent version 3.4.118 display this error in the Message field:
The message with action http://www.capitaes.co.uk/agent/2010...tVersionChecks cannot be processed at the receiver, due to a contractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched actions between sender and receiver) or a binding/security mismatch between sender and receiver. Check the sender and receiver have the same contract and the same binding (including security requirements, e.g. Messages, Transport, None).
Anyone come across this, or know of a working fix? Nothing on SupportNet but logged a call with Capita, but hoping someone's seen this before and got a 'quick fix'! :)