iT Synergy Blogs

Growing Innovation - Soluciones a problemas reales

Copyright © 2025 · iT Synergy·

File Sharing lock count exceeded (Error 3052). Enterprise Architect error Synchronizing replicas.
File Sharing lock count exceeded (Error 3052). Enterprise Architect error Synchronizing replicas. avatar

By Leave a Comment

I have been working with Enterprise Architect modeling different artifacts of an Integrations project. We are working about 10 people on it, so we are working under the schema: master and replicas.

To give a bit more information about this, we create a master (.EAP) as show the image below.

Each of us has a replica, this replica was created taking as a base the master created before.

So, it works like this: each person can make changes in different parts of the .EAP, then, at the end of the day every one synchronize the replica with the master, and the master gets all the change made by each person. Thus, we make a collaborative and parallel work.

Sometimes when you synchronize the replica using the master, an error comes up on a window showing as follow, and it doesn’t allow you get the changes which were made by other people on the master

To resolve this problem you have to increase the value of the field MaxLocksPerFile (as many time as it appears) in the Registry Editor. By default it comes with the value: 9500 (Decimal), I have put 300000 and now it works fine.

Schema referenced by Map has been deleted. The local, cached version of the BizTalk Server group configuration is out of date. You must refresh the BizTalk Server group configuration before making further changes.
Schema referenced by Map has been deleted. The local, cached version of the BizTalk Server group configuration is out of date. You must refresh the BizTalk Server group configuration before making further changes. avatar

By Leave a Comment

Sometimes when you try to update the BizTalk group within the BizTalk console (BizTalk Server Administration Console) the following error windows comes up saying that the BizTalk Server group is out of date and you must refresh, but the really estrange thing is when you try to do it you simply can’t! and the same windows error still there and you can’t see the BizTalk Application you have deployed.

It happens when a map´s reference is lost and the console can display all the application which are into the BizTalk Group.

So, what you have to do is:

  • Search the reference of the map that the windows error is showing you in the Database and delete it.

The Database’s name is: BizTalkMgmtDb and the table’s name where the maps information is store is: bt_MapSpec.

Query to delete it:

DELETE

FROM [BizTalkMgmtDb].[dbo].[bt_MapSpec]

WHERE id = ‘Somenthing’

The table has some columns, the columns that you are looking for to find quickly the map are:

  • [indoc_docspec_name]
  • [outdoc_docspec_name]

These columns constains the reference location which the map is using for example:

  • Maps name: ConsultaInfraYTecnoGenerico_To_ConsultaInfraYTecnoNCAReq.btm

The reference location that contains the file maps has the schema reference the map has like the pictures below shows:

Those references are the ones you are going to find in the table mentioned before just like that:

Be careful and make sure you delete the right reference (The reference which is lost). To do it, I recommend you find a column which has the
unique value for each row. In this case you can use the Id column.

When you have already done it, you can try again to update and everything is going to work fine again. 🙂

xlang/s engine event log entry: Exceptions.Types.InterceptorException. No events are expected after completion
xlang/s engine event log entry: Exceptions.Types.InterceptorException. No events are expected after completion avatar

By Leave a Comment

With this title I am making reference to an error we have when we try to track data from some shapes in a BizTalk application. The following code is a complement of an additional information that we got with this error.

Exception type: BAMTraceException

Source: Microsoft.BizTalk.Bam.EventObservation

Target Site: Microsoft.BizTalk.Bam.EventObservation.BAMTraceFragment CreateTraceFragment()

The following is a stack trace that identifies the location where the exception occured

at Microsoft.BizTalk.Bam.EventObservation.TraceInstanceToken.CreateTraceFragment()

at Microsoft.BizTalk.Bam.EventObservation.TraceReferenceTrackPoint.Execute(EventStream eventStream, IBAMDataExtractor extractor, Object location, Object data)

at Microsoft.BizTalk.Bam.EventObservation.BAMInterceptor.Microsoft.BizTalk.Bam.EventObservation.IRawStreamInterceptor.OnStep(IBAMDataExtractor extractor, Object location, Object data, Stream eventStream)

at Microsoft.XLANGs.Mozart.BIWrapperInterceptor.TrackEventHandler(Location loc, EventData data, Stream trackData)

at Microsoft.XLANGs.Core.Events.FireEvent(Location location, EventData args, ITrackStreamDispenser trackData)

 

Before explain what the reason is to get this error when we are tracking data from BizTalk I would like to give a little bit more context about BAM (Business Activity Monitoring) and TPE (Tracking Profile Editor) to get a better understanding of it. The TPE is a developer tool. Basically it is a graphical tool use to specify the orchestrations, ports and messages that are sources of the data captured by BAM.

 

I will place particular emphasis in something very important to know about TPE: The TPE  is only used when we are going to capture data from BizTalk application. This special emphasis is because BAM is a very powerful tool, with this one we can monitor WCF (Windows Communication Foundation), .NET Application and WF (Windows Workflow Foundation) as well, but we have to know which is the tool to do it, which for those cases is not the TPE.

 

When we use the TPE the following data sources types are displayed and we can use to track:

  1. Orchestrations
  2. Message payload schemas
  3. Context property schemas
  4. Message property schema

In another way, some message such a string type or System.XML.XMLDocument can’t be tracked with TPE. Only we can track messages that have a schema that is known at design time.

We can’t track any of the following orchestration shapes:

  1. Group (Task)
  2. Loop (While)
  3. Message assignment
  4. Suspend
  5. Terminate
  6. Throw exception
  7. Transform

In this stage when I have written about what we can do and don’t with the TPE, I will come back to the beginning of this post, the error I got doing a tracking!!. I got this error because I was trying to put and interceptor in a send shape (this shape allows us to track data without any problem), the real problem was that the send shape was inside the Group shape, and how we saw before in this post we can’t track data from this shape. This is a BAM limitation – Tracking data from some BizTalk application shapes!