blocks|key|308967|text|数据库连接被数据库服务器关闭。连接在应用程序的连接池中仍然有效；因此，当您选择共享连接字符串并尝试执行时，它无法访问数据库。如果您正在开发Visual+Studio，只需关闭任务栏上的临时web服务器即可。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|308968|如果它发生在生产环境中，重置web站点的应用程序池应该会回收连接池。|308969|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The database connection is closed by the database server. The connection remains valid in the connection pool of your app; as a result, when you pickup the shared connection string and try to execute it's not able to reach the database. If you are developing Visual Studio, simply close the temporary web server on your task bar.

If it happens in production, resetting your application pool for your web site should recycle the connection pool.

blocks|key|308882|text|在命令提示符下尝试执行以下命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|308883|netsh+interface+tcp+set+global+autotuning=disabled|code-block|syntax|javascript|308884|这将关闭网络堆栈的自动伸缩能力|308885|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Try the following command on the command prompt:

<pre><code>netsh interface tcp set global autotuning=disabled
</code></pre>

This turns off the auto scaling abilities of the network stack

blocks|key|3040845|text|我也有同样的问题。我重新启动了Visual+Studio，解决了这个问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3040846|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same problem. I restarted Visual Studio and that fixed the problem

blocks|key|3040679|text|对于那些不使用IIS的人，我在使用Visual+Studio2010进行调试时遇到了这个问题。我结束了所有的调试器进程:+WebDev.WebServer40.EXE，它解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3040680|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

For those not using IIS, I had this issue when debugging with Visual Studio 2010. I ended all of the debugger processes: WebDev.WebServer40.EXE which solved the issue.

blocks|key|3254641|text|传输层错误通常与到sql+server的连接断开有关。通常是网络。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3254642|Timeout+Expired通常在sql查询运行时间过长时抛出。|3254643|因此，可以选择的选项很少：|3254644|3254645|检查VPN+(如果使用)或任何其他工具中的连接|ordered-list-item|3254646|Restart+IIS+|3254647|Restart+machine+|3254648|Optimize+sql查询。|3254649|3254650|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|V|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|W|8|@]|9|@]|A|$]]|$1|J|3|K|5|I|7|X|8|@]|9|@]|A|$]]|$1|L|3|M|5|I|7|Y|8|@]|9|@]|A|$]]|$1|N|3|O|5|I|7|Z|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

Transport level errors are often linked to the connection to sql server being broken ... usually network.

Timeout Expired is usually thrown when a sql query takes too long to run.

So few options can be : 

<ol>
<li>Check for the connection in VPN (if used) or any other tool </li>
<li>Restart IIS </li>
<li>Restart machine </li>
<li>Optimize sql queries. </li>
</ol>

blocks|key|303873|text|您所需要做的就是停止ASP.NET开发服务器并再次运行项目|type|unstyled|depth|inlineStyleRanges|entityRanges|data|303874|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

All you need is to Stop the ASP.NET Development Server and run the project again

blocks|key|303674|text|如果通过Microsoft+SQL+Server管理连接到数据库，请关闭所有连接，然后重试。在连接到另一个Azure数据库时发生此错误，并在关闭它时为我工作。还是不知道为什么..。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|303675|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you are connected to your database via Microsoft SQL Server Management, close all your connections and retry.
Had this error when connected to another Azure Database, and worked for me when closed it.
Still don't know why ..

blocks|key|3041180|text|查看详细说明此错误的MSDN+blog：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3041181|3041182|删除连接|blockquote|3041183|3041184|在连接长时间处于空闲状态后，或者如果连接池检测到与服务器的连接已断开，则连接池将从池中删除该连接。|3041185|请注意，只有在尝试与服务器通信后才能检测到断开的连接。如果发现不再连接到服务器的连接，则将其标记为无效。|3041186|无效连接仅在关闭或回收时才会从连接池中删除。|3041187|如果存在到已消失的服务器的连接，则即使连接池未检测到断开的连接并将其标记为无效，也可以从池中提取此连接。|3041188|之所以会出现这种情况，是因为检查连接是否仍然有效的开销会导致发生另一次到服务器的往返，从而消除使用池子的好处。|3041189|当发生这种情况时，第一次尝试使用该连接将检测到该连接已被切断，并引发异常。|3041190|基本上，您看到的是最后一句话中的例外情况。|3041191|连接是从连接池获取的，应用程序不知道物理连接已经消失，在假设物理连接仍然存在的情况下尝试使用它。|3041192|你就会得到你的异常。|3041193|这有几个常见的原因。|3041194|3041195|3041196|服务器已重新启动，这将关闭现有连接。|ordered-list-item|3041197|3041198|在这种情况下，请查看SQL+Server日志，通常位于:+C:\Program+Files\Microsoft+SQL+Server\MSSQL\LOG|3041199|如果启动的时间戳是最近的，那么我们可以怀疑这就是导致错误的原因。尝试将此时间戳与异常时间相关联。|3041200|2009-04-16+11:32:15.62服务器将SQL+Server消息记录到文件‘C：\Program+Files\Microsoft+SQL+Server+\MSSQl.1\MSSQL\LOG\ERRORLOG’中。|3041201|3041202|某人或某事已杀死正在使用的SPID。|3041203|3041204|再次查看SQL+Server日志。如果你找到了一个with，试着把这个时间戳和异常的时间关联起来。|3041205|2009-04-16+11:34:09.57+spidXX进程ID+XX被主机名xxxxx、主机进程ID+XXXX终止。|3041206|3041207|再次出现故障切换(例如，在镜像设置中)，请查看SQL+Server日志。|3041208|3041209|如果存在故障转移，请尝试将此时间戳与异常时间相关联。|3041210|2009-04-16+11:35:12.93+spidXX由于故障切换，镜像数据库“”正在将角色从“主体”更改为“镜像”。|3041211|entityMap|0|LINK|mutability|MUTABLE|url|https://blogs.msdn.microsoft.com/spike/2009/04/16/a-transport-level-error-has-occurred-when-sending-the-request-to-the-server-provider-tcp-provider-error-0-an-existing-connection-was-forcibly-closed-by-the-remote-host/^0|A|9|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|22|8|@]|9|@$A|23|B|24|1|25]]|C|$]]|$1|D|3|-4|5|6|7|26|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|27|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|28|8|@]|9|@]|C|$]]|$1|I|3|J|5|6|7|29|8|@]|9|@]|C|$]]|$1|K|3|L|5|6|7|2A|8|@]|9|@]|C|$]]|$1|M|3|N|5|6|7|2B|8|@]|9|@]|C|$]]|$1|O|3|P|5|6|7|2C|8|@]|9|@]|C|$]]|$1|Q|3|R|5|6|7|2D|8|@]|9|@]|C|$]]|$1|S|3|T|5|6|7|2E|8|@]|9|@]|C|$]]|$1|U|3|V|5|6|7|2F|8|@]|9|@]|C|$]]|$1|W|3|X|5|6|7|2G|8|@]|9|@]|C|$]]|$1|Y|3|Z|5|6|7|2H|8|@]|9|@]|C|$]]|$1|10|3|11|5|6|7|2I|8|@]|9|@]|C|$]]|$1|12|3|-4|5|6|7|2J|8|@]|9|@]|C|$]]|$1|13|3|-4|5|6|7|2K|8|@]|9|@]|C|$]]|$1|14|3|15|5|16|7|2L|8|@]|9|@]|C|$]]|$1|17|3|-4|5|6|7|2M|8|@]|9|@]|C|$]]|$1|18|3|19|5|6|7|2N|8|@]|9|@]|C|$]]|$1|1A|3|1B|5|6|7|2O|8|@]|9|@]|C|$]]|$1|1C|3|1D|5|6|7|2P|8|@]|9|@]|C|$]]|$1|1E|3|-4|5|6|7|2Q|8|@]|9|@]|C|$]]|$1|1F|3|1G|5|16|7|2R|8|@]|9|@]|C|$]]|$1|1H|3|-4|5|6|7|2S|8|@]|9|@]|C|$]]|$1|1I|3|1J|5|6|7|2T|8|@]|9|@]|C|$]]|$1|1K|3|1L|5|6|7|2U|8|@]|9|@]|C|$]]|$1|1M|3|-4|5|6|7|2V|8|@]|9|@]|C|$]]|$1|1N|3|1O|5|16|7|2W|8|@]|9|@]|C|$]]|$1|1P|3|-4|5|6|7|2X|8|@]|9|@]|C|$]]|$1|1Q|3|1R|5|6|7|2Y|8|@]|9|@]|C|$]]|$1|1S|3|1T|5|6|7|2Z|8|@]|9|@]|C|$]]|$1|1U|3|-4|5|6|7|30|8|@]|9|@]|C|$]]]|1V|$1W|$5|1X|1Y|1Z|C|$20|21]]]]

Look at the <a href="https://blogs.msdn.microsoft.com/spike/2009/04/16/a-transport-level-error-has-occurred-when-sending-the-request-to-the-server-provider-tcp-provider-error-0-an-existing-connection-was-forcibly-closed-by-the-remote-host/" rel="noreferrer">MSDN blog</a> which details out this error:

<blockquote>
 Removing Connections
 
 The connection pooler removes a connection from the pool after it has
 been idle for a long time, or if the pooler detects that the
 connection with the server has been severed.
 
 Note that a severed connection can be detected only after attempting
 to communicate with the server. If a connection is found that is no
 longer connected to the server, it is marked as invalid.
 
 Invalid connections are removed from the connection pool only when
 they are closed or reclaimed.
 
 If a connection exists to a server that has disappeared, this
 connection can be drawn from the pool even if the connection pooler
 has not detected the severed connection and marked it as invalid.
 
 This is the case because the overhead of checking that the connection
 is still valid would eliminate the benefits of having a pooler by
 causing another round trip to the server to occur.
 
 When this occurs, the first attempt to use the connection will detect
 that the connection has been severed, and an exception is thrown.
 
 Basically what you are seeing is that exception in the last sentence.
 
 A connection is taken from the connection pool, the application does
 not know that the physical connection is gone, an attempt to use it is
 done under the assumption that the physical connection is still there.
 
 And you get your exception.
 
 There are a few common reasons for this.
 
 <ol>
 <li>The server has been restarted, this will close the existing connections.</li>
 </ol>
 
 In this case, have a look at the SQL Server log, usually found at:
 C:\Program Files\Microsoft SQL Server\\MSSQL\LOG
 
 If the timestamp for startup is very recent, then we can suspect that
 this is what caused the error. Try to correlate this timestamp with
 the time of exception.
 
 2009-04-16 11:32:15.62 Server Logging SQL Server messages in file
 ‘C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG’.
 
 <ol start="2">
 <li>Someone or something has killed the SPID that is being used.</li>
 </ol>
 
 Again, take a look in the SQL Server log. If you find a kill, try to
 correlate this timestamp with the time of exception.
 
 2009-04-16 11:34:09.57 spidXX Process ID XX was killed by
 hostname xxxxx, host process ID XXXX.
 
 <ol start="3">
 <li>There is a failover (in a mirror setup for example) again, take a look in the SQL Server log.</li>
 </ol>
 
 If there is a failover, try to correlate this timestamp with the time
 of exception.
 
 2009-04-16 11:35:12.93 spidXX The mirrored database “” is changing roles from “PRINCIPAL” to “MIRROR” due to
 Failover.
</blockquote>

blocks|key|303931|text|总是在大约5分钟的操作后得到这个。已调查并发现e1iexpress发出的警告始终出现在故障之前。这显然是与某些TCP/IP适配器有关的错误。但是，从WiFi更改为硬连接并没有影响它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|303932|因此尝试了计划B并重新启动了Visual+Studio。然后它工作得很好。|303933|在更仔细的研究中，我注意到，当正常工作时，消息The+Thread+'<No+Name>'+has+exited+with+code+0几乎恰好发生在先前尝试中运行崩溃的时间。一些谷歌搜索显示，当服务器正在修剪线程池时(以及其他一些事情)，该消息就会出现。|offset|length|style|CODE|303934|假设线程池中有一个假线程，每当服务器试图“修剪”它时，它就会关闭应用程序。|303935|entityMap^0|0|0|N|19|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@$F|Q|G|R|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

Was getting this, always after about 5 minutes of operation. Investigated and found that a warning from e1iexpress always occurred before the failure. This apparently is an error having to do with certain TCP/IP adapters. But changing from WiFi to hardwired didn't affect it.

So tried Plan B and restarted Visual Studio. Then it worked fine.

On closer study I noticed that, when working correctly, the message <code>The Thread '&lt;No Name&gt;' has exited with code 0</code> occurred at almost exactly the time the run crashed in previous attempts. Some Googling reveals that that message comes up when (among other things) the server is trimming the thread pool.

Presumably there was a bogus thread in the thread pool and every time the server attempted to "trim" it it took the app down.

blocks|key|306750|text|当您的脚本由于某些原因使SQL服务停止时，您会收到此消息。因此，如果您再次启动SQL服务，您的问题可能会得到解决。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|306751|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You get this message when your script make SQL Service stopped for some reasons. so if you start SQL Service again perhaps your problem will be resolved.

blocks|key|3040910|text|我知道这可能不会对每个人都有帮助(谁知道，也许是的)，但我也有同样的问题，一段时间后，我们意识到原因是代码本身之外的一些东西。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3040911|尝试连接到服务器的计算机位于另一个网络中，连接可以建立，但随后断开。|3040912|我们过去修复它的方法是向计算机添加一个静态路由，允许直接访问服务器，而不需要穿过防火墙。|3040913|route+add+–p+YourServerNetwork+mask+NetworkMask+Router+|code-block|syntax|javascript|3040914|示例：|3040915|route+add+–p+172.16.12.0+mask+255.255.255.0+192.168.11.2+|3040916|我希望它能帮助一些人，最好有这个，至少作为一个线索，所以如果你面对它，你知道如何解决它。|3040917|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|V|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|X|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

I know this may not help everyone (who knows, maybe yes), but I had the same problem and after some time, we realized that the cause was something out of the code itself.

The computer trying to reach the server, was in another network, the connection could be established but then dropped.

The way we used to fix it, was to add a static route to the computer, allowing direct access to the server without passing thru the firewall.

<pre><code>route add –p YourServerNetwork mask NetworkMask Router 
</code></pre>

Sample:

<pre><code>route add –p 172.16.12.0 mask 255.255.255.0 192.168.11.2 
</code></pre>

I hope it helps someone, it's better to have this, at least as a clue, so if you face it, you know how to solve it.

blocks|key|306844|text|我在Visual+Studion+2012开发环境中遇到了同样的错误，停止了IIS+Express并重新运行应用程序，它开始工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|306845|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I got the same error in Visual Studion 2012 development environment, stopped the IIS Express and rerun the application, it started working.

blocks|key|306035|text|我也有同样的问题。我解决了这个问题，截断了SQL+Server日志。检查是否这样做，然后告诉我们，此解决方案是否对您有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|306036|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same issue. I solved it, truncating the SQL Server LOG.
Check doing that, and then tell us, if this solution helped you.

blocks|key|306116|text|对我来说，解决方案完全不同。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|306117|在我的例子中，我有一个objectsource，它需要一个datetimestamp参数。即使ODS参数ConvertEmptyStringToNull为真，1/1/0001仍被传递给SelectMethod。当将该日期时间传递给sql服务器时，这反过来会导致sql日期时间溢出异常。|306118|为datetime.year+!=+0001添加了一个额外的检查，这为我解决了这个问题。|306119|奇怪的是，它会抛出一个传输层错误，而不是datetime溢出错误。不管怎样..。|306120|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

For me the solution was totally different.

In my case I had an objectsource which required a datetimestamp parameter. Even though that ODS parameter ConvertEmptyStringToNull was true 1/1/0001 was being passed to SelectMethod. That in turn caused a sql datetime overflow exception when that datetime was passed to the sql server.

Added an additional check for datetime.year != 0001 and that solved it for me. 

Weird that it would throw a transport level error and not a datetime overflow error.
Anyways..

blocks|key|307049|text|在我的例子中，"SQL+Server“Server服务停止了。当我重新启动使我能够运行查询并消除错误的服务时。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|307050|检查您的查询以找出查询导致此服务停止的原因也是一个好主意|307051|​|307052|📷|atomic|offset|length|307053|307054|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/8f2ebb1e63c70ccde4ce26a5bc155313.png|imageAlt^0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@$I|Y|J|Z|1|10]]|A|$]]|$1|K|3|E|5|6|7|11|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S|T|-4]]]]

In my case the "SQL Server" Server service stopped. When I restarted the service that enabled me to run the query and eliminate the error. 

Its also a good idea to examine your query to find out why the query made this service stop

<a href="https://i.stack.imgur.com/dnhXS.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/dnhXS.png" alt="enter image description here"></a>

blocks|key|303914|text|对我来说，答案是将操作系统从2008R2升级到2012R2，iisreset或重启apppool的解决方案对我不起作用。我还试图打开TCP烟囱卸载设置，但我没有重启服务器，因为它是一个生产服务器，这也不起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|303915|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

For me the answer is to upgrade the OS from 2008R2 to 2012R2, the solution of iisreset or restart apppool didn't work for me.
I also tried to turn of TCP Chimney Offload setting, but I didn't restart the server because it is a production server, which didn't work either.

blocks|key|306974|text|我们最近在业务服务器和数据库服务器之间遇到了这个错误。我们的解决方案是在网络接口上禁用"IP卸载“。然后错误就消失了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|306975|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

We encountered this error recently between our business server and our database server.
The solution for us was to disable "IP Offloading" on the network interfaces.
Then the error went away.

blocks|key|3255040|text|我发现这个错误的原因之一是连接字符串中的'Packet+Size=xxxxx‘。如果xxxx的值太大，我们将看到此错误。根据网络功能，可以删除此值并让SQL+server处理它，也可以保持较低的值。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3255041|entityMap^0|L|H|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

One of the reason I found for this error is 'Packet Size=xxxxx' in connection string. if the value of xxxx is too large, we will see this error. Either remove this value and let SQL server handle it or keep it low, depending on the network capabilities.

blocks|key|306184|text|当我尝试恢复SQL数据库并选中Options选项卡中的复选框时，它发生在我身上。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|306185|​|306186|📷|atomic|306187|306188|因为它是一个独立的数据库服务器，所以只需关闭SSMS并重新打开它，就为我解决了这个问题。|306189|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/e3abafba3f951ca692ee0e4bf3ca44b1.jpeg|imageAlt^0|F|7|0|0|0|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|10|8|@]|D|@$9|11|A|12|1|13]]|E|$]]|$1|K|3|G|5|6|7|14|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|15|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|O|$P|$5|Q|R|S|E|$T|U|V|-4]]]]

It happened to me when I was trying to restore a SQL database and checked following Check Box in <code>Options</code> tab,

<a href="https://i.stack.imgur.com/kCn3T.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/kCn3T.jpg" alt="enter image description here"></a>

As it's a stand alone database server just closing down SSMS and reopening it solved the issue for me.

blocks|key|307073|text|当数据库被删除并重新创建某些共享资源时，如果仍认为数据库仍然存在，则会发生这种情况，因此，当重新创建数据库后重新运行execute+query以在数据库中创建表时，将不会再次显示错误，并且将显示Command(s)+completed+successfully.消息而不是错误消息Msg+233,+Level+20,+State+0,+Line+0+A+transport-level+error+has+occurred+when+sending+the+request+to+the+server.+(provider:+Shared+Memory+Provider,+error:+0+-+No+process+is+on+the+other+end+of+the+pipe.)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|307074|在删除和重新创建数据库并重新执行DDL查询时，只需忽略此错误即可。|307075|entityMap^0|2P|Y|3W|5M|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

This occurs when the database is dropped and re-created some shared resources is still considering the database still exists, so when you re-run execute query to create tables in the database after it was re-created the error will not show again and <code>Command(s) completed successfully.</code> message will show instead of the error message <code>Msg 233, Level 20, State 0, Line 0 A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)</code>.

Simply ignore this error when you are dropping and recreating databases and re-execute your DDL queries with no worries.

blocks|key|309123|text|我最近遇到了同样的问题，但我在谷歌上找不到答案。所以我想在这里分享它，这样它就可以在未来帮助别人。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|309124|错误：|309125|当执行查询时，查询将提供很少的输出，然后它将抛出以下错误。|309126|309127|“从服务器接收输出时出现传输级别错误(TCP:提供程序，错误:0-指定的网络名称不再可用”|blockquote|309128|309129|309130|解决方案：|309131|309132|在该提供程序属性中检查该链接服务器的提供程序|ordered-list-item|309133|，为该特定提供程序启用"Allow+inprocess“选项以解决此问题。|309134|309135|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|10|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|11|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|13|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|O|3|P|5|Q|7|15|8|@]|9|@]|A|$]]|$1|R|3|S|5|Q|7|16|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|V|$]]

I faced the same issue recently, but i was not able to get answer in google.
So thought of sharing it here, so that it can help someone in future.

Error:

While executing query the query will provide few output then it will throw below error.

<blockquote>
 "Transport level error has occurred when receiving output from
 server(TCP:provider,error:0- specified network name is no longer
 available"
</blockquote>

Solution:

<ol>
<li>Check the provider of that linked server </li>
<li>In that provider properties ,Enable "Allow inprocess" option for that particular provider to fix the issue.</li>
</ol>

I'm getting a SQL Server error:

<blockquote>
 A transport-level error has occurred
 when receiving results from the
 server. (provider: Shared Memory
 Provider, error: 0 - The handle is
 invalid.)
</blockquote>

I'm running Sql Server 2008 SP1, Windows 2008 Standard 64 bit.

It's a .Net 4.0 web application. It happens when a request is made to the server. It's intermittent. Any idea how I can resolve it?

A transport-level error has occurred when receiving results from the server

我收到一个SQL Server错误：从服务器接收结果时出现传输级错误。(提供程序:共享内存提供程序，错误:0-句柄无效。)我运行的是Sql Server2008 SP1，Windows2008Standard 64位。这是一个.Net 4.0 web应用程序。当向服务器发出请求时，就会发生这种情况。这是间歇性的。你知道我该怎么解决这个问题吗？

问从服务器接收结果时出现传输级错误
EN

回答 21

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问从服务器接收结果时出现传输级错误EN

回答 21

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问从服务器接收结果时出现传输级错误
EN