Inserts failed sometimes ...

[Robson Reis]

We have installed a package developed by another company and sometimes
(when the server is with a big rate of transactions), we are seeing
the following messages in package debug file:
2004-04-22 14:23:27 3056:
------------------------------------------------------------

2004-04-22 14:23:27 3056: rlm03000: ls_PutOneRecord: Failed inserting
[04113SO07236054]
2004-04-22 14:23:27 3056: ODBCSetCursorName[3056]: Failed specifying
cursor concurrency to statement handle 1 for 'ls_rep_add'

2004-04-22 14:23:27 3056: dbc01003: ODBCSetCursorName[3056]:
ls_rep_add generated SQL error state: 24000
2004-04-22 14:23:27 3056: dbc01002: [Microsoft][ODBC Driver Manager]
Invalid cursor state
2004-04-22 14:23:27 3056: odbcFilterConnectErrors[3056]: set the
iState to ODBC_DISCONNECT for <24000>
2004-04-22 14:23:27 3056: Function Return Code [00001] ODBC_ERROR

2004-04-22 14:23:27 3056: Operation [00000] ls_PutOneRecord

2004-04-22 14:23:27 3056: Primary Return Code [00000] 00000

2004-04-22 14:23:27 3056: Secondary Return Code [0000000001] 00000

2004-04-22 14:23:27 3056:
------------------------------------------------------------

When this message appears in the app debug file we are loosing some
inserts that the application do in the database.

The MS SQL server configuration is:
4 Pentium 760Mhz 4 GB RAM

SQL 2000 Standard Edition 8.00.760 SP 4
MDAC 2.7 driver ODBC SQLSRV32.dll 2000.81.9031.14 15/11/2002
Any tip will be welcome,

Thanks in advance,
Reis

[Erland Sommarskog]

Robson Reis (re****@yahoo.com) writes:

We have installed a package developed by another company and sometimes
(when the server is with a big rate of transactions), we are seeing
the following messages in package debug file:

I'm afraid that this is not an issue that is easy resolved over a
newsgroup. The best would of course be to open a support case with
that vendor. If you don't have a support contract or that vendor
has gone bust, you may have to find some who can reverse-engineer
the package, or who can dig up the source code.

Judging from the log and your mentioning of heavy stress, I would
guess that there is poor error handling in conjunction with deadlocks.

A poor workaround could be to run this package against an idle
environment, and then replicate from that environment in your live
environment.
--
Erland Sommarskog, SQL Server MVP, so****@algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp

[Simon Hayes]

"Robson Reis" <re****@yahoo.com> wrote in message
news:33**************************@posting.google.c om...

We have installed a package developed by another company and sometimes
(when the server is with a big rate of transactions), we are seeing
the following messages in package debug file:
2004-04-22 14:23:27 3056:
------------------------------------------------------------

2004-04-22 14:23:27 3056: rlm03000: ls_PutOneRecord: Failed inserting
[04113SO07236054]
2004-04-22 14:23:27 3056: ODBCSetCursorName[3056]: Failed specifying
cursor concurrency to statement handle 1 for 'ls_rep_add'

2004-04-22 14:23:27 3056: dbc01003: ODBCSetCursorName[3056]:
ls_rep_add generated SQL error state: 24000
2004-04-22 14:23:27 3056: dbc01002: [Microsoft][ODBC Driver Manager]
Invalid cursor state
2004-04-22 14:23:27 3056: odbcFilterConnectErrors[3056]: set the
iState to ODBC_DISCONNECT for <24000>
2004-04-22 14:23:27 3056: Function Return Code [00001] ODBC_ERROR

2004-04-22 14:23:27 3056: Operation [00000] ls_PutOneRecord

2004-04-22 14:23:27 3056: Primary Return Code [00000] 00000

2004-04-22 14:23:27 3056: Secondary Return Code [0000000001] 00000

2004-04-22 14:23:27 3056:
------------------------------------------------------------

When this message appears in the app debug file we are loosing some
inserts that the application do in the database.

The MS SQL server configuration is:
4 Pentium 760Mhz 4 GB RAM

SQL 2000 Standard Edition 8.00.760 SP 4
MDAC 2.7 driver ODBC SQLSRV32.dll 2000.81.9031.14 15/11/2002
Any tip will be welcome,

Thanks in advance,
Reis

As I understand it, the error messages you've listed come from your
application log, not from SQL Server, so the first place to go for support
should be the application vendor.

You might get more information in microsoft.public.sqlserver.odbc or
..jdbcdriver, but without more knowledge of what the application is, what the
code looks like, and what the app is doing when this error occurs, it's
almost impossible to give more help.

Simon