locked
SSIS Package execution fails, then works if code altered and reverted RRS feed

  • Question

  • I have an SSIS Package that is writing table data into Sybase ASE from SQL Server 2016.  I'm kicking it off from a scheduled SQL Agent job. It fails the first time it runs the package with the following error.

    Code: 0x00000384   Source: Populate Table in Sybase Write to Sybase [284] Description: Open Database Connectivity (ODBC) error occurred. state: 'ZZZZZ'. Native Error Code: 5702. [SAP][ASE ODBC Driver][Adaptive Server Enterprise]ASE is terminating this process.

    If I change the source SQL to only pull 1000 rows, save it and schedule it, it executes without error.  If I then take the change out completely, revert to the original code that failed, save and schedule it, it executes without error.  It's the same code, so I can't figure out why it is failing the first time.  Does anyone have any ideas?

    Here is some information that maybe be helpful for troubleshooting.  The Sybase destination is an ODBC connection using a service account.  The Sybase ODBC connection is also established out on the server.  The SSIS is developed on a 32 bit machine and the server is 64 bit, but I've written other packages in this same environment without issue, and it does run fine the second and third times.  The Sybase driver version is 16.0.03.02.  I am writing this to a flash environment in Sybase since I'm testing, so the table is recreated daily as the flash happens from prod. Thanks in advance for any assistance.  It is much appreciated.

    Wednesday, January 23, 2019 7:19 PM

All replies

  • Hi Renee, 

    It seems that the error occurred on Sybase ASE, and then it terminated the connection. 

    You should be able to find some information in ASE error log. 

    You can also post the error message on SAP site


    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Thursday, January 24, 2019 10:01 AM