RE: ODBC Error with Sybase from Win2K Server (but works from WinXP!)

Note that in most cases, the error occured BEFORE the Sybase stored proc
created the tempDB..tempTable in the SELECT INTO part of the stored procedure.

"Patrick" wrote:

> Our company only allow the use of Merant 3.60 32-bit Sybase ODBC Driver
> (Version) for connection to Sybase Sybase 12.5.3 DB on Sun OS 5.3)
>
> I have a stored procedure on Sybase 12.5 ASE which
> a) Select 'dummy'
> b) Select lots of stuff using joins and filters into tempDB.tempTable
> using dirty read
>
> I tried
> 1) execute stroed proc on using Sybase 12 client Windows isql.exe (38,400
> bytes) ------ this succeeded
>
> 2) Tried to execute same stored procedure from a Microsoft SQL Server 2000
> DTS Package using
> 2.1) SQL Server 2000's DTSRun.exe (Version 2000.80.194.0)
> 2.2) Merant 3.60 32-bit Sybase ODBC Driver
> 2.3) same Sybase 12 windows client (script installed as per 1 above)
> 2.4.1) When run from Windows 2000 Server SP4
> 2.4.1.1) Following sys.out is returned to DTS:
> Step 'DTSStep_DTSExecuteSQLTask_6' failed
> Step Error Source: Microsoft OLE DB Provider for ODBC Drivers
> Step Error Description:[MERANT][ODBC Sybase
> driver][Sybase]ct_connect(): user api layer: internal Client Library
> error: Read from the server has timed out.
> Step Error code: 80004005
> Step Error Help File:
> Step Error Help Context ID:0
> Step Execution Started: 10/24/2005 3:12:05 PM
> Step Execution Completed: 10/24/2005 3:12:30 PM
> Total Step Execution Time: 25.062 seconds
> Progress count in Step: 0
>
> 2.4.1.2) ODBC Trace file indicate the following:
> fMYDTS_NAME a58-bf4 EXIT SQLDriverConnectW with return code -1 (SQL_ERROR)
> HDBC 028118D8
> HWND 00000000
> WCHAR * 0x1F7B1D38 [ -3] "******\ 0"
> SWORD -3
> WCHAR * 0x1F7B1D38
> SWORD 8
> SWORD * 0x00000000
> UWORD 0 <SQL_DRIVER_NOPROMPT>
>
> DIAG [S1T00] [MERANT][ODBC Sybase driver][Sybase]ct_connect(): user api
> layer: internal Client Library error: Read from the server has timed out.
> (63)
>
> fMYDTS_NAME a58-bf4 ENTER SQLGetDiagRecW
> SQLSMALLINT 2
> SQLHANDLE 028118D8
> SQLSMALLINT 1
> SQLWCHAR * 0x02C4F60C (NYI)
> SQLINTEGER * 0x02C4F630
> SQLWCHAR * 0x02C4F20C (NYI)
> SQLSMALLINT 512
> SQLSMALLINT * 0x02C4F634
>
> fMYDTS_NAME a58-bf4 EXIT SQLGetDiagRecW with return code 0 (SQL_SUCCESS)
> SQLSMALLINT 2
> SQLHANDLE 028118D8
> SQLSMALLINT 1
> SQLWCHAR * 0x02C4F60C (NYI)
> SQLINTEGER * 0x02C4F630 (63)
> SQLWCHAR * 0x02C4F20C (NYI)
> SQLSMALLINT 512
> SQLSMALLINT * 0x02C4F634 (132)
>
> fMYDTS_NAME a58-bf4 ENTER SQLGetDiagRecW
> SQLSMALLINT 2
> SQLHANDLE 028118D8
> SQLSMALLINT 2
> SQLWCHAR * 0x02C4F60C (NYI)
> SQLINTEGER * 0x02C4F630
> SQLWCHAR * 0x02C4F20C (NYI)
> SQLSMALLINT 512
> SQLSMALLINT * 0x02C4F634
>
> fMYDTS_NAME a58-bf4 EXIT SQLGetDiagRecW with return code 100
> (SQL_NO_DATA_FOUND)
> SQLSMALLINT 2
> SQLHANDLE 028118D8
> SQLSMALLINT 2
> SQLWCHAR * 0x02C4F60C (NYI)
> SQLINTEGER * 0x02C4F630
> SQLWCHAR * 0x02C4F20C (NYI)
> SQLSMALLINT 512
> SQLSMALLINT * 0x02C4F634
>
> HOWEVER, exeute the same stored proc on my workstation (WinXP Pro SP1, with
> otherwise the same scripted install config), and the DTS step that execute
> the Stored proc succeedeed. Confused! How could I investigate? Same logon
> credentials used in both server and WinXP environments! Tracert from
> workstation and server are OK (<10ms in each hop). Even using Sybase ISQL to
> execute stored proc on Sybase (using sybase open client instead of ODBC works
> from Dev/UAT Win2K server SP4!).
>
> SOS!
.

Relevant Pages

  • Strange ADO.NET/Sybase/Sybase OLEDB problem
    ... we have developed in VB.NET and that accesses a Sybase database using the ... Sybase OLEDB driver via ADO.NET. ... Every morning about 5am, the windows service checks a specified directory, ... MergeData stored proc has started to finish prematurely before it has ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Pls recommend a replacement for Microsoft Query
    ... SQL Server certainly does. ... The best approach is to create a stored procedure, ... on the server and call the stored proc from Excel. ... use MS Query to call the proc (even create it if you have the ...
    (microsoft.public.excel)
  • Stored procedure never finishes
    ... I have a stored proc that won't finish. ... When the stored procedure hangs SQL server is not consuming any ...
    (microsoft.public.sqlserver.server)
  • RE: ODBC Error with Sybase from Win2K Server (but works from WinXP!)
    ... I'd like to know if you create a DSN in odbc ... When configuring the DSN for the ODBC connection to Sybase, ... SQL Server connection. ... >> HOWEVER, exeute the same stored proc on my workstation (WinXP Pro SP1, ...
    (microsoft.public.sqlserver.odbc)
  • Re: Ignore SQL Server 2000 store proc errors and still get results?
    ... Raising errors and handling exceptions is ... >We have a SQL Server 2000 stored procedure that raises errors when run. ... >the stored proc and still get the result sets back. ...
    (microsoft.public.dotnet.framework.adonet)