Event ID 5 — ASP Availability

Event ID 5 — ASP Availability

Updated: January 20, 2010

Applies To: Windows Server 2008

An ASP page is an HTML page that contains server-side scripts that are processed by the Web server before it is sent to the user’s browser. Server-side scripts run when a browser requests an .asp file from the Web server. ASP is called by the Web server, which processes the requested file from top to bottom and executes any script commands. It then formats a standard Web page and sends it to the browser.

Event Details

Product: Internet Information Services
ID: 5
Source: Active Server Pages
Version: 7.0
Symbolic Name: MSG_DENALI_ERROR_1
Message: Error: %1.

Resolve
Correct an ASP application

If an ASP application error occurs, possible resolutions include the following:

  • If you purchased the application from a third-party vendor, contact the vendor regarding the error. The vendor should have more specific knowledge about the application’s features and behavior.
  • See the article ASP Troubleshooting Tips and Techniques.
  • Check the event log message for a specific error number included in the message. This error number will be different from the Event ID. To do this, see the following steps.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Check for a specific error number in the event log message

To check for a specific error number in the event log message:

  1. In the Event Viewer, select the event that you received.
  2. In the General tab, look for an error number in the event message. Here is one example of an event log message that contains an error number:

    Warning: ASP: UNC Access failed for file – \\SITES\MYSITE\DEFAULT.ASP with the error = -2147024829.

Find out more about a specific error number

To learn more about a specific error number:

  1. Download the Err.exe utility from the Microsoft Exchange Server Error Code Look-up page.
  2. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  3. At the command prompt, navigate to the directory where you downloaded Err.exe. For example, if you downloaded Err.exe to C:\Err, type cd C:\Err.
  4. Type err errornumber to obtain more information about the error. For example, if the error number is -2147024829 as in the example above, type err -2147024829.
  5. In the cited example, the error resolves to “The network name cannot be found”, which likely means that the wrong computer name was entered, the computer that is on the UNC path is down, or there is a WINS issue.

Verify

You can use IIS Manager to verify that ASP is functioning by performing a test browse.

To use IIS Manager to test browse an ASP page:

  1. Click Start, click Control Panel, and then click Administrative Tools.
  2. Right-click Internet Information Services (IIS) Manager and select Run as administrator.
  3. In the Connections pane, expand the computer name.
  4. Expand Sites.
  5. Select a Web site that uses an .asp file as its default page.
  6. In the Actions pane, click the link under Browse Web Site. If the Web page appears, the ASP is functioning correctly.

Related Management Information

ASP Availability

Internet Information Services (IIS) 7.0

Related:

Event ID 5 — RD Web Access Configuration

Event ID 5 — RD Web Access Configuration

Published: January 8, 2010

Applies To: Windows Server 2008 R2

When the Remote Desktop Web Access (RD Web Access) role service is installed, a default Web site is automatically created. By default, the Web site is located at http://server_name/RDWeb, where server_name is the name of the RD Web Access server.

To populate the Web page with a list of available RemoteApp programs or virtual desktops, you must specify a Remote Desktop Session Host server or Remote Desktop Connection Broker server for RD Web Access to use. Any RemoteApp programs on the specified RD Session Host server or RD Connection Broker server that are configured to show in RD Web Access will appear on the Web page.

Event Details

Product: Windows Operating System
ID: 5
Source: TSWebAccess
Version: 6.1
Symbolic Name: TSPORTAL_ERROR_5
Message: No programs were detected on %1. Ensure that the server is a terminal server and that it is online.

Resolve
Ensure that the server is configured as an RD Session Host server or RD Connection Broker server, and that the server is available on the network

To resolve this issue, do the following:

  • Determine the source that the RD Web Access server is configured to use.
  • Ensure that the source specified is configured as either an RD Session Host server or an RD Connection Broker server.
  • Identify and fix any network connectivity problems between the RD Web Access server and the source.

To perform these tasks, refer to the following sections.

Determine the source that the RD Web Access server is configured to use

To perform this procedure, you must be logged on with the local Administrator account or have membership in the local TS Web Access Administrators group on the RD Web Access server.

To determine the source that RD Web Access is configured to use:

  1. Connect to the RD Web Access Web site. To do this, use either of the following methods:
    • On the RD Web Access server, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Web Access Administration.
    • Use Internet Explorer to connect to the RD Web Access Web site. By default, the Web site is located at http://server_name/RDWeb, where server_name is the name of the RD Web Access server.
  2. Log on to the site by using either the local Administrator account, or an account that is a member of the local TS Web Access Administrators group. If you are already logged on to the computer as one of these accounts, you are not prompted for credentials.
  3. On the title bar, click the Configuration tab.

    Note:  If you access the RD Web Access Web site by using the RD Web Access Administration option, the page automatically opens to the Configuration tab.

  4. In the Select source to use area, select the An RD Connection Broker server option if you are using an RD Connection Broker server. If you are using one or more RD Session Host servers, select the One or more RemoteApp sources option.
  5. In the Source name box, enter the name of the RD Connection Broker server or RD Session Host server that you want to use as the data source.

    Note: If you are using multiple RD Session Host servers, enter each RD Session Host server in the Source name box separated by a semicolon.

  6. Click Apply to apply the changes.

Ensure that the source specified is configured as either an RD Session Host server or an RD Connection Broker server

To perform these procedures, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To check that the server is configured as an RD Session Host server:

  1. On the server, open Server Manager. To open Server Manager, click Start, point to Administrative Tools, and then click Server Manager.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. In the left pane, expand Roles. If listed, click Remote Desktop Services. If Remote Desktop Services is not listed, the server is not configured as an RD Session Host server.
  4. Under Role Services, the status of Remote Desktop Session Host should be listed as Installed. If the status is listed as Not installed, the server is not configured as an RD Session Host server.
  5. If the server is not configured as an RD Session Host server, do either of the following:
    • Add (install) the Remote Desktop Session Host role service onto the server.
    • Configure RD Web Access to use another server that is already configured as an RD Session Host server. To configure RD Web Acesss to use a different RD Session Host server, navigate to the Configuration tab of the RD Web Access Web site. In the Select source to use area, select the One or more RemoteApp sources option. In the Source name box, type the name of the Remote Desktop Session Host server, and then click Apply.

To check that the server is configured as an RD Connection Broker server:

  1. On the server, open Server Manager. To open Server Manager, click Start, point to Administrative Tools, and then click Server Manager.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. In the left pane, expand Roles. If listed, click Remote Desktop Services. If Remote Desktop Services is not listed, the server is not configured as an RD Connection Broker server.
  4. Under Role Services, the status of Remote Desktop Connection Broker should be listed as Installed. If the status is listed as Not installed, the server is not configured as an RD Connection Broker server.
  5. If the server is not configured as an RD Connection Broker server, do either of the following:
    • Add (install) the Remote Desktop Connection Broker role service onto the server.
    • Configure RD Web Access to use another server that is already configured as an RD Connection Broker server. To configure RD Web Acesss to use a different RD Connection Broker server, navigate to the Configuration tab of the RD Web Access Web site. In the Select source to use area, select the An RD Connection Broker option. In the Source name box, type the name of the RD Connection Broker server, and then click Apply.

Identify and fix any network connectivity problems between the RD Web Access server and the source

To identify and fix any network connectivity problems between the RD Web Access server and the source, do the following:

  • Determine if there is a network connectivity problem by using the ping command.
  • Perform additional troubleshooting steps, if necessary, to help identify the cause of the problem.

To perform these tasks, refer to the following sections.

Note:  The following procedures include steps for using the ping command to perform troubleshooting. Therefore, before performing these steps, check whether the firewall or Internet Protocol security (IPsec) settings on your network allow Internet Control Message Protocol (ICMP) traffic. ICMP is the TCP/IP protocol that is used by the ping command.

To perform these procedures, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

Determine if there is a network connectivity problem

To determine if there is a network connectivity problem between the RD Web Access server and the source:

  1. On the RD Web Access server, click Start, click Run, type cmd, and then click OK.
  2. At the command prompt, type ping server_FQDN, where server_FQDN is the fully qualified domain name (FQDN) of the source (for example, server1.contoso.com), and then press ENTER.

    If the ping was successful, you will receive a reply similar to the following:

    Reply from IP_address: bytes=32 time=3ms TTL=59

    Reply from IP_address: bytes=32 time=20ms TTL=59

    Reply from IP_address: bytes=32 time=3ms TTL=59

    Reply from IP_address: bytes=32 time=6ms TTL=59

  3. At the command prompt, type ping IP_address, where IP_address is the IP address of the source, and then press ENTER.

If you can successfully ping the source by IP address, but not by FQDN, this indicates a possible issue with DNS host name resolution.

If you cannot successfully ping the source by IP address, this indicates a possible issue with network connectivity, firewall configuration, or IPsec configuration.

Perform additional troubleshooting steps

The following are some additional troubleshooting steps that you can perform to help identify the root cause of the problem:

  • Ping other computers on the network to help determine the extent of the network connectivity issue.
  • If you can ping other servers but not the source, try to ping the source from another computer. If you cannot ping the source from any computer, first ensure that the source is running. If the source is running, check the network settings on the source.
  • Check the TCP/IP settings on the local computer by doing the following:
    1. Click Start, click Run, type cmd, and then click OK.
    2. At the command prompt, type ipconfig /all, and then press ENTER. Make sure that the information listed is correct.
    3. Type ping localhost to verify that TCP/IP is installed and correctly configured on the local computer. If the ping is unsuccessful, this may indicate a corrupt TCP/IP stack or a problem with your network adapter.
    4. Type ping IP_address, where IP_address is the IP address assigned to the computer. If you can ping the localhost address but not the local address, there may be an issue with the routing table or with the network adapter driver.
    5. Type ping DNS_server, where DNS_server is the IP address assigned to the DNS server. If there is more than one DNS server on your network, you should ping each one. If you cannot ping the DNS servers, this indicates a potential problem with the DNS servers, or with the network between the computer and the DNS servers.
    6. If the source is on a different subnet, try to ping the default gateway. If you cannot ping the default gateway, this might indicate a problem with the network adapter, the router or gateway device, cabling, or other connectivity hardware.
  • In Device Manager, check the status of the network adapter. To open Device Manager, click Start, click Run, type devmgmt.msc, and then click OK.
  • Check network connectivity indicator lights on the computer and at the hub or router. Check network cabling.
  • Check firewall settings by using the Windows Firewall with Advanced Security snap-in.
  • Check IPsec settings by using the IP Security Policy Management snap-in.

Verify

To verify that the RD Web Access server is correctly configured to make RemoteApp programs or virtual desktops available through RD Web Access, do the following:

  1. Use Internet Explorer to connect to the RD Web Access Web site. By default, the Web site is located at http://server_name/RDWeb, where server_name is the name of the RD Web Access server.
  2. Under RemoteApp Programs, click a program that is listed.
  3. If the RemoteApp program opens, the RD Web Access server and the RD Session Host server are correctly configured to make RemoteApp programs available through RD Web Access.

Related Management Information

RD Web Access Configuration

Remote Desktop Services

Related:

Event ID 5 Backup Operations

Event ID 5 — Backup Operations

Updated: January 27, 2011

Applies To: Windows Server 2008

You can use the Windows Server Backup snap-in or the wbadmin command to create and manage backups to protect your operating system, volumes, files, and application data. Backups can be saved to single or multiple disks, DVDs, removable media, or remote shared folders. They can also be scheduled to run automatically or manually.

However, system state backup is only available for the command line and is not available in the Windows Server Backup snap-in user interface. Also, you cannot configure a scheduled backup to create system state backups—but you can script the wbadmin start systemstatebackup command to run backups on a schedule.

In addition, you can use the Local Group Policy Editor snap-in (Gpedit.msc) to allow or disallow certain types of backups or backup locations. Policy settings for Windows Server Backup are located at: Local Computer Policy\Computer Configuration\Administrative Templates\Windows Components\Backup\Server.

Event Details

Product: Windows Operating System
ID: 5
Source: Microsoft-Windows-Backup
Version: 6.0
Symbolic Name: GENERIC_BACKUP_FAILED_EVENT
Message: Backup started at ‘%6’ failed with following error code ‘%2’.

Resolve
Review event details for solutions for failed backup

If a backup fails, review the details for the applicable events to find out why the backup operation failed. Then re-run the backup.

To do this, follow these general steps:

  1. Find the applicable events in Event Viewer, and then review the details for those events to find out why the backup operation failed. For more information, see “Review event details in Event Viewer.”
  2. Review the details provided about the failure in the Windows Server Backup snap-in start page. For more information, see “Review error messages in the Windows Server Backup snap-in.”
  3. Confirm that the location to perform the backup to is online.
  4. After resolving any errors that you find in performing the steps above, re-run another backup. For more information, see “Perform a backup using the command line.”

To perform these procedures, you must have membership in Backup Operators or Administrators, or you must have been delegated the appropriate authority.

Review event details in Event Viewer

To review event details for a backup in Event Viewer:

  1. Open Event Viewer. Click Start, click Administrative Tools, and then click Event Viewer.
  2. In the left pane, double-click Applications and Service Logs, double-click Microsoft, double-click Windows, double-click Backup, and then click Operational.
  3. In the right pane, click the Details tab, and then click XML View.
  4. Click an event in the list.
  5. Review <Data Name=”VolumesInfo”> to see the error code (XML Node: HResult) and detailed error code (XML Node: DetailedHResult), along with other details about the volumes whose backup failed.
  6. Review error messages for the error codes, as described in “Review error messages in the Windows Server Backup snap-in.”

Review error messages in the Windows Server Backup snap-in

To view error messages using Windows Server Backup:

  1. Open the Windows Server Backup snap-in. Click Start, click Administrative Tools, and then click Windows Server Backup.
  2. On the start page, under Messages, double-click the event for the failed volume recovery, click the Errors tab, and view the text under Message.

Perform a backup using the command line

To perform a one-time backup:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. At the prompt, type: wbadmin start backup. Use parameters, as needed. (To view the parameters and help for this command, at a command line, type: wbadmin start backup /?).

    For example, to create a backup that will be stored on drive f, of volumes e:, d:\mountpoint, and \\?\Volume{cc566d14-4410-11d9-9d93-806e6f6e6963}, type: wbadmin start backup -backupTarget:f: -include:e:,d:\mountpoint,\\?\Volume{cc566d14-44a0-11d9-9d93-806e6f6e6963}\.

Verify

To verify that backup operations are running, or will run, successfully, you should do one or more of the following, as needed:

  • For any backup operations that you have run, look for Event ID 4, which indicates that the operation completed successfully with no errors.
  • Verify that no other backup or recovery operations are running so that you can start an operation.
  • Verify that you have enabled a scheduled backup, and is configured correctly.
  • Verify that the location where you plan to store your backups is available and online.

To perform these procedures, you must have membership in Backup Operators or Administrators, or you must have been delegated the appropriate authority.

Verify the backup completed with no errors

To verify that a backup operation completed with no errors:

  1. Open Event Viewer. Click Start, click Administrative Tools, and then click Event Viewer.
  2. In the left pane, double-click Applications and Service Logs, double-click Microsoft, double-click Windows, double-click Backup, and then click Operational.
  3. In the Event ID column, look for event 4.  
  4. For this event, confirm that the value in the Source column is Backup.

Verify another operation is not running

To verify that another backup or recovery operation is not running:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. At the prompt, type: wbadmin get status.
  3. If the command output indicates that no operation is running, then you can start a backup.

Verify scheduled backup is enabled

To verify that a scheduled backup is enabled:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. At the prompt, type: wbadmin enable backup.
  3. If the command output shows a schedule, then a scheduled backup is enabled.
  4. Confirm that the schedule contains the correct parameters.

Verify storage location is online

To verify that a disk used to store backups is online:

  1. For the computer that contains the storage disk, open Disk Management. Click Start, click Run, and then type: diskmgmt.msc.
  2. Click View, click Top, and then click Disk List.
  3. For the disk that contains the volume that you will use to store backups, confirm that the value in the Status column is Online.

Related Management Information

Backup Operations

File Services

Related:

Printer %1 was paused.

Details
Product: Windows Operating System
Event ID: 5
Source: Print
Version: 5.0
Component: Application Event Log
Symbolic Name: MSG_PRINTER_PAUSED
Message: Printer %1 was paused.
   
Explanation
of the print server can pause a printer.)
   
User Action

All print jobs remain in the printing queue during a pause. When printing resumes, they are printed.

To stop logging this warning event

  1. In Control Panel, open Printers.
  2. On the File menu, click Server Properties.
  3. On the Advanced tab, clear the Log spooler warning events check box.

Related:

%2: ACPI BIOS is attempting to write to an illegal IO port address (%3), which lies in the %4 protected address range. This could lead to system instability. Please contact your system vendor for technical assistance.

Details
Product: Windows Operating System
Event ID: 5
Source: Acpi
Version: 5.2
Symbolic Name: ACPI_ERR_AMLI_ILLEGAL_IO_WRITE_FATAL
Message: %2: ACPI BIOS is attempting to write to an illegal IO port address (%3), which lies in the %4 protected
address range. This could lead to system instability. Please contact your system vendor for technical assistance.
   
Explanation

The system BIOS attempted to incorrectly access hardware resources concurrently with the operating system. This type of access cannot be synchronized and can cause system instability.

   
User Action

Contact the system vendor for an updated BIOS and follow the vendor’s instructions for installation.

Related:

An unexpected MAPI error occurred. Error returned was [].

Details
Product: Exchange
Event ID: 5
Source: MSExchangeES
Version: 6.5.6940.0
Message: An unexpected MAPI error occurred. Error returned was [<error code>].
   
Explanation

This event can occur when attempting to start the Microsoft Exchange Event service. It means that the service could not be started because an unexpected error was encountered. The Error Code in the Description section of the event can be converted to a readable message using the ERROR.EXE program included on the Exchange Server CD ROM. This error code will usually provide information as to the underlying cause of the problem.

This issue can be seen if there are multiple “EventConfig_(Servername)” folders or if the “EventConfig_(ServerName)” folder is not replicated to the Exchange Server named “ServerName.”

   
User Action

Try the following steps to resolve this issue:

  • Open Exchange System Manager and check if there is more than one instance of the same EventConfig_ServerName folder. If so, rename one of the instances so that both can be deleted. If you try to delete one while a duplicate exists, you get a warning tht indicates you must rename one of the folders. Delete both instances of the EventConfig_(servername) folder. Restart the Event service. This recreates a single instance of the EventConfig_(servername).
  • Error Code 0x8000ffff indicates “catastrophic failure.” This usually occurs in mixed mode environments, where an Exchange 5.X server existed but is no longer present. In such a case, you can try to start the Event service using the 5.5 Service Account. In Exchange Server versions 2000 and later, the Exchange Server Services always start in the context of the Local System Account, unlike earlier versions where a “Service Account” was used to initialize the services.
  • If there are multiple Exchange Servers, you should see one EventConfig(ServerName) Public Folder for each ServerName. Ensure that each of those Public Folders (also referred to as System Folders) has a replica on the server it corresponds to. So, for example, EventConfig(ServerOne) should have a replica on ServerOne and EventConfig(ServerTwo) should have a replica on ServerTwo.

Related:

The kerberos client received a KRB_AP_ERR_TKT_NYV error from the server %1. This indicates that the ticket used against that server is not yet valid (in relationship to that server time). Contact your system administrator to make sure the client and server times are in sync, and that the KDC in realm %2 is in sync with the KDC in the client realm.

Details
Product: Windows Operating System
Event ID: 5
Source: Kerberos
Version: 5.2
Symbolic Name: KERBEVT_KRB_AP_ERR_TKT_NYV
Message: The kerberos client received a KRB_AP_ERR_TKT_NYV error from the
server %1. This indicates that the ticket used against that server is not yet
valid (in relationship to that server time). Contact your system administrator
to make sure the client and server times are in sync, and that the KDC in realm %2 is
in sync with the KDC in the client realm.
   
Explanation

Kerberos cannot authenticate the Web program user because the time period for this service ticket has not started yet. The time on the server does not match the time on the Key Distribution Center (KDC) that issued the ticket, so the server does not recognize this as a valid ticket.

   
User Action

Ensure that the time on the server matches the time on the KDCs of its domain.

For more information about Kerberos, see Kerberos Authentication in Windows Server 2003.

Related:

LDM – Internal dmboot Service error

Details
Product: Windows Operating System
Event ID: 5
Source: dmboot
Version: 5.2.3790.1830
Message: LDM – Internal dmboot Service error
   
Explanation

This event indicates that the Logical Disk Manager service detected an internal error during the startup process of the server.

Cause

Possible causes include:

  • A hardware failure that prevents communication with a disk (for example, a loose cable, a loose disk controller card, or a cable failure).
  • Unexpected removal of a disk.
  • Uncorrectable bad sectors on a disk.
  • A software error.
   
User Action

Do one or more of the following:

  • Check the status of your hardware for any failures (for example, a disk, controller card, or cable failure).
  • Check Event Viewer for additional events from lower-level storage drivers that might indicate the cause of the failure.
  • Restart the system.
  • Contact Microsoft Customer Service and Support.

Related: