I have Biztalk 2009 and SQL server 2008 installed. I'm processing a file from Biztalk to another SQL server that has a different version of SQL server.

Does the difference in the versions affect file processing?

I'm receiving this warning in my Biztalk appication log. My log is full of this warning while processing my file.

Details:"Microsoft.ServiceModel.Channels.Common.ConnectionException: A severe error occurred on the current command.  The results, if any, should be discarded. ---> System.Data.SqlClient.SqlException: A severe error occurred on the current command.  The results, if any, should be discarded.

You have specified that you;re addressing a different version of SQL Server but not mentioned which one? It is possible that the target version of SQL is not supported by the existing version of the SQL Client deployed on the BizTalk machine then you;d face issues. So while your SQL Client 2008 would permit access to earlier versions, it would be INCOMPATIBLE with later versions.

SQL Server Native Client supports the version of SQL Server in which it is released, and the two preceding releases. That means that SQL Server Native Client 10.0 supports connections to SQL Server 2000, SQL Server 2005, and SQL Server 2008. - from http://technet.microsoft.com/en-us/library/cc280356(v=sql.100).aspx

SQL Server 2008 R2 Native Client supports the version of SQL Server in which it is released, and SQL Server 2000 SP4, SQL Server 2005, and SQL Server 2008. - from http://technet.microsoft.com/en-us/library/cc280356(v=sql.105).aspx

SQL Server Native Client 11.0 supports connections to SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, and Windows Azure SQL Database. - from http://technet.microsoft.com/en-us/library/cc280356(v=sql.110).aspx

Regards.

I have SQL server 2008 SP1 installed on Biztalk and I'm processing files to SQL server 2005 SP4.

Will that cause any time out issues? warnings on my application log?

To clarify one point, the version of SQL you use to support the BizTalk databases, BizTalkMgmtDb, BizTalkMsgBoxDb, etc...has nothing to do whatsoever, with any database, SQL or otherwise, you are connecting to with an Adapter.  They are completly unrelated.

Having said that, SQL Server 2005 SP4 is supported with the WCF SQL Adapter.

You will likely not be able to resolve this on the BizTalk side since the error is happening in SQL Server.  That's where you have to go next.

Hi Christiane,

As mentioned in your other post for similar error (http://social.msdn.microsoft.com/Forums/en-US/949ad74e-27ce-4550-a240-4ee4153c129b/biztalk-application-log-warning?forum=biztalkgeneral#eab625b5-3e1c-4a40-90cb-fefdd8c1fef4), this error is due to SQL-Server and nothing to do with BizTalk. Check the SQL eventlog entities for more info. If you don't support your SQL, speak to the relevant team and asked them to check for the eventlog entities.

BoatSeller,

You are asking me to check the event log on SQL server 2005?

If I change my sql adapter to process files to the same sql server (2008) that is installed with Biztalk, will that solve the timeout and warning issues?

We are saying that the problem is on the SQL Server.  That is where you have to continue the investigation.

I would assume the data has to go to a specific SQL Server tasked with some purpose in the overall app.  Changing the SQL Server may get rid of the Warning but if the data is not where it's suppoed to be, that's a step backwards.

• Marked as answer by Christiane0696 9 hours 52 minutes ago

We are saying that the problem is on the SQL Server.  That is where you have to continue the investigation.

I would assume the data has to go to a specific SQL Server tasked with some purpose in the overall app.  Changing the SQL Server may get rid of the Warning but if the data is not where it's suppoed to be, that's a step backwards.

• Marked as answer by Christiane0696 Saturday, February 22, 2014 1:33 AM

We are saying that the problem is on the SQL Server.  That is where you have to continue the investigation.

I would assume the data has to go to a specific SQL Server tasked with some purpose in the overall app.  Changing the SQL Server may get rid of the Warning but if the data is not where it's suppoed to be, that's a step backwards.

• Marked as answer by Christiane0696 Saturday, February 22, 2014 1:33 AM