CAPI2 Errors

pbcopter said:

I had this occur on two machines about six months ago and after completing the steps in the link I gave you, no more problems. I did them manually and did not use Fixit, however.

I did it manually twice already but still no joy. I'll try it one last time then I'll give up. Thanks for your reply. I've tried the fix (manually) again but to no avail. I even did a deletion of the Certificates registry entries (backed them up) but still no luck. Can this be a Microsoft issue? The process that the error relates to is Isass.exe rather than to some program or other. Thanks in advance for any additional replies.

The only reasons you'd get a 4107 is if the CRL on your machine is expired (requiring the manual intervention in the KB), or if the date was off (which you've validated is not). Unfortunately, you can't update the certificiate list if your current one is expired (which is normal for certificates, so it's not specifically a Microsoft issue), hence why there's a fixit to manually replace it.

However, if that doesn't work, you probably have an underlying CAPI issue on the machine itself, hence why it got out of date in the first place. What we need at this point are CAPI logs:

1. Open Event Viewer
2. Expand Application and Services Logs
3. Expand Microsoft, expand Windows, and expand CAPI2
4. Right-click "Operational" and click "Enable Log"
5. Allow the log to collect events until the next 4107 is logged, and then use the same steps above to disable the log
6. Save All the events in that log as an .evtx file, and then zip and upload the compressed log file (if it's too big for the boards, you may have to share from a file hosting site)

cluberti:

I'd like to know if this is (1) really a problem or (2) just an annoyance. A friend has a Win7 Pro 64-bit HP PC that recently started getting these. I only know because I was looking through the logs and saw the errors. It seems to work OK, though, it's just logging these errors over and over and over. I gave the machine back to them a couple of days ago.

If this is a real problem, then I need to figure out how to clean this up. If it's just an annoyance, I'll let it go.

Thanks.

It's a real problem, yes - anything that uses CAPI can fail (doesn't mean it will, but can). If you're seeing it, it is indeed a problem that should be dealt with.

Cluberti: Thanks for your reply. I'll try what you suggested. Mark: To me it is more of an annoyance than a problem as it does not seem to be causing any problems with functionality or anything else for that matter. I wish I could get to the bottom of it though! Cluberti: I've enabled the log as you suggested and am waiting for events to occur. One thing however is that none of the errors in the CAPI2 Operational Log are 4107 errors. (found this by scrolling down until I found previous errors) I'll wait awhile and see what gets logged in over the next few hours then I'll upload the log info.