Home | Site Map | Cisco How To | Net How To | Wireless | Search | Forums | Services | Quick Setup | Careers | About Us | Contact Us|
|
|
Home | Site Map | Cisco How To | Net How To | Wireless | Search | Forums | Services | Quick Setup | Careers | About Us | Contact Us| |
|
|
|
Event ID
from 1 to 999
Event Viewer display no information
Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here! Event ID 0 - The following fatal error occurred in the Remote Web Workplace Application Event ID 1 ThinPrint – Incorrect function Error in function number 3, error #: 11e0001 Event ID 1, 3201 and 3041 Vista can't access VPN with Event ID 1 Event ID 1, 7, 20, 39, 49 and 129: iSCSIprt issues Event ID 2 - IAS related Event IDs and Reason Codes. Event ID 3: IAS Reason-Code = 5 ISA event ID 3 and 5052 Event ID: 4 Troubleshooting Event ID 6, 142 and 4026 Event ID: 7 Can't logon domain with event ID 5719, 18, 29 ,7 Event ID 1, 7, 20, 39, 49 and 129: iSCSIprt issues Event ID 10 - User administrator at host x.x.x.x has timed-out after 120 seconds of inactivity Event ID 11- There are multiple accounts with name host/printsrv.chicagotech.net of type 10 Event ID: 11 - There are multiple accounts VSS Event 11 and 12292 are logged - 8004230f Event ID 13: RADIUS message was received from invalid client Event ID 14: Attempt to set time which differs by more than Event ID 18: authenticator attribute that is not valid Event ID 18: authenticator attribute that is not valid Can't logon domain with event ID 5719, 18, 29 ,7 Event ID: 20 Event ID 1, 7, 20, 39, 49 and 129: iSCSIprt issues Event ID: 21 and 41, Source: TermServLicensing Can't connect via RDP with event ID 26 Event ID 28: Port was prevented from using MAC address Event ID 29 - W32time Resolution: Event ID 29 and 7024 - TS Licensing Can't logon domain with event ID 5719, 18, 29 ,7 Event ID 30 - The server was unable to read the file... Hyper-V Event ID: 32, 12010 and 12570 - can't start VM Event ID 35: The shadow copies of volume F: were aborted because the shadow copy storage failed to grow Event ID 38, 47 and 29 - Source: W32Time Event ID 41 - The file system structure on the disk is corrupt and unusable. event 50 is generated on your machine Event ID: 49 Event ID 50: Delayed Write Failed Case collection of Event ID 50 Source TermDD Event ID 52 - Description: Object Name not found TS won't allow remote printing through RDP with Event ID 55 HP Server reboot with Event ID 57 Event ID: 112 - Details: Not enough space to write to the disk. Troubleshooting Event ID 6, 142 and 4026 Event ID 201 – “No license was available Event ID: 201: Task Scheduler successfully completed task "\SyncData" , instance "{854fcef7-7472-4c7f-9032-edbbba46bd50}" , action "C:\Windows\SYSTEM32\cmd.exe" with return code 16. Event ID 202 - License Service Event ID 215 - The backup has been stopped because it was halted by the client Event ID 333 - An I/O operation initiated by the Registry failed unrecoverablly Event ID 372: The document failed to print An error 401 access denied appears Event ID 434 - HP Network Team #1: PROBLEM Not able to access Windows Update website with Event ID 485 Event ID: 504 - DNS server could not create zone Windows 2008 backup has failed with Event ID 517 Event ID 529 - Logon Failure Event ID 529 - OWA error 401 Here are thousands of events 529 on the SBS Event ID 534 - Logon Failure: The user has not been granted the requested Event ID: 537 - An error occurred during logon Event ID 538 Event ID 539 - Logon Failure: Account locked out Event ID 552 - Logon attempt using explicit credentials Event ID 560 Event ID 675 – Pre-authentication failed Event ID: 675 Event ID 675 Event 4771, 675 and 673 Event ID from 1000 to 1999 Event ID from 2000 to 2999 Event ID from 3000 to 3999 Event ID from 4000 to 4999 Event ID from 5000 to 5999 Event ID from 6000 to 6999 Event ID from 7000 to 7999 Event ID from 8000 to 8999 Event ID from 9000 to 9999 Event ID over 10000 Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here! The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 14 minutes. NtpClient has no source of accurate time.
Resolution:
1. Synchronize the computer with the DC. Event ID 41 - Description: The file system structure on the disk is corrupt and unusable. Causes: 1. The
CPUs in your computer are not all at the same stepping level, and
Windows writes an informational message to the Event log. Event ID 1000 and 1001 - Windows cannot read the history of GPOs from the registry - The computer has rebooted from a bugcheck. - Security policy cannot be propagated. - The Group Policy client-side extension Security was passed flags (17) and returned a failure status code of (3).
If a multihomed domain controller does not have File and Printer Sharing bound to it, the following multiple problems are logged or displayed when you attempt to work with Group Policy objects on the domain controller:
1)UserEnv 1000 The Group Policy client-side
extension Security was passed flags (17) and returned a failure
status code of (3).
2) SceCli 1001 Security policy cannot be propagated. Cannot access the template. Error code = 3. \\domain name\sysvol\domain name\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine\Microsoft\Windows NT\SecEdit\GptTmpl.inf. 3) UserEnv 1000 Windows cannot access the registry information at \\domain name\sysvol\domain name\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine\registry.pol with (51). 4) Attempting to gain access to the Group Policy objects by using the Domain Security policy and the Default Domain Controller Security policy displays a "Group Policy Error" error message. The text of the message states: "Failed to Open Group Policy Object. You may not have appropriate rights. Details: The network path not found." 5) Attempting to access the Group Policy objects by using the Active Directory Users and Computers snap-in or Group Policy Editor displays a "Domain Controller for Domain domain name not found" error message. There are several options, none of which work. 6) Attempting to open the Sysvol share by using \\domain name\sysvol causes a "Remote Computer not available" error message.
RESOLUTION:
|
| Symptoms: your w2k/xp clients may receive this Event ID 1053 - Windows cannot determine the user or computer name. (<error description>). Group Policy processing aborted. Or error: "The specified user does not exist." |
Resolutions: 1.
Make sure that your internal DNS server is the server for the domain
you are logging in to.
2. Verify the DNS Settings. This will occur if your DNS server is
unable to resolve information about your domain.
3. Delete the problem computer from DNS records and re-create it.
Symptoms: when logon TS, System Event Viewer may receive the above messages.
Resolution: 1. Install the printer drive in the TS server.
2. You have to edit the Ntprint.inf file to fix this problem.
1. Windows 2000 domain controllers running Terminal Services configured to use Remote Administration mode do not permit regular user logon, with the exception of two concurrent administrator accounts for server management. When a user attempts to connect to a Windows 2000-based domain controller running Terminal Services configured to use Remote Administration mode, the following error message is generated: You do not have access to logon to this Session.
2. Windows 2003 domain controllers running RDC do not permit regular user logon, with the exception of administrator accounts.
3. The user attempting to log on does not have sufficient permissions on the appropriate RDP-TCP connection. Modify the RDP-TCP permissions by using Terminal Services Configuration to grant the user or group the logon permission.
4. Terminal Services has a default connection security setting allows only administrators to log on. If the security attributes on a specified connection have not been set, the connection inherits these default security settings.
Error 1311 - There are currently no logon servers available to service the logon request
Symptoms: The primary purpose of logging on with cached credentials is to enable you to access the local workstation. However, if you have logged on by cached credentials, you may be unable to access network resources because you have not been authenticated. For example 1) after you log on to a w2k/xp laptop by using cached credentials, you may be unable to access the network resources. This issue is commonly experienced by laptop users whose computer resides in a Windows Server domain and who log on to the computer by using cached credentials prior to being able to establish a remote access connection. 2) You log on to a w2k/xp laptop with a domain logon option in a workgroup network. After you establish the connection and you try to map the network drives, the operation may be unsuccessful, and you may receive the following error message: "System Error: (1311) There are currently no logon servers available to service the logon request."
Case Study - There are currently no logon servers available to logon your request
Event ID: 2011 When accessing shares on a server from a client, you may receive "Not enough server storage is available to process this command." error. .
Resolution: The registry value IRPstackSize may be not explicitly present. To increase the value of the parameter, go to the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ LanmanServer\Parameters. If the key is not present, choose Add Value in the Registry Editor. The Value Name should be IRPStackSize and the Data Type is REG_DWORD. Refer to MS Q106167 and Q177078 for more details.
Symptoms: Some
hardware like 3COM Dynamic Access Protocol and USRobotics PCI
56K faxmodem, and software such as Symantec's Norton AntiVirus, Open
File Manager and overloading services can cause to leak non-paged
pool memory. You may get the following symptoms.
1.You may receive Event ID 2019, "The server was unable to allocate
from the system non-paged pool because the pool was empty".
2. Your server may lose network connectivity with its clients and
report the following errors in the event log: Event ID: 2020, "The
server was unable to allocate from the system paged pool because the
pool was empty".
3. Event ID: 2021: Server was unable to create a work item n
times in the last seconds seconds.
4. Event ID 2022: "The server was unable to find a free connection 4
times in the last 60 seconds".
5. Your server may stop accepting new user connections and you may
receive this message "Windows cannot logon you because the profile
cannot be loaded. Contact your network administrator. DETAIL -
Insufficient system resources exist to complete the requested
service."
6. You may receive the following error: "Not enough storage
available to process this command".
7. If you keep getting above errors without fixing, the
server may need to reboot.
Resolutions: 1.
Apply the Latest Service Pack.
2. Apply the Latest Device Driver Updates.
3. Examine the Hard Disks for Errors and Defrayment the Hard Disk
Drives.
4. Upgrade or apply SP to the suspect software.
5. Try to maximize the resources that can be made available to the
Server service. This may eliminate the error messages or only lessen
the frequency of the errors.
Causes: Netlogon Issue
Symptoms: 1.
When you double-click My Network Places in a
client, an incomplete browse list is displayed.
2. Computers that do not have file and printer sharing turned on do
not appear in the browse list.
3. Windows client that try to use the browse list gets Event ID 8021
or 8032:
4. On the domain controller that does not have file and printer
sharing turned on gets Event ID: 2504 or Event ID: 2505
Cause: This update helps resolve an issue on computers running Windows XP Service Pack 2. Programs that connect to IP addresses in the loopback address range may not work as expected and you may receive an error message indicating you cannot establish a connection.
Event ID: 3095 - Source: NETLOGON - This Windows NT computer is configured as a member of a workgroup, not as a member of a domain. The Netlogon service does not need to run in this configuration.
1. Since the Netlogon service should not be
configured to start automatically on a server that is not a domain
member (a stand-alone server or non-networked Windows NT-based
computer), configure the Netlogon service so that its startup type
is set to "Manual."
2. Make sure workstation service is running and restart
Symptoms: After install or uninstall some services or patches, you may receive some the following messages:
Event ID : 4119 Source : TCP/IP Description: IP could not open registry key for NdiswanX. -or- Event ID : 4311 Source : NetBT Description: Initialization failed because the driver device could not be created.
Event ID 5701 - The Netlogon service failed to update the domain trust list
Netlogon Event ID 5701: The Netlogon service failed to update the domain trust list. The following error occurred: There are currently no logon servers to validate the logon request.
Causes: 1. You may have exhausted
the NetBT datagram buffer.
2. This error can be caused by a failing NIC or
defective device driver.
Event ID 5774, 5775 and 5781 - Netlogon
Symptoms: you may find Event ID 5774 and 5775 - Registration of the DNS record '<dns record>'. 600 IN SRV 0 100 3268 <domain name>.' failed with the following error: <error description>.on your AD with DNS server.
Resolutions: 1.
Make sure
the Domain Controller points to itself as a DNS
server.
2. If you have two NICs on this server, disable one of them
or point all NICs to the internal DNS.
3. If you just upgraded the server or changed the IP, you
may need delete the problem record manually and restart the
NETLOGON service.
Symptoms: when attempting to logon a domain, you keep getting an error that "The system cannot log you on now because the domain "name" is not available." Also, Event viewer shows Event ID: 5719. No Windows NT or Windows 2000 Domain Controller is available for domain <domain name>. The following error occurred: There are currently no logon servers available to service the logon request.
Resolutions: One possible cause of this error is that you have run out of buffer space in the NetBT datagram buffer. To resolve this problem, increase the MaxDgramBuffering value from 128 KB to 256 KB. Run Regedt32.exe, go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters. On the Edit menu, click Add Value, and then add the following information:
Value
Name: MaxDgramBuffering
Data Type: REG_DWORD
Value: 0x40000
Refer to 072704RL
Event
ID 5805 - Net Logon
Cause: A machine account
failed to authenticate, which is usually caused by
either multiple instances of the same computer name, or
the computer name has not replicated to every domain
controller.
Event ID: 7024 - Source: Service Control Manager - The Net Logon service terminated with service-specific error 3095.
Resolution: refer to Event ID: 3095
Resolutions: 1. Make sure Remote Access Connection Manager service, Remote Access Auto Connection Manager, and the Telephony service are enabled and running.
2. If the server is running IAS, you may have this issue if the Oledb32.dll and Oledb32r.dll files are incorrectly registered.
3. If the server is running ISA, it is better to use ISA instead of RRAS.
4. This can be caused by a third-party program installed on the computer. In this case, you may want to remove RRAS and Reinstall it.
5. You may try rarepair.exe download it here.
6. If you don't use IPX, delete IPX from HKEY_LOCAL_MACHINE>System>CurrentControlSet>Services>RemoteAccess>RouterManagers.
7. If you use IPX, manually set the internal network number and specify Manual Frame Type Detection for the properties of the NWLink IPX/SPX Compatible Transport.
Event id: 8021 - Source: Browser - Description: The browser was unable to retrieve a list of servers from the browser master <PDC> on the network \device\<protocol_netcard>. The data is the error code. Resolution: Fixing Browser Problem.
Event ID 20078 - The account for user <username> connected on port VPN# does not have Remote Access privilege. The line has been disconnected. Event ID 20189 - The user <username> connected from x.x.x.x but failed an authentication attempt due to the following reason: The user tried to connect using an unauthorized dial-in media.
Causes: 1. No dial-in permission. 2. Incorrected logon ID. 3. Check Error 649 resolution.
Event ID 20073 - The following error occurred in the Point to Point Protocol module on port %port%. There are no authentication protocols available for use.
Cause: 1. The RRAS
server's authentication and encryption settings are set to require
Microsoft encrypted authentication and you are using Remote
Authentication Dial-In User Service (RADIUS) as your authentication
provider.
2. Both client and server have different Authentication Methods.
Re: RAS/VPN Event ID 20049, Event ID 20073 and Error 619
Event ID 20097 -
A Demand Dial connection to the remote interface <interface name> on
port VPNx-y was successfully initiated but failed to complete
successfully because of the following error: The L2TP connection attempt
failed because security negotiation timed out.
Event ID 20111 -
1. A Demand Dial connection to the remote
interface ToChicagoTech on the port VPNx-### was successfully initiated
but failed to complete successfully because of the following error: No
more connections can be made to this remote computer at this time
because there are already as many connections as the computer can
accept.
2. A Demand Dial connection to the remote interface ToChicagoTech on the
port VPNx-### was successfully initiated but failed to complete
successfully because of the following error: The remote computer did not
respond.
3. A Demand Dial connection to the remote interface ToChicagoTech on the
port VPNx-### was successfully initiated but failed to complete
successfully because of the following error: There was no answer.
Cause: 1. The certificate on the VPN server is
not a valid machine certificate or is missing.
2. The IPSec Policy Agent service is stopped.
3. Enable the user to allow dial -in.
4. Too many connections.
5. No connections between two sites.
6. Incorrect routing table.
7. Also refer to RAS Error 792 or Error 781.
Event id 20106 - Unable to add the interface Internal with the Router Manager for the IP protocol.
Resolutions: 1. Make sure you have correct interface setup, for example, no NIC using 169.254.x.x IP and no 1394 interface.
2. Make sure no NIC of the RRAS is disabled.
3. If the RRAS server is configured only for LAN routing, you can ignore the event.
4. The interface type is not dedicated.
5. The loopback and router is configured in Lanonly mode
Post your questions, comments, feedbacks and suggestions
Related Topics
Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here!
|
|
|
This web is provided "AS IS" with no warranties.
Copyright © 2002-2012
ChicagoTech.net,
All rights reserved. Unauthorized reproduction forbidden.