Scott:
This has returned to haunt me. Two nights in a row I have had swremotes go off to la la land with this error reported on the server side. Is there any way you can force the swremote.exe to reload when this error is received?
Windows XP with 3 concurrent RDP sessions
SWRemote version 3.30a
Osler
Send Failed: Error 10054
-
- HouseBot Special Member
- Posts: 304
- Joined: Wed May 07, 2003 2:19 pm
- Location: Tel-Aviv, Israel
- Contact:
Re: Send Failed: Error 10054
I experience this when I start other programs on the same machine.
It feels like a reaction to a busy CPU.
Does it make sense?
I'm Using RDP. SWRemote version is 3.30a.
It feels like a reaction to a busy CPU.
Does it make sense?
I'm Using RDP. SWRemote version is 3.30a.
Re: Send Failed: Error 10054
I suppose timing could add to the issue, but there's an underlying problem elsewhere.
Scott
-
- HouseBot Special Member
- Posts: 409
- Joined: Tue Jul 13, 2004 9:13 am
- Location: Tigard, OR
Re: Send Failed: Error 10054
Yeah - there's definitely something going on. I am seeing this error too. In addition I just had the server process crash four or five times in a row. When it finally stabilized enough that I could investigate I found that two of my three remotes were in one of their continual restart modes. I closed and restarted them manually and that stabilized things. I have client tracing running on my server. I don't think there's much useful in the trace but if you want me to send it let me know.