Добрый день! Помогите, пожалуйста как справится с ошибкой которая возникает при включении контроля версий в MS Dynamycs AX 2012.
Hi Svetlana, this is an English-speaking forum, therefore please provide the description of your problem in English. Unfortunately, even the Russian text doesn’t explain what you’re doing.
In general, the error message is related to a workspace of Team Foundation Version Control system. You’re trying to create a workspace in Y:\Test, but one already exists there.
Aren’t you, for example, trying to use the same development VM by two developers? AX 2012 doesn’t allow you to change the path, therefore the same one will be used in both cases, which isn’t allowed. I have a workaround for that, but let’s first see whether it’s your case. Please provide more information.
Hi Martin.
Our goal is to have two developers a able to work on one DEV machine. This could be either working under one user (possibly from different machines), or working under different users.
We have DevOps 2019 deployed and created two collections (TestCollection and DevCollection)
When we link DAX2012 to TestCollection, version control works fine the first time. But if we exit DAX2012 and then re-enter it, we get an error:
Team foundation server error.
The path Y:\Test is alredy mapped in workspace S-DEV-AXWORKSPACE2
The error can be fixed by deleting the TFS cache. After deleting the cache, the system works the same way once, but the error returns the second time. Y:\Test is a network drive. Currently, only one user is logged in DAX2012.
When we link DAX2012 to DevCollection, we get an error;
This error can’t be fixed by clearing the cache. We also can’t fix the error using Visual Studio 2013 (we don’t have the Developer Command Prompt for Visual Studio, and we don’t see “Wordspaces” in Team Explorer/Source Control).
Having multiple developers working on a single development machine in parallel with TFVC isn’t supported by Microsoft. If you want to use vanilla AX 2012, you must use a separate DEV box for each developer. This is the recommended way, because it means that developers are fully isolated; they can modify the same objects in parallel, can’t block each other by their changes, they may have different DB schemas and so on.
If you want to use a single box despite of all the limitations, you must to customize AX to allow this scenario (and do some extra steps outside AX). For example, look at TFS workspaces in AX2012 to see how I addressed it.
This isn’t supported by Microsoft.