BizTalk ESB Toolkit Forum

BizTalk Server Std or Ent requirement for ESB Toolkit 2.0

Wed, 25 Nov 2009 19:44:33 Z

Hi

Is the BizTalk Server 2009 Enterprise Edition an absolute requirement in order to deploy ESB Toolkit 2.0 or can it be deployed on Standard Edition?
If Enterprise Edition is required why has the requirements changed from ESB Guidance 1.0 which only requires BizTalk Server 2006 R2 any edition and BAM?

cheers
/Henrik Sandqvist

ESB Fault Handling Bug: Message Content Type Incorrect

Tue, 13 Oct 2009 11:59:05 Z

We have an ESB Orchestration service & we are trapping errors and creating a fault message as per the ESB documentation, i.e. XLANG like

Microsoft.Practices.ESB.ExceptionHandling.ExceptionMgmt.AddMessage(FaultMessage, InMessage);

However when you view the message within the ESB Portal the content type of our failed message is always showing as text/plain when in fact it should be text/xml. This prevents resubmission because the ESB Portal fault handler treats text/plain messages as flat file & so we can't resubmit to the WCF receive handler.

I have not been able to find anyway of telling the ESB toolkit the correct content type of the message - how is it determining this? As far as BizTalk is concerned our message is an XML message - if I view the messages in the tracking database I can clearly see our incoming message as text/xml. On the All.Exceptions port I see 2 messages, one being the ESB fault message & the other is our failing message which BizTalk shows as text/xml.

So is this an ESB bug?

The ESB fault handler for messaging only scenarios seems to work fine.

ESB Toolkit not Capturing WCF-WSHttp Service Fault?

Wed, 25 Nov 2009 14:39:34 Z

Hi,

I have a messaging itinerary that invokes a WCF-WSHttp service via a dynamic send/receive port. If I send the service an invalid message (e.g. a non-numeric value in an int element), then the WCF service generates a fault message (when it tries to deserialize the msg), but this fault is not being raised so my itinerary continues with this "Bad" message. I have tried this with "enabled routing for failed messages" set to true (which is how I believe it should be set) and to false on the port, but an error is not raised in either case.

However I see 2 errors in the the event log:

Event ID: 5796
The transport proxy method MoveToNextTransport() failed for adapter WCF-WSHttp: Reason: "Messaging engine has no record of delivering the message to the adapter. This could happen if MoveToNextTransport() is called multiple times for the same message by the adapter or if it is called for a message which was never delivered to the adapter by the messaging engine". Contact the adapter vendor.

Event ID: 5677
The Messaging Engine encountered an error while suspending one or more messages.

BizTalk carries on regardless and returns this message to the itinerary:
<Fault xmlns="http://www.w3.org/2003/05/soap-envelope">
<Code>
    <Value>Receiver</Value>
    <Subcode>
      <Value xmlns:a="http://schemas.microsoft.com/net/2005/12/windowscommunicationfoundation/dispatcher">a:InternalServiceFault</Value>
    </Subcode>
</Code>
<Reason>
    <Text xml:lang="en-GB">Error in deserializing body of request message for operation 'SendMyMessageRequest'.</Text>
</Reason>
<Detail>
    <ExceptionDetail xmlns="http://schemas.datacontract.org/2004/07/System.ServiceModel" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
etc

I am not sure if this is a BizTalk or ESB bug. Looking at the context properties for the returned message I see that "IsFault=true" so BizTalk does seem to know that this is a fault message, but the usual context properties for faults (prefixed withh "Failure") are missing.

I am using the standard ESB ItineraryForwarderSendReceive pipeline on the receive port. I tried ItineraryForwarderSendReceiveXml and had the same result.

You can't route the <Fault> message directly to the All.Exceptions port since the standard Failure context properties are missing & also there is no copy of the original message at this time, so there is no way you can resubmit the message.

Dynamic Itinerary From Orchestration?

Thu, 12 Nov 2009 16:35:24 Z

I have an orchestration that receives 1 message then sends out X different messages. I would like to assign new itineraries to these messages so that they "go their own way".

To do this I tried invoking a custom pipeline based on the ESB ItinerarySelectXml pipeline directly within the orchestration using:

xxx = Microsoft.XLANGs.Pipeline.XLANGPipelineManager.ExecuteReceivePipeline(typeof(mypipeline), myMessage);

The custom pipeline has a BRI resolver specified.

I then send the message, initialising a correlation, directly to the message box.

It almost works - the pipeline finds the itinerary using the BRI and advances it as required. However it is not processing the resolvers within the pipeline, thus the context properties BTS.OutboundTransportLocation & BTS.OutboundTransportType are missing & thus BizTalk complains that there are no subscribers for the message I am writing. The ESB context properties such as ItineraryHeader, ServiceName, etc, are present & correct.

I know the itinerary works since I use the same BRI rule in a generic receive location & the message is delivered correctly.

So I am a bit stuck with this approach - it looked like a good solution with minimal code needed within the orchestration to make its messages ESB aware. I can't see why the resolver is not being invoked - I turned on ESB tracing but this gave no clues.

Anyone else tried this?

Or used a different approach?

I know there is a scatter-gather sample which uses resolvers - that is how I am doing it a present but I would rather each message type have its own itinerary, since I need to do this to enable resubmission. Using the above approach has the benefit of not requiring dynamic ports within the orchestration, just a direct bound port, and the resolvers live with the itinerary for the outboud message, not the itinerary containing the orchestration.

One thing I might try is to change the new itinerary from this:

on-ramp > messaging_service: resolve route -> off-ramp extender > off-ramp

to this:
on-ramp > orchesation-service > off-ramp extender > resolve route > off-ramp

then in the orchestration, prior to writing the new message, invoking Itinerary.Advance() & Itinerary.Write to invoke the resolver.

Service level security

Fri, 20 Nov 2009 19:48:54 Z

How is it possible to achieve service level security when using ESB and a WCF general on-ramp? With service level security I mean that I somehow need to figure out what services an itinerary will call on its way and then do some check to see if those services are allowed to called by that user/group etc who is doing the call.

Love to hear how other have done similar security functionality?

http://www.richardhallgren.com

ESB.Portal 401.2 Access Denied Error

Thu, 19 Nov 2009 13:12:02 Z

I have built a 2 box server: BizTalk on one, SQL on another. This server doesn't have Visual Studio installed, so I copied the binaries of the ESB portal from the development server then ran the install script which creates the web sites. When I browse to http://localhost/esb.portal I get prompted for my credentials (I am full admin) and then the 401.2 Access denied error. The event log shows I have authenticated via Negotiate protocol.

I am running on Win2008 IIS7.0 & SQL 2008.

Dynamic Transformation using BRE in Biztalk ESB 2.0

Tue, 24 Nov 2009 08:27:59 Z

Hi,
We are facing issues while calling Map resolvers using BRE.

Here is what we did,
Created an Itienerary , where in itinerary service space set properties

Itinerary service Extender= Orchestration
Service name=Microsoft.Practices.ESB.Services.Transform
Add new resolver , BRE resolver in which i am calling the BRE policy

Policy , rule1: When conditon => 1=1 and Action=> Set Transform Transform Type = <Fully qualified name of Map> It is working fine.

But when Condition => Country=IN ( Country is some node from input schema)
and Action=> Set Transform Transform Type = <Fully qualified name of Map> ,

it is throwing an error

"Exception while attempting to determine map type: The map name could not be resolved"
I also put the Debuger in to "Microsoft.Practices.ESB.Services.Transform" (inbuild Orch from ESB) , and see that the input message is coming inside the Orchestration.

Any Help on this will be highly appreciated.

Thanks & Regards,
Shailesh Kawade

Unable to configure ESB Management Portal on vista

Thu, 19 Nov 2009 19:21:10 Z

Hi,
I am trying to configure the ESB Portal on a Vista (SP2) system but getting following error while executing the Management_Install.cmd file:
++++++++++++++++++++++++++++++++++
Welcome To GIL Powershell
--------------------------------------------
Get-GILFuns (List GIL Functions)
--------------------------------------------
The term '.\Management_Install.ps1' is not recognized as a cmdlet, function, operable program, or script file. Verify the term and try again.
At line:1 char:25
+ .\Management_Install.ps1 <<<< 1
+++++++++++++++++++++++++++++++++++
Any pointer to resolve the issue is highly appreicated.

Thanks,
KRN.

custom pipeline for resolving itinerary

Thu, 19 Nov 2009 11:46:31 Z

hi,

i need to develop a custom pipeline component and resolve/select a itinerary based on some rules in DB. pls help with some sample code if u have done some custom pipeline for choosing itineraries.

thanks

Using another version of Enterprise Library in a web application with ESB installed

Mon, 23 Nov 2009 14:07:32 Z

Is there any possibility in the web.config (or someplace else for that matter) to make your web application use another version of Enterprise Library when the ESB is installed and the machine.config is altered stating the use of the 4.1 version?

Regards
Pål

ESB 2.0 Toolkit Installation/Configuration

Mon, 21 Sep 2009 23:34:56 Z

Hi,
I was able to install the ESB 2.0 toolkit on Win Vista Enterprise with SP2 but unable to configure the Exception Web Services. I am getting the error "IIS Parameters Registry key is missing". So I wanted to know if it is possible to install/configure ESB 2.0 toolkit on Win Vista Enterprise at all or it's only possible on Windows Server 2008/2003 as per the system requirements recommend on MSDN?

Here are more details of my system
Operating System: Windows Vista Enterprise with SP2
IIS 7.0
.Net Framework 3.5 with SP1
Visual Studio 2008 Professional Edition with SP1
SQL Server 2008
BizTalk Server 2009 Developer Edition

Any pointers/guidlines are highly appreicated.

Thanks,
J.

Question about repair and resubmit

Fri, 18 Sep 2009 22:47:40 Z

I am trying to create a simple demo that shows benefits of repair and resubmit.
I am using BRI resolver to determine the itinerary name. Everything is working fine.
When I send a message to a file receive location based on the content of my message an itinerary name is determined.
I have enabled failed message routing. When I send an invalid message the BRE cannot determine which Itinerary to assign and it errors out.
I can see this message in the Management Portal. I can edit it. I want to resubmit it. When I look at "Select a receive location" drop down I see only one entry EAIProcess.Resubmit_HTTP. I tried resubmitting to it and I saw an error telling me that no subscribers are found.
What do I need to do next?
Do I need to add resubmit port dedicated to receiving the resubmitted messages?
The documentation says that "Select a receive location" list is dynamic. It also says that I need to create a WCF, SOAP or HTTP OnRamp. How does a receive port become a resubmit port.
Is there is need to register this resubmit port in the portal web.config file?
Since the resubmission does not resubmit the context properties I am assuming that I have to use an Itinerary Select Receive Pipeline in my resubmit port to resubmit the message.

Thanks for your response.

Integration Architect

ESBImportUtil Failing: Could not load file or assembly Microsoft.Practices.Modeling.Services

Thu, 19 Nov 2009 15:21:15 Z

I am trying to run the ESBImportutil on a server that does not have Visual Studio installed & I get the error:

Could not load file or assembly Microsoft.Practices.Modeling.Services.

I cannot find this dll anywhere in the ESB toolkit directory.

I checked on a development server & found these .DLLs under the "Tools\Itinerary Designer" directory. These dlls need to be in the core BIN directory of the ESB since they are needed by this utility!

Contacts (WSDL and schema) in a generic on-ramp/off-ramp?

Thu, 19 Nov 2009 11:30:21 Z

We're planning to start using the ESB Toolkit 2.0 as a way to create configurable service compositions. Basically we have a number of services in our backend system. We want to expose these using orchestrations, register these in ESB and use these as services.

We'll then create itinerates to dynamically route between these services. This will hopefully make our SOA implementation more agile and easier to develop and evolve.

My problem is however that different services will require different request data. There will also be a difference in the response we get back depending on the route setup by the itinerary.

How can I then make it easy for my client to make the call and handle the response. Do I then have to handcraft the WSDL to hand them? I guess I also need some sort of schema in BizTalk to send between the services and map different orchestrations response into one single response back to the client - right? How can I make this as dynamic as possible?

Thanks in advance!

http://www.richardhallgren.com

ESB Portal in a distributed scenario

Mon, 16 Nov 2009 23:57:59 Z

I am running ESB.Portal on a general web server and the respective services (ESB.Exception.Service, ESB.BAM.Service, ESB.UDDI.Service) on the BizTalk server. I am getting the following error below. I also checked the IIS log file where I am running ESB.Exception.Service. I am seeting 401.1 and 401.2 errors. I have already configured web.config for ESB.Portal to use domain accounts, updated URLs, etc.

Environment Info (All Servers)
-Windows Server 2008 R2
-IIS7
-BizTalk 2009
-ESB Toolkit 2 RTM
-SQL 2008

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Net.WebException: The operation has timed out

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[WebException: The operation has timed out]
   System.Net.HttpWebRequest.GetResponse() +1126
   System.ServiceModel.Channels.HttpChannelRequest.WaitForReply(TimeSpan timeout) +81

[TimeoutException: The HTTP request to 'http://<SNIPPED>/ESB.Exceptions.Service/ExceptionService.svc/GetUserSettings?username=DOMAIN\USER' has exceeded the allotted timeout of 00:00:59.9530000. The time allotted to this operation may have been a portion of a longer timeout.]
   System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason) +6663493
   System.ServiceModel.Channels.HttpChannelRequest.WaitForReply(TimeSpan timeout) +15272027
   System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout) +415

[TimeoutException: The request channel timed out while waiting for a reply after 00:00:59.9531244. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.]
   System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) +10256378
   System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) +539
   ESB.Exceptions.Service.Implementation.IExceptionService.GetUserSettings(String username) +0
   Microsoft.Practices.ESB.Portal.PortalHelper.LoadUserSettingsToSession(HttpContext context) +138
   System.Web.SessionState.SessionStateModule.RaiseOnStart(EventArgs e) +11154828
   System.Web.SessionState.SessionStateModule.CompleteAcquireState() +366
   System.Web.SessionState.SessionStateModule.BeginAcquireState(Object source, EventArgs e, AsyncCallback cb, Object extraData) +1281
   System.Web.AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +85
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +263

#Date: 2009-11-16 23:46:51
#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status time-taken
2009-11-16 23:46:51 10.50.95.25 GET /ESB.Exceptions.Service/ExceptionService.svc/GetUserSettings username=DOMAIN%5cUSERNAME 80 - 10.50.54.11 - 401 2 5 187
2009-11-16 23:47:31 10.50.95.25 GET /ESB.Exceptions.Service/ExceptionService.svc/GetUserSettings username=DOMAIN%5cUSERNAME 80 - 10.50.54.11 - 401 1 64 0

Server Error in '/ESB.Portal' Application.

The operation has timed out

Error while trying to configure Exception Web Services

Thu, 22 Oct 2009 10:31:27 Z

Hi,
I'm pretty new to ESB and I'm in process of setting up BizTalk ESB ToolKit 2.0 on my box. The configuration is Win Server 2003 EE with SP2, BizTalk 2009, SQL 2008, IIS 6.0. While trying to configure the Exception Web Services, I'm getting the error "The specified network name is no longer available. (Exception from HRESULT: 0x80070040)"

and the details logged in the EsbConfigurationTool.log is,

ESBConfigurationTool.exe Information: 0 : Executing script: databaseExistsSmoIntegrated.ps1 in view: ExceptionManagementDatabase with parameters: Key: serverInstance Value: blrkec77432d, Key: databaseName Value: EsbExceptionDb,
ESBConfigurationTool.exe Error: 0 : An error has occurred:
The specified network name is no longer available. (Exception from HRESULT: 0x80070040)
The specified network name is no longer available. (Exception from HRESULT: 0x80070040)
Stack Trace:
   at System.DirectoryServices.AccountManagement.CredentialValidator.BindSam(String target, String userName, String password)
   at System.DirectoryServices.AccountManagement.CredentialValidator.Validate(String userName, String password, ContextOptions connectionMethod)
   at System.DirectoryServices.AccountManagement.PrincipalContext.ValidateCredentials(String userName, String password, ContextOptions options)
   at EsbConfigurationTool.Panels.PanelBase.ValidateCredential(NetworkCredential credentials, String groupName)

ESBConfigurationTool.exe Information: 0 : The specified network name is no longer available. (Exception from HRESULT: 0x80070040)
ESBConfigurationTool.exe Error: 0 : An error has occurred:
The specified network name is no longer available. (Exception from HRESULT: 0x80070040)

ESBConfigurationTool.exe Information: 0 : The configuration source found was: ESB File Configuration Source
ESBConfigurationTool.exe Information: 0 : D:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\esb.config
ESBConfigurationTool.exe Information: 0 : The configuration settings were saved to file: D:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\Bin\ESBConfigurationTool.exe.Config
ESBConfigurationTool.exe Information: 0 : The configuration settings were saved to file: c:\SYSROOT\Microsoft.NET\Framework\v2.0.50727\Config\machine.config
ESBConfigurationTool.exe Information: 0 : The machine configuration file for x64 was not found. Path: c:\SYSROOT\Microsoft.NET\Framework64\v2.0.50727\Config\machine.config
ESBConfigurationTool.exe Information: 0 : The configuration changes were persited to 'ESB File Configuration Source'' from view 'Configuration

I'm using a local user account who is a member of the Administrators and BizTalk Isolated Host Users groups. Also, BizTalk 2009 has been configured with this local user account only.

Seems to me like a credential issue but I'm not able to figure out why. I would appreciate any guidance on this issue. Thanks in advance.

Regards,
Pandit.

Error trying to configure Exception Web Services: The server could not be contacted

Thu, 19 Nov 2009 11:56:49 Z

I am using domain accounts and domain groups. I specify these accounts in the ESB configuration tool but get this error:

The server could not be contacted.
The LDAP server is unavailable.
Stack Trace:
   at System.DirectoryServices.AccountManagement.PrincipalContext.ReadServerConfig(String serverName, ServerProperties& properties)
   at System.DirectoryServices.AccountManagement.PrincipalContext.DoServerVerifyAndPropRetrieval()
   at System.DirectoryServices.AccountManagement.PrincipalContext..ctor(ContextType contextType, String name, String container, ContextOptions options, String userName, String password)
   at System.DirectoryServices.AccountManagement.PrincipalContext..ctor(ContextType contextType, String name)
   at EsbConfigurationTool.Panels.PanelBase.ValidateCredential(NetworkCredential credentials, String groupName)
   at EsbConfigurationTool.Panels.WebServicesException.Save()
   at EsbConfigurationTool.EsbConfiguration.OnTsBtnSaveClick(Object sender, EventArgs e)

I saw entries (http://social.msdn.microsoft.com/Forums/en/biztalkesb/thread/13b3f024-2610-4810-8f43-7effbaca7861 & http://social.msdn.microsoft.com/Forums/en/biztalkesb/thread/e3e0d4c4-27f2-4348-9b80-712495aeaf15) that said AD needs to be at Windows 2003 level, which it is. I can't proceed with configuration due to this error in the configurator.

For the user account I am specifying the BizTalk service account (myDomain\biztalksvc) and the BizTalk isolated host group (myDomain\TestBizTalkIsolatedHostGroup).

The only way I can proceed is to temporarily set up a local account & local group & then manually change the application pools to use the BizTalk service account. However I am not sure what configuration is performed using the "Isolated Host" & how to manually replicate this configuration.

how to find the map in the Exception Handling project

Wed, 11 Nov 2009 13:01:53 Z

I am trying to study the Exception Handling project:
C:\Projects\Microsoft.Practices.ESB\Source\Samples\Exception Handling

First of all, the project can be compiled without error. However, in the EAIProcess.odx -> Build Denied Message (Construct Message)
When I try to view the map : by double click the "Set Denied Req..: shape, it prompts me the "Map file not found, GlobalBank.ESB.ExceptionHandling.Schemas.MapToReqDenied" Error. the map could not be resolved.

I tried to to manually find/add the existing map in the referece assembly, I could not see the refereced assembly in the "select artifact type" dialog box.

I varified the reference is pointing to the ESB.ExceptionHandling.Schemas project.

It is seems very odd to me, I can compile the solution, but I can't view (resolve) the map in the solution.

Any thoughts would be greately appriciated.

ESB Toolkit and Ordered Delivery

Wed, 11 Nov 2009 21:14:25 Z

Hi:

Many of of Healthcare customers and financial customers required Ordered Delivery. This can be done in BizTalk but it is cumbersome to implement it.
What are your thoughts about implementing Ordered Delivery with ESB Toolkit? Will it work? Are there issues we should consider before diving into this.

Thanks

Integration Architect

ESB Toolkit 2.0 and Queues

Mon, 16 Nov 2009 21:59:10 Z

Currently in our environment most of the application interfaces are very tigtly coupled and we are entertaining the idea of migrating them to ESB solution. We are working on implementing scatter-gather pattern with toolkit and I was wondering if we can use MSMQ as a receive pipeling for ESB?

Promoting message type in ItinerarySelectReceivePassthrough pipeline

Mon, 16 Nov 2009 00:33:37 Z

I am using Business rule to attach itinerary based on message type. How to promote this message type to the message context. I am using ItinerarySelectReceivePassthrough. Any other way without writing custom pipeline.

Resolver.Itinerary

BRI:\\policy=ResolveItineraryBasedOnMsgType;useMsg=true;recognizeMessageFormat=true;

Exception:

There was a failure executing the receive pipeline: "Microsoft.Practices.ESB.Itinerary.Pipelines.ItinerarySelectReceivePasshrough, Microsoft.Practices.ESB.Itinerary.Pipelines, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "ESB Itinerary Selector" Receive Port: "WcfReceivePort_BizTalkWcfService/ESBServiceWCF" URI: "/BizTalkWcfService/ESBServiceWCF.svc" Reason: Procedure or function 'Itinerary_getitinerary' expects parameter '@name', which was not supplied.

Appreciate your help

Thanks,

Ram.

ManagementPortal Install Script Fails (x86) (ESB 2.0)

Mon, 28 Sep 2009 08:09:21 Z

Hi Folks,

I am trying to use the ManagementPortal Install Script and its failing with the below error.

The term 'C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.com'
is not recognized as a cmdlet, function, operable program, or script file. Veri
fy the term and try again.
At D:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\Install
\Scripts\Management_Install.ps1:19 char:3
+ &$ <<<< env:VS\devenv.com "$solutionPath\Samples\Management Portal\ESB.Al
ertService\ESB.AlertService.sln" /clean $buildType
The term 'C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.com'
is not recognized as a cmdlet, function, operable program, or script file. Veri
fy the term and try again.

Has anyone got any ideas how to solve this?

Note I am following this install guide: http://www.biztalkgurus.com/blogs/biztalksyn/archive/2009/06/10/getting-up-and-running-with-biztalk-esb-toolkit-2-0.aspx

Windows Server 2003
VS 2008 SP1
SQL Server 2008
Biztalk 2009
IIS 6.0

Cheers

UDDI configuration with Microsoft.Practices.ESB.UDDIPublisher keeps failing to run correctly

Mon, 26 Oct 2009 14:58:52 Z

When I try to run the Publisher application for the registration of the ESB webservices I keep getting an error. I searched all of internet and found some hints like SSL is checked in the UDDI server (Not the case.). Also looked in the Service Trace Viewer and found that an exception is thrown when running the publish application. (Details below). The error is :
Error 285012: An unexpected error occurred retrieving the Business information in Uddi for Business name, 'Microsoft.Practices.ESB.UDDI3.UddiClientException: Error 285008: An unexpected error occurred retrieving all the Uddi Business Information for the Business name 'System.ServiceModel.FaultException

Server stack trace:
   at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Microsoft.Practices.ESB.UDDI3.UDDI_Inquiry_PortType.find_business(find_businessRequest request)
   at Microsoft.Practices.ESB.UDDI3.UDDI_Inquiry_PortTypeClient.Microsoft.Practices.ESB.UDDI3.UDDI_Inquiry_PortType.find_business(find_businessRequest request)
   at Microsoft.Practices.ESB.UDDI3.UddiClient.GetBusinessByName(String businessName)'.
   at Microsoft.Practices.ESB.UDDI3.UddiClient.GetBusinessByName(String businessName)
   at Microsoft.Practices.ESB.UDDI3.UddiClient.GetMyBusinessByName(String businessName)'.

Source: Microsoft.Practices.ESB.UDDI3.UddiClient

Method: System.String SaveBusiness(System.String, System.String)

Error Source: Microsoft.Practices.ESB.UDDI3

Error TargetSite: Microsoft.Practices.ESB.UDDI3.businessInfo GetMyBusinessByName(System.String)

Error StackTrace:    at Microsoft.Practices.ESB.UDDI3.UddiClient.GetMyBusinessByName(String businessName)
   at Microsoft.Practices.ESB.UDDI3.UddiClient.SaveBusiness(String businessName, String description)

XML Of the trace log for the application.
<E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent">
<System xmlns="http://schemas.microsoft.com/2004/06/windows/eventlog/system">
<EventID>131075</EventID>
<Type>3</Type>
<SubType Name="Warning">0</SubType>
<Level>4</Level>
<TimeCreated SystemTime="2009-10-26T14:20:41.1395953Z" />
<Source Name="System.ServiceModel" />
<Correlation ActivityID="{00000000-0000-0000-0000-000000000000}" />
<Execution ProcessName="Microsoft.Practices.ESB.UDDIPublisher" ProcessID="2508" ThreadID="1" />
<Channel />
<Computer>WIN-PMEJJ9LORO3</Computer>
</System>
<ApplicationData>
<TraceData>
<DataItem>
<TraceRecord xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord" Severity="Warning">
<TraceIdentifier>http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.ThrowingException.aspx</TraceIdentifier>
<Description>Throwing an exception.</Description>
<AppDomain>Microsoft.Practices.ESB.UDDIPublisher.exe</AppDomain>
<Exception>
<ExceptionType>System.ServiceModel.FaultException, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
<Message></Message>
<StackTrace>
at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.Practices.ESB.UDDI3.UDDI_Security_PortType.get_authToken(get_authTokenRequest request)
at Microsoft.Practices.ESB.UDDI3.UDDI_Security_PortTypeClient.Microsoft.Practices.ESB.UDDI3.UDDI_Security_PortType.get_authToken(get_authTokenRequest request)
at Microsoft.Practices.ESB.UDDI3.UddiClient.SetUddiAuthentication(String username, String password, String url, BasicHttpSecurityMode securityMode, HttpClientCredentialType credential)
at Microsoft.Practices.ESB.UDDIPublisher.Publish.Main(String[] args)
</StackTrace>
<ExceptionString>System.ServiceModel.FaultException</ExceptionString>
</Exception>
</TraceRecord>
</DataItem>
</TraceData>
</ApplicationData>
</E2ETraceEvent>

The system consists of a 2008 Server with UDDI 3.0 SQL 2008.
Anybody recognizes this error or has a solution ?

How To Pass Large Messages through WCF Generic onRamp

Wed, 11 Nov 2009 11:06:22 Z

Hi,

In My Organization I have to deal with large messages(10-30MB)

how can i receive these messages through the generic onramp?(MTOM encoding??)

TNX,

Routing failure (ItinerarySelectReceivePassthrough->OnRamp->Orchestration)

Sun, 15 Nov 2009 00:23:01 Z

I deployed schema (XLANGS.BaseTypes.Any) as web service and submitted message to the ESB through web service.

Here is the message flow:

- ItinerarySelectReceivePassthrough (Configured to BRE which will attach itinerary)

- Message received on OnRamp

- Sends to the Orchestration

Here is the issue, Orchestration is not picking up the message, I did setup filter expressions for servicename, servicetype and servicestate.

Here is the exception:

A message received by adapter "SOAP" on receive location "WebService_ESBServiceDev1/ESBServiceDev1" with URI "/ESBServiceDev1/ESBServiceDev1.asmx" is suspended.

Error details: The published message could not be routed because no subscribers were found. This error occurs if the subscribing orchestration or send port has not been enlisted, or if some of the message properties necessary for subscription evaluation have not been promoted. Please use the Biztalk Administration console to troubleshoot this failure.

MessageId: {E61211E8-3929-4299-8B76-996E41E1581C}

InstanceID: {CF97CF82-8400-403D-BEDB-CA7EBB3F66BE}

However if i set messaging extender instead of orchestration and also static resolver message is processing but this is not what i needed.

Any suggestions greatly appreciated.

Thanks,

Ram.

Problems with ESB Fault Handling

Thu, 05 Nov 2009 10:50:01 Z

I am testing out the ESB fault handling process and I am encountering some very basic issues. I took a simple scenario - an itinerary that receives a message via WCF & then routes via a dynamic ESB send port using WCF transport, the routing information being specified via a business rule. In the receiving WCF application I deliberately throw an exception. These are the issues I see:

a) Unable to deteremine error reason due to error message truncation
In the the ESB portal I find the error but the fault description & exception is truncated to 4096 characters. WCF generates very long exception messages so all I see is a message beginning "System.ServiceModel.FaultException ....". The ESB Portal doesn't even try to display the full 4096 characters, in fact I don't quite understand what it is displaying - it certainly does not look the same as the fault exception message found in the EsbExceptionDb. In the database I see:

System.ServiceModel.FaultException: <s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing" xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"><s:Header><a:Action s:mustUnderstand="1" u:Id="_2">http://schemas.microsoft.com/net/2005/12/windowscommunicationfoundation/dispatcher/fault</a:Action> ... etc

Whilst the ESB portal shows:

System.ServiceModel.FaultException: http://schemas.microsoft.com/net/2005/12/windowscommunicationfoundation/dispatcher/faulturn:uuid:021231b7-c5d1-441c-be45-b714fe8cf8182009-11-05T09:57:25.755Z2009-11-05T10:02:25.755Z024HALTMLJLHbupEDkpp5HwzA==WWZrr07Cx529SgpdjMdjhQ

which would be totally useless to any operator trying to determine the error. What is the ESB Portal doing? Is it having a problem because the full error is not being logged?

Buried in the WCF fault message is the actual error in the "<Body><Fault>..." - the ESB should be picking that up since inside it is the actual error message from the faulting target application.

b) Incorrect Service Name and Fault Generator
I have an itinerary with an orchestration service. The orchestration is sending a message to WCF using a dynamic port. If the receiving WCF service faults the ESB logs the error (with all the issues noted above) but "Service Name" and "Fault Generator" are being set to values from earlier in the itinerary and not the current service and port.

c) Message Retries
On a static send or send/receive port BizTalk normally defaults to performing 3 retries before failing the message, but with a dynamic send or send/receive an error is being generated immediately. How do we specify message retry and retry interval for ESB dynamic ports?

d) Message Content Type Set to "text/plain"
The ESB is capturing the failed message but it is setting the content type to "text/plain" within the EsbExceptionDb, yet BizTalk clearly shows these messages as being text/xml. The ESB Portal then subsequently does not allow you to resubmit the message since it will only submit text/xml messages back to the WCF OnRamp.

The ESB Fault handling is one of the things Microsoft says is a significant bonus of the ESB toolkit, but this catalogue of problems with the error handling starts to make it rather unusable.

Transport Retry Options in a BRE Rule

Thu, 05 Nov 2009 18:59:33 Z

Hi,

does anyone know how you specify the transport retry and retry interval options within a BRE rule for a dynamic send or send/receive port?

Problem with creating a custom resolver

Wed, 11 Nov 2009 19:14:15 Z

I am trying to create a custom resolver.
I have followed the instructions in the Help file.

To create a custom resolver

1. Create an assembly with a class that implements the IResolveProvider interface and contains a Resolve method that returns resolver facts as an instance of the Dictionary class.
2. Register the resolver by adding it to the Esb.config configuration file using a <resolver> element that contains the root moniker as the name attribute and the fully qualified assembly name as the type attribute.
3. Added the assembly to GAC

When I try to add a new Resolver I don't see the newly added resolver. I have reviewed my class that implements IResolverProvider and the esb.config settings. I don't see anything wrong but I cannot get the resolver implementation list to show me my new resolver. There are no errors logged so it is hard to debug.

I was wondering if the instructions are complete or if a step is missing. If you have written a custom resolver please share any tips to fix this issue.

Thank

Integration Architect

Calling WebService From Itinerary

Fri, 30 Oct 2009 14:14:23 Z

Hi,

I trying to call Web Service from Itinerary. The Web Service is invoked and I am also getting the response from the Web Service if it is without any parameters.
But when I am calling Web Method with Parameter(which is of XMLDocument type, to receive the Itinerary Message) the Parameter value is always null, the Itinerary Message is not getting passed to the Web Method.

Can someone please suggest how to proceed.

Thanks.

esb.portal -> faults page

Fri, 18 Sep 2009 13:06:22 Z

hi,

got strange issue,
portal up and running, exception service working...
2 projects set to use esb exception handling...

until now everything looks fine...

had around 1000 - 2000 errors in db, everything works (portal, errorhandling)

i've started load testing the esb toolkit (exception handling)

with around 3 - 4 k of errors... suddenly page responsible for showing faults throws such exception:
{"The HTTP request is unauthorized with client authentication scheme 'Negotiate'. The authentication header received from the server was 'Negotiate,NTLM'."}

the strange thing is that it worked ... nothing changed in configuration....
i've spent 1/2 day looking in what to ____ is going on... then i've came to wild idea... delete rows from db...
now db has 0 records... fault page shows ok,
added few errors shows ok,

is there somekind of limit that im not aware of ?
did any of you got similar issues ?

WCF-Adapter + Linked Server + ESB

Thu, 05 Nov 2009 19:55:28 Z

I'm trying to connect all those three things together.

System is Windows Server 2008, Biztalk 2009, ESB, MSSQL 2008.

I have some data in Oracle 10G database, I'm trying to access this data. The scenario I try is the following. I have a View in MSSQL, view selects the data from a Linked oracle server. I consume that data in WCF-custom adapter in Off-Ramp extender using sqlBinding.

Every piece of the puzzle works great separately, but when I try get the data from itinerary, over WCF-Custom (sqlBinding), linked server to Oracle 10g I get the following message:

System.Data.SqlClient.SqlException: The operation could not be performed because OLE DB provider "OraOLEDB.Oracle" for linked server "RTW" was unable to begin a distributed transaction.

The Distributed Transaction Coordinator is up and running, and accepring remote clients, allows inbound and outbound, does not require any authentication has XA Transactions enabled and works as a NetworkService.

What is that I should configure, enable/disable or read to get what is that needed to get this thing working.

I appritiate any help. Thanks

BRI Rule Problem with Content Based Routing

Thu, 05 Nov 2009 16:21:58 Z

Hi,

I am using the ESB generic WCF receive port and I am using a "generic" business rule to assign the correct itinerary. I am having a problem writing a business rule that does this:

IF Context Message Type = "some-doc-spec-1"
AND
    (doc-content = 'X' OR doc-content = 'Y')
OR Context Message Type = "some-doc-spec-2"
OR Context Message Type = "some-doc-spec-3"
THEN
  Set Itinerary Name = zzzz

Using the above rule, messages of context type "some-doc-spec-1" get selected if they have the correct content, but never for the "OR" conditions. The BRE rule is actually written as:

OR
|_ AND
|    |_   Context Message Type = "some-doc-spec-1"
|    |_   OR
|           |_ doc-content = 'X'
|          |_ doc-content = 'Y'
|_ Context Message Type = "some-doc-spec-2"
|_  Context Message Type = "some-doc-spec-3"

If I split this rule into 2 rules by putting the outer OR's into another rule:

IF Context Message Type = "some-doc-spec-1"
AND
    (doc-content = 'X' OR doc-content = 'Y')
THEN
  Set Itinerary Name = zzzz

plus:

IF Context Message Type = "some-doc-spec-2"
OR Context Message Type = "some-doc-spec-3"
THEN
  Set Itinerary Name = zzzz

then itineraries are set for all document types. But this is not ideal - I would rather have one rule per itinerary so I can see all the logic in one place.

Thus it seems you can't have a rule that mixes CONTENT based routing with CONTEXT based routing for different

Does anyone know how to invoke "Test Policy" to test a BRI rule? I believe you need fact creators for the ESB facts, but I don't know where they are.

MSMQ Adapter Provider for ESB Toolkit 2.0

Tue, 10 Nov 2009 22:27:47 Z

I just wrote a detailed blog post about how you can connect to MSMQ from ESB Toolkit.
One of the option is to use a custom adapter provider for MSMQ.
You can look at this post and code samples at

http://rajsinghblog.wordpress.com/2009/11/10/sending-messages-from-esb-toolkit-to-msmq-2/

Cheers

Integration Architect

Dynamic Transformation using ESB

Mon, 09 Nov 2009 09:08:18 Z

Hi,

I have the following requirement:

I have an EDI message coming into BizTalk. I have to select a particular map depending on the MessageType and the PartyName that are present as context properties.

For this I have a SQL table that has entries for PartyName, MessageType and Map Name.

I have created an itinerary that has the following components: an On-Ramp to receive the EDI message->An Itinerary Service(Messaging Extender) that has a BRE Resolver->An off-Ramp Extender that specifies the output location->An off-Ramp that specifies the send port.

The Messaging Extender has the Service Name set to Microsoft.Practices.ESB.Transform.Service.

The BRE resolver has the UseMsg set to True. This calls a business rule that gets the map name depending on the PartyName from the database.
I am getting a routing error saying there is no subscribing orchestration or Send Port. Also, the suspended message has not been transformed.

The Send Port is a dynamic one-way send port with ItineraryPassThroughPipeline and has three filters
Microsoft.Practices.ESB.Itinerary.Schemas.ServiceName
Microsoft.Practices.ESB.Itinerary.Schemas.ServiceState
Microsoft.Practices.ESB.Itinerary.Schemas.ServiceType

Could you please guide me as to how to apply the transformation dynamically depending on the context property "PartyName" and "MessageType"?

Thanks,

Sumana.

Unofficial ESB Toolkit Survey

Wed, 28 Oct 2009 20:34:34 Z

Hello all,

I have some survey-style questions for anyone that feels like answering them. This is to satisfy my personal curiosity, and is not an official survey in anyway, nor will it likely have any effect on anything (though it might affect how I talk about and/or explain ESB). Hopefully we will be able to learn from each other though, in seeing how each of us is using (or not using) the Toolkit.

1.) What types of scenarios have you found that the ESB Toolkit (not just the exception handling stuff) is helpful? In which types of scenarios has using it increased productivity? Be as specific as you can.

2.) What types of scenarios have you found that just using regular BizTalk stuff (pipelines / orchestrations) without ESB has been more helpful? Be as specific as you can.

3.) What types of scenarios have you tried using ESB and then reverted to using regular BizTalk stuff? Be as specific as you can.

4.) What would you say is the biggest pain point in the Toolkit? How do you deal with it?

5.) What pain point (for you personally) does the Tookit address, if any?

BizTalk ESB Toolkit 2.0 Training: http://quicklearn.com/redir/?r=esbtraining

SQL Standard Edition OK for ESB Toolkit?

Mon, 02 Nov 2009 11:03:46 Z

Hi all
is there anything in the ESB toolkit that requires SQL Enterprise Edition rather than standard edition?
The two-node cluster limit it ok but is there anything lurking in the restrictions to Analysis Services that would cause a problem?

thanks

Codeplex ESB Extensions

Fri, 06 Nov 2009 15:20:50 Z

Hi,

not sure if this has been posted before on this forum, but I noticed that some ESB extensions have been published that overcome some of the limitations of the ESB toolkit and provide extra functionality.

See here: http://esbextensions.codeplex.com/

ESB Management Console - cant get date ranges working for faults!!!

Mon, 02 Nov 2009 04:52:41 Z

Hi All,
I am actually using the ESB Guidance framework for 2006/r2 but I have created and can view faults succesfully in the Console. However it only works if I select the "all" date range. If I select "hour" for example - even though the fault was recorded in the last five minutes it doesnt display. Only if I select "all" can I see it.

I can clearly see the datetime of the fault as occuring within the hour.

Any ideas would be appreciated

Thanks

Biztalk Developer

Can't call itinerary without restarting the application

Sun, 01 Nov 2009 02:20:17 Z

i have a problem with calling itinerary everytime i start my server. i have only one server and since it doesnt have much capacity, i need to turn off the biztalk server(running on vmware) when i am not using it. when i start the computer and try to send itinerary request using test client, i get the error, request timed out. there are no errors in the event log. all the applications microsoft.practices.esb, globalbank.esb and my application consisting of orchestrations are started. i don't know what's wrong.

but when i run the script setup_bin.cmd for installing the itinerary onramp sampe ( which restarts globalbank.esb and other applications), it works instantly.

i am getting paranoid. everytime i start the server, i need to re-install itinerary onramp sample for all those things to work. is there anything i am doing wrong?

Error: The itinerary header could not be found

Tue, 27 Oct 2009 09:59:46 Z

I receive the next message: "The itinerary header could not be found". I have 2 scenarios. In the first scenario I'm using the ItinerarySelectReceivePassthrough pipeline. In this scenario I'm calling a webservice via the Itinerary and it just works fine. In the second scenario I've created a custom pipeline with the same components (ESB Itinerary Selector and ESB Dispatcher) as in the ItinerarySelectReceivePassthrough, but with an additional component: BTAHL7 2.X Disassembler (second stage). The ResolverConnectionString is entered correctly. I also see that the ItineraryHeader is on the context from the message. But it still fails in the ESB Dispatcher (note: setting the Enabled to false is not an option).

The complete message I receive: 'There was a failure executing the receive pipeline: "mycompany.myproduct.BTAHL7PipelinesESB.ItinerarySelectReceivePassthroughHL7X, mycompany.myproduct.BTAHL7PipelinesESB, Version=1.0.0.0, Culture=neutral, PublicKeyToken=91608530323964c9" Source: "ESB Dispatcher" Receive Port: "ReceiveADTMessage" URI: "127.0.0.1:14123" Reason: The itinerary header could not be found. '

Anyone a suggestion? Or a clue?