Protocol error in TDS stream

dataservices administration
1

Hi Folks,

We have two of Source databases which are configured as a Linked Server. We receive this error when our production job is running in BODS 4.0

The database error message is <SQL submitted to ODBC data source <VNHQPSQL01v\bobjpro> resulted in error [Microsoft][SQL Server Native Client 10.0][SQL Server]OLE DB provider “SQLNCLI10” for linked server “CORE” returned message “Protocol error in TDS stream”.>

I checked the connectivity of the Linked Server and it is working fine. Also checked the TCP/IP and Named Pipe protocol which are set in the SQL Server Configuration Manager

Our Environment: BODS 4.0 SP2
DB: SQL Server 2008 R2
Datastore connection Type: OLEDB

Does anybody have any idea where is this error coming from. Is it something to do with the connection between Linked Server and Target database

Regards
Arun Sasi

searchforarun :india: (BOB member since 2012-10-09)

2

I don’t know the SQL Server communication stack as well as I would like to but when I am forced to use SQL Server I always make sure I am connecting using the native client, not ODBC or OLEDB (I never have to configure a DSN). In your Datastore is your Database type ODBC or Microsoft SQL Server? What is the Database version set to in the Datastore?

Is your SQL Server client software up to date? This could be the root of your problem as MS has identified a bug that is related to this error. However, your client software would have to be very old. Since you are on DS 4.0 I doubt this is the case unless you are using a very old O/S install.

And finally, according to a Google search this error can occur when the network is very busy and/or the amount of data to be transferred is very large.

eganjp :us: (BOB member since 2007-09-12)

3

Hi Jim,

Thanks for the reply.

Here are the answers to your questions

In your Datastore is your Database type ODBC or Microsoft SQL Server?
Microsoft SQL Server
What is the Database version set to in the Datastore?
SQL Server 2008 R2
Microsoft SQL Server Enterprise Edition (64-bit) Ver: 10.50.1600.1

Is your SQL Server client software up to date?
We havent installed any Service Pack or Fix Pack on top of the SQL Server 2008 R2 installation.

It might be possible that the error occurs whenever there is a heavy network traffic as one of our Source database has the maximum number of hits.

Would appreciate if you could let me know the fix for the bug in SQL Server 2008 R2 if there are any.

Regards
Arun Sasi

searchforarun :india: (BOB member since 2012-10-09)

4

Check the version of the client software that run on the Job Server O/S.

eganjp :us: (BOB member since 2007-09-12)

5

Hey Jim,

The version of the BODS client software running on the Job Server O/S is 14.0.2.322 and BODS Server version is 14.0.2.197.

The only relevant post I found was below

http://www.windowsitpro.com/article/john-savills-windows-faqs/i-am-getting-a-message-protocol-error-in-tds-datastream-from-a-sql-server-query-

I also checked the log files on Job Server and it only states that

DBS-070404: |Data flow DF_STAGE_TPRODUCTATTRIBUTEVALUE_ALL|Reader Query
SQL submitted to ODBC data source <VNHQPSQL01v\bobjpro> resulted in error <[Microsoft][SQL Server Native Client 10.0][SQL
Server]OLE DB provider “SQLNCLI10” for linked server “CORE” returned message “Protocol error in TDS stream”.>

Although the query is not complicated it fails even while executing simple data flows.

Ran a diagnostic utility called sqldiag but could not find anything related to
the error.

Thanks!!

Regards
Arun Sasi

searchforarun :india: (BOB member since 2012-10-09)

6

No, you need to check the version of the database client software. I think you can get the version by looking for a file that is named sqlncli*.

eganjp :us: (BOB member since 2007-09-12)

7

Hi Jim,

SQL Server Client version is:

Microsoft SQL Server Management Studio 10.50.1600.1
Microsoft Analysis Services Client Tools 10.50.1600.1
Microsoft Data Access Components (MDAC) 6.1.7601.17514

Regards
Arun Sasi

searchforarun :india: (BOB member since 2012-10-09)

8

That version is fairly new so I doubt that the bug they had identified is in there. It was a very old client version that had the problem.

eganjp :us: (BOB member since 2007-09-12)

9

Ok Jim!!

No problem. We have reported the Protocol error to our client and very soon this issue will be sorted out by their in house DBA.

Regards
Arun Sasi

searchforarun :india: (BOB member since 2012-10-09)