KB ID 0000606 Dtd 21/05/12
A client showed me this today, I don’t support their Sage, but I was on site and the people who do support their Sage (I wont name and shame one of our competitors), had told them it was their DNS server that was causing the error.
Logon Error Loon failed due to unexpected error. Please check if the Sage200Configuration database is configured and running. (Message was: The remote server returned an error: (502) Bad Gateway.)
A couple of quick ping tests on the affected machine disproved the DNS theory! I thought it might be permissions as it didn’t error on my domain admin account. After some frowning, I though the error looked vaguely “web server” related and had a brain wave.
The affected client was set to web browse through a proxy server, as soon as I created an exception for the server that was running Sage, It started working!
Related Articles, References, Credits, or External Links