2012-09-13 :738 892 5c0 PT PT: Synchronizing server updates 2012-09-13 :738 892 5c0 PT Service Id = , Server URL = Web Service/2012-09-13 :769 892 5c0 PT WARNING: Cached cookie has expired or new PID is available 2012-09-13 :769 892 5c0 PT Initializing simple targeting cookie, client Id = a6c96caf-d9ca-4f31-a003-827e7089ff64, target group = Server, DNS name = srv-exchange.porta.2012-09-13 :769 892 5c0 PT Server URL = Auth Web Service/Simple 2012-09-13 :957 892 5c0 PT WARNING: Get Authorization Cookie failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404 2012-09-13 :957 892 5c0 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80244019 2012-09-13 :957 892 5c0 PT WARNING: Populate Auth Cookies failed: 0x80244019 2012-09-13 :957 892 5c0 PT WARNING: Refresh Cookie failed: 0x80244019 2012-09-13 :957 892 5c0 PT WARNING: Refresh PTState failed: 0x80244019 2012-09-13 :957 892 5c0 PT WARNING: Sync of Updates: 0x80244019 2012-09-13 :957 892 5c0 PT WARNING: Sync Server Updates Internal failed: 0x80244019 2012-09-13 :957 892 5c0 Agent * WARNING: Failed to synchronize, error = 0x80244019 2012-09-13 :957 892 5c0 Agent * WARNING: Exit code = 0x80244019 And, actually, another support article caught my eye: You cannot download updates when you access the Windows Update Web site from a Windows XP-based computer that is behind a firewall or a proxy server That article refers to XP, but I had to recently tweak with the Win HTTP settings on that server to resolve yet another issue (Please see the support article Error message when you import a third-party certificate into Exchange Server 2010: "The certificate status could not be determined because the revocation check failed" for further details).
The package offers a set of R functions for the installation and updating of software (currently, only on Windows OS), with a special focus on R itself. You can see the latest version of installr on github, where you can also submit bug reports (you may also just leave a comment in this post).
Usually, Microsoft themselves will notice this error and be able to fix it within a week.
However, if you want the update before then, it is important to correct this error.2.
However, the answers concept for Microsoft works fairly well, so check it out here if you have any additional questions.