7

I just upgraded my web role project (and solution) from Azure SDK 2.4 to Azure SDK 2.6 using the upgrade functionality under project properties > application.

When I am building my application, everything works well but when I try to run it (and start up the Azure emulator and such) it gives the following error when I click "NO" if I want to proceeed with build errors:

unable to get setting value Parameter name: profileName

See build output: Build output

Nothing more. When I open my output I can not find anything related to this. It looks like the build is done successfully.

If I click "YES" VS serves a popup with this message:

Failed to debug the Microsoft Azure Cloud Service project. The output directory "D:\path\to\folder\src\project\csx\O" does not exist.

Maybe it has something to do with the emulator?

Can some one help? Much appreciated!

Hans Leautaud
  • 1,742
  • 1
  • 19
  • 34
  • That is the exact wording of the error message? – Claies May 12 '15 at 16:40
  • Yes. That's why it is marked as quote :) – Hans Leautaud May 12 '15 at 16:42
  • that's quite the unusual use of English for an error message. Can you show a screenshot of that? Also, have you tried rebuilding your project? – Claies May 12 '15 at 16:44
  • Added a screenshot. Yes, I've tried rebuilding it, but the error only occurs when I run my application, not during build. – Hans Leautaud May 12 '15 at 16:48
  • seems like a bug to me. I would submit a bug report at http://connect.microsoft.com/VisualStudio – Claies May 12 '15 at 16:55
  • definitely shows 1 failed there though, so one of your projects isn't compiling; Presumably it has a `profileNameError` property within it somewhere. – Claies May 12 '15 at 16:56
  • Yes, it says that but none of my projects are failing. I think that is my web role project (ccproj), not any of my csproj files. – Hans Leautaud May 12 '15 at 16:58
  • one definitely ***is*** failing to compile. You are getting an error asking if you want to continue after receiving a build error. If you hit NO, then your build is aborted. If you hit YES, then it still tries to run the program anyway, but it can't, because the project didn't build, hence it doesn't exist in the output directory. – Claies May 12 '15 at 17:02
  • Let us [continue this discussion in chat](http://chat.stackoverflow.com/rooms/77637/discussion-between-ydd1987-and-claies). – Hans Leautaud May 12 '15 at 17:03

4 Answers4

15

We also encountered this issue.

It appears that even if the Service Configuration you've selected in the Run/Debug settings is say, Dev.Local - you need to have a service configuration called ServiceConfiguration.Local.cscfg or you'll encounter this precise error.

At any case, once we created a cscfg called ServiceConfiguration.Local.cscfg this problem ceased, even though we were not referencing it.

Youngjae
  • 24,352
  • 18
  • 113
  • 198
Brian Gambs
  • 209
  • 2
  • 3
  • Interesting. About two weeks ago we upgraded from 2.4 to 2.6 and did not see this error on any of our Azure projects. We have six Azure projects in our solution, only one has a ServiceConfiguration.Local.cscfg, the other five only have ServiceConfiguration.Cloud.cscfg. – Craig W. May 20 '15 at 16:24
  • I had the exact same problem. Using 2.8 SDK, cleaned up my solution. Search in files does not bring up "Local" at all but still i need to have it. – Eleasar Dec 15 '15 at 09:19
  • OMG...We have to have `ServiceConfiguration.Local.cscfg`! – Youngjae Apr 19 '17 at 02:38
10

It's something nasty about diagnostics which the 2.7 upgrade (in my case) attaches everywhere. Remove diagnostics from your roles (web.config, role definitions) and I bet you'll have some luck.

Update: we never got to the bottom of this. Unless you are happy without diagnostics, life really is simpler if you just give in and make sure you have a Foo.Local.cscfg!

ledneb
  • 1,371
  • 1
  • 13
  • 25
  • 1
    Worked for me. For those wondering where the Diagnostics option is: right-click the role > Properties > Uncheck Enable Diagnostics. – Nick Aug 12 '15 at 16:49
  • For us the problem was that the diagnostic connection string wasn't specified where the 2.7 SDK expects it to be. Simply unchecking "Enable Diagnostics", saving, and re-checking "Enable Diagnostics" has rectified the problem and Diagnostics is working as well. – Balint Farkas Sep 11 '15 at 09:20
  • Cool. Do you have any record of what that actually reconfigured in xml? – ledneb Sep 21 '15 at 10:51
  • Diagnostics option is problem here. – afr0 Sep 22 '15 at 03:16
1

This seems to be a catch-all error. I've just encountered it, and the root cause in my case appears to be that I had the thumbprintAlgorithm for a certificate incorrectly set. I found this out when I tried to Package... it and got a useful error message, so that's one thing to try.

Peter Taylor
  • 4,918
  • 1
  • 34
  • 59
0

Check if you have an XML syntax error in ServiceConfiguration.Cloud.cscfg

PaulAndrewLang
  • 379
  • 3
  • 4