Error and warning in Event log -- SuperSocket info

Question

Error and warning in Event log -- SuperSocket info

Mark Fleming

Mr or Mrs. 500

Points: 589
More actions
January 29, 2003 at 8:43 am

#101365

Hey folks,
I wasn't sure where to post this but here goes...
We have 3 database servers running Win 2K Advanced with SP3 with SQL Server 2K SP3
(All recent installs -- within the last month)
2 of the database servers use a domain account at startup as the service account.
When the SP3 was applied I was logged in using my account (domain admin) instead of the service account.
We are getting an error message:
"SuperSocket info: Failed to get Exclusive port use(MSAFD Tcpip [TCP/IP]) : Error 10013."
and a warning message:
"SuperSocket info: (SpnRegister) : Error 8344."
I found a solution to the error message -- reapply SP3 while logged in as service account.
However I'm still getting the warning message.
I can't find any information anywhere about it.
I've searched here, Microsoft, Google, Technet
and can find absolutely nothing on it.
Does anyone have any ideas as to the cause/possible resolutions?
Thanks
Mark
-- Edit --
I just went back and checked the event log again -- the error was occurring before the SP3 install.
So does anyone have any suggestions still
-- End Edit --
Edited by - mark.fleming on 01/29/2003 08:52:32 AM

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply

K. Brian Kelley SSC Guru Points: 114642 More actions · Answer 1

The error message is because something else has grabbed the port. 1433 is in the dynamic port range, unfortunately. Usually identifying the offending network application and stopping it frees up the port. Failing that, a reboot usually does.

http://support.microsoft.com/default.aspx?scid=kb;en-us;293107

As for the warning, if it's error 1355, it's a known non-issue. It should be an informational message.

http://support.microsoft.com/default.aspx?scid=kb;en-us;303411

Haven't seen an 8344 error before.

K. Brian Kelley

http://www.truthsolutions.com/

Author: Start to Finish Guide to SQL Server Performance Monitoring

http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1

K. Brian Kelley
@kbriankelley

Mark Fleming Mr or Mrs. 500 Points: 589 More actions · Answer 2

Hey bkelley,

I fixed the error message about port 1433 by reinstalling the SP3 while logged in as the service account.

The warning messge that I still receive is an 8344 error.

It's an event id of 19011, category 8 for MSSqlServer.

I've been searching all over but have not found anywhere that mentions this error.

Thanks for the help.

Mark

K. Brian Kelley SSC Guru Points: 114642 More actions · Answer 3

Not sure why it's 8344. Any case, the 19011 MSSQLServer error connected with SpnRegister usually means you aren't able to register with an AD domain. If you aren't running in an Active Directory environment, the error is meaningless. If you are, then is your MSSQLServerADHelper service set to LocalSystem as its account?

K. Brian Kelley

http://www.truthsolutions.com/

Author: Start to Finish Guide to SQL Server Performance Monitoring

http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1

K. Brian Kelley
@kbriankelley

Mark Fleming Mr or Mrs. 500 Points: 589 More actions · Answer 4

Hi again,

The MSSQLServerADHelper is set to run as the local system account.

It is not started on either server, and is set to manual startup.

We are in an AD domain, the service account is a member of the AD domain as well.

Any other suggestions?

Should this service be started?

Thanks,

Mark

K. Brian Kelley SSC Guru Points: 114642 More actions · Answer 5

Are you trying to register the SQL Server with AD Services? Is the SQL Server registering successfully with AD?

As far as MSSQLServerADHelper, no, it shouldn't be started. SQL Server kicks this service off when it needs to register with AD. In order to register with AD Services, the account doing the registering must either be a domain admin or the localsystem account. SQL Server isn't typically run under a domain admin account (obvious security reasons) nor a localsystem account (no access to network resources and full admin rights on the box). As a result, the MSSQLServerADHelper service is used to register with AD.

I'll keep looking for that 8344 error. So far I haven't come across anything, either.

K. Brian Kelley

http://www.truthsolutions.com/

Author: Start to Finish Guide to SQL Server Performance Monitoring

http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1

K. Brian Kelley
@kbriankelley

Mark Fleming Mr or Mrs. 500 Points: 589 More actions · Answer 6

Nope, I'm not trying to add it, and it doesn't appear to be registering successfully either.

Under the properties of the server, under the "AD" tab, it hasn't been added.

I didn't think the MSSQLServerADHelper needed to be started, so I left it as is.

It is still set to use local system account.

The Sql Server service account is an AD domain account, but not a domain admin.

I'm not overly worried about it, I'm just trying to figure out why it's there.

Hopefully someone might have run into 8344 before as well.

Thanks for the help bkelley.

Mark

K. Brian Kelley SSC Guru Points: 114642 More actions · Answer 7

If you haven't registered it, it shouldn't be. The new error number has me intrigued, though.

K. Brian Kelley

http://www.truthsolutions.com/

Author: Start to Finish Guide to SQL Server Performance Monitoring

http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1

K. Brian Kelley
@kbriankelley

Mark Fleming Mr or Mrs. 500 Points: 589 More actions · Answer 8

Hey bkelley,

I haven't registered either of the servers to AD.

I do want to thank your for the information though.

Here's a pic of the message box just in case you think I'm cracking up lol

george sibbald SSC Guru Points: 104210 More actions · Answer 9

Hey guys,

I have been getting the 8344 error since the machine dropped out of the domain last week. Unfortunately it also means we are not able to connect remotely to the machine using windows authentification, we get the 'cannot generate sspi context' error.

did you get to the bottom of your problem?.

We are working our way through article http://support.microsoft.com/kb/811889 with no luck so far.

Interestingly another machine where SQL runs under the same service account (log ship pair) gives the 8344 error but can be connected to fine.

regards

george

---------------------------------------------------------------------

george sibbald SSC Guru Points: 104210 More actions · Answer 10

ok, solved out 'cannot generate sspi context' error -

as machine had dropped out of domain we -

moved computer to its own workgroup

deleted computer name entry from AD

moved computer back to domain

bounced computer

and hey presto all ok

We still get the 8834 warning messaage in application evntvwr, but seems we can live with this as all is working and I guess SQL will use NTLM authentication.

regards

george

---------------------------------------------------------------------

Vidhya Sagar SSCrazy Eights Points: 8216 More actions · Answer 11

Try connecting the servername in FQDN format else use ip address as shown below

Eg.) servername.eur.nsroot.net,1433 -->FQDN servername

169.187.0.25,1433

Regards..Vidhya Sagar
SQL-Articles