MSBuild (64bit) fails to find the “GraphCmd.exe” command (Architecture layer diagram validation) - by omjbe

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 768379 Comments
Status Closed Workarounds
Type Bug Repros 2
Opened 10/23/2012 4:31:11 AM
Access Restriction Public


Our build servers are unable to find the “GraphCmd.exe” file after Visual Studio 2012 was installed on them. It worked with only Visual Studio 2010 installed (now both versions are installed – VS2010 and VS2012).
Error message:
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\ArchitectureTools\Microsoft.VisualStudio.TeamArchitect.LayerDesigner.targets (148): The "GraphCmd" task failed unexpectedly. System.InvalidOperationException: Cannot start process because a file name has not been provided.
I found an issue in the TeamArchitect targets file:
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\ArchitectureTools\Microsoft.VisualStudio.TeamArchitect.LayerDesigner.targets
The last GraphCmdPath property definition works only if MSBuild is running as 32bit process because the registry entry was written by a 32bit process and thus it is under der “Wow6432Node” section of the registry:
<!-- Determine GraphCmd location -->
    <GraphCmdPath Condition="'$(GraphCmdPath)'==''">$(Registry:HKEY_LOCAL_MACHINE\Software\Microsoft\VisualStudio\11.0\Architect\@GraphCmdDir)</GraphCmdPath>
I have found a workaround so that we can use VS2012 with our Modeling projects. See the Workaround section of this bug entry.
Sign in to post a comment.
Posted by PWilliams on 3/1/2013 at 8:26 AM
I realize no more investigation is being done on this, but I would like to know if the workaround will be fixed in future versions as the change is in a Microsoft installed file.
Posted by James [MSFT] on 2/7/2013 at 5:49 PM
Thanks for the feedbacks. Given that it is very hard for us to repro this issue and there's an easy fix for you, we'll not continue the investigation on this. Please let us now if you see further issues.
Posted by Microsoft on 10/30/2012 at 6:36 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by omjbe on 10/30/2012 at 1:26 AM
Unfortunately, this issue is not that easy to reproduce. As I mentioned it happens on our build servers and not on our developer machines.

But the fix is very easy to do. Just add the following line to the file I have mentioned in the description.

<GraphCmdPath Condition="'$(GraphCmdPath)'=='' and '$(Registry:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\11.0\Architect@GraphCmdDir)' != ''">$(Registry:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\11.0\Architect@GraphCmdDir)</GraphCmdPath>

Please show this to the responsible development team. They will immediately know what the issue is. Just mention to have a look at the “Wow6432Node” part in the line above.

Thank you.
Posted by Microsoft on 10/29/2012 at 3:17 AM
Hello again. We wanted to give you a quick reminder that to efficiently investigate and reproduce your issue, we need you submit the additional information we requested . If we haven't heard back from you with the requested information in the next 3 days, we will go ahead and close the issue.
Posted by Microsoft on 10/23/2012 at 11:54 PM
Thanks for your feedback.

In order to fix the issue, we must first reproduce the issue in our labs. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a vs setup log so that we can conduct further research?

You can get the log files with the following steps:
1) Download collect.exe from the link below. <>
2) You may choose to save the tool for later use, or to run directly.
3) The utility creates a compressed cabinet of all the VS and .NET logs to %TEMP%\

Please submit this information to us within 3 business days. We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Macy [MSFT] on 10/23/2012 at 4:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(