Bridge Deployment Error

Question

Hi all,

I'm trying to get started using Service Bus EAI and EDI but I'm having some trouble deploying a One-Way Bridge.  The error that I get is:

<Error><Code>400</Code><Detail>Pipeline configuration is invalid. Validation of configuration failed with error Object reference not set to an instance of an object

The schema's and mappings all deploy successfully.  Has anyone encountered this problem before?  If so, could you please explain to me what it means?

Thanks

Hin

Answer 1

Hi Hin

Could you please share the pipeline configuration file? If you look under your bin\Debug folder, there should be a file with the name <bridge name>.Pipeline.atom.

Thanks
Neha

Answer 2

Hi Neha,

Here are the contents of the pipeline configuration file:

<?xml version="1.0" encoding="utf-8"?><entry xmlns="http://www.w3.org/2005/Atom"><id>uuid:9bc6d00c-4dcd-40e7-9645-258c09384a57;id=1</id><title type="text">XmlOneWayBridge1</title><updated>2012-04-10T03:44:41Z</updated><link rel="self" href="XmlOneWayBridge1" /><content type="application/xml"><Pipeline xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/integration"><ArtifactReferences xmlns:d3p1="http://schemas.datacontract.org/2004/07/Microsoft.ApplicationServer.Integration.Services.Repository" /><Configuration><configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0"><configSections>
                                                                               <sectionGroup name="pipelines" type="Microsoft.ApplicationServer.Integration.Pipeline.Configuration.PipelineSectionGroup, Microsoft.ApplicationServer.Integration.Pipeline.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
                                                                                   <section name="extensions" type="Microsoft.ApplicationServer.Integration.Pipeline.Configuration.ExtensionsSection, Microsoft.ApplicationServer.Integration.Pipeline.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
                                                                                   <section name="lookupProviders" type="Microsoft.ApplicationServer.Integration.Pipeline.Configuration.LookupProvidersSection, Microsoft.ApplicationServer.Integration.Pipeline.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
                                                                                   <section name="pipelines" type="Microsoft.ApplicationServer.Integration.Pipeline.Configuration.PipelineSection, Microsoft.ApplicationServer.Integration.Pipeline.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
                                                                               </sectionGroup>
                                                                           </configSections>
                                                                           <system.serviceModel>
  <client>
    <endpoint address="https://hintse.servicebus.appfabriclabs.com/Orders" binding="netMessagingBinding" contract="System.ServiceModel.Routing.ISimplexDatagramRouter" name="Orders" />
  </client>
  <extensions>
    <bindingExtensions>
      <add name="netMessagingBinding" type="Microsoft.ServiceBus.Messaging.Configuration.NetMessagingBindingCollectionElement, Microsoft.ServiceBus, Version=0.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
    </bindingExtensions>
  </extensions>
</system.serviceModel><pipelines>
        <extensions>
            <pipeline>
                <add name="oneWayXmlPipeline" type="Microsoft.ApplicationServer.Integration.Pipeline.Activities.Configuration.OneWayXmlVETERPiplineCollectionElement, Microsoft.ApplicationServer.Integration.Pipeline.Activities.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
            </pipeline>
            <lookupProviders>
                <add name="SqlTable" type="Microsoft.ApplicationServer.Integration.Pipeline.Configuration.SqlTableLookupCollectionElement, Microsoft.ApplicationServer.Integration.Pipeline.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
            </lookupProviders>
        </extensions>
        <pipelines>
            <oneWayXmlPipeline>
                <pipeline name="name">
                    <artifacts>
                        <artifact name="SourceSchema.xsd" type="XmlSchemaDefinition" path="/SourceSchema.xsd" />
                        <artifact name="OrderTransform.trfm" type="TransformDefinition" path="/OrderTransform.trfm" />
                    </artifacts>
                    <validator enabled="true">
                        <xmlValidator>
                            <messageTypes>
                                <add messageType="http://Bridge.SourceSchema#Root" schemaPath="/SourceSchema.xsd" />
                            </messageTypes>
                        </xmlValidator>
                    </validator>
                    <requestMessageExtractor enabled="true" />
                    <requestMessageTransform enabled="true">
                        <xmlTransform>
                            <transforms>
                                <add predicate="X_PIPELINE_MESSAGETYPE = 'http://Bridge.SourceSchema#Root'" transformPath="/OrderTransform.trfm" />
                            </transforms>
                        </xmlTransform>
                    </requestMessageTransform>
                    <transformedMessageExtractor enabled="true" />
                    <route enabled="true">
                        <Route>
                            <routeTable xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                                <entries>
                                    <staticRouteEntry>
                                        <sqlFilterCondition sqlExpression="1=1" />
                                        <topicDestination name="Orders1" contractType="OneWay" path="Orders" messagingProtocol="SOAP">
                                            <protocolProperties />
                                        </topicDestination>
                                    </staticRouteEntry>
                                </entries>
                            </routeTable>
                        </Route>
                    </route>
                </pipeline>
            </oneWayXmlPipeline>
        </pipelines>
    </pipelines>
</configuration></Configuration><PipelineTemplateName>OneWayXmlPipeline</PipelineTemplateName></Pipeline></content></entry>

Thanks!

Hin

Answer 3

From the looks of the pipeline configuration, it seems that you are using an earlier version of the SDK. Can you please make sure that you have the latest version installed?

You can download the SDK from here: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17691

After installing, if you check under Control Panel -> Programs -> Programs and Features, you should see an entry for "Windows Azure ServiceBus EAI & EDI Labs SDK - April 2010" with version "2.0.846.0".

Answer 4

I upgraded the SDK and the error I get now is:

XmlOneWayBridge1 deployment failed.
InternalServerError

Thanks

Answer 5

Hi Hin

Did the schema and map get uploaded successfully after updating the SDK? Also, could you please retry and see if you're still seeing the error?

Regards
Neha

Answer 6

Hi Neha,

The schema and map got uploaded successfully.  However, even before I updated the SDK, they were uploaded successfully too.  The error I get from deploying is still:

XmlOneWayBridge1 deployment failed.
InternalServerError

I also tried creating a new EAI project (in case the new version of the new SDK generates the initial project files differently) but I still get the above error.

Thanks

Hin

Answer 7

Hello Hin,

Could you create a new EAI project, configure the Bridge as desired and then try deploying again.

If still deployment fails, please post the .Pipeline.atom file (as you did last time) and we will take a look.

Thanks,

Arpit

Answer 8

Hi Arpit,

I just redeployed the same EAI project I was having trouble with (without doing anything to it) just then and it somehow worked.  Do you have any idea why this happened?

Thanks Neha and Arpit

Hin