Event ID 19 — WUA Update Installation

Event ID 19 — WUA Update Installation

Updated: December 13, 2007

Applies To: Windows Server 2008

Windows Update Agent installs updates from Windows Update, Microsoft Update, or Windows Server Update Services.

Windows Update Agent detects updates every day at the user configured time or by default at 3:00 A.M. If the computer is configured for Automatic Updates to take place, the downloading and installation of updates also take place at this time.

Event Details

Product: Windows Operating System
ID: 19
Source: Microsoft-Windows-WindowsUpdateClient
Version: 7.0
Symbolic Name: VISTA_MSG_INSTALL_SUCCEEDED
Message: Installation successful: Windows successfully installed the following update: %1

Resolve

This is a normal condition. No further action is required.

Related Management Information

WUA Update Installation

Windows Update

Related:

Event ID 19 — Backup Operations

Event ID 19 — 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: 19
Source: Microsoft-Windows-Backup
Version: 6.0
Symbolic Name: BACKUP_FAILED_DID_NOT_START_EVENT
Message: Backup attempted at ‘%4’ failed to start, error code ‘%5’.

Resolve
Review event details for why backup failed to start

If a backup fails to start, 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. Confirm that the location to perform the backup to is online.
  3. After resolving any errors that you find in performing the steps above, re-run another backup. For more information, see “Peform 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. Look at the error code mentioned in the event details to find out why the backup failed to start.

Perform a backup using the command line

Make sure that the backup storage location specified by -backupTarget is online.

Note: If the backup operation that failed was a scheduled backup, you can use wbadmin start backup with no parameters. This will run a backup using the settings for the scheduled backup.

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:

While locating a user, a provider returned a warning.

Details
Product: MapPoint Location Server
Event ID: 19
Source: Microsoft MapPoint Location Server
Version: 1.0.0.0
Message: While locating a user, a provider returned a warning.
   
Explanation
Location providers (and to a lesser extent, notification providers) log this message when a low-severity error is thrown by the mobile operator or notification service provider. A small number of these errors appear in the event log regularly during normal operations.
   
User Action
Retry the request. Check the description that is appended to the message to determine the cause. If a large number of these messages appear, contact your mobile operator or notification service provider for support.
   
Description
ProviderWarning

Related:

Outlook Web Access did not initialize.File “%1” in theme folder “%2” was not parsed. The XML element “%3” is missing.

Details
Product: Exchange
Event ID: 19
Source: MSExchange OWA
Version: 8.0
Symbolic Name: ThemeInfoExpectedElement
Message: Outlook Web Access did not initialize.File “%1” in theme folder “%2” was not parsed. The XML element “%3” is missing.
   
Explanation

This Error event indicates that Microsoft® Office Outlook® Web Access did not initialize. This event may occur if the following conditions are true:

  • The Outlook Web Access themeinfo.xml file that is stored in the themes folder referenced in the event description contains no contents.

  • The required XML element, “theme,” is missing from the file.

The default location of the themes folder is C:\Program Files\Microsoft\Exchange Server\ClientAccess\Owa\<version>\.

   
User Action

To resolve the error, follow these steps:

  • Replace the themes folder and the default subfolders with the files and folders that are located on the Microsoft Exchange Server 2007 DVD. By default, those files and folders are located in the \Setup\ServerRoles\ClientAccess\owa\version\ folder of the Exchange 2007 DVD.

  • If a custom Outlook Web Access theme is used, re-create all the files that are associated with the custom theme.

  • Make sure that the themeinfo.xml file contains an XML element called “theme.”

For more information about Outlook Web Access themes, see How to Create a Theme for Outlook Web Access.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

The media is write protected.

Details
Product: Windows Operating System
Event ID: 19
Source: Kernel
Version: 5.0
Component: System Resources
Symbolic Name: ERROR_WRITE_PROTECT
Message: The media is write protected.
   
Explanation

No information can be changed or added to a write-protected drive.

   
User Action

If this is a removable media drive, make sure that the proper disk is being used, or remove the write-protection. Then retry the command.

Related:

Sharing printer failed %1, Printer %2 share name %3.

Details
Product: Windows Operating System
Event ID: 19
Source: Print
Version: 5.2
Symbolic Name: MSG_SHARE_FAILED
Message: Sharing printer failed %1, Printer %2 share name %3.
   
Explanation

The printer cannot be used by others on the network.

This can happen for many reasons; for example, the File and Printer Sharing component might not be bound to the network.

   
User Action

Verify that printer sharing is possible and correct any problems that you find.

To troubleshoot printer sharing issues, try one or all of the following:

  • Determine whether you can share files from your computer. Correct any general sharing problem and try sharing the printer again.
  • Ensure that the printer share name for this printer is not identical to any other shared printer in the domain. Rename this printer share if necessary.
  • In the Group Policy Object Editor snap-in in Microsoft Management Console (MMC), ensure that the Allow Print Spooler to accept client connections policy is enabled. To find this item, In Local Computer Policy, click Computer Configuration, click Administrative Templates, and then click Printers.

If the printer is properly shared, examine the previous errors in Event Viewer to determine the underlying cause for this error.

Related: