Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 19011 Source: MSSQLServer

Source
Level
Description
SuperSocket info: <description>
Comments
 
- Description: (SpnRegister), Error 2 - This occurs as part of the procedure to reset TCP/IP on Windows 2000, procedure that is detailed in ME837333. Correct the network configuration. If the HLM\SYSTEM\CurrentControlSet\Services\Winsock registry key is missing then restore it from a backup or from a similar computer.
- Description: "ConnectionListen(Shared-Memory (LPC)): Error 5" - Review the REG_MULTI_SZ key under "HKLM\Software\Microsoft\Microsoft SQL Server\{instancename}\MSSQLServer\SuperSocketNetLib\ProtocolList". It should contain entries for "tcp" and "np" and maybe more if you have more subkeys under "SuperSocketNetLib". Also check the two REG_SZ keys under "HKLM\Software\Microsoft\Microsoft SQL Server\{instancename}\MSSQLServer\SuperSocketNetLib\Tcp\TcpDynamicPorts" and
"HKLM\Software\Microsoft\Microsoft SQL Server\{instancename}\MSSQLServer\SuperSocketNetLib\Tcp\TcpPort". In my case, both values were empty. I changed both values to "2624" (as seen on another working server) and the MSSQL MSDE2000 engine started without the above error.
- Description: "Failed to get Exclusive port use(MSAFD Tcpip [TCP/IP]) : Error 10013" - As per Microsoft: "This problem occurs because the SQL Server service account is not a member of the local administrators group on the computer. Therefore, the SQL Server service account does not have the necessary access permissions to exclusively use the TCP/IP ports. You can safely ignore the error message if the SQL Server service account is not a member of the local administrators group on the computer. This message is an informational warning message". See ME830215 for more details.

From a newsgroup post: "To avoid seeing this message again, with Microsoft Windows 2000 Service Pack 3 (SP3), you can enable Kerberos authentication on server clusters. For instructions on how to do this, see ME319723".

From a newsgroup post: "According to my check, "SpnRegister" is used to register in Active Directory. Error 8344 indicates insufficient access rights to perform the operation. According to my experience, if the account starting SQL Server service does not have enough permissions, it may also give this message: SuperSocket Info: Failed to get Exclusive port use(MSAFD Tcpip [TCP/IP]) : Error 10013 (An attempt was made to access a socket in a way forbidden by its access permissions.). Check the account that starts SQL Server service. Make sure it has enough permissions. Try to add it to Local Administrators".

You can use the "MDAC Component Checker" to verify the installation on MDAC.
Description: "Failed to get Exclusive port use(MSAFD Tcpip [TCP/IP]) : Error 10013." - WinSock code 10013 means "Permission denied. An attempt was made to access a socket in a way forbidden by its access permissions.

Description: "ConnectionListen(Shared-Memory (LPC)) : Error 5." - SQL Server uses Cnfgsrv.exe when the setup attempts to configure the SQL Server computer. The Cnfgsrv.exe file forces SQL Server to start and listen only on Local Shared Memory (LPC).

Description: (SpnRegister), Error 8344 - See ME811889.

Description: (SpnRegister) : Error 1355 - An error that can be safely ignored according to Microsoft (ME303411). It is also an indicator of the fact that the SQL server service was restarted.
- Description: "SuperSocket info: ConnectionListen(Shared-Memory (LPC)): Error 5." - See ME815249 for a hotfix for Microsoft SQL Server 2000.


Description: "(SpnRegister) : Error 1355" - 1355 means: "The specified domain either does not exist or could not be contacted". The message usually appears because the SQL Server service account is running as a domain user who does not have requisite permissions to register SPNs. Additionally, the error may be related to the fact that the server is a clustered or fail-over virtual server, which are not currently supported by Active Directory. See ME303411.
This event is related to SQL trying to register with Active Directory. If there is not an AD environment or the server SQL 2000 is running on is in a workgroup this event will likely continue to appear. Possible causes:
1. There is no Active Directory Configured.
2. The service account that SQL Server is using doesn't have the required rights. (If possible give the account domain admin rights).
3. The SQL server can not locate a DC.
Source: Newsgroups

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net.

Read more...

 

Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.

Read more...