https://www.betaarchive.com/wiki/index.php?title=Microsoft_KB_Archive/926929&feed=atom&action=history
Microsoft KB Archive/926929 - Revision history
2024-03-28T08:56:52Z
Revision history for this page on the wiki
MediaWiki 1.39.3
https://www.betaarchive.com/wiki/index.php?title=Microsoft_KB_Archive/926929&diff=224857&oldid=prev
3155ffGd: importing KB archive
2020-07-18T17:33:54Z
<p>importing KB archive</p>
<p><b>New page</b></p><div><div id="nsbanner"><br />
<br />
<div id="bannerrow1"><br />
<br />
{|<br />
| Knowledge Base<br />
|<br />
|}<br />
<br />
<br />
</div><br />
<div id="TitleRow"><br />
<br />
= <span id="KB926929"></span>You cannot connect to a named instance of SQL Server 2000 by using the shared memory protocol after you remove the default instance =<br />
<br />
<br />
</div><br />
<br />
</div><br />
<div id="nstext" valign="BOTTOM"><br />
<br />
Article ID: 926929<br />
<br />
Article Last Modified on 11/2/2007<br />
<br />
<br />
-----<br />
<br />
APPLIES TO<br /><br />
<br /><br />
<br />
* Microsoft SQL Server 2000 Developer Edition<br />
* Microsoft SQL Server 2000 Enterprise Edition<br />
* Microsoft SQL Server 2000 Standard Edition<br />
* Microsoft SQL Server 2000 Personal Edition<br />
<br />
<br />
-----<br />
<br />
<div class="notice_section"><br />
<br />
SQL Bug #: 444012 (SQLBUDT)<br />
<br />
</div><br />
<div class="notice_section"><br />
<br />
'''Important''' This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:<br />
<div class="indent"><br />
<br />
[[../256986|256986]] Description of the Microsoft Windows registry<br />
<br />
<br />
</div><br />
<br />
</div><br />
<div class="symptoms_section"><br />
<br />
== SYMPTOMS ==<br />
<br />
Consider the following scenario. You are running Microsoft SQL Server 2000 as a default instance and as a named instance. You connect to SQL Server 2000 by using the shared memory protocol. You uninstall the default instance of SQL Server 2000. In this scenario, you cannot use local client applications to connect to the named instance. Additionally, you may receive an error message when you try to connect by using Microsoft SQL Native Client or Microsoft Visual Studio 2005.<br /><br />
<br /><br />
When you try to connect to the named instance by using SQL Native Client, you receive the following error message:<br />
<div class="errormessage"><br />
<br />
[SQL Native Client]Shared Memory Provider: Shared memory connectivity to SQL Server 2000 is either disabled or not available on this machine [87].<br /><br />
[SQL Native Client]Login timeout expired<br /><br />
[SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.<br />
<br />
</div><br />
When you try to connect to the named instance by using Visual Studio 2005, you receive the following error message:<br />
<div class="errormessage"><br />
<br />
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)<br />
<br />
</div><br />
<br />
</div><br />
<div class="cause_section"><br />
<br />
== CAUSE ==<br />
<br />
This problem occurs because the <code>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SharedMemoryOn</code> registry subkey is removed when you uninstall the default instance of SQL Server 2000.<br />
<br />
</div><br />
<div class="workaround_section"><br />
<br />
== WORKAROUND ==<br />
<br />
'''Warning''' Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.<br /><br />
<br /><br />
To work around this problem, use one of the following methods:<br />
<ul><br />
<li>Use the Cliconfg.exe utility to re-enable the shared memory protocol. Alternatively, create the following <code>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SharedMemoryOn</code> registry subkey. Follow these steps, and then quit Registry Editor:<br />
<ol><br />
<li>Click '''Start''', click '''Run''', type <span class="kbd userinput"> regedit</span>, and then click '''OK'''.</li><br />
<li>Locate and then click the following key in the registry:<br />
<div class="indent"><br />
<br />
<p>'''<code>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client</code>'''</p><br />
<br />
</div></li><br />
<li>On the '''Edit''' menu, point to '''New''', and then click '''DWORD Value'''.</li><br />
<li>Type <span class="kbd userinput"> SharedMemoryOn</span>, and then press ENTER.</li><br />
<li>On the '''Edit''' menu, click '''Modify'''.</li><br />
<li>Type <span class="kbd userinput"> 1</span>, and then click '''OK'''.</li></ol><br />
</li><br />
<li>Use the TCP/IP protocol or the Named Pipes protocol to connect to the named instance.</li></ul><br />
<br />
<br />
</div><br />
<div class="status_section"><br />
<br />
== STATUS ==<br />
<br />
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.<br />
<br />
</div><br />
Keywords: kbtshoot kbprb KB926929<br />
<br />
<div class="footer"><br />
<br />
<br /><br />
<br />
<br />
-----<br />
<br />
[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]<br />
<br />
<span>© Microsoft Corporation. All rights reserved.</span><br />
<br />
<br />
</div><br />
<br />
</div></div>
3155ffGd