Thursday, September 13, 2012 9:32 PM
Orchestration 1: Queries SQL- WCF Custom port-SQL Binding,
Gets the a message , debatches message with xpath. Resulting messages gets stored in BizTalk with Direct Binding.
Orchestration2: Picks up the message with Direct Binding. Expression shape immediately after receive shape has distingished field values aassigned to Orchestration varibales.
This is where (expression shape), orchestration throws error on Production Box. We didnt get any error on Development box or QA Box. Error Deatils is at bottam of this post.
One of the reason mentioned in many of the forum is its beacuse of Null value in distinguished filed.
Ok, that was the case with my message, so we put in some dummy integer in a element (which is promoted as distinguished field and previously getting null values) . But Orcestration throwing same error (ONLY on Production BOX ).
During Initial Deployment: We added only only Schemas, MAP and Orchestration artifacts to Application using Application > Add Resouces > dll of artifacts mentioned above > Overwrites and GAC selected.
Second Deployment: Deleted complete Applicationd, removed dlls from GAC and Application > Import MSI File
ONLY DIFFERENCE BETWEEN QA AND PROD IS : cumulative update package 5 for biztalk is not applied on Production box
Uncaught exception (see the 'inner exception' below) has suspended an instance of service 'BTNextGen.BizTalk.AccountProfiles.Orchestration.ImportAccountProfiles(4cc3f151-e7fb-7023-bfaa-140b8db7de30)'.
The service instance will remain suspended until administratively resumed or terminated.
If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception.
Shape name: get legacy details
Exception thrown from: segment 1, progress 24
Exception type: RuntimeInternalErrorException
Target Site: Microsoft.XLANGs.RuntimeTypes.DistinguishedFieldDefinition GetDFDef(System.String)
The following is a stack trace that identifies the location where the exception occured
at Microsoft.XLANGs.Core.Part.GetDFDef(String dottedPath)
at Microsoft.XLANGs.Core.XSDPart.GetDistinguishedField(String dottedPath)
Thursday, September 13, 2012 9:38 PMDid you bounce the biztalk hosts after second deployment? This will ensure that all the references to the old artifacts are flushed out.
Friday, September 14, 2012 6:44 AM
If you get this behavior on your Prod and not on your other environments, then there must be a difference.
As mentioned CU 5 is not applied on Prod, that could be the cause. Are you sure that this is the only difference? Maybe there is also a difference in security updates or hotfixes?
If you want to be certain about this, you can setup a Dev/QA box with the same configuration as Prod.
In any case it is a best practice to have your Dev/QA/Prod enviroment setup exactly the same, to prevent issues like this on Prod that aren't reproducable on Dev/QA.
Friday, September 14, 2012 6:48 AM
On the other hand, it can be something as simple as redeployment
Or this one, but you should have caught this in Dev/QA already:http://ninocrudele.ugics.org/en/errore-biztalk-distinquish-field-problem-error-microsoft-xlangs-runtimetypes-distinguishedfielddefinition-getdfdefsystem-string/
- Marked As Answer by LeoTangModerator Thursday, September 20, 2012 9:26 AM