Windows socket error 10054

I am working on a Windows (Microsoft Visual C++ 2005) application that uses several processes
running on different hosts in an intranet.

Processes communicate with each other using TCP/IP. Different processes can be on the
same host or on different hosts (i.e. the communication can be both within the same
host or between different hosts).

We have currently a bug that appears irregularly. The communication seems to work
for a while, then it stops working. Then it works again for some time.

When the communication does not work, we get an error (apparently while a process
was trying to send data). The call looks like this:

send(socket, (char *) data, (int) data_size, 0);

By inspecting the error code we get from

WSAGetLastError()

we see that it is an error 10054. Here is what I found in the Microsoft documentation
(see here):

WSAECONNRESET
10054

Connection reset by peer.

An existing connection was forcibly closed by the remote host. This normally
results if the peer application on the remote host is suddenly stopped, the
host is rebooted, the host or remote network interface is disabled, or the
remote host uses a hard close (see setsockopt for more information on the
SO_LINGER option on the remote socket). This error may also result if a
connection was broken due to keep-alive activity detecting a failure while
one or more operations are in progress. Operations that were in progress
fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.

So, as far as I understand, the connection was interrupted by the receiving process.
In some cases this error is (AFAIK) correct: one process has terminated and
is therefore not reachable. In other cases both the sender and receiver are running
and logging activity, but they cannot communicate due to the above error (the error
is reported in the logs).

My questions.

• What does the SO_LINGER option mean?
• What is a keep-alive activity and how can it break a connection?
• How is it possible to avoid this problem or recover from it?

Regarding the last question. The first solution we tried (actually, it is rather a
workaround) was resending the message when the error occurs. Unfortunately, the
same error occurs over and over again for a while (a few minutes). So this is not
a solution.

At the moment we do not understand if we have a software problem or a configuration
issue: maybe we should check something in the windows registry?

One hypothesis was that the OS runs out of ephemeral ports (in case connections are
closed but ports are not released because of TcpTimedWaitDelay), but by analyzing
this issue we think that there should be plenty of them: the problem occurs even
if messages are not sent too frequently between processes. However, we still are not
100% sure that we can exclude this: can ephemeral ports get lost in some way (???)

Another detail that might help is that sending and receiving occurs in each process
concurrently in separate threads: are there any shared data structures in the
TCP/IP libraries that might get corrupted?

What is also very strange is that the problem occurs irregularly: communication works
OK for a few minutes, then it does not work for a few minutes, then it works again.

Thank you for any ideas and suggestions.

EDIT

Thanks for the hints confirming that the only possible explanation was a connection closed error. By further analysis of the problem, we found out that the server-side process of the connection had crashed / had been terminated and had been restarted. So there was a new server process running and listening on the correct port, but the client had not detected this and was still trying to use the old connection. We now have a mechanism to detect such situations and reset the connection on the client side.

Причины возникновения
Причины этой ошибки разняться по своей «природе», но их объединяето то, что уже существующее (т.е. ранее установленое) соединение с клиентом разрывает сервер.

1. С версии 8.1.11 включен циклический перезапуск процессов, по наступлению интервала происходит автоматический перезапуск рабочих процессов rphost.

2. В некоторых случаях причиной ошибки могут стать утечки памяти.

3. Действия администратора в консоли (команда удалить пользователя)

4. Процесс rphost на серверном компьютере завершился аварийно

5. Ошибочное принятие высокой интенсивности пользователей за атаку на протокол в некоторых случаях Windows

6. Устаревание данных в кэшах

7. Плохо отслеживаемые события в фоновых процессах

8. Нестандартные запросы могут приводить к падениям rphost

Способы устранения
1. с 8.1.11 включен циклический перезапуск процессов, для анализа этого события на компьютере сервера 1С:Предприятия необходимо включить запись в технологический журнал событий PROC (пример файла logcfg.xml).
Когда процесс выключается, будет выведено событие PROC со свойством Txt=Process become disable.
Когда процесс останавливается, будет выведено событие PROC со свойством Txt=Process terminated. Any clients finished with error. Если аварийные завершения работы пользователей совпадают по времени с выводом этого события, то причиной является принудительная остановка рабочего процесса либо администратором (через консоль кластера), либо вследствие автоматического перезапуска.

2. перезагрузить сервер
3. убедиться, что причиной являются/не являются действия администратора в консоли
4. создать на сервере приложения два или более рабочих процесса, чтобы иметь возможность переподключиться в случаи сбоя рабочего процесса
5. Запусти программу regedit.exe, добавь новое значение типа DWORD с именем SynAttackProtect в раздел реестра HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParameters и присвой ему значение 00000000
Имеет смысл делать для ОС Windows 2003 SP1 (http://msdn.microsoft.com/ru-ru/library/ms189083.aspx).

6. arp -d *
ipconfig /flushdns
ipconfig /registerdns
nbtstat -R
nbtstat -RR

7. отключить фоновые процессы во всех базах

8. найти технологическим журналом запрос, приводящий к падению

p.s. Кроме того, 54 ошибку можно получить на релизах <= 8.1.12.98 при ри конвертации конвертором ИБ 77(DBF) -> 81(SQL) в типовой ТиС (демо, взятой с ИТС) релиз. 954 в клиент-серверном варианте.

обойти можно так:

— выполните конвертацию в файловый фариант информационной базы 1С:Предприятия 8.1,
— выгрузите полученную информационную базу в файл,
— загрузите в клиент-серверный вариант информационной базы 1С:Предприятия 8.1.

Подробнее на www.gilev.ru

Windows error 10054: Connection reset by peer.
An existing connection was forcibly closed by the remote host.

Got this error message and looking for a fix?

This Windows error 10054 occurs when the connection is reset by the peer application.

It happens usually due to an incorrect firewall configuration.

At Bobcares, we often get requests to fix windows errors, as a part of our Server Management Services

Today, let’s see how our Support Engineers fix the Windows error 10054 for our customers.

5 Symptoms of Windows error 10054

Basically, the error indicates that the remote host closed the connection unexpectedly. So we cannot do anything on the program except to accept that the connection lost.

Let’s discuss the symptoms of this windows error.

1. When running the same script, the PC frequently crashes with Error 10054.
2. System displays “Windows Error Code 10054”.
3. Windows is slow to react to mouse or keyboard input.
4. The system periodically “freezes” for a few seconds at a time.
5. “Error 10054” appears and crashes the active program window.

Causes of Windows Error 10054?

We just saw the 5 Symptoms of windows error 10054.

Let’s check the main causes of this Error 10054.

1. Infection with a virus or malware that has infected Windows system files.
2. Another program maliciously or mistakenly deleted Windows-related files.
3. Corrupt update/download and incomplete Windows software installation.
4. Corruption in the Windows registry.
5. Firewall restrictions.

The typical error shows up as :

How we fix the Windows Error 10054?

Let’s see how our Support Engineers fix this error for our customers.

 1. Firewall and router configuration

One of the main reasons for this windows error is an incorrect configuration of firewall and router. So we recommend that the customers test the firewall and that the routers configured properly.

If any unwanted settings are existing on the customers’ system, we ask them to uninstall it or reinstall it again.

2. Disable peer-to-peer functionality.

On certain systems, the problem occurs when connected via a peer-to-peer connection.

To disable this functionality, we do like this:

1.  We open the Windows Update.
2. Then after, we click or tap Advanced options
3. And then click or tap Choose how updates are delivered.
4. On this screen, we choose to toggle the slider to Off to completely disable P2P.

This fixes the error.

3. Clean Out System Junk (Temporary Files and Folders).

If the system accumulates junk files, it can also cause Windows to respond slowly or show a 10054 error.

So cleaning up these temporary files usually solve the 10054 error. We use the utility cleanmgr on the Windows servers to perform this task.

4. Install All Available Windows Updates.

Sometimes resolving your Runtime Errors problems help to resolve the windows error.
To check for the windows updates.

1. We first, Click >> Start button.
2. Then we type >> update into the search box and hit ENTER
3. Then after the Windows Update dialog box will appear.
4. If updates are available, we click >> Install Updates button.

5. Conduct a Full Malware Scan of Your PC

At times, there is a chance that the 10054 error could be related to a malware infection on the PC.

These malicious intruders can destroy, corrupt, or even delete files associated with runtime errors.

So we help our customers to run a full malware scan on their PC to resolve the windows error.

6. Perform a Clean Installation of Windows

This is the last option in trying to resolve the Error 10054.

Reinstalling Windows will erase everything from your hard drive, allowing you to start again with a fresh system. However, this method requires the proper backup of data. A clean install of Windows will also quickly clean out any and all “junk” that has accumulated over the normal usage of your computer.

This fixes the customer’s windows error.

[Need more assistance in windows error 10054?  We’ll fix it for you.]

Conclusion

In short, the windows error 10054 occurs when the connection is reset by the peer application. It usually due to an incorrect firewall configuration. Today we saw how our Support Engineers fix this error for our customers.