Home > BizTalk Server > Help w/BizTalk Server 2006/SQL Server Errors

Help w/BizTalk Server 2006/SQL Server Errors

I’d like to see if someone out here has seen any of these errors before… I couldn’t find anything on the internet so far, but I imagine they have a common cause. Ideas?

Severity: Critical Error
Status: New
Source: BizTalk Server 2006
Name: Critical Error: A stored procedure call failed.
Description: The following stored procedure call failed: ” { call [dbo].[bts_GetServiceStaticTrackingInfo]( ?)}”. SQL Server returned error string: “”.
Severity: Critical Error
Status: New
Source: BizTalk Server 2006
Name: Critical Error: A stored procedure call failed.
Description: The following stored procedure call failed: ” { call [dbo].[bts_InsertDynamicStateInfo_BizTalkServerApplication]( ?, ?, ?, ?, ?, ?, ?, ?)}”. SQL Server returned error string: “”.
Severity: Critical Error
Status: New
Source: BizTalk Server 2006
Name: Critical Error: A stored procedure call failed.
Description: The following stored procedure call failed: ” { call [dbo].[bts_GetDynamicStateInfo_BizTalkServerApplication]( ?, ?, ?)}”. SQL Server returned error string: “”.
Severity: Critical Error
Status: New
Source: BizTalk Server 2006
Name: Critical Error: A stored procedure call failed.
Description: The following stored procedure call failed: ” { call [dbo].[bts_CreateSubscription_ACCISHost]( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}”. SQL Server returned error string: “Cannot create new connection because in manual or distributed transaction mode.”.
Severity: Critical Error
Status: New
Source: BizTalk Server 2006
Name: Critical Error: A stored procedure call failed.
Description: The following stored procedure call failed: ” { call admsvr_SendPortToPEP( ?)}”. SQL Server returned error string: “”.
Advertisements
Categories: BizTalk Server
  1. June 2, 2008 at 11:51 am

    Victor,
    That looks quite terminal!!

    Is there anything in your SQL Server logs? If not, I would suggest a re-installation of your database if that is an option.

    Nick.

  2. Jeff Lockard
    June 23, 2008 at 5:30 am

    I’ve seen some of the same errors in a recently re-built BTS 2006 environment, with the SQL Server hosted on another physical server. I don’t see any indication of a problem in the SQL Error logs, so I am also not sure what is going on with these errors.

  3. June 23, 2008 at 9:17 am

    Jeff, it’s good to hear someone else out there is having these issues (although I feel sorry for both of us now). Just as a note, I’m still working on trying to find a resolution to this. The one thing I’ve found so far is that if I change my solution to run on a single machine (as opposed to 2), the frequency of these errors is drastically reduced, perhaps by a factor of 4. I’ll let you know what I find if I indeed ever solve this one.

  4. Jeff Lockard
    July 3, 2008 at 6:04 am

    Victor,
    Thanks for the feedback. I’ll keep looking on my end as well, but will be sure to check back here periodically for more info and possibly/hopefully some resolution!

    Thanks…Jeff

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: