CODEWITHSUNDEEP
asp.net-mvc-3azure
CMircea
CMircea

Reputation: 3568

Blank page on Azure

I have an application running in Azure (trial account). So far so good, everything has been nice, except for a long deploy times (10-15 minutes).

I've done a deploy recently and got a lot of weird bugs I cannot trace. For example, if I log in and thus a cookie is created (I use FormsAuthentication) all I get from the application is a blank page, as in, absolutely nothing is sent to the browser. The application works fine in the ASP.NET Web Dev Server, IIS Express, even the Azure Emulator!

What could be the issue? Searching the web hasn't been much help, with only a couple of unrelated issues.

Upvotes: 2

Views: 2988

Answers (4)

Florin Dumitrescu
Florin Dumitrescu

Reputation: 8282

I tried logging into the site (if I correctly understood from one if the comments, the url is versulo.com) and I didn't get any blank page with 404 status code.

However, there is another problem I spotted. Your site seems to be implementing caching inappropriately. The main page, the one from which you trigger the login and which is dynamic in nature contains an Expires header set at 5 minutes after the pages first load. That means that each call or redirect to that page within 5 minutes since it was first loaded, will be served from the browser's cache.

Because of that, after I login into your application I am redirected back to the home page which looks like I am not logged in. If I force a F5 refresh on the browser, then the page will indeed show me as logged in.

If instead of a refresh I try to login again (which is what I did in my first trials, since it looked like the login didn't work in the first time), I am getting an error page with the following message:

Sorry, there has been an error on the server. 500

The page looks like an application error page and even if it displays the 500 number, it is actually served with an HTTP 200.

So, while I am not 100% sure if this is also the cause of the problem described by you, you should remove the Expires headers from the dynamic pages your application is serving.

Upvotes: 2

Richard Astbury
Richard Astbury

Reputation: 2353

Could you provide a link to the application, or perhaps some source code?

When you say 'blank page', what is actually returned, a 404 / 500?

Have you inspected the IIS logs, or added some trace information to your code?

Have you tried accessing the service using it's ip address rather than domain name?

Upvotes: 0

Ming Xu - MSFT
Ming Xu - MSFT

Reputation: 2116

some partial views are not rendered at all;

Do you mean some pages are working fine, but others are not? It would be better if you can point out a pattern on what’s working and what’s not? For now, please make sure all referenced assemblies (except for default .NET assemblies and Windows Azure runtime) have Copy Local set to true. For example, MVC assemblies are considered as extensions to .NET, so please set Copy Local to true. In addition, you can also try to use Fiddler to monitor the requests to see what’s returned from the server.

Best Regards,

Ming Xu.

Upvotes: 0

Sandrino Di Mattia
Sandrino Di Mattia

Reputation: 24895

This can be because you're combining Forms Authentication with multiple instances. Are you using multiple instances? If that's the case, could you:

Upvotes: 0

Related Questions