The funniest part of having an intern working and learning from you, especially for a person like me that really love to write about Errors and Warnings, Causes and Solutions, is that they are able to make the funniest and unexpected questions, they will find things that because we are so accustomed to doing the job and to avoiding them, that we do not even realize anymore that they exist and they are there.
So yesterday, after solution deployment, my intern was complaining that he was always receiving the following error while creating a receive port:
TITLE: BizTalk Server Administration
——————————
Concurrency Violation encountered while Updating the ReceivePort ‘rprtReceive’. 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. (Microsoft.BizTalk.ExplorerOM)For help, click: http://go.microsoft.com/fwlink/?LinkId=47400&ProdName=Microsoft+BizTalk+Server+2016&ProdVer=3.12.774.0&EvtSrc=Microsoft.BizTalk.ExplorerOM.Resources&EvtID=IDS_ERR_OBJECT_CONCURRENCY
——————————
BUTTONS:
OK
—————————–
📝 One-Minute Brief
A troubleshooting note that explains why the BizTalk Server Administration Console throws a Concurrency Violation when updating a Receive Port and how refreshing the cached configuration after a deployment resolves the issue.
Cause
While open and navigating in the BizTalk Administration Console, you will notice that the first request on expanding the navigation tree or opening a BizTalk Server Application or Host Instance will take longer than further interactions, because in the first request, the Administration Console will query your BizTalk databases for information and after that, cache the result.
So, unless you force a refresh it will use that cache information, nevertheless it will have some kind of mechanism (like a hash) to verify if the cache is updated will the current BizTalk Server Configuration on the database when you try to perform an operation like create or change a Receive Location.
Assuming that you deploy a new version or new artifact to a BizTalk Application, you need to refresh that Application before you perform any kind of operations; otherwise, you will receive this or similar errors.
The reason this error happened was that my intern already had the BizTalk Administration Console running and had focused (selected) the Application in concern before he deployed a new version of the solution from Visual Studio. After he deploys.
Solution
This is, in fact, a simple problem to solve:
- Concurrency Violation encountered while Updating the ReceivePort – Option 1:
- Close the BizTalk Administration Console and open it again (stupid and simple)
- Concurrency Violation encountered while Updating the ReceivePort – Option 2:
- Right-click on the BizTalk Application you want to refresh, and then select the Refresh option.
- Concurrency Violation encountered while Updating the ReceivePort – Option 3:
- Select the resource inside your BizTalk Application you want to refresh, for example, Receive Locations, and press F5.
There are several alternatives. The important thing is to refresh the BizTalk Administration Console if something has changed in your BizTalk Server environment.
Hope you find this helpful! If you liked the content or found it useful and would like to support me in writing more, consider buying (or helping to buy) a Star Wars Lego set for my son.
