February 29, 2004 at 11:18 pm
I am getting an error in the application log.
SuperSocket info:SpnRegister Error 8335
Does anybody have an idea what this means. Since this error has been happening the remote app can no longer connect to the server. keeps indicating that the server is temperaly unavailable. But of course the same app on the server connects. The remote app does pass through a firewall and this could be the problem. But I just want to know what the error message means.
Ken
If you don't ask you never get an anwser.
March 1, 2004 at 1:32 pm
Sounds like an authentication error. Are you accessing SQL Server via Integrated Security? Have you tried the remote app using A SQL Server login? (Just to see if the security setup is at fault) Look at http://support.microsoft.com/default.aspx?scid=kb;en-us;811889 or
This is a step by step connectivity flowchart for SQL Server: http://support.microsoft.com/default.aspx?scid=kb;en-us;827422
Francis
March 1, 2004 at 3:19 pm
Thanks for the reply.
I did try it with an sql server login, with the same result.
I also thought it was an authentication error, but my initial thought was that something was happening to the values at the firewall. As the app can be executed using the same user details on the server.
I will have a read of the links you provided and see what I can come up with.
Ken
If you don't ask you never get an anwser.
March 2, 2004 at 4:48 am
Check the SQL Server log to see if it was able to bind to the TCP/IP port. Sometimes when the server is re-booted, SQL will come up on shared memory and named pipes, but will not be able to bind to the IP port. Then local apps, or apps using named pipes will function, but TCP/IP app will not.
March 2, 2004 at 9:22 am
Normally, "SuperSocket info:SpnRegister Error" errors occur when SQL Server is started. "SpnRegister Error" means that SQL Server was unable to register a Service Principal Name (SPN) with Active Directory. This will occur if the SQL Service Account is a domain user id, but not a domain admin. I'm not sure what your particular error number (8335) refers to, though. Many different error numbers are possible.
Microsoft points out that these errors are informational only, and that NTLM authentication will be used instead of Kerberos.
However, if remote apps cannot connect, but any app on the SQL Server itself can connect, then you are probably getting 'Cannot generate SSPI context' errors when attempting to connect from the remote apps.
There may be bad DNS records in AD. Have a domain admin check that for you. If not, maybe a domain admin can create an SPN for your server using the SETSPN.EXE utility from Microsoft.
http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/setspn-o.asp
Mike
March 3, 2004 at 4:33 pm
Thank's for the help guys. It turned out it was a bad dns in ad
Ken
If you don't ask you never get an anwser.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply