Ever since the policy to disable TLS 1.0 was pushed down to the local machines, we started getting the error “an authentication error has occurred(code 0x80004005)” when accessing few of our Windows 2008 R2 servers. It was interesting because we have a bunch of other servers with no problems accessing. This seems to be a very generic error code as google results were showing multiple problems and multiple solutions for this.
Apparently, in my case, the patch to add RDS support for TLS 1.1 and TLS 1.2 was not installed in 3 of the servers with this problem. So I had to download the patch from this Microsoft website and install and reboot them remotely. Once installed and rebooted, voila!!
Edit: There are multiple reasons for this problem, and there are multiple ways to fix it. I am just sharing what worked for me, and it may not work for all. Saying this because this post is now in the first page of google results and I am getting lot of traffic to this, and I do not want to disappoint you. Thanks
Mccormick deering hand corn sheller manual. Nov 28, 2019 Refer to knowledge base article Sophos Enterprise Console: Significant files and registry entries used by the Sophos management service component. Getting more help If you have worked through all the above steps, and not solved the issue, you may need additional help from Sophos Technical Support. The first error, indicating a synchronisation error with a 0x80004005 error code and another saying he needed the password with a 0xE4010668 error code. As these errors disappeared as soon a I deactivated the proxy, I knew I had to create an exception rule. 0x80004005 - Unspecified error; Applies to the following Sophos products and versions PureMessage for Microsoft Exchange What to do Create a folder for the logging Create a folder C: PMDebugLogs. Note: This path can be changed, though ensure you use the same path in step 9 of the 'Enable logging' section, and collect the log from this folder. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.
The Sophos Central agent installer may report an error preventing migration.
In this case, in Sophos Central Migration Tool, you'll see 'Sophos Central agent installer' error in the Status column next to the computer.
In Sophos Enterprise Console, you'll see the following status in the Computer description column:
{SC:Error:<jobid>;<error code>}
Sophos 0x80004005 Vs
where <jobid> is a unique integer associated with the migration request and <error code> is an error code returned by the Sophos Central agent installer.
Sophos 0x80004005 Update
Always on anyconnect windows. You can look up the error by its error code and read about remediation steps in Precondition checks performed by the Sophos installer.