asked
Sybase and SQL Server communication error[TDS]
Hi! We are having huge problems with executing SSIS package that transfers data from Sybase source to SQL Server. The errors we are getting: [ASEOLEDB]Bad TDS response stream received from server. Unexpected token type received: 16.". An OLE DB record is available. Source: "ASEOLEDB" Hresult: 0x00000000 Description: "[08S01] [Native Code: 30016] [ASEOLEDB]Bad TDS response stream received from server. Unexpected token type received: 68.". An OLE DB record is available. Source: "ASEOLEDB" Hresult: 0x00000000 Description: "[08S01] [Native Code: 30016] [ASEOLEDB]Bad TDS response stream received from server. Unexpected token type received: 0.". The funny part about it is that errors dont occur every time we try to exec the package. Sometimes there are no errors and process finishes succesfully. Sometimes there is only 'token: 0' error. I've spend hours on google trying to find out what is going on, but there is no single explanation about this kind of error(what does it really mean). I've found out what TDS protocol is, I can find topics with TDS errors, but there's rarely a solution. Anyone can help?
Is this package new? If no; was something changed in the package or code? Any known upgrade in versions of SQL server or Sybase?
Package is rather new, we've noticed that all problems started after our client did 'something' with source database. We dont know what he has done, he does not brag about it, but they changed something, probably more than just data operations, maybe updated server, I dont know. We consider 2 possible options, either driver mismatch or problem with encoding. But I'm not sure where to configure encoding on Sybase driver.
Have you solved this?
18 People are following this question.
