[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | SQL/Services Forum |
| Notice: | kits(3) ft info(7) QAR access (8) SPR access (10) |
| Moderator: | SQLSRV::MAVRIS |
|
| Created: | Thu Oct 13 1988 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2214 |
| Total number of notes: | 8586 |
2180.0. "API Write Routine Failed... among other errors" by BROKE::BASTINE () Fri Mar 28 1997 19:21
I have a customer having problems accessing one table in Rdb from his
powerbuilder application. He can get to the table via the ODBC test
and it appears that his connection is OK, because he sees other tables
in the same database, but whenever he tries to open this particular table,
the following error occurs:
0327 16500172 %SQLSRV-F-ERRAPIABT, API connection aborted
0327 16500172 -SQLSRV-F-WRTCMPRETSTS, API Write routine failed
0327 16500172 -SQLSRV-I-DRVERRSIGARG, Signal arguments (hex): 000020EC 000DB89E
0327 16500172 %SQLSRV-I-DRVERRSIGMSG, Message text of first argument:
0327 16500172 -SYSTEM-F-LINKDISCON, network partner disconnected logical link
0327 16500174 %SQLSRV-I-DRVERRCHNIOSB1, IOSB status: %X20EC, 2nd word: %X0020
0327 16500175 -SQLSRV-I-DRVERRCHNIOSB2, IOSB 2nd longword: %X000DB8E5, status:
0327 16500175 -SYSTEM-F-LINKDISCON, network partner disconnected logical link
.
.
.
0328 08583091 %SQLSRV-F-ERRAPIABT, API connection aborted
0328 08583091 -SQLSRV-F-REDCMPINTERR, Error at read completion from API
0328 08583091 -SQLSRV-I-DRVERRSIGARG, Signal arguments (hex): 000D6962
0328 08583098 %SQLSRV-I-DRVERRSIGMSG, Message text of first argument:
0328 08583098 -CERB-E-NOMSG, Message number 000D6962
0328 08583098 %SQLSRV-I-DRVERRCHNIOSB1, IOSB status: %X0001, 2nd word: %X0004
0328 08583098 -SQLSRV-I-DRVERRCHNIOSB2, IOSB 2nd longword: %X000D6BB3, status:
0328 08583098 -SYSTEM-S-NORMAL, normal successful completion
On the client side they see the error:
WINSOCK ERROR ENTRY
recv() unexpected close Ret 0 Err#0 UNKNOWN Unknown WINSOCK Error
.
.
.
WINSOCK ERROR ENTRY
send() Ret -1 Err#10093 WSANOTINITIALISED Windows Sockets not initialised
Old notes indicate that there is a possible socket buffer size problem on
port 118, so I had them check it, but it is 4096, which is what the note
suggested. I cannot find any leads in any other notes, although this problem
seems to be reported sporadically throughout the notes, there are no
solutions documented other than the socket buffer size.
From the front of the sqlsrv$.log file, tcp/ip is activated. The customer
did mention use of ipx/spx from the client side, however, if the network
weren't set up properly, they wouldn't see any tables, not just having
problems with this particular table.
I have full client logs and a powerbuilder log file with many details...
nothing looks that useful to me, and a full sqlsrv$.log, if anyone is
interested.
Thanks for any suggestions... I don't know where to go with this one.
Renee
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2180.1 | Anyone have any ideas?? | BROKE::BASTINE | | Mon Mar 31 1997 14:19 | 94 |
| I have the winsock log too, nothing in there that isn't already
mentioned here, but here is the bottom of it:
.
.
.
Read
ctx:24 errno:0 hWnd:0 sts:0
Before Read recv()
ctx:24 errno:0 hWnd:0 sts:0
After Read recv()
ctx:24 errno:0 hWnd:0 sts:4
Read
ctx:24 errno:0 hWnd:0 sts:4
Before Read recv()
ctx:24 errno:0 hWnd:0 sts:4
After Read recv()
ctx:24 errno:0 hWnd:0 sts:20
Write
ctx:24 errno:0 hWnd:0 sts:0
Before Write send()
ctx:24 errno:0 hWnd:0 sts:0
After Write send()
ctx:24 errno:0 hWnd:0 sts:530
size:530 bytwrt:530 ptr:6592 Full Write
Read
ctx:24 errno:0 hWnd:0 sts:0
Before Read recv()
ctx:24 errno:0 hWnd:0 sts:0
After Read recv()
ctx:24 errno:0 hWnd:0 sts:0
Error
ctx:24 errno:0 hWnd:0 sts:0
recv() unexpected close Ret 0 Err#0 UNKNOWN Unknown WINSOCK Error
Close
ctx:24 errno:0 hWnd:0 sts:0
Before setsockopt()
ctx:24 errno:0 hWnd:0 sts:0
After setsockopt()
ctx:24 errno:0 hWnd:0 sts:0
Before closesocket()
ctx:24 errno:0 hWnd:0 sts:0
After closesocket()
ctx:24 errno:0 hWnd:0 sts:0
Before WSACleanup()
ctx:24 errno:0 hWnd:0 sts:0
After WSACleanup()
ctx:24 errno:0 hWnd:0 sts:0
Close
ctx:24 errno:0 hWnd:0 sts:0
Write
ctx:24 errno:0 hWnd:0 sts:0
Before Write send()
ctx:24 errno:0 hWnd:0 sts:0
After Write send()
ctx:24 errno:0 hWnd:0 sts:-1
size:119 bytwrt:-1 ptr:6592 Full Write
Error
ctx:24 errno:10093 hWnd:0 sts:-1
send() Ret -1 Err#10093 WSANOTINITIALISED Windows Sockets not initialised
Close
ctx:24 errno:10093 hWnd:0 sts:-1
Close
ctx:24 errno:10093 hWnd:0 sts:-1
Write
ctx:24 errno:10093 hWnd:0 sts:0
Before Write send()
ctx:24 errno:10093 hWnd:0 sts:0
After Write send()
ctx:24 errno:10093 hWnd:0 sts:-1
size:378 bytwrt:-1 ptr:6592 Full Write
Error
ctx:24 errno:10093 hWnd:0 sts:-1
send() Ret -1 Err#10093 WSANOTINITIALISED Windows Sockets not initialised
Close
ctx:24 errno:10093 hWnd:0 sts:-1
Close
ctx:24 errno:10093 hWnd:0 sts:-1
Write
ctx:24 errno:10093 hWnd:0 sts:0
Before Write send()
ctx:24 errno:10093 hWnd:0 sts:0
After Write send()
ctx:24 errno:10093 hWnd:0 sts:-1
size:327 bytwrt:-1 ptr:6592 Full Write
Error
ctx:24 errno:10093 hWnd:0 sts:-1
send() Ret -1 Err#10093 WSANOTINITIALISED Windows Sockets not initialised
Close
ctx:24 errno:10093 hWnd:0 sts:-1
Close
ctx:24 errno:10093 hWnd:0 sts:-1
Close
ctx:24 errno:10093 hWnd:0 sts:-1
|
| 2180.2 | | BROKE::BASTINE | | Mon Apr 07 1997 09:26 | 11 |
| Does anyone have any ideas on what might be wrong here, or what additional
logging might help? We have checked all sql/services log files, powerbuilder
log files, pc log files... nothing is helping in what the bottom line problem
might be. I have also checked stars and it appears that all notes that
indicate this problem end the same way that this one has... no response.
Does anyone have any ideas?
Thanks,
Renee
|
| 2180.3 | | M5::JBALOGH | | Mon Apr 07 1997 10:33 | 12 |
| What version of SQLServices is this?
I suspect the winsock error on the client is a result of an execute
server failing or the application is referencing a connection which it
has disconnected.
If it is the executer, you should see an entry in the sqlsrv$.log that
points you to an execute server log file with an actual error.
If they are below 6.1-02, get them to upgrade...
John
|