Atitit. troubleshooting --- the current command encountered a serious error. Should discard any possible issues

Atitit. troubleshooting --- the current command encountered a serious error. Should discard any possible results sqlserver20081. phenomenon 12. cause: SQL Server bug or restriction. Too many resources are used during query, which exceeds the limits of operating system firewall security software... 22. 1. reasons for firewall security software: long-time connection is automatically disabled

Atitit. troubleshooting --- the current command encountered a serious error. Discard any possible results SQL server 2008 1. symptom 1 2. cause: SQL server bug or restriction. Too many resources are used during query, which exceeds the limits of operating system/Firewall/security software... 2 2.1. firewall/security software reason: long-time connection is automatically disabled

Atitit. troubleshooting --- the current command encountered a serious error. Discard any possible results. SQL server 2008

1. symptom 1

2. Cause: the SQL server bug or restriction. Too many resources are used during query, which exceeds the operating system/Firewall/security software restrictions... 2

2.1. Firewall/security software reasons: long-time connections and multi-resource connections are automatically disabled... 2

2.2. When the number of concurrent connections exceeds the capacity, the server will drop some of the connections; 2

3. Solution: 2

3.1 patch sp 2

3.2. Use top n/where to reduce the number of queries (attialx verifies OK) 2

3.3. Upgrade the computer configuration (recommended, verify OK) 2

3.4. Add an index for a query field 2

3.5. Reduce select large field queries... only select small field 2

3.6. Modifying the length of a field may be caused by this .. 3

3.7. strSql And Param are too many, leading to errors. 3

3.8. The detailed data type is not specified in the stored procedure of the call. (According to google's results, sp4 is used. This is unknown.) 3

4. Reference 3

1. symptom

This error occurs when an SQL statement is executed. The blackheads in the Korean-style code manager are all in the middle ..

Solved "a serious error occurred in the current command. Should discard any possible results ." Problems

A transmission error occurs when receiving results from the server. (Provider: named pipeline provider, error: 0-there is no process on the other end of the pipeline .)

The current command has a serious error. Should discard any possible results

There are often cases where conn is automatically closed... socket close ..

Org. springframework. transaction. TransactionSystemException: cocould not roll back Hibernate transaction; nested exception is org. hibernate. TransactionException: rollback failed

Org. springframework. transaction. cannotCreateTransactionException: cocould not open Hibernate Session for transaction; nested exception is org. hibernate. service. unknownServiceException: Unknown service requested [org. hibernate. service. jdbc. connections. spi. connectionProvider]

Caused by: com. microsoft. sqlserver. jdbc. SQLServerException: Connection reset by peer: socket write error

Caused by: com. microsoft. sqlserver. jdbc. SQLServerException: the connection is closed.

Org. springframework. transaction. TransactionSystemException: cocould not commit Hibernate transaction; nested exception is org. hibernate. TransactionException: commit failed

Author: old wow's paw Attilax iron, EMAIL: 1466519819@qq.com

Reprinted please indicate Source: http://blog.csdn.net/attilax

2. Cause: SQL server bug or restriction. Too many resources are used during query, which exceeds the operating system/Firewall/security software restrictions...

The data size is only 75 w. This error occurs during query .....

During query, the memory usage is too large...

But there is no problem with the same data volume on the same mysql computer ..

2.1. Firewall/security software reason: the connection with long-time connections and multiple resources is automatically closed... 2.2. The number of concurrent connections exceeds the carrying capacity, and the server will drop some of the connections;

3. solution: 3.1. patch sp3.2. use top n/where to reduce the number of queries (attialx verification OK) by 3.3. upgrade Computer Configuration (recommended, verify OK) 3.4. add an index to the query field 3.5. reduce select large field queries .. only select the small field 3.6. modifying the length of a field may be caused by this ..

It is estimated that the length of the article is too long, so the code db. AddInParameter (dbCommand, "Content", DbType. AnsiString, model. Content) is found );

Change it

Db. AddInParameter (dbCommand, "Content", DbType. String, model. Content );

3.7. strSql And Param are too many, leading to errors.

An error is reported if the number of param for loops is 51, that is, 2092.

3.8. The detailed data type is not specified in the stored procedure of the call. (According to google's results, sp4 is used. This is unknown)

4. Reference

22,212 exception: a serious error occurred in the current command. Should you discard the final result .htm

113,357 the current command encountered a serious error. Should you discard the final result .htm

2014/11/25 12,669 resolved "a serious error occurred in the current command. Should discard any possible results ." Problem-Sam Lin-blog. htm

42,875 a serious error occurred in the current command to solve the problem. Discard any possible results-wthorse's column-blog channel-CSDN.NET.htm