Handling custom exceptions thrown from BizTalk maps February 8, 2012
Posted by Genuine Basil in BizTalk, Uncategorized.Tags: BizTalk, BizTalk Map Handling Custom Exceptions, Exception Handing, Handling, Map
add a comment
After setting a friendly custom exception message in a functoid helper class, I was expecting it to appear in the inner exception message of the exception caught by BizTalk orchestration. But, contrary to my expectations, I got the below standard exception messages which prompted me to look more deep into this.
Error encountered while executing the transform Map.ExceptionHandling.TransformInputToOutput. Error:Transformation failed..
Function ‘userCSharp:SomeMethod()’ has failed.
In order to test this scenario, I created a map with scripting functoid as below, which will force an exception
This map is used from an orchestration which will handle the exception.
Exception caught in the catch block is passed to a helper method to analyze the exception.
Within the helper method, a ‘GetAllErrorMessages’ method is being used to iterate through all the inner exceptions.
Upon debugging the solution, custom exception was found in the 4th level of inner exceptions.
WCF-WSHttp Error December 12, 2011
Posted by Genuine Basil in BizTalk.Tags: BizTalk Server 2010, error, WCF-WSHttp
add a comment
Error:
System.ServiceModel.Security.SecurityNegotiationException: Secure channel cannot be opened because security negotiation with the remote endpoint has failed. This may be due to absent or incorrectly specified EndpointIdentity in the EndpointAddress used to create the channel. Please verify the EndpointIdentity specified or implied by the EndpointAddress correctly identifies the remote endpoint. —> System.ServiceModel.FaultException: The request for security token has invalid or malformed elements.
at System.ServiceModel.Security.SecurityUtils.ThrowIfNegotiationFault(Message message, EndpointAddress target)
at System.ServiceModel.Security.SspiNegotiationTokenProvider.GetNextOutgoingMessageBody(Message incomingMessage, SspiNegotiationTokenProviderState sspiState)
— End of inner exception stack trace —
Server stack trace:
at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
Resolution:
Updated URI with IP instead of server name. Possible DNS issue.
This slideshow requires JavaScript.
Monitor BizTalk Server Job – Hotfix July 15, 2011
Posted by Genuine Basil in BizTalk.Tags: BizTalk, BizTalk SQL Job Error, Hotfix, SQL JOB
add a comment
Error:
Executed as user: XXXXX\Svc-BizTalk_SQL_Serv. Unclosed quotation mark after the character string ‘InstanceStateMessageReferences_BizTalkServerIsolatedHo’. [SQLSTATE 42000] (Error 105) Incorrect syntax near ‘InstanceStateMessageReferences_BizTalkServerIsolatedHo’. [SQLSTATE 42000] (Error 102). The step failed.
Resolution:
Essential Tools for a BizTalk Developer June 21, 2011
Posted by Genuine Basil in BizTalk.Tags: BizTalk, essential, tools, utilities
add a comment
- Test your xpath using DanSharp XmlViewer
- DebugView to view the trace
- BizTalk Server Best Practices Analyzer to examine BizTalk server deployments
- SSO Configuration Application MMC Snap-In to manage SSO configuration
- SOAP UI to test WCF and asmx Webservices
- MsgBoxViewer to analyse your MsgBox database
- BizUnit to test BizTalk Solutions
- BizTalk Terminator to supplement BizTalk Administration
BizTalk Setup Error May 20, 2011
Posted by Genuine Basil in BizTalk.add a comment
Below error occured when I ran BizTalk setup after installing UDDI service.
“Setup has detected that the Enterprise Edition of BizTalk Server 2010 was installed. Upgrading from the Enterprise Edition to the Developer Edition is not supported.
Please uninstall the Enterprise Edition and then run Setup again.”
Resolution (found in BizTalk readme doc):
On a BizTalk Server 2010 Standard/Developer/Branch edition, after you install and configure UDDI services, if you try to repair BizTalk Server 2010 by running the BizTalk Server 2010 setup from the product DVD, you may receive this error. Workaround is to repair BizTalk Server 2010 installation using ‘Program and Features’.
