I tested MSDN StockTrader5 online and it doesn't work
https://azurestocktrader.cloudapp.net/Quotes.aspx?symbols=s:100;s:101;s:102;s:103
what's the cause ?
It's working now...
My guess is that this might have been a genuine outage - but it's impossible from here to tell whether it was caused by an incorrect application upgrade or by an outage within SQL Azure.
Overall, I've found Azure and SQL Azure to be very reliable, but obviously when a someone comes along and sees an error in an online showcase then it's not a good first impression for them.
As stated in the error message:
Login failed for user 'trade'.
It looks like this application is trying to login to the MSSQL database using a username/password that isn't correct. It looks to be a simple configuration error.
Related
We are hosting our website in Azure. During the deployment(TFS) we will do the below Steps as the part of the deployment pipeline.
Stop the WebApp
Deploy Web App Service
Start the WebApp
After the 1st step, if anyone tries to access our website, then by default Azure will return the below page
We really don't want our users to show this page during the outage. We are planning to show our own outage image/page in such case.
Is there is any way to achieve this?
Since Azure Web Apps in a Paas model, I'm wondering how to do this?
Any inputs Appreciated!
It seems that it does not suppport custom error page at this time. There is feedback on Enabling users to create custom error pages for 403 and 503 service unavailable messages.
I think you could up vote to promote the realization of this feature.
Putting some additional information regarding the solution for my own question here,
Just found the OP in SO where the feedback originated
There are two categories of HTTP errors that can happen on Azure Web
Apps:
Those that happen in IIS on the Web Worker where your site is running.
Those that happen before it reaches that. This includes cases when the
site is stopped, in the process of restarting, or potentially affected
by some other issue in the system. One way to tell if an error is #1
or #2 is to turn on http logging, and see if it gets logged. Only #1
will.
For #1, you can customize errors using standard techniques. But for For #2, there is currently no way for you to customize the pages returned by Azure.
Thanks, #David Ebbo and #SamJolly
We have developed a website. This will be deployed in IIS in server machine of a network. n number of people will access our website from their allocated pc's. What happens now is, if the browser is left open for an extended period of time, it is getting crashed, then i will have to reload the page to get access to my site. What should i do to overcome this problem?
Please advise on this.
Thanks
Venkat
You havent provided much information here so cant really comment anything specific (for e.g. runtime env, database servers, any specific tech. in use such as TCP/IP, web sockets.
There can be number of things that you could look into.
For the start you could look into resources that are not being disposed properly. For e.g. Database connection, large in memory .NET objects for e.g. file streams. Now this could be something as simple as using statements or exception handling(if .NET).
You could use profiler applications such as MiniProfiler (do google), Again if its Microsoft then you could use Microsoft Load Testing to see where the problem is.
Try using fiddler to see if it shows anything.
If you are using TCP/IP communication for e.g. push notifications from server side using websockets or node.js then you need to investigate if there are any threads/connections not properly closed/disposed.
list is sort of endless.. good luck
I make an application for querying from and inserting data to the database using ASP.NET 3.5 linq to SQL.
It works fine in the development server.
But after deploying to the staging server, after the first few requests, the application seems unresponsive no matter what I type in the URL. The whole IIS application is frozen. I know I can restart the application to fix that. But I don't want it to happen again in the future.
What are the possible causes of this?
I've just found a ref about this problem:
http://blogs.msdn.com/lucascan/archive/2009/04/14/troubleshooting-an-unresponsive-web-server-iis-part-1-of-2-gathering-the-data.aspx
http://forums.iis.net/p/1154624/1893546.aspx
It's not easy to provide an exact cause since we have no idea how the application was written, what dependencies exist, whether service packs/patches are installed etc. What we could help with is debugging the application.
Things I would start with:
Find out if other applications have the same problems.
Review the server event logs on both servers.
Memory, CPU usage etc on the server with Performance Monitor (perfmon.exe)
See what SQL is being generated with SQL Profiler.
Use an HTTP Analyzer like Fiddler to find out if the server is running anything in particular but the browser is not displaying it.
As BrianLy says this is one of those tricky to pin down situations. We had several problems with ASP.NET apps taking seemingly forever to start, this was down to our corporate firewall blocking crl.microsoft.com.
It's probably a stab in the dark, but it might be worth investigating. The chances of your issue being this sound slim though.
A quick test to see if it is something related to this is to add 127.0.0.1 crl.microsoft.com to your hosts file.
Got reports of a web app going down twice in three weeks. Need to do some root cause analysis. works fine after a reboot. I'm not really an expert in this field.
It is hosted on IIS and Windows 2003.
There is nothing interesting in the event viewer, and IIS logs just show lots of successful GET operations. There is nothing interesting in SQL logs on the remote SQL server it connects to.
I'm not sure how to decipher the IIS log. It just looks like a bunch of successful GET messages with no errors.
I don't think I can really get too much further with root cause analysis track down the cause of the issue?
The only thing you could try to get some real results is this excellent blog by Tess Ferrandez. I think that you will find crash lab very enlightening :)
Take a look at this, it might help you find the app shutdown cause.
Depending on your traffic, twice in three weeks doesn't sound like a lot. The root cause may relate to the fix- if you were able to bring it back up by restarting IIS, it could be a memory leak. If you had to restart the server, it could be a deeper problem.
I have a web app which queries a Lucene index and it works just fine in a W2K3 server in my network. Now I got my azure code so I wanted to test the service uploading the app. In order to do that I had to install Vista (I did it in a Virtual machine) cause the Azure SDK won't install on an XP box.
I created my Cloud Service, added the files from my app but when I run it (just F5) I get a SecurityException, when I call Lucene to query the index, saying:
The application attempted to perform
an operation not allowed by the
security policy. To grant this
application the required permission
please contact your system
administrator or change the
application's trust level in the
configuration file.
I've been googling around and the solutions I've found concern modifying the machine.config file which is something I won't be able to do "in the cloud".
Could anybody help on this?
Ok, in case somebody is facing the same issues, this is the correct answer which I got from the Azure forum:
This is because of the trust policy
for the Windows Azure CTP. The
enviroment variablies TEMP and TMP are
avaliable and set up appropiately.
However, System.IO.Path.GetTempPath
and System.IO.GetTempFile do not work
as they require unrestricted
environment permissions. I would
suggest you contact the Lucene
developers to see if they can modify
the code so it runs properly in medium
trust environments.
Thanks to Daniel C. Wang for the answer.
I also found a question regarding my same issue and how if was fixed.
Here the link: Lucene.Net fails at my host because it calls GetTempPath(). What’s the work around?
You can change trust in the web.config, unless that has been disallowed in the machine.config (which it often is in shared hosting). inside your put and see what happens.
If you are not allowed to do that, see if you can get your control GACd by talking to your provider. If that doesn't work, sorry to say but you are out of luck. Sometimes you can find workarounds that don't require full trust for a specific method, but if a third party dll requires it there is not much you can do
Haven't done this but isn't it possible to have a desktop version of the Live Operating Environment? This would seem a good start for troubleshooting.