Last post Jan 14, 2016 08:39 AM by Weibo Zhang
Jan 12, 2016 05:07 PM|jpuga|LINK
I have installed a new Windows server 2012 r2 on it, I have set an IIS 8.5 server also in the same box I have SQL server 2012 standard edition.
I have deployed a Visual Basic Application using Visual Studio 2010 Pro, My Application uses Microsoft membership databases.
Once I deployed the application successfully , I tried to login on my application and I got and error :
A network-related or instance -specific error occurred while establishing a connection to SQL server. the server was not found or was not accessible. verify that the instance name is correct and that SQL server is configured to allow remote connections (Provider:
SQL Network Interface, error: 26 - error location server/instance specified.
As soon as I got the error I started troubleshooting the connection to my sql server, and I didn't find any issue. I did some research about it I found a post saying I have to check the SQL server log, which I did and I found the following message on it.
SQL server is attempting to register a SERVICE PRINCIPAL NAME(SPN) for the sql server services. Kerberos authentication will not be possible until a SPN is registered for the sql server service
SQL network interface library could not register the (SPN) MSSQLSVC/SSI-SRV-NET windows return code 0xfffffff state 63 failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos
I checked what kind of authentication I have on the SQL server and this is what I found AUTH_SCHEME = SQL
As a matter of comment on the SQL server installation I change the authentication method from Windows authentication to SQL authentication.
I believe is important to mention my server has not been joined to a Domain or Active directory.
I would appreciate if I can get some help of how I might fix the SPN issue, I believe once this issue is fixed my Application will be working great.
Thanks in advance for your help it is greatly appreciated.
Jan 14, 2016 08:39 AM|Weibo Zhang|LINK
You could first have a look at the following link and refer to it to try solving your issue.
If the issue not be solved, you could have a look at the following blog which provides a solution to solve this same error. In your case, as your server is not in a Domain or Active directory, you could first find the IIS application pool identity by
this article, then create a SPN with this account.