on 11-27-2014 1:36 PM
Hi,
one of our customers reported a problem with our application. We checked the console log and found this messages:
...
I. 27.10 08:51:54. Verbindung wurde abnormal beendet, Fehlercode 121
I. 27.10 08:51:54. AppInfo des getrennten TCPIP-Clients: HOST=WIN2K8TS;OS=Windows NT 6.2 Build 9200 ;PID=0x8e4;THREAD=0x7b4;EXE=X:\TelApp.exe;VERSION=7.0.4.3541;API=ODBC
...
Translated that would be something like this:
Connection was terminated abnormally, error code 121
AppInfo of the disconnected TCPIP-client: ...
Any idea where I could look up this error code?
Hello, Reimer
Does the specified application use cursors on the client side?
It could be that in some case the cursor is not properly closed.
Does it happen in a specific procedure?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Reimer,
More specifically to Jason's answer, the error should be a Windows *operating system* error code (which does turn out to be frequently a Winsock error error code when working with networks: Windows Sockets Error Codes (Windows) )
In this specific case however, it is a regular System Error code: System Error Codes (Windows)
You can always see which system code it is by using 'net helpmsg #' at a Command Prompt:
C:\>net helpmsg 121
The semaphore timeout period has expired.
You can then use this information to search for further issues, for instance on Microsoft's website about this error (ERROR_SEM_TIMEOUT) and network adapters: http://support.microsoft.com/kb/325487
Regards,
Jeff Albion
SAP Active Global Support
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.