Turns out the VM role in Azure is in Beta and shouldn't be used for
anything but the most trivial sites. Doesn't say that anywhere during
the sign up procedure or when MS takes your credit card details. Lesson
learned.

 

From: ozdotnet-boun...@ozdotnet.com
[mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Ken Schaefer
Sent: Sunday, 2 September 2012 5:38 PM
To: ozDotNet
Subject: RE: Windows Azure VM issues

 

If there was a problem with the page file (e.g. it couldn't be accessed)
then the server would blue screen (KERNEL_DATA_INPAGE_ERROR or similar
bugcheck).

 

What's the event details you are seeing? (If you open the event, there's
a "copy" button you can use to copy all the event details out to
clipboard)

 

Generally, if the OS is shutdown gracefully it doesn't have any capacity
to power itself back on. You need the virtualisation software (or your
UPS if you have a physical machine) to power the machine back on.

 

Cheers

Ken

 

From: ozdotnet-boun...@ozdotnet.com
[mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Nicholas Oxby
Sent: Friday, 31 August 2012 10:07 AM
To: ozdotnet@ozdotnet.com
Subject: Windows Azure VM issues

 

Hi All

 

We here at work have just gone down the Azure path to host, what will be
a fairly high traffic site. We've gone the VM route and it's been a bit
problematic. 

 

I could use some advice, or links to advice if anyone has some. 

 

Issue : Server shutdown and didn't reboot at 3am. Nice. Event log says
disk error (I can get the actual number/message if need) and the
services all started to shut down, until the server switched off. We
think it's because the page file has been located (by default) on the
temporary storage drive, not the c:drive. 

 

Is there a good reason why it's been placed on the d:?  Can we move it?
Is this the issue?

 

And

 

Why didn't the server reboot automagically? What setting have we missed
that gets it to restart itself?

 

It's fairly vanilla server, with 2 websites and the smtp service
running.

 

Thanks for your help

 

Nick

Reply via email to