The Inetinfo.exe process repeatedly crashes and restarts, and "Event ID 7031" and "Event ID 7034" error events are repeatedly logged in the system log in Windows Server 2003.
This is from Knowledge Base article Q827214.
What you might notice is that your SMTP fails, emails stop coming in and out, and there are zillionz of 7034/7031 messages in the event log. Rebooting might fix it for a few minutes, hours, or days.
To fix this you have to download the fix, farther down this post.
SYMPTOMS
After you restart a Microsoft Windows Server 2003-based computer that is running the Simple Mail Transfer Protocol (SMTP) service with or without Microsoft Exchange Server 2003, the Inetinfo.exe process the Inetinfo.exe process unexpectedly crashes and then restarts. This problem occurs several times. The Error Reporting dialog box appears on the screen every time that the Inetinfo.exe process crashes. Additionally, the following events are repeatedly logged in the system event log:
Source: Service Control ManagerType: ErrorEvent ID: 7031Description:The IIS Admin Service service terminated unexpectedly. It has done this x time(s).
Source: Service Control ManagerType: ErrorEvent ID: 7034Description:The Simple Mail Transport Protocol (SMTP) service terminated unexpectedly. It has done this x time(s). Note You may also see additional "Event ID 7034" error events logged by services that are dependent on the IIS Admin Service.
RESOLUTION
Download informationTo resolve this problem, install the following update file. The following file is available for download from the Microsoft Download Center:
Download the Windows Server 2003 Standard Edition or Windows Server 2003 Enterprise Edition package now.Download the Windows Server 2003, 64-Bit Enterprise Edition package now.
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.
Update information
PrerequisitesNo prerequisites are required.
Restart requirementYou must restart your computer after you install this update.
Update replacement informationThis update does not replace any other updates.
File informationThe English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
32-bit editions of Windows Server 2003Date Time Version Size File name
------------------------------------------------------
25-Aug-2003 22:15 6.0.3790.80 456,192 Smtpsvc.dll
64-bit editions of Windows Server 2003Date Time Version Size File name Platform
-----------------------------------------------------------------
25-Aug-2003 20:38 6.0.3790.80 1,174,528 Smtpsvc.dll IA-64
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATIONFor additional information about standard terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
"An operation was attempted on something that is not a socket"
Another post to save KB articles that might go away...this tends to occur during spyware removal.
Microsoft Knowledge Base Article - 817571
You receive an "An operation was attempted on something that is not a socket" error message when you try to connect to a network (Windows 2000 Pro, XP)
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SYMPTOMS: When you try to connect your computer to a network, you may receive the following error message:
An operation was attempted on something that is not a socket. This symptom occurs on a computer that obtains an IP address from a Dynamic Host Configuration Protocol (DHCP) server. If you assign a static IP address to your computer, you do not receive this message.
CAUSE: This issue may occur if you have a third-party product installed that uses Windows sockets and also uses the ipconfig, release, and renew commands. The Windows sockets registry subkeys may be corrupted.
RESOLUTION: Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. To resolve this problem, use either of the following methods.
Method 1 We recommend that you use Method 1 if either of the following conditions are true:
You only have one computer.
You do not have access to a computer that is similar to the first computer where you experienced the symptoms that are described in the "Symptoms" section. A computer that is similar to the first computer is another computer that has the same operating system version and a similar hardware configuration.Use Registry Editor to export and delete the Winsock and Winsock2 registry subkeys, and then remove and reinstall TCP/IP on Microsoft Windows 2000 or Microsoft Windows XP. To do this, follow these steps.
Export and delete the corrupted registry subkeys
Insert a floppy disk in the floppy disk drive of the computer whose registry entries you are exporting.
Click Start, click Run, type regedit, and then click OK.
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Winsock
On the File menu, click Export.
In the Save in box, click 3½ Floppy (A:), type a name for the file in the File name box, and then click Save.
Right-click Winsock, and then click Delete. When you are prompted to confirm the deletion, click Yes.
Repeat steps 3 through 6 for the following subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Winsock2
Note Each .reg file that you save must have a different name.
Right-click Winsock2, click Delete, and then click Yes.
Quit Registry Editor.
Windows 2000-based computer
Remove TCP/IP on a Windows 2000-based computer
Log on to Windows as administrator.
In Control Panel, double-click Network Connections, right-click Local Area Connection, and then click Properties.
Under This component uses the following items, click Internet Protocol (TCP/IP), and then click Uninstall.
Follow the instructions on the screen to remove TCP/IP.
Restart your computer, but click No if you are prompted to let Windows enable a protocol.
Install TCP/IP on a Windows 2000-based computer
Log on to Windows as administrator.
In Control Panel, double-click Network Connections, right-click Local Area Connection, and then click Properties.
Click Install.
In the Select Network Component Type dialog box, click Protocol, and then click Add.
Under Network Protocol, click Internet Protocol (TCP/IP), and then click OK.
When the protocol is installed, click Close.
Restart your computer.
Windows XP-based computer
Reinstall TCP/IP on a Windows XP-based computerIn Windows XP, the TCP/IP stack is a core component of the operating system. Therefore, you cannot remove TCP/IP in Windows XP.
Install TCP/IP on top of itself. To do this, follow these steps:
In Control Panel, double-click Network Connections, right-click Local Area Connection, and then click Properties.
Click Install.
Click Protocol, and then click Add.
Click Have Disk.
In the Copy manufacturer's files from box, type System_Drive_Letter:\windows\inf, and then click OK.
In the list of available protocols, click Internet Protocol (TCP/IP), and then click OK.
Restart your computer.
Method 2
If you are correcting this problem on several computers and you have access to a working computer with the same operating system version and a similar hardware configuration, we recommend Method 2.
To resolve this issue, delete the corrupted registry entries, and then replace them with the registry key information that you exported from a computer that has a working installation of TCP/IP. To do this, follow these steps.
Delete the corrupted registry entriesOn the computer that has the corrupted registry entries, follow these steps:
Click Start, click Run, type regedit, and then click OK.
In Registry Editor, locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services.
Right-click Winsock, and then click Delete. When you are prompted to confirm the deletion, click Yes.
Right-click Winsock2, and then click Delete. When you are prompted to confirm the deletion, click Yes.
Export the registry entries to a floppy disk On the computer that has a working installation of TCP/IP, follow these steps.Note The computer that you are importing the registry entries from must use the same version of Windows and be either similar to or a duplicate of the computer that is experiencing the symptoms that are described in the "Symptoms" section.
Insert a floppy disk in the floppy disk drive of the computer that has the registry entries that you are exporting.
Click Start, click Run, type regedit, and then click OK.
In Registry Editor, locate and then click the following registry subkey and then click Winsock:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services
Click File, and then click Export.
In the Save in box, click 3½ Floppy(A:), type a name for the file in the File name box, and then click Save.
Click Winsock2, click File, and then click Export.
In the Save in box, click 3½ Floppy(A:), type a name for the file in the File name box, and then click Save. Note Each .reg file that you save must have a different name.
Quit Registry Editor.
Import the registry entries from the floppy disk:
On the computer that had the corrupted registry entries, follow these steps:
Insert the floppy disk that contains the .reg files in the floppy disk drive of the computer that is experiencing the symptoms that are described in the "Symptoms" section.
Start Windows Explorer, click My Computer, and then double-click 3½ Floppy(A:).
Double-click each .reg file that you created and saved to the floppy disk in the "Export the registry keys to a floppy disk" section.
Click Yes when you are prompted to add information to the registry.
Click OK when you receive the message that the information is successfully entered in the registry.
Quit Registry Editor.
MORE INFORMATION: These methods restore basic functionality to the Winsock and the Winsock2 subkeys. You may have to reinstall some third-party proxy software or firewalls.
Symantec NAVCE Server Group Password Changed
or How do I get into my server group?
change this key in registry
HKLM\SOFTWARE\INTEL\LANDesk\VirusProtect6\CurrentVersion\ConsolePassword
to value
1084A085DC6BD2D755D4D6A7726
The password is now: symantec
