Update Manager stuck at Downloading Binaries

Question

I've noticed that my Update manager (only 1 server) has been stuck at Downloading Binaries since Aug 15th. It's showing Version 1.6.1.124, and there are no errors/alerts showing on that Dashboard screen. 
 I've look this issue online, and tried a few things, Delete folders, restart services, restarted server and so on... nothing worked. I even have a ticket open with Sophos, and I'm currently not impressed with their support... i've had better service from TrendMicro. 
 I've upgraded the Enterprise Console back in May from 5.2.2 to 5.5.0, and haven't had a problem since. Looks like my Endpoints are still getting updates via the manager, and they seem current, but when doesn't the Console show it? 
 I've tried to reinstall the update manager, as per support, and it seemed to go through... i didn't get any errors, it just went by quick. 
 Only thing I've noticed different was that there seemed to have been an update to the Update Manager on that same day, and it hasn't worked since. 
 Any ideas on what I should do next? Since support isn't too helpful....

jak · Accepted Answer

Of the 5 IPs on the server, there are 3 169 addresses in the router and 2 other IPs. Of those 2 IPs, is the server managing computers via both those interfaces or could all the clients you're managing just use one? If the IP is static you could explicitly define it by editing: 
 "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SophosMessageRouter" changing the value for 'ImagePath' from (for example): 
 "C:\Program Files\Sophos\Remote Management System\RouterNT.exe" -service -name Router -ORBListenEndpoints iiop://:8193/ssl_port=8194 
 to 
 "C:\Program Files\Sophos\Remote Management System\RouterNT.exe" -service -name Router -ORBListenEndpoints iiop://192.168.15.1:8193/ssl_port=8194 
 The IP address should be the one that the clients can connect to. 
 Then Edit "HKEY_LOCAL_MACHINE\SOFTWARE\sophos\Messaging System\Router", changing the value for ''ServiceArgs" from (for example): 
 "-ORBListenEndpoints iiop://:8193/ssl_port=8194" 
 to 
 "-ORBListenEndpoints iiop://192.168.15.1:8193/ssl_port=8194" Again the IP address should be the one that the clients can connect to and the same as above. If you restart the Sophos Message Router service then and check the IOR it will be shorter and only have reference to the one IP. This way, after clients read this IOR string they will come straight back to the right IP and port 8194. Once done. I would be interested to see some logs of the messaging system. Restart the Sophos Router and Agent service on a client, wait 1 minute (to guarantee a status message has been generated). Can we see the new Agent and Router log file that has been created?

Bryan Gritton · Answer

I'm having this same problem. I followed these instructions and this registry change fixed it.