Saturday, 15 February 2014

biztalk - Microsoft.XLANGs.Core.Context.RootService.ExceptionLocation returns null -


We have now installed the BizTalk 2013 R2 Live Environment in the live system 2 active-active clusters BizTalk Server and 2 Active-Passive SQL There are cluster servers. In our previous live system, we have a BizTEK Server 2010 and a SQL Server (no cluster). In the last BizTalk 2010 live system, we have a code block to get the name of the current size and everything was fine. 

  Context.RootService.FriendlyNameFromShapeId (context.RootService.ExceptionLocation.ShapeID)

But when we transfer this code to the new BizTalk 2013 cluster environment , The exception is zero, and we get the object reference exception.

Any thoughts? Is it related to BizTalk 2013 R2 bug or is it related to clustering?

We found solutions after a thorough analysis. The problem is that, in the adm_group table, in the bztekmgmtdb, the global trekking option column has a value of 0. 0. Why the Exceptional Place has zero value in. When we changed this value to 1 (in BizLock setup, the default value of this column is 1), the sadding is fine. On the other hand, we will analyze the efficiency problems of changing this column to 1.


Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)