• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1078
  • Last Modified:

Crypt32 Error in Application Event Log

In the Application log of a Windows Server 2003 Standard Edition Service Pack 2 server we continually get the error:

Failed auto update retrieval of third-party root list sequence number from: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootseq.txt> with error: This operation returned because the timeout period expired.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

We have Symantec End Point Protection so I tried this fix: http://www.symantec.com/business/support/index?page=content&id=TECH106277&locale=en_US and it did not work, even after a reboot.

I also updated Internet Exporer 6 to Internet Explorer 7.

- I see you can uninstall Root Certificates Add/Remove Windows Components but I would like to keep the configuration the same. This seems like a workaround and not a fix.
  • 2
  • 2
1 Solution
- do you use proxy to access Internet?
- in most case this happen when your servers cannot connect to Microsoft to retrieve some updates (especially the crypt32 process).
AIRITServiceDeskAuthor Commented:
We have an Proxy (ISA) setup for our client workstations but not on the server in question. We have several domain controllers in the same subnet and only one of them is getting generating this error. It looks like it started occuring when Symantec End Point Protection was installed based on the timestamps in the Event Log.
Personnaly i've often encounter this issue and the only way we found was to manually install root certificate update or as you suggested to remove the Root Certificates in Add/Remove programs.
Are your servers getting updates from WSUS? Because this could help to ensure your root certificates are up to date.
If you suspect Symantec (and i think you're right), then you could maybe review the settings of this

Else i've found many information about this on Symantec:
And some solution too with ISA

Maybe have you configured proxy autodiscovery with ISA (WPAD) and probably with DHCP, so all your clients discover this information. But if DHCP traffic between your DC and the server is unallowed by SEP, then unable to discover proxy and fails.
Review this, it's for wsus but it's interesting to understand what happens:
AIRITServiceDeskAuthor Commented:
- We do not use a Proxy on our servers.
- As soon as Symantec End Point Protection is uninstalled, the errors is stops.
- As soon as Symantec End Point Protection is installed, the error starts occuring every 10 minutes.
- I spoke to Symantec Technicial Support and the only reccomendations they had were the ones I found in the following Knowedge Base articles:

        - Symantec KB article:
        - Microsoft KB
- We have uninstalled Root Certificates from Add/Remove windows Components
- You cannot apply Root Certificate Updates to Servers, via WSUS, because the Root Certificate Updates "only apply to Windows XP workstations" based on WSUS.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now