Sorry, for posting not much of contents lately. This moment I'm very busy at a customer side in Papendrecht (Netherlands). Right now I'm working on a implementation of a complete MOSS2007 infrastructure. This infrastructure is also placed in a staging environment where deployment of webparts, solutions and features are daily tasks. This day we see some strange behaviours in our IIS6.0 server running on Windows Server Standard Edition R2 X64 SP2.
Event ID 7076, 6398, and 6432 recurring errors;-(
After a lot of debugging I focussed myself on this item.
In our eventvwr we saw the following error messages: 7076, 6398, and 6432. Microsoft has now found the root cause of this problem to be the IIS ADSI provider. Essentially, if you have a process with more than one thread and two threads access IIS 6.0 at the same time, then this issue occurs. This problem is likely to occur for the SharePoint Timer service (OWSTimer.exe) in Microsoft Office SharePoint Server 2007. In our customer case it was the OWSTimer responsible for throwing up this error.
So I contacted Microsoft Customer Support Services to pickup my custom hotfix (WindowsServer2003.WindowsXP-KB946517-x64-ENU) for x64 systems where IIS6.0 is installed. After downloading the hotfix I install the hotfix and my eventvwr was completely clean ;-).
So, my tips for all users when installing OCS2007 or MOSS2007 on Windows Server 2003 x64/IIS6.0 (WOW64 support) please make sure this hotfix is installed when you have problems with eventid 7076, 6398, and 6432.