* ** The socket connection has been suspended. This may be caused by an error in message processing, remote host receiving timeout, or potential network resource problems.

When debugging the WCF Service today, the following message is displayed: *** the socket connection has been suspended. This may be caused by an error in message processing, remote host receiving timeout, or potential network resource problems.

After debugging for half a day, I finally found the problem:

Because we have an intermediate component project Common class library that references Asp.net MVC 2.0 DLL, while the WCF Service references the common class library but does not reference Asp.net mvc dll, the local debugging result is always correct, an error is reported as soon as it is published to the server's WCF Service!

After debugging for half a day, I finally solved the problem. If you encounter similar problems, you may have made the same mistake.