Microsoft Sql Server 2008 Error 64
Contents |
the following error message while attempting to connect to a MS SQL Server instance: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The specified network name is the specified network name is no longer available sql server 2012 no longer available.) (Microsoft SQL Server, Error: 64) It had been working previously, what tcp provider error 0 - the specified network name is no longer available could have changed to cause the problem? I did a quick google but the suggested fixes had mixed results, and none solved my the specified network name is no longer available sql server error 64 problem. I stumbled on this article: SQL SERVER – FIX : ERROR… It wasn't the answer to my problem, but it led me down the right path. I was connecting to a MS SQL Server instance on
Microsoft Sql Server Error 64 2012
a Virtual Machine I had running locally. Recently, I installed tethering software for my mobile phone which had corrupted my windows network configuration. Not saying that this you did the same, or were using a VM, but it helps explain the cause a bit. I had to re-install my VM software, and the VM networking components were re-configured in doing so. The IP address of my VM had changed. That was the culprit. The solution: the specified network name is no longer available sql server 2008 r2 Go to the SQL Configuration Manager. (You can refer to the link above for a walk through with screen shots to get there) Expand the SQL Network Configuration and click on the PROTOCOLS node Right click on TCP/IP and open up the PROPERTIES panel Select the IP ADDRESS tab Make sure the values for the IP ADDRESS fields are correct and match the system it is running on. Restart the service, and you should be back in business, I was. On a side note, this is also the same place where lots of people get hung up when setting up remote access to a SQL Server instance. Make sure you fill in the TCP PORT, even if you are using the default 1433. Post navigation ← MySQL Madness? INT(SIZE) what is it good for? Absolutely Nothin' Got Eclipse? Optimize your IDE (CFEclipse, CFBuilder, Subversive, etc) → Leave a Reply Cancel reply Your email address will not be published. Required fields are marked *Comment Name * Email * Website Search for: Recent Posts ColdFusion and beyond…Python or Ruby? Got Eclipse? Optimize your IDE (CFEclipse, CFBuilder, Subversive, etc) Microsoft SQL Server, Error: 64 A connection was successfully established with the server… MySQL Madness? INT(SIZE) what is it good for? Absolutely Nothin' YUICompressor CFC v0.1 Released Recent CommentsArchives February 2011 January 2011 June 2010 Februa
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies a connection was successfully established with the server but then an error pre-login handshake of this site About Us Learn more about Stack Overflow the company
Error 64 In Sql Server
Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges
Ssms Error 64
Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: http://escapekeys.com/microsoft-sql-server-error-64-a-connection-was-successfully-established-with-the-server/89 Sign up SQL server - can connect via remote server but not local machine - why? up vote 1 down vote favorite I am able to login to a remote server and connect to a database on another server from there. When I do the same thing from my local machine it fails, giving me the error below - A connection was http://stackoverflow.com/questions/19148863/sql-server-can-connect-via-remote-server-but-not-local-machine-why successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (Microsoft SQL Server, Error: 64) Why does this error happen and how do I fix it ? I am trying to connect via management studio. What I tried so far - Error message: (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) It does not work for me. As an aside, I already mentioned what I tried in the first 2 lines of my question. But, it went unnoticed. Those two lines suggest that the problem may be in my local system. But, what could the problem be ? sql-server sql-server-2008 sql-server-2008-r2 share|improve this question edited Oct 3 '13 at 0:47 asked Oct 3 '13 at 0:17 Steam 1,94694083 why vote to close this ? –Steam Oct 3 '13 at 0:27 I didn't vote to close, but it's probably because you've shown no effort to solve this yourself. Did you even Google for a soluti
to Create Database Role and grant permission to role » SQL Server Error 64 A connection was successfully established with the server 28 Feb 2014 | SQL Server Database Maintenance We got email http://www.sqlserver-query.com/sql-server-error-64-a-connection-was-successfully-established-with-the-server/ from developer saying they are getting error while connecting to database server as shown below A connection was successfully established with the server, but then an error occurred during the login process ( provider: TCP provider, error:0 - the specified network name is no longer available) Microsoft Sql server, Error: 64) Checked sql server services that were up and running also looked in to access permission for those user. sql server All were having permission to connect the respective database server. Later on, we diagnosed the issue. If we use the ip-address of the target SQL server, which forces NTLM authentication (see http://davenport.sourceforge.net/ntlm.html), the problem goes away. The long term solution is to add a registry key to each server to override the default MaxTokenSize (too low to handle large AD groups) that is defined on Server 2008 R2 servers the specified network (and others) Each server needs to have the registry key added and then the server needs to be rebooted. The manual instructions for adding the key are as follows… 1. Start Registry Editor (Start->Run->regedit). 2. Locate and click the following key in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters 3. If this key (‘Parameters') is not present, create the key. To do so: 1. Click on the parent key in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos 2. On the Edit menu, click ‘Add Key'. 3. Create a key named ‘Parameters' 4. Click on the Parameters key. 5. On the Edit menu, click Add Value, and then add the following registry value: Data type: REG_DWORD Value name: MaxTokenSize Base: click the ‘Hexadecimal' radio button Value data: ffff Here's what the key will look like in the ‘Edit DWORD' dialog box… Leave a Reply Cancel Reply Author (required) Email (will not be published)(required) Website 9 + 9 = « SQL Server - How to use WHILE loop with Break and Continue keyword SQL Server - Simple Example to Create Database Role and grant permission to role » Recent Posts SQL Server - Configure tempdb to improve performance Install Upgrade advisor 2014 – Before database upgrade SQL Server - Create table statement and