Hi Daniel, Even with no -n parameter, still happens.
There is a bug in my test script related to concurrency :) I fixed it. Following is a revised version. === BEGIN Win32 BATCH FILE Script ==== @ECHO OFF SETLOCAL REM *** REM *** Change the following O= line to be unique for each run REM *** You can also revise the Udbm and DB1 params to match SAPDB installation. REM *** SET O=lasterr1.txt SET Udbm=dbm,dbm SET DB1=TST SET A= :Top SET A=%A%! IF %A%==!!!!!!!!!!!!!!!!!! GOTO ShowOne dbmcli -d %DB1% -u %Udbm% -uSQL -c info state > %O% IF ERRORLEVEL 1 GOTO ERROR2 GOTO Top :ShowOne ERASE %0% dbmcli -d %DB1% -u %Udbm% -uSQL -c info state IF ERRORLEVEL 1 GOTO ERROR1 rem *** ping a host you can't find to simulate a sleep comand. ping -w 1000 -n 1 192.187.188.2 SET A= GOTO Top :ERROR1 ECHO *** ECHO *** Error encountered! ECHO *** Should show above. ECHO *** GOTO Done :ERROR2 ECHO *** ECHO *** Error encountered! ECHO *** Output of last execution: ECHO *** TYPE %O% GOTO Done :Done ===== END Win32 BATCH File Script ===== Forgot my "SETLOCAL". When you run multiple copies, you need to revise the SET O= line to a unqiue file per instance. Line #7 of the batch file above. Example instructions to reproduce: 1. Copy this batch file from your e-mail to c:\test1.bat 2. Copy test1.bat to test2.bat. 3. Edit test2.bat and change line #7 to "SET O=lasterr2.txt" 4. Open two CMD.EXE shells (using Start/Run) on Windows XP Professional or Windows 2000 Professional / Server. 5. Start test1.bat in the first CMD.EXE shell, start test2.bat in the second CMD.EXE session. Within a few minutes I get a: ERR -24988,ERR_SQL: sql error -4008,Unknown user name/password combination As also noted in my original post, if I run a looping ODBC.NET program and one instance of this batch file at the same time.... I get socket errors on the ODBC side. Thanks. Stephen -----Original Message----- From: Dittmar, Daniel [mailto:[EMAIL PROTECTED]] Sent: Friday, October 04, 2002 2:02 AM To: 'Stephen Gutknecht (SAPDB)'; [EMAIL PROTECTED] Subject: RE: More SAPDB connect issues - DBMCLI concurrent Could you rerun the test by omitting the -n localhost option? This bypasses socket communication. If the same errors occur we can at least rule out a problem with the xserver. Some of the errors occuring with dbmcli happen before the dbm server connects to the database. So unless there is really a problem with the socket communication, those errors and the ODBC problem are probably unrelated. Daniel Dittmar -- Daniel Dittmar SAP DB, SAP Labs Berlin [EMAIL PROTECTED] http://www.sapdb.org/ _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
