Home > Windows 7 > Cap12 Error 4107

Cap12 Error 4107

Contents

This error has no impact to functionality and no troubleshooting is needed. Join the IT Network or Login. A valid CTL was available on WU before the signing certificate expired. If the expired certificate is cached in one of the local system profiles, you must delete the content of some directories by using Windows Explorer.

Email Reset Password Cancel Need to recover your Spiceworks IT Desktop password? Source: http://support.microsoft.com/kb/2328240 Event ID 4107 or Event ID 11 is logged in the Application log in Windows and in Windows Server This error occurs because the Microsoft Certificate Trust List Publisher The only file in it was authroot.stl. First you need to get some detailed logging on what's failing, Click Start > Control Panel > Administrative tools > Event Viewer > Expand Applications and Services > Microsoft > Windows

Event Id 4107 Capi2 Windows 7

Instances of such an error can occur when the network retrieval attempt for the .cab file fails to go through a proxy server. Windows 7 Ultimate x64 - WU up to date. This was likely caused by the following issue: The signing certificate for the automatic root update CTL expired on 7/9.

Microsoft Customer Support Microsoft Community Forums Windows Client   Sign in United States (English) Brasil (Português)Česká republika (Čeština)Deutschland (Deutsch)España (Español)France (Français)Indonesia (Bahasa)Italia (Italiano)România (Română)Türkiye (Türkçe)Россия (Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 Choose operational and enable logging. Thursday, September 02, 2010 12:21 PM Reply | Quote 1 Sign in to vote I have now finally resolved the CAPI2 4107 issue with following method: Turn off UAC, restart machine Capi2 4107 Error Windows 7 By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks.

I won't do that until I hear back. What Is Capi2 Marco on July 21, 2010 at 4:02 am said: I'm so glad I found this site! Hang loose. See the article on how to clear the expired certificate from the cache.

Eventually this should be corrected from Microsoft. A Required Certificate Is Not Within Its Validity Period When Verifying Against The Current System Add Cancel × Insert code Language Apache AppleScript Awk BASH Batchfile C C++ C# CSS ERB HTML Java JavaScript Lua ObjectiveC PHP Perl Text Powershell Python R Ruby Sass Scala SQL The certutil command must be run for every user on the workstation. Open a Command Prompt window. (To do this, click Start, click All Programs, click Accessories, and then click Command Prompt.) 2.

What Is Capi2

handler has a max of 1024 and becomes confused. Best greetings from Germany Olaf Tuesday, August 03, 2010 10:01 PM Reply | Quote 0 Sign in to vote Eaxactly how long does the "cache" stay valid and how can we Event Id 4107 Capi2 Windows 7 A copy of the CTL with an expired signing certificate exists in the %windir%\ServiceProfiles\LocalService\AppData\LocalLow\Microsoft\CryptnetUrlCache\CryptnetUrlCachefolder directory. What Is Microsoft Windows Capi2 Open Windows Explorer. (To do this, click Start, click All Programs, click Accessories, and then click Windows Explorer.) 2.

Drove me nuts! Wednesday, November 24, 2010 1:23 PM Reply | Quote 0 Sign in to vote Does anyone know what to do or what the problem is if the certificates cannot be deleted? Login here! Since the cached CTL does not have a time valid signature, CAPI will retrieve the CTL from WU and obtain the valid CTL. Capi2 4107

Note: Your problem may not be McAfee, but at least you now have a better idea of what it is 🙂 Related Articles, References, Credits, or External Links NA Author: Migrated Here is the information from the Dev team: The event log error indicates that the signing certificate for the CTL (certificate trust list) has expired. RAC Task seems to coincide timewise with error log. I'm getting that in my daily detailed reports from all my SBS 2008 servers.

Recommend Us Quick Tip Connect to EventID.Net directly from the Microsoft Event Viewer!Instructions Customer services Contact usSupportTerms of Use Help & FAQ Sales FAQEventID.Net FAQ Advertise with us Articles Managing logsRecommended A Required Certificate Is Not Within Its Validity Period Windows 10 I also noticed this event error logged on my servers, and have consulted the Dev team. There are several behaviors that may cause this error in Event Log.

Positively!

Since the cached CTL does not have a time valid signature, CAPI will retrieve the CTL from WU and obtain the valid CTL. Troubleshooting PKI Problems on Windows Vista Arthur Xie TechNet Subscriber Support in forum If you have any feedback on our support, please contact [email protected] remember to click “Mark as Answer” on read more... Capi2 Error 513 A valid CTL was available on WU before the signing certificate expired.

x 24 Private comment: Subscribers only. Creating your account only takes a few minutes. To determine the cause of the CAPI2 error, I enabled CAPI2 logging in the event log. Exactly what steps do we need to do to get this error to stop?

Thanks! -------------------------------------------------------------------------------- Best regards, Tony Ma Partner Online Technical Community ----------------------------------------------------------------------------------------- We hope you get value from our new forums platform! I noticed my error occurred every time I rebooted, so rebooted the server and checked that event log by nativating to Applications and Services Logs\Microsoft\Windows\CAPI2\Operational.One of the log items indicated an Wiki Ninjas Blog (Announcements) Wiki Ninjas on Twitter TechNet Wiki Discussion Forum Can You Improve This Article? bradley on August 27, 2010 at 1:26 am said: Event ID 4107 or 11 is logged in the Application Log in Windows Vista or Windows Server 2008 and later: http://support.microsoft.com/default.aspx?scid=kb;en-us;2328240&sd=rss&spid=14498 Testing

Makes sense to ignore, IMO. If you are seeing this too, hang loose and don't follow what I previously posted on eventid.net Posted in: Uncategorized 20 Thoughts on “Failed extract of third-party root list from auto Here is the information from the Dev team: The event log error indicates that the signing certificate for the CTL (certificate trust list) has expired. and don't "runas" GeoffB on September 1, 2010 at 12:26 am said: http://support.microsoft.com/default.aspx?scid=kb;en-us;2328240&sd=rss&spid=14498 This solution does not work.

Has anyone at Microsoft checked the new certificate chain is correct? Login By creating an account, you're agreeing to our Terms of Use and our Privacy Policy © Copyright 2006-2016 Spiceworks Inc. I am seeing this on Server 2003 (Standard and SBS) along with Server 2008 (Standard and SBS). We re-signed the CTL with a renewed certificate and published it on Windows Update on 7/7.

Solution If you have been hunting for a fix, and got here, you may of already tried some or all of these which DID NOT WORK, downloading and installing the certs However, for any machine that had the older CTL cached, CAPI will first try to use the cached CTL which would result in the error you are seeing. I guess my question is; why then, if once the CTL has been updated is the error still present?