troubleshooting Question

Event ID Error 4625 SBS 2008

Avatar of bmilne1957
bmilne1957Flag for United States of America asked on
SBSServer HardwareWindows Server 2008
3 Comments1 Solution5032 ViewsLast Modified:
I have a SBS 2008 I have inherited and I am receiving a Event ID
4625 Audit Failure.

According to  KB 920783 I need to "Select Users, Computers, or Groups dialog box, type the domain user account that you specified as the Windows SharePoint Services 3.0 service account, click Check Names, and then click OK In the Permissions for UserName list, click to select the Allow check box that is next to Local Activation, and then click OK two times."

It appears that "testuser" was used then deleted. How would I proceed to correct this error? It logs almost two errors per second.




Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          10/26/2009 6:39:27 PM
Event ID:      4625
Task Category: Logon
Level:         Information
Keywords:      Audit Failure
User:          N/A
Computer:      SERVER1.office.local
Description:
An account failed to log on.
 
Subject:
	Security ID:		SYSTEM
	Account Name:		SERVER1$
	Account Domain:		OFFICE
	Logon ID:		0x3e7
 
Logon Type:			8
 
Account For Which Logon Failed:
	Security ID:		NULL SID
	Account Name:		testuser
	Account Domain:		OFFICE
 
Failure Information:
	Failure Reason:		Unknown user name or bad password.
	Status:			0xc000006d
	Sub Status:		0xc0000064
 
Process Information:
	Caller Process ID:	0x5ec
	Caller Process Name:	C:\Windows\System32\inetsrv\inetinfo.exe
 
Network Information:
	Workstation Name:	SERVER1
	Source Network Address:	-
	Source Port:		-
 
Detailed Authentication Information:
	Logon Process:		Advapi  
	Authentication Package:	MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
	Transited Services:	-
	Package Name (NTLM only):	-
	Key Length:		0
 
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
 
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
 
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
 
The Process Information fields indicate which account and process on the system requested the logon.
 
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
 
The authentication information fields provide detailed information about this specific logon request.
	- Transited services indicate which intermediate services have participated in this logon request.
	- Package name indicates which sub-protocol was used among the NTLM protocols.
	- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-a5ba-3e3b0328c30d}" />
    <EventID>4625</EventID>
    <Version>0</Version>
    <Level>0</Level>
    <Task>12544</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8010000000000000</Keywords>
    <TimeCreated SystemTime="2009-10-26T23:39:27.678Z" />
    <EventRecordID>12261856</EventRecordID>
    <Correlation />
    <Execution ProcessID="652" ThreadID="32920" />
    <Channel>Security</Channel>
    <Computer>SERVER1.office.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="SubjectUserSid">S-1-5-18</Data>
    <Data Name="SubjectUserName">SERVER1$</Data>
    <Data Name="SubjectDomainName">OFFICE</Data>
    <Data Name="SubjectLogonId">0x3e7</Data>
    <Data Name="TargetUserSid">S-1-0-0</Data>
    <Data Name="TargetUserName">testuser</Data>
    <Data Name="TargetDomainName">OFFICE</Data>
    <Data Name="Status">0xc000006d</Data>
    <Data Name="FailureReason">%%2313</Data>
    <Data Name="SubStatus">0xc0000064</Data>
    <Data Name="LogonType">8</Data>
    <Data Name="LogonProcessName">Advapi  </Data>
    <Data Name="AuthenticationPackageName">MICROSOFT_AUTHENTICATION_PACKAGE_V1_0</Data>
    <Data Name="WorkstationName">SERVER1</Data>
    <Data Name="TransmittedServices">-</Data>
    <Data Name="LmPackageName">-</Data>
    <Data Name="KeyLength">0</Data>
    <Data Name="ProcessId">0x5ec</Data>
    <Data Name="ProcessName">C:\Windows\System32\inetsrv\inetinfo.exe</Data>
    <Data Name="IpAddress">-</Data>
    <Data Name="IpPort">-</Data>
  </EventData>
</Event>
ASKER CERTIFIED SOLUTION
Manpreet SIngh Khatra
Solutions Architect, Project Lead
Join our community to see this answer!
Unlock 1 Answer and 3 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 3 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros