код ошибки 10054 ammyy admin
Как исправить ошибку Windows 10054
| Номер ошибки: | Ошибка 10054 | |
| Название ошибки: | Windows Error Code 10054 | |
| Описание ошибки: | Ошибка 10054: Возникла ошибка в приложении Windows. Приложение будет закрыто. Приносим извинения за неудобства. | |
| Разработчик: | Microsoft Corporation | |
| Программное обеспечение: | Windows | |
| Относится к: | Windows XP, Vista, 7, 8, 10, 11 |
Определение «Windows Error Code 10054»
Это наиболее распространенное условие «Windows Error Code 10054», известное как ошибка времени выполнения (ошибка). Программисты работают через различные уровни отладки, пытаясь убедиться, что Windows как можно ближе к безошибочным. Хотя эти превентивные действия принимаются, иногда ошибки, такие как ошибка 10054, будут пропущены.
Ошибка 10054, рассматриваемая как «Windows Error Code 10054», может возникнуть пользователями Windows в результате нормального использования программы. Когда появится ошибка, пользователи компьютеров смогут уведомить разработчика о наличии ошибки 10054 через отчеты об ошибках. Разработчик сможет исправить свой исходный код и выпустить обновление на рынке. Чтобы исправить любые документированные ошибки (например, ошибку 10054) в системе, разработчик может использовать комплект обновления Windows.
В чем причина ошибки 10054?
Проблема с исходным кодом Windows приведет к этому «Windows Error Code 10054», чаще всего на этапе запуска. Проанализируем некоторые из наиболее распространенных причин ошибок ошибки 10054 во время выполнения:
Как правило, такие Microsoft Corporation ошибки возникают из-за повреждённых или отсутствующих файлов Windows Error Code 10054, а иногда — в результате заражения вредоносным ПО в настоящем или прошлом, что оказало влияние на Windows. Большую часть проблем, связанных с данными файлами, можно решить посредством скачивания и установки последней версии файла Microsoft Corporation. Помимо прочего, в качестве общей меры по профилактике и очистке мы рекомендуем использовать очиститель реестра для очистки любых недопустимых записей файлов, расширений файлов Microsoft Corporation или разделов реестра, что позволит предотвратить появление связанных с ними сообщений об ошибках.
Типичные ошибки Windows Error Code 10054
Частичный список ошибок Windows Error Code 10054 Windows:
Ошибки Windows Error Code 10054 EXE возникают во время установки Windows, при запуске приложений, связанных с Windows Error Code 10054 (Windows), во время запуска или завершения работы или во время установки ОС Windows. Выделение при возникновении ошибок Windows Error Code 10054 имеет первостепенное значение для поиска причины проблем Windows и сообщения о них вMicrosoft Corporation за помощью.
Причины проблем Windows Error Code 10054
Эти проблемы Windows Error Code 10054 создаются отсутствующими или поврежденными файлами Windows Error Code 10054, недопустимыми записями реестра Windows или вредоносным программным обеспечением.
В частности, проблемы Windows Error Code 10054 возникают через:
Совместима с Windows 2000, XP, Vista, 7, 8, 10 и 11
Ammy Admin ошибки (error) подключения
При работе с программой по удаленному доступу Ammy Admin возникают ошибки и предупреждения, которые могут препятствовать подключению и корректной работе программы. Рассмотрим наиболее распространенные из них:
Такая ошибка возникает, когда оператор разрешает удаленный доступ через Ammy Admin с помощью удаленного рабочего стола (протокол RDP) или других программных средств. Соединение через Ammy Admin в этом случае будет не стабильно. Для создания устойчивой связи оператору необходимо разрешить доступ непосредственно на удаленном компьютере без использования средств удаленной связи.
3. В процессе работы с удаленным рабочим столом появляется ошибка ERROR 10054-1 in TransortTCP2::ReadExact…
Эта ошибка говорит о нестабильном интернет-соединении, которое может быть нестабильно, как на стороне клиента, так и на Вашей стороне. Восстанавливается соединение простым пепеподключением. Если такие случаи будут повторяться регулярно- стоит задуматься о смене провайдера (поставщику интернета) или о повышении качества интернет-соединения у текущего.
4. При запуске службы Ammy Admin:
появляется ошибка ERROR 5 while starting the AMMYY service:
Эта ошибка говорит о отказе доступа при перезагрузке службы Ammy Admin. Необходимо попросить перезапустить службу Ammy владельца компьютера с правами администратора.
5. При подключении к удаленному компьютеру появляется ошибка Remote desktop is unavailable:
Решение: Устранить эту ошибку помог запуск программы Ammy Admin на удаленном компьютере c правами администратора:
Сообщение Remote desktop is unavailable появляется также в случае, когда соединение было разрешено (кнопка «Разрешить») через удаленный сеанс связи (удаленный рабочий стол mstsc.exe) и окно удаленного рабочего стола свернуто.
В данном случае нельзя сворачивать окно удаленного рабочего стола иначе будет появляться сообщение Remote desktop is unavailable.
6. Ошибка 228 Unknown encoder=228 или Unknown encoder=75.
Эта ошибка связана с расхождениями в версиях программы Ammy Admin между подключаемыми компьютерами. Необходимо установить на оба компьютера одинаковую версию программы Ammy Admin.
7. Во время сеанса удаленной связи появляется ошибка Failed to open clipboard
Решение: решается переподключением (закрыть и запустить заново) программы Ammy Admin на обоих компьютерах, участвующих в сеансе удаленной связи.
8. Потеря подключений в Контактной книге, например, после переустановки операционной системы (ОС). Такое может быть, т.к. по заверению тех. поддержки Ammy Admin Контактная книга хранится в C:\Program Data\AMMYY\ или C:\Documents and Settings\All Users\Application Data\AMMYY. Изменить ее расположение невозможно. Таким образом при переустановки ОС она удаляется. Ее можно экспортировать и затем импортировать.
Решение : Сохраните файл с базой данных контактной книги (файл по умолчанию «Ammyy_Contact_Book.bin») на съемный носитель перед установкой ОС или иными действиями, связанными с редактированием системного диска.
Решение: использовать для скачивания другие браузеры, например, Internet Explorer, Mozilla Farefox или Opera. Наиболее стабильная в этом плане версия 3.0, на которую меньше всего «ругаются» антивирусы.
Код ошибки 10054 ammyy admin как исправить
Error 10054 1 in transporttcp2 readexact 2
This article will be useful for those using Ammyy Admin as well as other remote access application users as it contains general info on remote control software which can be applied while using similar remote access applications.
It happens quite often when Ammyy Admin users ask «What is the minimum Internet connection bandwidth that makes Ammyy Admin work ok?». Usually we give an answer like this «Ammyy Admin will work with any Internet bandwidth, but the better Internet is the faster Ammyy Admin works». However, it’s impossible to identify the minimum Internet connection speed required for comfort work because there is no any standard for «comfort work» and the meaning of this term may vary from person to person. Thus «comfort work» term used in this article is nothing more than my personal opinion on the matter and you may have your own different one.
Step 1: Connection speed test
1.1. Connect to a client in «Speed Test Only» mode. The new window will show you «TCP by router: port» or «Direct TCP with ip:port» or «Direct UDP with ip:port». The 1st phrase tells the traffic is going through a router, the 2nd and 3rd mean direct traffic transfer. In most cases direct connection provides faster performance rather than connection through router thus it’s always better to establish direct connection although it’s not always possible.
1.2. First of all, make sure that client and operator have «Allow Direct TCP/UDP» box checked. Direct TCP is possible in cases when:
– Both PCs are located in one LAN, or
– One of the PCs can receive incoming TCP connections onto a certain port and this port is listed in «External TCP Port» and has «On» status.
After that click «Start». You’ll get the test results (picture 1) including:
1) Ping time min-avr-max (also called round trip time). This is time a minimal data packet spends for round-trip and reflects minimal, average and maximal time. This parameter has almost no affect on data transfer speed of a bigger size, but it’s crucial for work in remote desktop mode. Comfort work requires average time of 150ms at maximum.
2) Dnload speed – «from client to operator» bandwidth.
3) Upload speed – «from operator to client» bandwidth.
picture 1
picture 1Р°
Bandwidth is often called connection speed. In case you have Direct TCP connection the speed will depend only on Internet providers of client and operator. Ammyy Company will not be able to help you in this case. If you have TCP by router connection and the speed test results are much worse than minimal client and operator Internet bandwidth you should sort out the issue with router before writing to Ammyy tech support.
Step 2: Router check
2.1. Please open https://rl. ammyy. com/ on client side. Here you can see your external IP and country of current location. The closest router that will provide connection between operator and client will be defined based on the country. In case the country was defined wrong, please tell about it Ammyy Company. Keep in mind that this might be due to the following reasons:
– Your Internet provider gave wrong info about your IP.
– You work through a Proxy Server which is located in other country.
– Information on your IP doesn’t match in Ammyy Data Base.
picture 2
1280 x 1024 x 32 bits – desktop resolution and color depth.
4.14 ms – average time of screen capturing.
7.35ms – 2 screen frames average time of comparing. It usually depends on CPU and RAM characteristics, and doesn’t depend on the video system.
To make work comfortable the sum of the 1st and the 2nd line should not be bigger than 50 ms, and a very comfortable work implies the sum to be not more than 20 ms.
It’s remarkable that these are results of a system with disabled hardware acceleration. When hardware acceleration was turned on the test laptop showed average time of capturing increase up to 35 ms, what is by 31ms longer! It might be justified by the fact that disabled hardware acceleration makes graphic adapter use basic RAM and CPU reading speed from RAM is much higher than reading from video memory. Please, check this parameter, and in case average capturing time is too long, one has to look for a reason why graphic adapter works so slowly.
To disable hardware acceleration in Windows 7/XP, please, do the following:
1. Right click on the desktop and select Screen Resolution
2. On the window that opens up, click on the Advanced Settings link
3. Select the Troubleshoot tab, then click Change Settings
4. Move the Hardware acceleration slider towards none to reduce or turn off video hardware acceleration.
5. Click OK, and then click Restart Now.
picture 3
If UAC is enabled, it’ll require user confirmation. In some cases in windows 7 it’s impossible to turn off video hardware acceleration because video adapter and its driver don’t allow changing this settings.
Step 4: Encoder settings
picture 4
To make remote desktop speed faster please follow this recommended encoder settings:
1) It’s recommended to disable desktop background, visual effects and desktop composition. This simplifies remote desktop image and increases compression level and as a result make the system work faster.
2) Don’t use RAW encoder – it’s destined only for testing and transmits the image without compression.
3) AAFC encoder is used for connection within one LAN where connection bandwidth is more than 10 Mbit/sec. If you’ve got less use AAC.
4) To improve performance you can also decrease color depth and remote desktop complexity as well as choose optimal encoder settings. For example, to watch pictures it might be the best option to turn on jpeg compression.
Maxim Prokopenko, independent Internet and network technologies expert and co-developer of Ammyy Admin.
Try instant connection with Ammyy Admin
How to establish connection within 30 sec (first run guide)
Ammyy Admin features
Ammyy Admin manual
Comments
Copy link Quote reply
Ratinod commented Mar 26, 2019
Godot version:
3.1 (March 13, 2019) and 3.0.6
OS/device including version:
Windows 10 x64
GeForce GTX 770/PCIe/SSE2
Issue description:
The game crashes after a while. The game window will freeze and then close, giving the error:
drivers/unix/net_socket_posix. cpp:190 – Socket error: 10054
Steps to reproduce:
This comment has been minimized.
Copy link Quote reply
qarmin commented Mar 26, 2019
I got this backtrace, when I opened all scenes at once:
This comment has been minimized.
Copy link Quote reply
qarmin commented Mar 26, 2019
Also sometimes error about missing function happens:
This comment has been minimized.
Copy link Quote reply
Chaosus commented Apr 2, 2019
Play until the error appears
Can you bisect this bug to – Run the game and its crash?
This comment has been minimized.
Copy link Quote reply
CEDoromal commented Apr 2, 2019
I previously encountered this error in my tilemap game.
For me, the fix was to load in the textures to the tilemap node.
Maybe you have a node with a property that is not properly loaded.
(I’m new to Godot so I’m not really the one to trust with this, but maybe I could help)
This comment has been minimized.
Copy link Quote reply
CEDoromal commented Apr 2, 2019 •
I think it has something to do with Winsock. And if it does, that means that the error is WSAECONNRESET (Error Code: 10054, see https://docs. microsoft. com/en-us/windows/desktop/winsock/windows-sockets-error-codes-2 for more info)
I don’t really know how and why Godot is using Winsock, but these stuffs are beyond my current knowledge.
This comment has been minimized.
Copy link Quote reply
Zireael07 commented Apr 2, 2019
Socket error 10054 is because the debugger is using Winsock, and it’s disconnecting when the crash happens and/or it gets unexpected data. (Yes, I have had cases where the game runs perfectly IF I don’t touch the remote tree tab, then it crashes, because the debugger for some reason cannot handle it)
This comment has been minimized.
Copy link Quote reply
CEDoromal commented Apr 2, 2019
Socket error 10054 is because the debugger is using Winsock, and it’s disconnecting when the crash happens and/or it gets unexpected data. (Yes, I have had cases where the game runs perfectly IF I don’t touch the remote tree tab, then it crashes, because the debugger for some reason cannot handle it)
This comment has been minimized.
Copy link Quote reply
Zireael07 commented Apr 2, 2019
Most probably your project is doing something which causes the project itself to crash. badly named variables, recursive references, missing assets could all be the reason.
This comment has been minimized.
Copy link Quote reply
Ratinod commented Apr 2, 2019
Play until the error appears
Can you bisect this bug to – Run the game and its crash?
No. The game never crashed on launch. You need to play for a while until you get an error.
Most probably your project is doing something which causes the project itself to crash. badly named variables, recursive references, missing assets could all be the reason.
I am new to Godot. And this project was done strictly following the tutorial. Twice from scratch (on versions 3.0.6 and 3.1). And this problem occurred both times. The problem does not allow itself to be found (not an informative error without any specifics).
This comment has been minimized.
Copy link Quote reply
OlexiyKravchuk commented May 5, 2019
I have the same problem with my project in Godot_v3.1-stable_win64.
This comment has been minimized.
Copy link Quote reply
OlexiyKravchuk commented May 5, 2019 •
I completely deleted a lot of comments in which they hit lines like this – («»»some kind of code» value of the line «some kind of code»»») and this helped, after this, such error stopped appearing. If there are relapses I will inform.
This comment has been minimized.
Copy link Quote reply
Hedre commented May 12, 2019
I have this problem too
This comment has been minimized.
Copy link Quote reply
ScepticDope commented May 13, 2019 •
Same error here, Windows 8.1 V3.1.1 Mono stable. After a reboot everything works fine again? I only get this on launch after messing around with 3D camera’s.
This comment has been minimized.
Copy link Quote reply
robertarnborg commented May 16, 2019 •
This comment has been minimized.
Copy link Quote reply
paacardoso commented May 16, 2019
I found out that disabling the debugger agent (in Project Settings/Mono/Debugger Agent/Wait For Debugger) will solve this issue.
This comment has been minimized.
Copy link Quote reply
hedgehog90 commented May 30, 2019
I get this error + crash when trying to debug Godot using vs code.
This comment has been minimized.
Copy link Quote reply
Obr00007576 commented Jun 2, 2019
This comment has been minimized.
Copy link Quote reply
Obr00007576 commented Jun 3, 2019
I’ve solved my problem. At the beggining I tried to use ‘export(packedscene) var scene’ to export the scene and then use function change_scene_to to get into another scene. The error occured in this way but when I tried to use change_scene with parameter of the path of the scene, everything was in order. So, I guess, the operation of export happens at the begginning of the programm and it is the first step. If the scenes are exported in circle just as what I said in the last comment, godot will stick on loading those scenes in dead circle. When it got the limit of memory or quantity of functions or anything else I’m not sure, godot got broken with this error because its debugger had been broken.
This comment has been minimized.
Copy link Quote reply
winston-yallow commented Jun 17, 2019 •
I have the same error message (only on windows, Linux seems to run smooth for me). I am not sure if it is caused by the same thing as the error message itself is not very descriptive. My project has only a few nodes. The only one with a script is a RigidBody with some _integrate_forces() things. The error consistently appears after the game ran for a few seconds (basically the error appears when the body reaches a «stable» position). My code was a small test for an idea I had (limiting the movement of a RigidBody onto a Curve3D. ). The code is far from perfect, however it should not make the engine crash.
If you think this is not related to this issue please let me know so I can create a separate issue. The error message itself does not really tell me what is wrong or why it appears.
Godot Version:
v3.2.dev. calinou.197b65f32
OS:
Windows 10 x64
Minimal reproduction project:
testing. zip
Code that enables the bug:
This comment has been minimized.
Copy link Quote reply
Zireael07 commented Jun 17, 2019
That doesn’t look like GDScript, nor C#. What language/bindings is that?
This comment has been minimized.
Copy link Quote reply
winston-yallow commented Jun 17, 2019
Do you mean my example? It is GDScript (using type annotations)
This comment has been minimized.
Copy link Quote reply
winston-yallow commented Jun 17, 2019
After further investigation I think the drivers/unix/net_socket_posix. cpp:190 – Socket error: 10054 error is only hiding another error which causes the game to crash. In my case I found an error in my code:
This comment has been minimized.
Copy link Quote reply
Klassix commented Jun 18, 2019 •
Hi iam currently doing the «Discovering Godot: Make Video Games in Python-like GDScript» on udemy. While trying around for an exercise ive also run into this bug. Heres the bugged project:
This comment has been minimized.
Copy link Quote reply
qarmin commented Aug 23, 2019
If you thinks it might be a Godot bug, then attach here a minimal project to reproduce it.
This comment has been minimized.
Copy link Quote reply
golddotasksquestions commented Aug 23, 2019 •
Only after shutting down and restarting Windows, Godot stopped crashing when I started to run my project.
This crashing behavior and error cost me way too much time though. I did not consider restart earlier, because I had no problem with Windows or other Window applications while the issue was present. I also had no problem working within the Godot editor while the crashing was occurring, as it only crashed the window in which I tried to run my project. Restarting Godot itself did not help.
After trying to run another Godot project which I did not touch that day with the same crash and error was it clear that I had to restart my system.
Even if this is not a Godot bug, the error message (as it is so often) could be a lot more informative about what is going on and how to solve the issue.
This comment has been minimized.
Copy link Quote reply
SarojKumar10 commented Aug 28, 2019
It happened to me when I deleted a material on which a model was depended on. Making the material with same name and extension fixed it.
This comment has been minimized.
Copy link Quote reply
akien-mga commented Oct 10, 2019 •
To everyone who reported issues in this thread apart from OP, please open your own issues.
This issue should have been renamed earlier but «Socket error: 10054» is NOT A BUG and this is also not a common denominator between the issues you are facing. It’s just a message from the debugger telling you that the debugger can’t connect anymore — because your game process crashed.
As such this issue is basically a collection of «my game can crash» comments, which you can easily imagine might have a thousand different causes for every single commenter here.
This issue should be solely about debugging the crash when playing the game in #27444 (comment), all other issues should have their own ticket with detailed steps to reproduce and reproduction project, otherwise they have no change to be fixed.
This comment has been minimized.
Copy link Quote reply
akien-mga commented Oct 10, 2019
@Ratinod I played the match3 game for a few minutes on Godot 3.2 alpha 1 and did not get any issue. Can you still reproduce the crash?
This comment has been minimized.
Copy link Quote reply
Toshiwoz commented Oct 10, 2019
@akien-mga, to my understanding what happens is what is mentioned here:
Socket error 10054 is because the debugger is using Winsock, and it’s disconnecting when the crash happens and/or it gets unexpected data. (Yes, I have had cases where the game runs perfectly IF I don’t touch the remote tree tab, then it crashes, because the debugger for some reason cannot handle it)
Based on this comment #27444 (comment)
So, if the debugger cannot handle the error, there’s no error message to look at. And, this way it becomes very hard to debug the issue. Meaning that it would become very hard to create a minimal reproduction project, as the CAUSE of the issue is unknown.
This issue should have been renamed earlier but «Socket error: 10054» is NOT A BUG
all other issues should have their own ticket with detailed steps to reproduce and reproduction project, otherwise they have no change to be fixed.
And this worries me, because I don’t know how to find the source of the problem, in other words it will become very hard to fix my specific issue. And given what you say it sounds like there will be no help from here.
I’ll delete my «spam» comment anyhow. (not this one)
This comment has been minimized.
Copy link Quote reply
akien-mga commented Oct 10, 2019 •
@Toshiwoz I didn’t mean that any comment was spam – but each comment stating that they have the «same» issue should actually be their own issue with detailed information on what issue you actually have.
So, if the debugger cannot handle the error, there’s no error message to look at. And, this way it becomes very hard to debug the issue. Meaning that it would become very hard to create a minimal reproduction project, as the CAUSE of the issue is unknown.
It’s not about the debugger not being able to handle the error. The game crashes (process killed), so the connection to the debugger is severed. The debugger notifies it and reports that.
The fact that there is no other error is not related to the debugger losing its connection.
Исправлено: ошибка WarFrame 10054
Ошибка Warframe 10054 может быть вызвана проблемами с маршрутизатором, интернет-провайдерами или игровыми сетевыми настройками. Warframe показывает ошибку 10054 с сообщением «Существующее соединение было принудительно закрыто удаленным хостом. ОШИБКА 10054.
Вы не сможете получать сообщения при возникновении этой ошибки. После повторного подключения после имени пользователя может отображаться «_1» (число может варьироваться в зависимости от того, как часто это отключение происходит с пользователем), и поэтому игроки не смогут приглашать пользователя на матчи. Это может стать большей проблемой в личных сообщениях / шепотах, так как пользователь не сможет увидеть, отправил ли ему кто-то сообщение. Вот некоторые общие обходные пути, которые вы должны попробовать, прежде чем переходить к подробным решениям:
Чтобы исправить / исправить чат в Warframe, следуйте приведенным ниже решениям:
Решение 1: переключите свой игровой регион
Ошибка 10054 может быть просто ошибкой связи между регионом вашей игры и серверами Warframe. Это можно просто проверить, просто перейдя в другой регион, а затем вернувшись обратно в свой регион.
Решение 2. Включите IPv6 для игры, Windows и маршрутизатора
IPv6 (Интернет-протокол версии 6) является последней версией стандарта IP. Интернет-протокол – это протокол связи, который используется для обеспечения механизма идентификации и определения местоположения компьютеров в сетях и маршрутизации веб-трафика через Интернет. Warframe лучше связывается с IPV6. Включив этот протокол в игре, Windows и ваш роутер могут решить проблему.
Решение 3. Обновите сетевые настройки Windows
Если сетевые настройки вашей системы Windows повреждены или не оптимальны для Warframe, то это может вызвать текущую ошибку Warframe. В этом случае изменение / сброс этих настроек может решить проблему.
ipconfig / renew (пропустите, если вы используете статический IP).
Решение 4. Используйте Google DNS
DNS-сервер используется для перевода названия веб-сайта в IP-адрес их хостов. Если у вашего DNS-сервера возникают проблемы с запросом серверов Warframe, игра может выдать ошибку 10054. В этом случае использование DNS-сервера Google может решить эту проблему.
Решение 5. Создайте новую учетную запись WarFrame
Текущая ошибка Warframe может произойти из-за проблемы с вашей учетной записью. Вы можете проверить это, создав другую учетную запись Warframe. Но имейте в виду, что пользователю разрешено иметь несколько учетных записей, но ему запрещено торговать, дарить подарки или взаимодействовать между счетами. Если он это сделает, DE заблокирует оба своих аккаунта.
Решение 6. Отключите UPnP и NAT-PMP в настройках игры
В игре могут быть разные параметры, которые могут вызвать обсуждаемую проблему. Изменение этих параметров может решить проблему.
Решение 7. Используйте статический IP-адрес в маршрутизаторе
Обычно схема IP домашней сети поддерживается автоматически с использованием DHCP. У этого есть свои преимущества, но связь Warframe использует IP-адрес вашего ПК, который может автоматически изменяться DHCP и, таким образом, вызывать проблему. В этом случае установка статического IP-адреса для вашего ПК может решить проблему.
Решение 8. Отключите UPnP / NAT-PMP / Strict NAT в маршрутизаторе
Универсальный Plug and Play (UPnP) – это сетевой протокол, который позволяет подключать проводные / беспроводные соединения к Интернету с минимальной конфигурацией. Но из-за открытого характера этого протокола у Warframe есть проблемы со связью при использовании этого протокола. Отключение UPnP может решить проблему, с которой вы сейчас столкнулись.
Решение 9. Используйте Regedit для отключения TCP / IP
Протокол управления передачей по интернет-протоколу, обычно известный как TCP / IP, представляет собой набор правил, которые используются для соединения различных систем через Интернет. Если связанные с ним записи реестра Windows повреждены, то Warframe может выдать обсуждаемую ошибку. В этом случае отключение разделов реестра Windows, относящихся к TCP / IP вашего компьютера, может решить эту проблему.
HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services Tcpip Parameters
Решение 10. Измените настройки вашего маршрутизатора
Если настройки вашего маршрутизатора не настроены должным образом для Warframe, то Warframe может выдать текущую обсуждаемую ошибку. В этом случае изменение этих настроек может решить проблему. Проблема может быть вызвана межсетевым экраном вашего маршрутизатора, включенным QoS, отключенной DMZ
Если у вас все еще есть проблемы, то проблема может быть вызвана настройками NAT вашего маршрутизатора. NAT играет важную роль в переназначении пространства IP-адресов. Возможно, ваши настройки протокола NAT не настроены должным образом для Warframe и, следовательно, вызывают ошибку 10054. В этом случае настройка этих параметров может решить проблему.
Если у вас ничего не получилось, попробуйте остаться в региональном чате, если это не решено. Также вам следует обратиться к вашему провайдеру для решения проблемы. Если вы используете любую форму мобильного интернета, то, возможно, ваш трафик направляется через APN, так как эти интернет-провайдеры используют APN. Но эти APN запрещены NAT (изменение настроек NAT на вашем маршрутизаторе не повлияет на блокировку провайдера) и может вызвать проблему. Интернет-провайдер может предоставить вам APN, где NAT не запрещен (но обычно это не так).
Error 10054 1 in transporttcp2 readexact 2
This article will be useful for those using Ammyy Admin as well as other remote access application users as it contains general info on remote control software which can be applied while using similar remote access applications.
It happens quite often when Ammyy Admin users ask «What is the minimum Internet connection bandwidth that makes Ammyy Admin work ok?». Usually we give an answer like this «Ammyy Admin will work with any Internet bandwidth, but the better Internet is the faster Ammyy Admin works». However, it’s impossible to identify the minimum Internet connection speed required for comfort work because there is no any standard for «comfort work» and the meaning of this term may vary from person to person. Thus «comfort work» term used in this article is nothing more than my personal opinion on the matter and you may have your own different one.
Step 1: Connection speed test
1.1. Connect to a client in «Speed Test Only» mode. The new window will show you «TCP by router: port» or «Direct TCP with ip:port» or «Direct UDP with ip:port». The 1st phrase tells the traffic is going through a router, the 2nd and 3rd mean direct traffic transfer. In most cases direct connection provides faster performance rather than connection through router thus it’s always better to establish direct connection although it’s not always possible.
1.2. First of all, make sure that client and operator have «Allow Direct TCP/UDP» box checked. Direct TCP is possible in cases when:
– Both PCs are located in one LAN, or
– One of the PCs can receive incoming TCP connections onto a certain port and this port is listed in «External TCP Port» and has «On» status.
After that click «Start». You’ll get the test results (picture 1) including:
1) Ping time min-avr-max (also called round trip time). This is time a minimal data packet spends for round-trip and reflects minimal, average and maximal time. This parameter has almost no affect on data transfer speed of a bigger size, but it’s crucial for work in remote desktop mode. Comfort work requires average time of 150ms at maximum.
2) Dnload speed – «from client to operator» bandwidth.
3) Upload speed – «from operator to client» bandwidth.
picture 1
picture 1Р°
Bandwidth is often called connection speed. In case you have Direct TCP connection the speed will depend only on Internet providers of client and operator. Ammyy Company will not be able to help you in this case. If you have TCP by router connection and the speed test results are much worse than minimal client and operator Internet bandwidth you should sort out the issue with router before writing to Ammyy tech support.
Step 2: Router check
2.1. Please open https://rl. ammyy. com/ on client side. Here you can see your external IP and country of current location. The closest router that will provide connection between operator and client will be defined based on the country. In case the country was defined wrong, please tell about it Ammyy Company. Keep in mind that this might be due to the following reasons:
– Your Internet provider gave wrong info about your IP.
– You work through a Proxy Server which is located in other country.
– Information on your IP doesn’t match in Ammyy Data Base.
picture 2
1280 x 1024 x 32 bits – desktop resolution and color depth.
4.14 ms – average time of screen capturing.
7.35ms – 2 screen frames average time of comparing. It usually depends on CPU and RAM characteristics, and doesn’t depend on the video system.
To make work comfortable the sum of the 1st and the 2nd line should not be bigger than 50 ms, and a very comfortable work implies the sum to be not more than 20 ms.
It’s remarkable that these are results of a system with disabled hardware acceleration. When hardware acceleration was turned on the test laptop showed average time of capturing increase up to 35 ms, what is by 31ms longer! It might be justified by the fact that disabled hardware acceleration makes graphic adapter use basic RAM and CPU reading speed from RAM is much higher than reading from video memory. Please, check this parameter, and in case average capturing time is too long, one has to look for a reason why graphic adapter works so slowly.
To disable hardware acceleration in Windows 7/XP, please, do the following:
1. Right click on the desktop and select Screen Resolution
2. On the window that opens up, click on the Advanced Settings link
3. Select the Troubleshoot tab, then click Change Settings
4. Move the Hardware acceleration slider towards none to reduce or turn off video hardware acceleration.
5. Click OK, and then click Restart Now.
picture 3
If UAC is enabled, it’ll require user confirmation. In some cases in windows 7 it’s impossible to turn off video hardware acceleration because video adapter and its driver don’t allow changing this settings.
Step 4: Encoder settings
picture 4
To make remote desktop speed faster please follow this recommended encoder settings:
1) It’s recommended to disable desktop background, visual effects and desktop composition. This simplifies remote desktop image and increases compression level and as a result make the system work faster.
2) Don’t use RAW encoder – it’s destined only for testing and transmits the image without compression.
3) AAFC encoder is used for connection within one LAN where connection bandwidth is more than 10 Mbit/sec. If you’ve got less use AAC.
4) To improve performance you can also decrease color depth and remote desktop complexity as well as choose optimal encoder settings. For example, to watch pictures it might be the best option to turn on jpeg compression.
Maxim Prokopenko, independent Internet and network technologies expert and co-developer of Ammyy Admin.
Try instant connection with Ammyy Admin
How to establish connection within 30 sec (first run guide)
Ammyy Admin features
Ammyy Admin manual
Comments
Copy link Quote reply
Ratinod commented Mar 26, 2019
Godot version:
3.1 (March 13, 2019) and 3.0.6
OS/device including version:
Windows 10 x64
GeForce GTX 770/PCIe/SSE2
Issue description:
The game crashes after a while. The game window will freeze and then close, giving the error:
drivers/unix/net_socket_posix. cpp:190 – Socket error: 10054
Steps to reproduce:
This comment has been minimized.
Copy link Quote reply
qarmin commented Mar 26, 2019
I got this backtrace, when I opened all scenes at once:
This comment has been minimized.
Copy link Quote reply
qarmin commented Mar 26, 2019
Also sometimes error about missing function happens:
This comment has been minimized.
Copy link Quote reply
Chaosus commented Apr 2, 2019
Play until the error appears
Can you bisect this bug to – Run the game and its crash?
This comment has been minimized.
Copy link Quote reply
CEDoromal commented Apr 2, 2019
I previously encountered this error in my tilemap game.
For me, the fix was to load in the textures to the tilemap node.
Maybe you have a node with a property that is not properly loaded.
(I’m new to Godot so I’m not really the one to trust with this, but maybe I could help)
This comment has been minimized.
Copy link Quote reply
CEDoromal commented Apr 2, 2019 •
I think it has something to do with Winsock. And if it does, that means that the error is WSAECONNRESET (Error Code: 10054, see https://docs. microsoft. com/en-us/windows/desktop/winsock/windows-sockets-error-codes-2 for more info)
I don’t really know how and why Godot is using Winsock, but these stuffs are beyond my current knowledge.
This comment has been minimized.
Copy link Quote reply
Zireael07 commented Apr 2, 2019
Socket error 10054 is because the debugger is using Winsock, and it’s disconnecting when the crash happens and/or it gets unexpected data. (Yes, I have had cases where the game runs perfectly IF I don’t touch the remote tree tab, then it crashes, because the debugger for some reason cannot handle it)
This comment has been minimized.
Copy link Quote reply
CEDoromal commented Apr 2, 2019
Socket error 10054 is because the debugger is using Winsock, and it’s disconnecting when the crash happens and/or it gets unexpected data. (Yes, I have had cases where the game runs perfectly IF I don’t touch the remote tree tab, then it crashes, because the debugger for some reason cannot handle it)
This comment has been minimized.
Copy link Quote reply
Zireael07 commented Apr 2, 2019
Most probably your project is doing something which causes the project itself to crash. badly named variables, recursive references, missing assets could all be the reason.
This comment has been minimized.
Copy link Quote reply
Ratinod commented Apr 2, 2019
Play until the error appears
Can you bisect this bug to – Run the game and its crash?
No. The game never crashed on launch. You need to play for a while until you get an error.
Most probably your project is doing something which causes the project itself to crash. badly named variables, recursive references, missing assets could all be the reason.
I am new to Godot. And this project was done strictly following the tutorial. Twice from scratch (on versions 3.0.6 and 3.1). And this problem occurred both times. The problem does not allow itself to be found (not an informative error without any specifics).
This comment has been minimized.
Copy link Quote reply
OlexiyKravchuk commented May 5, 2019
I have the same problem with my project in Godot_v3.1-stable_win64.
This comment has been minimized.
Copy link Quote reply
OlexiyKravchuk commented May 5, 2019 •
I completely deleted a lot of comments in which they hit lines like this – («»»some kind of code» value of the line «some kind of code»»») and this helped, after this, such error stopped appearing. If there are relapses I will inform.
This comment has been minimized.
Copy link Quote reply
Hedre commented May 12, 2019
I have this problem too
This comment has been minimized.
Copy link Quote reply
ScepticDope commented May 13, 2019 •
Same error here, Windows 8.1 V3.1.1 Mono stable. After a reboot everything works fine again? I only get this on launch after messing around with 3D camera’s.
This comment has been minimized.
Copy link Quote reply
robertarnborg commented May 16, 2019 •
This comment has been minimized.
Copy link Quote reply
paacardoso commented May 16, 2019
I found out that disabling the debugger agent (in Project Settings/Mono/Debugger Agent/Wait For Debugger) will solve this issue.
This comment has been minimized.
Copy link Quote reply
hedgehog90 commented May 30, 2019
I get this error + crash when trying to debug Godot using vs code.
This comment has been minimized.
Copy link Quote reply
Obr00007576 commented Jun 2, 2019
This comment has been minimized.
Copy link Quote reply
Obr00007576 commented Jun 3, 2019
I’ve solved my problem. At the beggining I tried to use ‘export(packedscene) var scene’ to export the scene and then use function change_scene_to to get into another scene. The error occured in this way but when I tried to use change_scene with parameter of the path of the scene, everything was in order. So, I guess, the operation of export happens at the begginning of the programm and it is the first step. If the scenes are exported in circle just as what I said in the last comment, godot will stick on loading those scenes in dead circle. When it got the limit of memory or quantity of functions or anything else I’m not sure, godot got broken with this error because its debugger had been broken.
This comment has been minimized.
Copy link Quote reply
winston-yallow commented Jun 17, 2019 •
I have the same error message (only on windows, Linux seems to run smooth for me). I am not sure if it is caused by the same thing as the error message itself is not very descriptive. My project has only a few nodes. The only one with a script is a RigidBody with some _integrate_forces() things. The error consistently appears after the game ran for a few seconds (basically the error appears when the body reaches a «stable» position). My code was a small test for an idea I had (limiting the movement of a RigidBody onto a Curve3D. ). The code is far from perfect, however it should not make the engine crash.
If you think this is not related to this issue please let me know so I can create a separate issue. The error message itself does not really tell me what is wrong or why it appears.
Godot Version:
v3.2.dev. calinou.197b65f32
OS:
Windows 10 x64
Minimal reproduction project:
testing. zip
Code that enables the bug:
This comment has been minimized.
Copy link Quote reply
Zireael07 commented Jun 17, 2019
That doesn’t look like GDScript, nor C#. What language/bindings is that?
This comment has been minimized.
Copy link Quote reply
winston-yallow commented Jun 17, 2019
Do you mean my example? It is GDScript (using type annotations)
This comment has been minimized.
Copy link Quote reply
winston-yallow commented Jun 17, 2019
After further investigation I think the drivers/unix/net_socket_posix. cpp:190 – Socket error: 10054 error is only hiding another error which causes the game to crash. In my case I found an error in my code:
This comment has been minimized.
Copy link Quote reply
Klassix commented Jun 18, 2019 •
Hi iam currently doing the «Discovering Godot: Make Video Games in Python-like GDScript» on udemy. While trying around for an exercise ive also run into this bug. Heres the bugged project:
This comment has been minimized.
Copy link Quote reply
qarmin commented Aug 23, 2019
If you thinks it might be a Godot bug, then attach here a minimal project to reproduce it.
This comment has been minimized.
Copy link Quote reply
golddotasksquestions commented Aug 23, 2019 •
Only after shutting down and restarting Windows, Godot stopped crashing when I started to run my project.
This crashing behavior and error cost me way too much time though. I did not consider restart earlier, because I had no problem with Windows or other Window applications while the issue was present. I also had no problem working within the Godot editor while the crashing was occurring, as it only crashed the window in which I tried to run my project. Restarting Godot itself did not help.
After trying to run another Godot project which I did not touch that day with the same crash and error was it clear that I had to restart my system.
Even if this is not a Godot bug, the error message (as it is so often) could be a lot more informative about what is going on and how to solve the issue.
This comment has been minimized.
Copy link Quote reply
SarojKumar10 commented Aug 28, 2019
It happened to me when I deleted a material on which a model was depended on. Making the material with same name and extension fixed it.
This comment has been minimized.
Copy link Quote reply
akien-mga commented Oct 10, 2019 •
To everyone who reported issues in this thread apart from OP, please open your own issues.
This issue should have been renamed earlier but «Socket error: 10054» is NOT A BUG and this is also not a common denominator between the issues you are facing. It’s just a message from the debugger telling you that the debugger can’t connect anymore — because your game process crashed.
As such this issue is basically a collection of «my game can crash» comments, which you can easily imagine might have a thousand different causes for every single commenter here.
This issue should be solely about debugging the crash when playing the game in #27444 (comment), all other issues should have their own ticket with detailed steps to reproduce and reproduction project, otherwise they have no change to be fixed.
This comment has been minimized.
Copy link Quote reply
akien-mga commented Oct 10, 2019
@Ratinod I played the match3 game for a few minutes on Godot 3.2 alpha 1 and did not get any issue. Can you still reproduce the crash?
This comment has been minimized.
Copy link Quote reply
Toshiwoz commented Oct 10, 2019
@akien-mga, to my understanding what happens is what is mentioned here:
Socket error 10054 is because the debugger is using Winsock, and it’s disconnecting when the crash happens and/or it gets unexpected data. (Yes, I have had cases where the game runs perfectly IF I don’t touch the remote tree tab, then it crashes, because the debugger for some reason cannot handle it)
Based on this comment #27444 (comment)
So, if the debugger cannot handle the error, there’s no error message to look at. And, this way it becomes very hard to debug the issue. Meaning that it would become very hard to create a minimal reproduction project, as the CAUSE of the issue is unknown.
This issue should have been renamed earlier but «Socket error: 10054» is NOT A BUG
all other issues should have their own ticket with detailed steps to reproduce and reproduction project, otherwise they have no change to be fixed.
And this worries me, because I don’t know how to find the source of the problem, in other words it will become very hard to fix my specific issue. And given what you say it sounds like there will be no help from here.
I’ll delete my «spam» comment anyhow. (not this one)
This comment has been minimized.
Copy link Quote reply
akien-mga commented Oct 10, 2019 •
@Toshiwoz I didn’t mean that any comment was spam – but each comment stating that they have the «same» issue should actually be their own issue with detailed information on what issue you actually have.
So, if the debugger cannot handle the error, there’s no error message to look at. And, this way it becomes very hard to debug the issue. Meaning that it would become very hard to create a minimal reproduction project, as the CAUSE of the issue is unknown.
It’s not about the debugger not being able to handle the error. The game crashes (process killed), so the connection to the debugger is severed. The debugger notifies it and reports that.
The fact that there is no other error is not related to the debugger losing its connection.