A . The following error was returned by the Net Web Services application when bulk loading documents using the CEWS. 2006/06/26 21:45:08. 054 091c 0001 Caught WASP exception at line 517 of . ‘XMLTokenWriter. cpp: Your host machine’s software terminated an established connection. thrown at ‘src’transport’tcp’TCPOutputStream. cpp:69 caught at . ‘XMLTokenWriter. cpp:515 2006/06/26 21:45:08. 054 091c 0001 <-(1) CWebRequestHandler::ExecuteOperation 0x00000000 2006/06/26 21:45:08. 069 091c 0001 <-(0) CSOAPServerMethods::process 2006/06/26 21:50:22. 667 0514 0076 -> (0) CSrvCatalog::GetMetadata [for USPLSMEDP066. P8Apache. The Systinet web service appeared to be timing out the connection in error 1420. NET web service application. The wsiconfig utility’s hts:rwtimeout setting was changed from 30 seconds to 3 minutes to resolve the problem. The object store service was then restarted. [{“Product”:{“code”:”SSNVNV”,”label”:”FileNet Content Manager”},”Business Unit”:{“code”:”BU053″,”label”:”Cloud & Data Platform”},”Component”:”Content Engine”,”Platform”:[{“code”:”PF025″,”label”:”Platform Independent”}],”Version”:”3. 5. 1″,”Edition”:””,”Line of Business”:{“code”:”LOB45″,”label”:”Automation”}}].
[FIXED] An Established Connection was Aborted by the Software in Your Host Machine
19 Answers 19
Sorted by:
Eclipse can be easily restarted after being closed in order to solve this issue. This can occur in some circumstances when Eclipse fails to establish a connection with the emulator.
Look into the possibility of two Eclipse instances pointing to the same Android SDK. just keep one instance of Eclipse and try again. This is the reason why the error message “established connection was aborted by the software in your host machine” is displayed. look into the specifics of Android adb (Android Debug Bridge), and you’ll find it.
I was getting these errors too and was stumped. I read the two answers above and tried them, but I still received the error.
But I looked in Task Manager’s processes tab for a rogue instance of eclipse. exe *32 that the UI didn t show as running. Since the error does imply that the emulator/phone can’t connect because it has already established a connection with the second copy, I suppose this should have been obvious.
To sum up, check in Task Manager to make sure there aren’t any other Eclipse instances running before restarting your computer!
Try closing them as well if you work on projects in multiple IDEs or other applications that connect to AVD.
If Netbeans is configured for NBAndroid, it can also conflict with Eclipse.
I had the problem with multiple IDE. Closing Eclipse, killing from task manager or restarting didnt help. Just deleted the AVD and created it again.
SOLUTION :-
If you have two devices connected to the computer simultaneously, this issue might arise. Adb does not support reaching both devices via command/console. Therefore, you will probably encounter this issue if you debug your app after connecting and disconnecting the second device. One solution might be restarting adb and/or eclipse if necessary. There isn’t another way to deal with it, which is sometimes quite annoying.
When you simultaneously launch Android Studio and Eclipse, this issue might also arise. If you try to close one of them, your problem might be resolved.
In my case, I was simultaneously running Eclipse and Android Studio. Through adb, AS and Eclipse were attempting to communicate with a device/emulator.
Solution: I closed Android Studio. Then I restarted Eclipse.
Hope this helps you 🙂
Close the emulator if already opened. Right-click your project and choose “Run as,” “Run Configurations,” and “Run.” Right-click your project and choose “Run as” “Android project” after the emulator has launched.
When using Android Studio 2, I ran into this problem on my Windows 7 64-bit development machine. 1. x and Android Studio 2. 2. x side-by-side.
I had deployed an application via the 2. 2. x instance the day before, leaving that IDE running. I released a different application from the two the following day. 1. x IDE and this is when I encountered the issue.
Shutting down both IDEs and then restarting the 2. 1. x IDE resolved the issue for me.
The issue can be fixed by restarting Eclipse, which will also end the “adb disconnect” and “adb kill-server” processes.
The following commands did not function on a Windows machine when I tried to avoid rebooting: * /android/adt-bundle-windows/sdk/platform-tools/adb kill-server
Therefore, what was successful in getting adb to function normally again was
The IDE had to be reopened as administrator for it to work for me (under Windows). All worked smoothly after that.
Eclipse needed to be stopped and restarted in order for me to solve this issue. This can occur when Eclipse fails to establish a connection with the emulator or device.
Running my app from Eclipse Luna while using the WifiADB app on my phone, I started receiving this error. Strangely, it was functioning properly in Indigo (I installed Luna last night).
My issue was that I was using the phone to charge on the PC while also running a When using the bat script to terminate ADB, it appeared that a second instance had been launched. It was resolved by charging the phone while debugging over wifi by plugging it into the monitor. Sometimes I have to perform wifi debugging to check if my app stops/starts when the power state changes.
Of course it’s reasonable to assume (very likely), but I haven’t configured Luna the same way.
This issue arises when two programs share the same port. For example, Android Studio typically uses port 5037. To resolve, try closing the port using cmd and restarting Android Studio or Eclipse.
I was having this problem. Things I tried:
This is what worked for me
How to Fix An Established Connection Was Aborted by the Software in Your Host Machine Error
Troubleshooting this Error can be done by the following methods. The command prompt will be used in the first technique to fix the error. In the second approach, we’ll turn off Windows Firewall to fix the issue.
A . The following error was returned by the Net Web Services application when bulk loading documents using the CEWS. 2006/06/26 21:45:08. 054 091c 0001 Caught WASP exception at line 517 of . ‘XMLTokenWriter. cpp: Your host machine’s software terminated an established connection. thrown at ‘src’transport’tcp’TCPOutputStream. cpp:69 caught at . ‘XMLTokenWriter. cpp:515 2006/06/26 21:45:08. 054 091c 0001 <-(1) CWebRequestHandler::ExecuteOperation 0x00000000 2006/06/26 21:45:08. 069 091c 0001 <-(0) CSOAPServerMethods::process 2006/06/26 21:50:22. 667 0514 0076 -> (0) CSrvCatalog::GetMetadata [for USPLSMEDP066. P8Apache. The Systinet web service appeared to be timing out the connection in error 1420. NET web service application. The wsiconfig utility’s hts:rwtimeout setting was changed from 30 seconds to 3 minutes to resolve the problem. The object store service was then restarted. [{“Product”:{“code”:”SSNVNV”,”label”:”FileNet Content Manager”},”Business Unit”:{“code”:”BU053″,”label”:”Cloud & Data Platform”},”Component”:”Content Engine”,”Platform”:[{“code”:”PF025″,”label”:”Platform Independent”}],”Version”:”3. 5. 1″,”Edition”:””,”Line of Business”:{“code”:”LOB45″,”label”:”Automation”}}].
