Error Event Id 2012
Contents |
Event ID 2012 Source srv appears in the System event log. Solution: 1. Ensure the Network Interface Card (NIC) drivers are current. 2. Ensure the NIC firmware is current. 3. Ensure the NIC event id 2012 perfos drivers and firmware match. NIC vendors often release drivers and firmware together and windows event id 2012 require they are updated at the same time to resolve known issues. 4. Ensure the network switch firmware is current.
Event Id 2012 Server 2008
5. Event ID 2012 Source srv are often times normal and can safely be ignored. Refer to the Additional Information section of this article for further details. 6. Disable TCP/IP Offload Engine (TOE)
Event Id 2012 Windows 2003
in the NIC vendor software. 7. Disable Receive Side Scaling (RSS) in the NIC vendor software. 8. Disable Large Send Offload (LSO) in the NIC vendor software. 9. Disable the following using an elevated Command Prompt. a. Press the Windows Logo+R, type runas /user:administrator@domain.local cmd where domain.local is replaced by the name of the Active Directory domain or local server name and press Enter. The event id 2029 same task can be accomplished using the Command Prompt and Run as Administrator. b. Type the Administrator account password when prompted and press Enter. Note: The command on line e. is available on Windows Server 2008 and Windows Server 2008 R2. c. Type netsh int tcp set global rss=disabled and press Enter. d. Type netsh int tcp set global netdma=disabled and press Enter. e. Type netsh int tcp set global chimney=disabled and press Enter. f. Type netsh int tcp set global autotuninglevel=disabled and press Enter. g. Type netsh int tcp set global congestionprovider=none and press Enter. h. Reboot the server. Additional Information: This information applies to Windows Server 2008, Windows Server 2008 R2, Windows Server 2012 and Windows Server 2012 R2. Event ID 2012 Source srv can occur for many reasons some of which are completely normal. Some examples of normal conditions are below. Heavy network congestion during peak times. Older Windows server and client operating systems using older versions of SMB with newer versions of Windows server. Unix or Apple server and client computers in the environment using older versions of SMB with newer versions of Windows server. Server or client computers using redirecte
★★★★★★★★★★★★★★★ YongRhee[MSFT.]May 16, 20150 0 0 0 Applies to: Windows Server 2012 R2 Windows 8.1 Windows Server 2012 Windows
Event Id 2013
8.0 Windows Server 2008 R2 Windows 7 Windows Server 2008 Windows event id 2009 Vista In the System event log, you might notice: Log Name: System Source: srv Event event id 2012 srv windows 2008 r2 ID: 2012 Level: Warning Computer: MachineName.fqdn Description: While transmitting or receiving data, the server encountered a network error. Occassional errors are expected, but large amounts of these http://www.dell.com/support/article/us/en/19/SLN290686/EN indicate a possible error in your network configuration. The error status code is contained within the returned data (formatted as Words) and may point you towards the problem.
Topic Printable Version Translate Topic zizebra Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 20 May 2009 http://forum.sysinternals.com/event-id-2012-error-transmititing-and-recieving_topic19973_page2.html Location: CT Status: Offline Points: 150 Post Options Post Reply Quotezizebra Report Post Thanks(0) QuoteReply Posted: 14 August 2009 at 11:34am The DCs are running Windows 2008 and the rest 2008. We have about 20 DCs in about 10 Geographically spaced locations and they are all logging the same errors. These servers are not necessarily the same but event id most are HPs. The whole network is running on1Gb ethernet.I am highly doubtful that this has anything to do with NICs failing. but it might as well be true. How can we read the status code in the data or can we use Network Monitor to see the issue if it is stemming from the network. I have disjoined event id 2012 and rejoined several clients on the network but the problem stays on. The client will still log errors as well. Iam thinking that the servers might not be coping and there are some fine tuning parameters that needs to be in place. molotov Members Profile Send Private Message Find Members Posts Add to Buddy List Moderator Group Joined: 04 October 2006 Status: Offline Points: 17526 Post Options Post Reply Quotemolotov Report Post Thanks(0) QuoteReply Posted: 14 August 2009 at 11:50am The status code is found in the data associated with the 2012 event. Some occurrences of 2012 are normal, as the message says... . Occassional errors are expected, but large amounts of these indicate a possible error in your network configuration. Daily affirmation: net helpmsg 4006 zizebra Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 20 May 2009 Location: CT Status: Offline Points: 150 Post Options Post Reply Quotezizebra Report Post Thanks(0) QuoteReply Posted: 14 August 2009 at 12:09pm These are happening every 45 minutes