How to Determine a Server Down (Sev A) Situation for IIS

Last reviewed: January 6, 1998
Article ID: Q159454

The information in this article applies to:

  • Microsoft Internet Information Server versions 1.0 and 2.0

SYMPTOMS

How to determine if a Support Incident is a Server Down (Severity A or Sev A) Situation.

NOTE: Below are general guidelines on how to determine if an Internet Information Server service request is a Server down or Sev A condition. These are general guidelines and not absolute rules.

RESOLUTION

The following criteria can be used to determine if this is a Server Down situation.

Question 1

Has this server worked previously?

This is a Server that has been up and running and is no longer functioning. This is not a test Server or an MSDN incident.

Question 2

Will your business be adversely affected due to this server not working?

Will there be loss of customers, business, revenue due to this server not functioning?

Question 3

Can this issue be opened for a callback the next morning during normal support hours (6 A.M. to 6 P.M. PST).

Can it wait until morning?

If this computer, with its current configuration and operating system (OS), has been previously working and/or there will be a loss of business, revenue, and/or productivity and/or this issue cannot be opened and deferred for callback in the morning, this could be considered appropriate and handled according to Sev A guidelines.

Keywords          : iis
Version           : WINNT: 1.0,2.0
Platform          : winnt
Hardware          : ALPHA x86
Issue type        : kbinfo


================================================================================


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: January 6, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.