Consider the following scenario:
- You have a computer that is running Microsoft BizTalk Server 2009. The BizTalk server is configured to use a case-sensitive database.
- You install Microsoft BizTalk ESB Toolkit 2.0 and configure it to use the case-sensitive database.
- You use BizTalk ESB Toolkit 2.0 to create a BizTalk application.
A message sent to adapter "SQL" on send port "ALL.Exceptions" with URI "SQL://(local)/EsbExceptionDb/" is suspended.
Error details: There was a failure executing the send pipeline: "Microsoft.Practices.ESB.ExceptionHandling.Pipelines.ESBFaultProcessor, Microsoft.Practices.ESB.ExceptionHandling.Pipelines, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "ESB Exception Encoder" Send Port: "ALL.Exceptions" URI: "SQL://(local)/EsbExceptionDb/" Reason: Invalid object name 'bts_Application'.
Error details: There was a failure executing the send pipeline: "Microsoft.Practices.ESB.ExceptionHandling.Pipelines.ESBFaultProcessor, Microsoft.Practices.ESB.ExceptionHandling.Pipelines, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "ESB Exception Encoder" Send Port: "ALL.Exceptions" URI: "SQL://(local)/EsbExceptionDb/" Reason: Invalid object name 'bts_Application'.