Biztalk: Side-by-Side Versioning in different Applications -
i want deploy 2 applications, publish biztalk wcf service publishing wizard different endpoints. second application new version of first application. have changed assembly version , target namespaces in schema properties. applications , ports have different names.
the first application works before deploy second application.
then first 1 fails following message:
<s:envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"> <s:body> <s:fault> <faultcode xmlns:a="http://schemas.microsoft.com/net/2005/12/windowscommunicationfoundation/dispatcher">a:internalservicefault</faultcode> <faultstring xml:lang="de-de"><?xml version="1.0"?> <string>unexpected error occured.</string></faultstring> <detail> <exceptiondetail xmlns="http://schemas.datacontract.org/2004/07/system.servicemodel" xmlns:i="http://www.w3.org/2001/xmlschema-instance"> <helplink i:nil="true"/> <innerexception i:nil="true"/> <message><?xml version="1.0"?> <string>unexpected error occured.</string></message> <stacktrace>at microsoft.biztalk.adapter.wcf.runtime.biztalkserviceinstance.endoperation(iasyncresult result) @ asyncinvokeendendtwowaymethod(object , object[] , iasyncresult ) @ system.servicemodel.dispatcher.asyncmethodinvoker.invokeend(object instance, object[]& outputs, iasyncresult result) @ system.servicemodel.dispatcher.dispatchoperationruntime.invokeend(messagerpc& rpc) @ system.servicemodel.dispatcher.immutabledispatchruntime.processmessage7(messagerpc& rpc) @ system.servicemodel.dispatcher.messagerpc.process(boolean isoperationcontextset)</stacktrace> <type>microsoft.biztalk.adapter.wcf.runtime.biztalknackexception</type> </exceptiondetail> </detail> </s:fault> </s:body> </s:envelope>
the second application works fine. reason?
msdn recommends against doing this.
trying side side versioning in biztalk introduces whole world of complexity - versions hard coded bindings files, schema deployments have use different namespaces, , web services published through wizard have redone. there plethora of reasons why service might experiencing error, fixing 1 might uncover dozen more. if insist on going down road, start looking more closely @ eventlog entries rather soap responses - may give more of clue why isn't working expected.
it better give new application , artifacts new name , deploy them new application - if results in repeated code between two.
Comments
Post a Comment