Results 1 to 4 of 4
  1. #1
    Join Date
    Sep 2002
    Posts
    6

    Red face Unanswered: MDAC 2.8 Issues?

    Most of our Windows 98 SE workstations that are running
    MDAC 2.8 have an issue when posting a transaction against
    a SQL Server 2000 SP2 database. OLE DB Provider for SQL
    Server is the database connector and the application
    making the call is coded in Visual Basic 6.1.

    The client sees this error returned as an "Runtime 6 -
    Overflow Error" on the Visual Basic end as reported by the
    OLE DB Provider. Below is a snippet as taken from the SQL
    Server Profiler trace:

    declare @P1 int
    set @P1=180150062
    declare @P2 int
    set @P2=2
    declare @P3 int
    set @P3=4
    declare @P4 int
    set @P4=-1
    exec sp_cursoropen @P1 output, N'SELECT TblJobs.[Control
    Status Code], TblJobs.[Sales Date], TblJobs.[Promise
    Date], TblCust.Last, TblCust.First, TblCust.MI, TblCust.
    [Home Phone] FROM TblCust RIGHT JOIN TblJobs ON TblCust.
    [Customer ID] = TblJobs.[Customer ID] WHERE TblJobs.
    [Control Number] = 00801328', @P2 output, @P3 output, @P4
    output
    select @P1, @P2, @P3, @P4

    exec sp_cursorfetch 180150062, 32, 1, 1

    exec sp_cursorclose 180150062

    Error: 2809, Severity: 18, State: 1

    Error: 16945, Severity: 16, State: 1

    declare @P1 int
    set @P1=0
    declare @P2 int
    set @P2=229378
    declare @P3 int
    set @P3=294916
    declare @P4 int
    set @P4=0
    exec sp_cursoropen @P1 output, N'exec TblTransactions',
    @P2 output, @P3 output, @P4 output
    select @P1, @P2, @P3, @P4

    Error: 2809, Severity: 18, State: 1

    Error: 16945, Severity: 16, State: 1

    Any suggestions? Would using a stored procedure benefit
    any? Are there known issues with MDAC 2.8 operating in
    this manner? When I rollback to MDAC 2.5 or 2.6 the
    operation goes through successfully. I don't relish
    rolling back a decent number of client workstations seeing
    other MDAC-dependent applications work fine. Unfortunately
    I don't have the VB source code to post, so I might be
    grasping at straws by posting here.

    Any help would be appreciated!

  2. #2
    Join Date
    May 2003
    Location
    UK
    Posts
    220
    Howdy

    MDAC 2.8 should really be run against SQL 2000 SP3A - nothing less.
    You are running SQL 2000 SP2.

    Seems to be lots of problems with SQL 2000 and MDAC & VB ( 6 & .NET )

    Cheers,

    SG

  3. #3
    Join Date
    Sep 2002
    Posts
    6
    I just tested this out by upgrading my local MSDE to sp3a. Restarted and tried the same transaction type and it failed just the same. I really am dreading rolling back all of these workstations, especially since just this one custom app is the one giving me trouble. Wish I myself was a VB programmer so I could dig into things for myself!

    Can't imagine something as simple as trying to append a row to an existing set could offer problems. And if MDAC 2.8 is the culprit (since rolling back seems to fix things) I can't imagine no one else piping up about odd MADC 2.8 behavior. Oh well....*sigh*

  4. #4
    Join Date
    May 2003
    Location
    UK
    Posts
    220
    Howdy,

    It might be worth trying setting nocount on in the sprocs to see what that does....

    It may be the "chatter" that the app produces may be causing buffer overflows perhaps. I found setting nocount to on helps with some apps

    Cheers,

    SG.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •