Home Page › Forums › BizTalk 2004 – BizTalk 2010 › SQL Adapter failure
- This topic has 3 replies, 1 voice, and was last updated 8 years, 3 months ago by
community-content.
-
AuthorPosts
-
-
March 20, 2008 at 10:04 AM #19093
Hi.
i am currently working on migration project for one of our customers – from BTS2004 to 2006, and in this project we started to use SQL adapter more massively. On the previous version of application – there was a use with external code for ceratin message to an SQL 2000 table, where was a call to a stored procedure, which was opening a transaction and splitting a message between some tables.
Now’ the problem occurred while we tryed to send the same message to same tables but using SQL adapter – and that what I got :
The adapter “SQL” raised an error message. Details “HRESULT=”0x80040e57″ Description=”The statement has been terminated.”
HRESULT=”0x80040e57″ Description=”String or binary data would be truncated.”
HRESULT=”0x80004005″ Description=”Cannot roll back RoentgenTrans. No transaction or savepoint of that name was found.”
HRESULT=”0x80004005″ Description=”Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = 1, current count = 2.”
HRESULT=”0x80004005″ Description=”Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = 1, current count = 2.”
The problem occurres not every run, but like 1:5 – where one succedes and 5 fail. Any ideas?
BTW – the stored procedure has transactive objects inside it. Is There any issue with transaction clash like ADAPTER vs. STORED PROCEDURE ???
Thanx a lot 🙂
-
March 20, 2008 at 10:22 AM #19094
I’ve encountered the same problem. It occurs when your outbound message has data longer than the SQL column allows. For example if you are trying to write “Hello World!” to a column in your SQL table that is defined as CHAR(10).
This also explains why it doesn’t happen all the time.
I solved this by placing a String Left functoid just before the outbound node and specifying a length equal to the max data length for the table column.
It’s probably not a bad idea to do this to every outbound node where your inbound data could be longer than the table allows.
Hope this solves your problem.
-
May 20, 2009 at 5:00 PM #22434
I am calling a SP from BizTalk that returns XML without actually storing it in any tables. So I am returning the XML the SP is creating on the fly. I am however getting the error:
Event Type: Warning
Event Source: BizTalk Server 2006
Event Category: BizTalk Server 2006
Event ID: 5740
Date: 21/05/2009
Time: 11:45:16
User: N/A
Computer: XXXX
Description:
The adapter “SQL” raised an error message. Details “HRESULT=”0x80004005″ Description=”Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = 1, current count = 0.”
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Any help will be fantastic.
-
May 29, 2009 at 7:44 PM #22531
Hi,
If you haven’t figured this out already, remove your BEGIN TRANSACTION, COMMIT TRANSACTION and ROLLBACK TRANSACTION statements from the code in your stored procedure, as using transactions in the SP cause problems when interfacing with BizTalk.
Cheers.
Daniel.
-
-
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.