patterns & practices: Enterprise Service Bus Guidance

New Post: FaultCode and FailureCategory Best Practices?

Chompers — Wed, 27 Aug 2008 13:27:30 GMT

Does anyone have advice regarding a list of the options they have used when setting the FailureCategory and FaultCode properties of a fault message?
What is the difference between a fault and a failure?
Are fault codes a subset of failures with all faults for a failures type handled by single orchestration fault handler?
How are you managing your failure/fault options (enum, list of constants in a class file, a .NET collection, other)?
How do you ensure there is a fault handler for each failure/fault option?

New Post: Saving messages to messagebox and ProcessItinerary subscribing to it

BrendonBirdoes — Fri, 22 Aug 2008 21:27:26 GMT

There are four web services available to you that allow an input message and the itinerary you would like to run. These are the ESB on-ramps.
1. ESB.ItineraryServices - Classic asmx web service that allows for one-way messaging. You can send a payload message and the itinerary, but do not expect a return message.
2. ESB.ItineraryServices.WCF - Same function as above but exposes a WCF basic http endpoint.
3. ESB.ItineraryServices.Response - Classic asmx web service that allows for two-way messaging. You can send a payload and the itinerary and receive a message back from the service.
4. ESB.ItineraryServices.Response.WCF - Same function as above but exposes a WCF basic http endpoint.

Each of these web services are set up in BizTalk as receive locations and have the ItineraryReceiveXml pipeline. This pipeline understands itineraries and will process the itinerary passed with the message. Generally you would set up your own off-ramps (usually dynamic send ports) that will subscribe to the resulting message put into the message box by these on-ramp services. The Itinerary sample is a great place to start to see this processing in action.

Hope that helps!

New Post: Saving messages to messagebox and ProcessItinerary subscribing to it

Keirol — Thu, 21 Aug 2008 22:06:06 GMT

Hello,

I don't know if I miss it in the documentation of ESB..but I have a requirement that is kinda off the right process documented in running the itinerary.
1. Do we have a web service or a method in the ESB Guidance that client application can use to save messages in a messagebox? Message construct would contain input data plus itinerary xml.
2. Can we setup the ProcessItinerary web service to subscribe to the messagebox and run the itinerary processing? Assuming the message saved in the messagebox is constructed in number 1 above?

Hope to get your comments on this one. Thanks!

Created Issue: UDDI resolver timeouts (not configurable UDDI Client)

mtelleria — Thu, 21 Aug 2008 11:38:56 GMT

I our project we have detected that sometimes, if a itinerary has a uddi resolution sometimes throw an exception of timeout to de UDDI webserver.
Checking the code, i have found that the uddi client from the ESB don't have any configurable timeouts and max buffers. Also if an exception is thrown it don't retry an other call.
I have modified this projects: Microsoft.Practices.ESB.Resolver.UDDI and Microsoft.Practices.ESB.UDDI to customize the configuration.

The Class: Microsoft.Practices.ESB.Resolver.UDDI.ResolveProvider
• There are three procedures named Resolver, this procedures call to ResolveUDDI. I have added the possibility to do retries, if an exception is thrown, to the call to ResolveUDDI, these retries are configurable in the machine config : <add key="Retries" value="3" />. The default value if this key is not present is 3.

/// <summary>
/// Uses the UDDI to query a UDDI server for end point info. Will
/// check for either custom bindings that represent config, or will look
/// for ESB UDDI category keys. Called from Pipeline
/// </summary>
/// <param name="config">resolver configuration passed as argument in pipeline</param>
/// <param name="resolver">name of Resolver</param>
/// <param name="message">IBaseMessage used to set context properties</param>
/// <param name="pipelineContext">IPipelineContext passed to SetContext method</param>
/// <returns>Populated Dictionary Object</returns>
public Dictionary<string, string> Resolve(string config, string resolver, IBaseMessage message, IPipelineContext pipelineContext)
{
#region Argument Check
if (String.IsNullOrEmpty(config))
throw new ArgumentNullException("config");
if (String.IsNullOrEmpty(resolver))
throw new ArgumentNullException("resolver");
if (null == message)
throw new ArgumentNullException("message");
if (null == pipelineContext)
throw new ArgumentNullException("pipelineContext");
#endregion Argument Check

Resolution resolution = new Resolution();

//Modified by Miguel Telleria
bool redo = false;
int maxRetries = 3;
int retries = 0;
Dictionary<string, string> output = null;
Hashtable uddiClientConfigHash = (Hashtable)ConfigurationManager.GetSection("ESBProcessor/UDDIClientConfig");
if (uddiClientConfigHash.ContainsKey("Retries"))
maxRetries = int.Parse(uddiClientConfigHash["Retries"].ToString());
do
//End Modification

try
{
// Populate context
ResolverMgr.SetContext(resolution, message, pipelineContext);

// resolve with uddi and return dictionary
output = ResolveUddi(config, resolver, resolution);
redo = false;
}
catch (System.Exception ex)
{
EventLogger.Write(MethodInfo.GetCurrentMethod(), ex);
redo = true;
++retries;
if (retries >= maxRetries)
{
throw;
}
}
//catch (System.Exception ex)
//{
// EventLogger.Write(MethodInfo.GetCurrentMethod(), ex);
// throw;
//}
while (redo && (retries < maxRetries));
return output;
}

/// <summary>
/// Uses the UDDI to query a UDDI server for end point info. Will
/// check for either custom bindings that represent config, or will look
/// for ESB UDDI category keys.
/// </summary>
/// <param name="config">resolver configuration passed as argument</param>
/// <param name="resolver">name of Resolver</param>
/// <param name="message">XML Document of message</param>
/// <returns>Populated Dictionary Object</returns>
public Dictionary<string, string> Resolve(string config, string resolver, XmlDocument message)
{
#region Argument Check
if (String.IsNullOrEmpty(config))
throw new ArgumentNullException("config");
if (String.IsNullOrEmpty(resolver))
throw new ArgumentNullException("resolver");
#endregion Argument Check

Resolution resolution = new Resolution();

//Modified by Miguel Telleria
bool redo = false;
int maxRetries = 3;
int retries = 0;
Dictionary<string, string> output = null;
Hashtable uddiClientConfigHash = (Hashtable)ConfigurationManager.GetSection("ESBProcessor/UDDIClientConfig");
if (uddiClientConfigHash.ContainsKey("Retries"))
maxRetries = int.Parse(uddiClientConfigHash["Retries"].ToString());
do
//End Modification
try
{
// resolve with uddi and return dictionary
output = ResolveUddi(config, resolver, resolution);
redo = false;
}
catch (System.Exception ex)
{
EventLogger.Write(MethodInfo.GetCurrentMethod(), ex);
redo = true;
++retries;
if (retries >= maxRetries)
{
throw;
}
}
//catch (System.Exception ex)
//{
// EventLogger.Write(MethodInfo.GetCurrentMethod(), ex);
// throw;
//}
while (redo && retries < maxRetries);
return output;
}

/// <summary>
/// Uses the UDDI to query a UDDI server for end point info. Will
/// check for either custom bindings that represent config, or will look
/// for ESB UDDI category keys.
/// </summary>
/// <param name="resolverInfo">Configuration string containing config and resolver</param>
/// <param name="message">XLANGMessage passed from orchestration</param>
/// <returns>Dictionary object fully populated</returns>
public Dictionary<string, string> Resolve(ResolverInfo resolverInfo, XLANGMessage message)
{
#region Argument Check
if (null == message)
throw new ArgumentNullException("message");
#endregion Argument Check

// Resolve the params from arguments by creating
// class from schema, and storing the results
Resolution resolution = new Resolution();

//Modified by Miguel Telleria
bool redo = false;
int maxRetries = 3;
int retries = 0;
Dictionary<string, string> output = null;

Hashtable uddiClientConfigHash = (Hashtable)ConfigurationManager.GetSection("ESBProcessor/UDDIClientConfig");
if (uddiClientConfigHash.ContainsKey("Retries"))
maxRetries = int.Parse(uddiClientConfigHash["Retries"].ToString());
do
//End Modification
try
{
// Populate context
ResolverMgr.SetContext(resolution, message);

// resolve with UDDI and return dictionary
output = ResolveUddi(resolverInfo.Config, resolverInfo.Resolver, resolution);
redo = false;
}
catch (System.Exception ex)
{
EventLogger.Write(MethodInfo.GetCurrentMethod(), ex);
redo = true;
++retries;
if (retries >= maxRetries)
{
//Finally
if (null != resolution)
resolution = null;
throw;
}
}
//catch (System.Exception ex)
//{
// //Finally
// if (null != resolution)
// resolution = null;
// EventLogger.Write(MethodInfo.GetCurrentMethod(), ex);
// throw;
//}
while (redo && retries < maxRetries);
//Finally
if (null != resolution)
resolution = null;
return output;
}

• In the procedure “ResolveUddi”
I have added the lines below, this lines set the Security mode for the UDDI proxy client

//Get Security Mode Config
//Modified by Miguel Telleria
Hashtable uddiClientConfigHash = (Hashtable)ConfigurationManager.GetSection("ESBProcessor/UDDIClientConfig");
BasicHttpSecurityMode securityMode = BasicHttpSecurityMode.TransportCredentialOnly;
if (uddiClientConfigHash.ContainsKey("BasicHttpSecurityMode"))
{
string value = ((string)uddiClientConfigHash["BasicHttpSecurityMode"]).Trim().ToUpper();
switch (value)
{
case "TRANSPORTCREDENTIALONLY":
securityMode = BasicHttpSecurityMode.TransportCredentialOnly;
break;
case "TRANSPORTWITHMESSAGECREDENTIAL":
securityMode = BasicHttpSecurityMode.TransportWithMessageCredential;
break;
case "TRANSPORT":
securityMode = BasicHttpSecurityMode.Transport;
break;
case "NONE":
securityMode = BasicHttpSecurityMode.None;
break;
case "MESSAGE":
securityMode = BasicHttpSecurityMode.Message;
break;
default:
securityMode = BasicHttpSecurityMode.TransportCredentialOnly;
break;
}
}
//End Modification

The Class: Microsoft.Practices.ESB.Core.UDDIClient

• In the creation of the instance UddiClient I have added all the rest of the config parameters like timeouts….
//Get the UDDI client Config
//Modified by Miguel Telleria
Hashtable uddiClientConfigHash = (Hashtable)ConfigurationManager.GetSection("ESBProcessor/UDDIClientConfig");
if (uddiClientConfigHash.ContainsKey("sendTimeout"))
binding.SendTimeout = new TimeSpan(0, 0, int.Parse(uddiClientConfigHash["sendTimeout"].ToString()) );

if (uddiClientConfigHash.ContainsKey("recieveTimeout"))
binding.ReceiveTimeout = new TimeSpan(0, 0, int.Parse(uddiClientConfigHash["recieveTimeout"].ToString()));

if (uddiClientConfigHash.ContainsKey("openTimeout"))
binding.OpenTimeout = new TimeSpan(0, 0, int.Parse(uddiClientConfigHash["openTimeout"].ToString()));

if (uddiClientConfigHash.ContainsKey("closeTimeout"))
binding.CloseTimeout = new TimeSpan(0, 0, int.Parse(uddiClientConfigHash["closeTimeout"].ToString()));

if (uddiClientConfigHash.ContainsKey("maxBufferPoolSize"))
binding.MaxBufferPoolSize = long.Parse(uddiClientConfigHash["maxBufferPoolSize"].ToString());

if (uddiClientConfigHash.ContainsKey("maxRecievedMessageSize"))
binding.MaxReceivedMessageSize = long.Parse(uddiClientConfigHash["maxRecievedMessageSize"].ToString());

if (uddiClientConfigHash.ContainsKey("maxBufferSize"))
binding.MaxBufferSize = int.Parse(uddiClientConfigHash["maxBufferSize"].ToString());

//End Modification

To add this new uddi resolver for ESB you need to install the new dlls in the GAC.
Also to customize all the possible config parameters you will need to modify the machine config (C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG):

Add the lines at the beginning of the file:

<configSections>
<sectionGroup name="ESBProcessor">
<section name="Resolver" type="System.Configuration.DictionarySectionHandler,
 System,Version=2.0.0.0,Culture=neutral,
 PublicKeyToken=b77a5c561934e089" />
<section name="AdapterProvider" type="System.Configuration.DictionarySectionHandler,
 System,Version=2.0.0.0,Culture=neutral,
 PublicKeyToken=b77a5c561934e089" />
<section name="ItineraryCache" type="System.Configuration.DictionarySectionHandler,
 System,Version=2.0.0.0,Culture=neutral,
 PublicKeyToken=b77a5c561934e089" />
<section name="Cache" type="System.Configuration.DictionarySectionHandler,
 System,Version=2.0.0.0,Culture=neutral,
 PublicKeyToken=b77a5c561934e089" />
<section name="UDDIClientConfig" type="System.Configuration.DictionarySectionHandler,
 System,Version=2.0.0.0,Culture=neutral,
 PublicKeyToken=b77a5c561934e089" />
</sectionGroup>

Modify this line below, and add the other one. Please check if the public token key is different and add the new one

<ESBProcessor>
<Resolver>
 (The old one)
<add key="UDDI" value="Microsoft.Practices.ESB.Resolver.UDDI, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e00" /> (The new One)
</ESBProcessor>
.
.
.

Also add these lines at the end of the file:
.
.
<ItineraryCache>
<add key="timeout" value="120" />
</ItineraryCache>
<Cache>
<add key="UDDI" value="600" />
<add key="WSMEX" value="600" />
</Cache>

<UDDIClientConfig>
<add key="sendTimeout" value="60" /> 
<add key="recieveTimeout" value="600" /> 
<add key="openTimeout" value="60" /> 
<add key="closeTimeout" value="60" /> 


<add key="BasicHttpSecurityMode" value="TransportCredentialOnly" />

<add key="Retries" value="3" />
<add key="maxBufferPoolSize" value="524288" />
<add key="maxBufferSize" value="65536" />
<add key="maxRecievedMessageSize" value="65536" />
</UDDIClientConfig>
</ESBProcessor>

And thats all to create a configurable uddi resolver for ESB.

New Post: ESB Guidance Webcast next Friday (May 9th 2008)

BrianLoesgen — Wed, 20 Aug 2008 18:32:44 GMT

Kallol,

I am wanting to do something about an end-to-end implementation including governance (per my recent post) as I feel it's really imnportant and that the community here would be interested in it, but my current challenge is my travel schedule. I have 2 days at home in this 30 day period. After that it "settles down" to "only" about 70% travel the following month. It's not all bad, as some of that is really cool vacation time, however it severely limits my abilitity to commit to things like webcasts.

As soon as more stability returns though, I will do my best to make one happen.

Brian Loesgen, Neudesic
http://geekswithblogs.com/bloesgen

New Post: ESB Guidance Itinerary On ramp Service from Java Client

Sujesh — Tue, 19 Aug 2008 10:10:29 GMT

Finally managed to get it going. We have used Axis framework (wsdl2java tool) to create proxy of onramp service.

New Post: ESB Guidance Webcast next Friday (May 9th 2008)

shortwire — Wed, 13 Aug 2008 14:03:57 GMT

Brian,

When is your next webcast on guidance happening? Sometime soon pls :-)

Regards,
Kallol

New Post: Security in ESB Guidance

BrianLoesgen — Fri, 08 Aug 2008 22:19:14 GMT

Kallol:

You could use different maps for the different endpoints, only sending them each the subset of the employee data that they need.

Best regards,

Brian Loesgen, Neudesic
http://geekswithblogs.net/bloesgen

New Post: Security in ESB Guidance

shortwire — Tue, 05 Aug 2008 02:47:43 GMT

Hello,

I have a requirement where two interfaces want the employee data. But one of them should not be shown the address of the employee. That means for each message, the interface should be authorized to receive its contents.
Can you please let me know how to implement this using the guidance package. I need a small write (about 5-6 sentences) on how guidance package can address this. This is for responding to a customer query.

Thx in anticipation.

Regards,
Kallol

New Post: Using SOA Software with Microsoft's ESB Guidance

BrianLoesgen — Sun, 03 Aug 2008 16:25:42 GMT

Although I haven’t seen any traffic here concerning SOA Governance as it relates to Microsoft's ESB Guidance, I have had a few people ask me about it (and I get lots of “oooos” and “ahhhhhhs” when I demo it J), so, I thought I’d post something here for the benefit of people that are interested in this and may not be sure how it integrates. I’d drawing these comments from the real-world project I am on, which is a country-scale ESB based on Microsoft’s ESB Guidance.

We are using SOA Software’s Service Manager product to do policy-based security and monitoring. We need to do complete end-to-end, meaning we want to secure and monitor on-ramps (messages coming in to the ESB) as well as off-ramps (services being invoked from the ESB).

So, how did we do this?

A couple of the challenges we faced:

· The ESB Guidance does include a SOA Software integration pipeline component, however the component is for monitoring only, so it was not applicable to our need

· We are building an infrastructure project, the services we will be calling (request response, one-way or async) are not going to be under our control. How do you manage something that is not under your control?

For the first challenge, SOA Software has an IIS “Management Point” that is effectively an agent that sits on your IIS box and will auto-magically manage any services deployed there (great if you’re in an environment with “cowboy developers” and have loose deployment processes J). However, it only manages ASMX-based services. As everything we’re doing will be WS-* compliant using the WCF on-ramps, this was not an option. Working with SOA Software, we are now using a WCF Management Point which will be in a soon-to-be-released product offering. By setting the binding on the on-ramp, we are able to monitor and manage it.

For the second challenge, the functionality was already there. Service Manager supports the notion of “service virtualization”. You feed it the WSDL of a service, and it creates a proxy for you. That proxy sits in our infrastructure, and runs inside a management point container, so we are able to do all the governance we need at this level. I was initially concerned about the latency cost of introducing an extra hop, however early indications are that the latency impact is neglible, and the cost is well worth the benefits we gain.

Those are just a couple of the challenges we faced, there are more. The guys at SOA have been great to work with and have been very responsive to our needs. We’re not done yet, but so far it looks like Service Manager will be adding significant value to the project.

New Post: Trying to run the scatter sample and received an error.

BrianLoesgen — Wed, 30 Jul 2008 18:51:36 GMT

Ryan,

You're talking about the ResolverService sample, right?

The serviceKey is created dynamically by UDDI when the service is published. You will need to edit the ResolverList.xml to reflect the service keys that were created when the service was published on your machine.

Brian Loesgen, Neudesic
http://geekswithblogs.net/bloesgen

New Post: Trying to run the scatter sample and received an error.

ryancrawcour — Wed, 30 Jul 2008 18:11:50 GMT

Brian;

I am getting the same error as above with the UDDI stuff.
I fixed the treenode thing; but still get the error of no service found.
Looking at my Resolvers.xml it shows the same as above, and also the service ids in my uddi are different.

How do i fix this problem?

Thanks
Ryan

New Post: Is there a way to easy detect errors for SubmitRequestResponse call

BrianLoesgen — Wed, 30 Jul 2008 16:31:14 GMT

Nice question Gary J

If we were talking about an orchestration published as a Web service, the normal way to report an error would be to add a Fault message (type string usually) at the orchestration port and the fault would automatically get returned to the caller as a SOAP fault.

However, I just tried doing that, and I get correlation set initialization errors. Without looking deeper, my theory is that this is due to the fact that the fault message is a simple type (string). What this means is that I cannot get the response back to the on-ramp using this technique.

So, one way you could handle this is to add more smarts at the on-ramp so that it knows that something failed, and have the on-ramp throw an exception which would be returned to the caller as a SOAP fault. Remember, nothing says you can only have one on-ramp. In fact, for the Jordan project, we will have several, because different on-ramps will have different security and monitoring policies assigned to them.

HTH,

Brian Loesgen, Neudesic
http://geekswithblogs.net/bloesgen

Commented Issue: CreateFaultMessage() does not handle '&' in Exceptions (includes Fix)

sshewale — Tue, 29 Jul 2008 11:07:22 GMT

When calling CreateFaultMessage() from an orchestration exception handle, if the exception description contains the '&' character. An example is the System.Net.Sockets.SocketException from WCF which contains a stack trace description 'at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)' containing the '&' character.

In such cases, the following error is thrown from CreateFaultMessage():

An error occurred while parsing EntityName. Line 25, position 75.
Source: Microsoft.Practices.ESB.ExceptionHandling.ExceptionMgmt
Method: Microsoft.XLANGs.BaseTypes.XLANGMessage CreateFaultMessage()
Error Source: System.Xml
Error TargetSite: Void Throw(System.Exception)
Error StackTrace: at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
at System.Xml.XmlTextReaderImpl.ParseEntityName()
at System.Xml.XmlTextReaderImpl.ParseEntityReference()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
at System.Xml.XmlDocument.Load(XmlReader reader)
at System.Xml.XmlDocument.LoadXml(String xml)
at Microsoft.Practices.ESB.ExceptionHandling.ExceptionMgmt.CreateFaultMessage()

It occurs in Microsoft.Practices.ESB.ExceptionHandling.ExceptionMgmt.cs Line 50 'xDoc.LoadXml(...)'. My current workaround is to call String.Replace() on the parameter to strip out the offending characters. Not sure if this is the cleanest way of doing it but it works.
Comments: ** Comment from web user: sshewale **

Good catch. It saved my lots of unfruitful efforts. :)

New Post: Portal Management setup issue

ryancrawcour — Mon, 28 Jul 2008 20:29:15 GMT

Greyfox;

Thanks for your suggestion; this fixed it for me aswell.
Shoo. Must admit whilst this ESB Guidance is really great; to get it to work aint the easiest thing in the world. If it's this difficult to get the samples working; what is it going to be like to build a real application with it?

Updated Wiki: Home

ndelgado — Fri, 25 Jul 2008 23:35:17 GMT

Overview

The Microsoft ESB Guidance provides architectural guidance, patterns, practices, and a set of BizTalk Server and .NET components to simplify the development of an Enterprise Service Bus (ESB) on the Microsoft platform and to allow Microsoft customers to extend their own messaging and integration solutions.

Status

The ESB Guidance released on November 8, 2007! Please see the official ESB Guidance page on MSDN for more information about its contents, intended audience, design goals, and to download the complete ESB Guidance (source code, samples, and documentation).
You can download the final CHM version of the documentation here.

PowerPoint Presentations

Future Plans

Our team started working on the next release of ESB Guidance for Microsoft BizTalk Server 2006 R3. The version 2 release date will coincide with BizTalk 2006 R3 release.

Created Issue: Error with the UDDIPublisher Project Title is required

satyajit_m — Fri, 25 Jul 2008 07:07:30 GMT

have gone through all the steps of the installation till i came to the step of installing the "PreProcessingCORE.vbs" ,, i started by creating the Virtual directory and then stopped at the step of running the uddipublisher project giving the following exception

"Error Creating UDDI Entries... Class:Microsoft.Practices.ESB.UDDI.UddiClient Method: Void .ctor<System.String, System.ServiceModel.BasicHttpSecurityMode, System.String, System.String> : Exception: System.ServiceModle.FaultException'1[uddiorg.api_v2.dispositionReport]: <Fault Detail is equal to uddiorg.api_v2.dispositionReport>"

I am still facing the same issue, I have set proper credentials but still no good. any idea why?

Commented Issue: November 2007 Release missing DundasWebChart.dll

tfabraham — Tue, 22 Jul 2008 16:24:09 GMT

The ESB Management Portal references DundasWebChart.dll and the project has references to specific versions (Version 5...) of the dll. These dlls are not supplied in the source kit. I have found different versions of the dll in other products (V9 in VS2005 and SQLServer).
Comments: ** Comment from web user: tfabraham **

Dundas Chart for ASP.NET Enterprise is a third-party product that you must purchase if you wish to use the chart controls included in the portal. If you don't wish to purchase the license, then remove the charts from the portal site.

Commented Issue: ESB.BizTalkOperationsService Security

tfabraham — Tue, 22 Jul 2008 16:20:31 GMT

Hi

My portal is not working at all and all I get is the default error catcher page. I tracked the error down (debugging) to the BizTalkQuery constructor. The line of code "bizTalkOps = new Microsoft.BizTalk.Operations.BizTalkOperations(bizTalkServer.BizTalkMgmtDb, bizTalkServer.BizTalkMgmtDbName);" is throwing an exception as below;

Failed to connect to the BizTalkMgmtDb database on the PFBT01 server

Source: Microsoft.Practices.ESB.BizTalkOperations.BizTalkQuery

Method: Void .ctor()

Error Source: Microsoft.BizTalk.DBAccessor

Error TargetSite: Void Connect()

Error StackTrace: at Microsoft.BizTalk.Database.DatabaseAccessor.Connect()
at Microsoft.BizTalk.Database.DatabaseAccessor.ExecuteReader(Int32 procIndex, Object[] procParams)
at Microsoft.BizTalk.Operations.BizTalkManagementDb.PopulateServiceTypesHT()
at Microsoft.BizTalk.Operations.BizTalkManagementDb..ctor(String dbServer, String dbName)
at Microsoft.BizTalk.Operations.OperationsGroup..ctor(String ManagementDBServer, String ManagementDBName)
at Microsoft.BizTalk.Operations.BizTalkOperations..ctor(String mgmtDbServer, String mgmtDbName)
at Microsoft.Practices.ESB.BizTalkOperations.BizTalkQuery..ctor()

My Portal as well as the services are configured for integration security in the config file and in IIS. When I look at the exception object while debuging I notice the error indicates that "NT AUTHORITY\ANONYMOUS LOGON" does not have access to the database.

Which security setting could I be missing, as I think I have looked at them all numerous times now... and cannot figure out why an anonymous account is trying to access the messagebox db?
Comments: ** Comment from web user: tfabraham **

In the BizTalkOperations virtual directory properties, Directory Security, turn off Anonymous access and enable Windows Integrated security.

New Post: Is there a way to easy detect errors for SubmitRequestResponse call

ggallagher — Thu, 17 Jul 2008 17:16:01 GMT

When calling the twoway itinerary service "SubmitRequestResponse" is there a way to easy detect errors?

will the xml string always return the error contents starting with "<soap:Fault xmlns:soap=\"ht........"

I'm trying to serialize the return response with a web-service proxy of the web method response and it fails when errors messages are returned. I need a reliable way to detect ESB errors in the call.