Windows Azure project cannot start due to an error: could not find fileDFUI.exe, please check the installation

Question

I get the following error: whenever I add an existing Asp.Net web application as an existing web role project.

---

Microsoft Visual Studio Could not find file.fu.exe, please check your installation.

Ok

---

I am using Nov 2011 SDK through WPI. Steps to recreate:

• Create an empty Azure project (without any role).
• Add an existing Asp.Net MVC3 project to the solution.
• Right-click on the "Add an Existing Web Role Project in the Solution" role to indicate only the added project.
• Rebuild and run to see the error.

Please, help.

Answer 1

The loan belongs to Carson Wa from Microsoft, which answered this question on msdn forums.

The cause of the problem is that visual studio is trying to load DFUI.exe from the AppData temporary directory, i.e. C: \ Users \\ AppData \ Local \ assembly \ dl3 \ GPO8L9XL.JW4 \ X9X8K6MA.13N \ 139aad8f \ 00a876bf_fa99cc01 \ DFUI.exe

DFUI.exe does not exist in the AppData directory, so the visual studio reports an error. In SDK 1.5, visual studio reads the registry key to find the correct location. However, it looks like the registry search has been deleted in SDK 1.6.

Currently, one of the workarounds is to copy all the files under C: \ Program Files \ Windows Azure Emulator \ emulator to the Temp AppData directory. Please note that the path to the temp directory may be different on your computer. You can find the path using Process Monitor. http://technet.microsoft.com/en-us/sysinternals/bb896645 Please start the process monitor and reproduce the problem in the visual studio. Find DFUI.exe in the log and you will find the path.

Thank,

Carson

Answer 2

It was just the same mistake ...

November 2011 Azure Toolkit seems to check the correct folder (according to Process Monitor), but you also get this error if you just have the Azure Deployment project installed as a launch project instead of your website.

It's nice to see that you find a problem with the SQL instance name ... Guess there are several ways to upset Azure.

Answer 3

I'm not sure if you need to load it into your project (Azure Compute Emulator user interface from SDK)?

If not, remove it from the existing ASP.NET project in which it resides. Redeploy to Azure, and everything should be fine?

Answer 4

It is very important to note:

" Please note that the path to the temp directory may vary on your computer . You can find the path using Process Monitor. Http://technet.microsoft.com/en-us/sysinternals/bb896645 Please start the process monitor and reproduce the problem in visual studio. Locate DFUI.exe in the log and you will find the path "

Answer 5

I tried to follow without success:

• Reinstalled the Windows Azure Nov 2011 SDK.

• DFUI.exe exists in C: \ Program Files \ Windows Azure Emulator \ emulator \ devfabric

I am using Visual Studio 2010 with Windows7 x64 Ultimate and SQL Server 2008 R2 Express (v10.50.1617.0). The instance of SQL Server does not use the default name "SQLExpress".

I could recreate the problem with another machine with a similar configuration.

The warehouse emulator did not start because the SQL Server instance name was not "SQLExpress". I configured the storage emulator using DSInit / sqlInstance :. He fixed the storage emulator. When I manually start the memory and computation emulators and restart in Visual Studio 2010, I can no longer see this error.

The moral of the story ... Do not change the name of your default instance of SQL Server Express ("SQLExpress") unless you have a very good reason for this.

Edit: The error returned. Not sure what the reason is. Not marked as an answer.

Answer 6

Oddly enough, installing MVC 3 from asp.net fixed the problem for me.

Answer 7

I have a simpler answer, at least it worked for me.

I had two instances of Visual Studio. I closed one and it worked.

Answer 8

I often used this error (and fixed it as other answers), but I have not done this since installing Azure SDK 1.7