VS2012 Azure Publish Fails - Unhandled Exception

Question

When I am publishing my ASP.NET MVC 4 web application via Azure project's Publish.... it fails and tells me the web app is producing an unhandled exception and cannot continue.

How can I view this error and/or how do I correct to get it to fully deploy? Thanks in advance!

Answer 1

Hi,

Do you got any exception or stack message when your publishing is failed(text or screenshots), and if you create a new Azure application with MVC 4 web role to see if the same issue could be reproduced. 

BR,

Arwind

---

Please mark the replies as answers if they help or unmark if not. If you have any feedback about my replies, please contact [e-mail] Microsoft One Code Framework

Answer 2

I've made it a bit further in the deployment process, but it still never finishes.... however I can now get to the site and use it mostly, even though the deployment process hasn't 100% completed in visual studio... I managed to turn on Intellitrace and was able to download those log files... see here for log files...

Other than that, I'm not sure how to get a hold of anymore debugging information... any further direction would be appreciated.

Answer 3

Hi,

It seems that you've fix the problem on this thread:

http://social.msdn.microsoft.com/Forums/en-US/windowsazuretroubleshooting/thread/2552d855-1f48-4ac9-ab26-fb8f8d7c4079

BR,

Arwind

---

Please mark the replies as answers if they help or unmark if not. If you have any feedback about my replies, please contact [e-mail] Microsoft One Code Framework

Answer 4

Not with the site we are trying to migrate to Azure's platform.... the successful deployment was with the starter MVC4 app that vs2012 creates for you, not our web app.... we still can't deploy that successfully.... trying to figure out what the error is since it just sits there with progress bar almost full forever (overnight) and never completes....

Site on Dashboard continually says "Busy"... over 24 hours it's been doing this....

Answer 5

The log files above are from the "Busy", never completing deployment.... that's why I attached them... hoping you could point me in the right direction as to WHAT the problem is....?

Answer 6

Turns out we we previously upgraded from MVC3 to MVC4 and were successfully running this on a GoDaddy vm, as well as here locally... but failed to deploy to Windows Azure web role... after working with Microsoft Azure support... they were able to see an exception that I didn't have access to or didn't know how to attain... that said there was something in our solution that was still referencing MVC3....

Turns out one of our referenced assemblies was pointing to MVC3 and needed to be updated to MVC4... once we did that.. it successfully deployed.... YAY!!! :)

My only guess is that the GoDaddy vm and locally... we had MVC3 installed, so it was ok with the old reference... but the Azure WebRole did not, so it bombed.... too bad it didn't show me that error during the deployment process.... would have made correcting it MUCH easier.....