on 11-11-2009 7:47 PM
Hi,
Since our hoster moved from SQL2000 to SQL2005 (ECC 5.0 system) we are getting every few days the following error in different transactions:
st22:
DYNPRO_READ_FAILED
It's everytime the screen SAPLV50E but everytime different number e.g. 0770
sm21:
11:24:07 DIA 000 010 DELG10 ME21 BY4 Datenbankfehler 0 beim SEL-Zugriff auf Tabelle DYNPLOAD aufgetreten
11:24:07 DIA 000 010 DELG10 ME21 BY0 > [-1] Session Provider: Connection has been closed by peer
11:24:07 DIA 000 010 DELG10 ME21 BY0 > [xFFFFFFFF].#[-1] Communication link failure#[-1] Session
11:24:07 DIA 000 010 DELG10 ME21 BY0 > Provider: Connection has been closed by peer
11:24:07 DIA 000 010 DELG10 ME21 BY0 > [xFFFFFFFF].#[-1] Communication link failure#[0] Protocol
11:24:07 DIA 000 010 DELG10 ME21 BY0 > error in TDS stream
SQL Server Fehlerprotokoll:
Nov 10 2009 11:24AM spid85 Error: 7884, Severity: 20, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
Any idea about a possible cause? Unfortunately we can't reproduce the error.
Thank you in advance!
Kind regards,
Frank
Hi Frank,
Any information you got ?
If possible, pls update.
Thanks & Regards,
Nagendra.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Nagendra,
Sorry for the delay. The two errors belong together. Further analyses of the SQL error code 7884 resulted in a shared memory cause. I also opened a SAP Call and they also suggested to disable the shared memory protocol on the SQL Server network configuration. At the moment we are waiting if the error still occure or not.
Kind regards,
Frank
Hi Frank,
11:24:07 DIA 000 010 DELG10 ME21 BY0 > -1 Session Provider: Connection has been closed by peer
11:24:07 DIA 000 010 DELG10 ME21 BY0 > xFFFFFFFF.#-1 Communication link failure#-1 Session
11:24:07 DIA 000 010 DELG10 ME21 BY0 > Provider: Connection has been closed by peer
11:24:07 DIA 000 010 DELG10 ME21 BY0 > xFFFFFFFF.#-1 Communication link failure#[0] Protocol
As per above error,its a communication error and its related to your network.
To get an idea about DYNPRO_READ_FAILED dump error, Provide the error Analysis from ST22
Thanks & Regards,
Nagendra.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
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.