Links

Microsoft Support - How to recover from a corrupted registry that prevents Windows XP from starting (KB307545)
Software Sleuthing - Errors (007) FACILITY_WIN32 veel van de 0x8007#### errors in één overzicht.

MicroSoft Support - The Framework.log file grows larger than 64 KB when you use WMI on a Windows Server 2003 or Windows XP computer (KB836605)

Seen this one time so far on a Windows Server 2003 Std SP2 server with a Framework.log of around 230 MB.
After granting Modify NTFS rights to NETWORK SERVICE on C:\Windows\system32\wbem\logs\, the old FrameWork.log file was renamed to FrameWork.lo_ and a new one was created.

See also:Smallvoid.com - Configure the WMI logging level

The contents of the FrameWork.log might look like this:

Unable to locate Shell Process, Impersonation failed.	06/20/2011 09:45:25.823	thread:24660	[d:\nt\admin\wmi\wbem\providers\win32provider\common\implogonuser.cpp.175]
Shell Name Explorer.exe in Registry not found in process list.	06/20/2011 09:45:25.823	thread:23868	[d:\nt\admin\wmi\wbem\providers\win32provider\common\implogonuser.cpp.163]

If so then you can “safely” ignore the error because:

“After a time.. Microsoft say's “You can Ignore this , it's by design” . It has something to do with the Kerberos/ NTLM authorization. On win2003 machines Kerberos used instead of NTLM. But WMI is first trying NTLM , this fails and the log records are created, then WMI try's Kerberos.”
Source:PC Review > Forums > Newsgroups > Windows XP > Windows XP WMI > Shell Name Explorer.exe in Registry not found in process list alternate links here and here.

Soms wil je de security op een XP systeem herstellen naar de default, hiervoor kun je gebruik maken van secedit in combinatie met de security template secsetup.inf in de %windir%\repair directory. Dit gaat als volgt:

secedit /configure /cfg %windir%\repair\secsetup.inf /db secsetup.sdb /verbose

Bron:Mike-Tech.com - Reset Windows Security Back To Default Settings

Probleem op Windows Server 2003 VM was dat na een x aantal uur deze melding opdook.

De VM gebruikte Scheduled Tasks om elke minuut een heleboel kleine bestanden te verplaatsen. Dit werd gedaan door middel van een VBScript dat een drive mapping aanmaakte (en niet verwijderde) en vervolgens daarvandaan de bestanden haalde en er bestanden plaatste.

Na het bijzetten van twee extra directories werden er na een x aantal uren geen bestanden meer verplaatst, terwijl de taken wel zonder foutmelding draaiden. Alleen een robocopy actie gaf de melding “The network BIOS session limit was exceeded” weer.

Oplossing lijkt te zijn om geen drive mappings te gebruiken, want na het aanpassen van het script zodat deze UNC paden in plaats van drive mappings gebruikte was het probleem verdwenen.

Bronnen:
TechArena Community - Error 69 -The network BIOS session limit was exceeded
Microsoft Support - Error Message: The Network BIOS Session Limit Exceeded (KB297972)
Zie ook:Microsoft Support - "The network BIOS command limit has been reached" error message in Windows Server 2003, in Windows XP, and in Windows 2000 Server (KB810886)

Windows Error Reporting can fill up C:\ProgramData\Microsoft\Windows\WER\ReportQueue with error reports.

If you want to disable it, here's how:

1. Go to Start
2. Enter 'problem' in the search box select “Choose how to report problems”
3. Click on “Change report settings for all users”
4. select “Never check for solutions(not recommended)”
5. Click on OK

Source:Walker News - How To Disable Vista Error Reporting Feature

EventID.Net - Event ID: 2012 Source: Srv
EduGeek.net forum - Event ID 2012 Source Srv on Server 2008
Windows Sysinternals forum - Event Id 2012 error transmititing and receiving

OS: Windows Vista SP2 x64.
MSI: PhysX_9.12.1031_SystemSoftware.msi

An MSI installer is giving the following error:

The installer has encountered an unexpected error installing this package. 
This may indicate a problem with this package. 
The error code is 2738. The arguments are: , , 

From the log you get when you try to install the MSI like this:

msiexec /i C:\NVIDIA\DisplayDriver\310.90\Win8_WinVista_Win7_64\English\PhysX\PhysX_9.12.1031_SystemSoftware.msi /lv c:\log.txt

You get the following:

DEBUG: Error 2738:  Could not access VBScript runtime for custom action 

If the following (in an elevated command prompt) isn't enough:

cd C:\Windows\system32
regsvr32.exe vbscript.dll
cd C:\Windows\SysWOW64
regsvr32.exe vbscript.dll

Do this:

reg delete "HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f
reg delete "HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{F414C260-6AC0-11CF-B6D1-00AA00BBBB58}" /f

Sources:
Mitch Denny - The error code is 2738
Aaron Stebner's WebLog - How I resolved Windows Installer error code 2738 on Vista while running light.exe from WiX v3.0