Ask a questionAsk a question
 

AnswerBizTalk 2009 SQL MsgBox Error

  • Wednesday, August 19, 2009 10:57 AMMikeGBUK Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi,

    I have a clean BTS2009 environment on Win2008 64bit & SQL 2008. Just installed the ESB Toolkit and I have created a simple FILE receive & send port. When I drop I file I get the following error:

    The following stored procedure call failed: " { call [dbo].[bts_UpdateMsgbox_BizTalkServerApplication]( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}". SQL Server returned error string: "Warning: The join order has been enforced because a local join hint is used.;Warning: The join order has been enforced because a local join hint is used.;Duplicate key was ignored.".

    The file does get through to the send port though. Any clues?

Answers

  • Wednesday, August 19, 2009 3:29 PMKiran mp Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    sometimes we get this error when sql server is too busy to execute this stored proc, so better keep an eye on sql server performance
    KiranMP
    • Marked As Answer byMikeGBUK Thursday, August 20, 2009 10:00 PM
    •  

All Replies

  • Wednesday, August 19, 2009 1:11 PMMikeGBUK Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    SELECT @@SERVERNAME does return the name of a server, no funny characters in it.

  • Wednesday, August 19, 2009 1:13 PMKiran mp Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    there could be temporory network glitch,
    are you getting this error regularly?
    KiranMP
  • Wednesday, August 19, 2009 3:19 PMMikeGBUK Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I have just built a self-contained, single server development environment running under Hyper-V. Nothing much else is running on the server. I will continue to monitor the situation. It is not happening on every receive.
  • Wednesday, August 19, 2009 3:29 PMKiran mp Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    sometimes we get this error when sql server is too busy to execute this stored proc, so better keep an eye on sql server performance
    KiranMP
    • Marked As Answer byMikeGBUK Thursday, August 20, 2009 10:00 PM
    •  
  • Thursday, August 20, 2009 10:00 PMMikeGBUK Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    OK,

    I'll monitor the situation.
  • Friday, October 02, 2009 2:10 AMJunaidKazi Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    OK,

    I'll monitor the situation.

    Hi Mike . . Did you find out something about this ? I get the same error sometimes on my VM. . . If you know the exact reason . . Please update . .
  • Friday, October 02, 2009 8:15 AMMikeGBUK Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer
    I don't seem to be getting the problem now. I increased the VM memory to 2Gb and reduced the amount of BizTalk tracking - if I set tracking of properties & message bodies on receive, the problem seemed to occur more often.
    • Proposed As Answer byGaPrabhakar Tuesday, November 03, 2009 12:57 PM
    •  
  • Tuesday, November 03, 2009 1:02 PMGaPrabhakar Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    The Problem Doesn't Seem to Occur if the tracking message bodies on receive Port is not been Set.


    Thanks
    Prabhakar