Event ID 55 — Printer Driver Installation Status

Event ID 55 — Printer Driver Installation Status

Updated: November 30, 2007

Applies To: Windows Server 2008

Printer driver installation status relates to the process of installing or updating printer drivers.

Event Details

Product: Windows Operating System
ID: 55
Source: Microsoft-Windows-PrintSpooler
Version: 6.0
Symbolic Name: MSG_KM_PRINTERS_BLOCKED
Message: The attempt for %1 to use a Windows NT 4.0 (kernel mode) driver failed because this version of Windows does not support Windows NT 4.0 printer drivers. Please obtain and install a new version of the driver from the manufacturer (if available), or choose an alternate driver that works with this print device.

Resolve
Install an updated driver

Windows NT 4.0 printer drivers are not supported on computers running Microsoft Windows Vista or later. Obtain from the printer manufacturer a driver (that displays the Designed for Windows logo) for the specific model of printer, and install the driver on the affected computer.

Verify

To verify that you resolved the problem:

  1. Open the Printers folder on the affected computer, right-click an open area, and then click Server Properties. Make sure that the expected driver is installed.
  2. In the Printers folder, right-click the printer and then click Properties. On the Advanced tab, confirm that the expected driver is selected.
  3. Print a test page. If the print server logs spooler information events, look for Print Spooler Event 10 after printing, and then examine the document to confirm that it printed correctly.

Related Management Information

Printer Driver Installation Status

Printing Infrastructure

Related:

LDM – Volume Health state change rule

Details
Product: Windows Operating System
Event ID: 55
Source: DiskPart
Version: 5.2.3790.1830
Message: LDM – Volume Health state change rule
   
Explanation

This event occurs any time the health state of a volume changes. The possible health states are:

  • Healthy.
  • Failed.
  • Rebuilding.
  • Regenerating.
  • Failing redundancy mode.
  • Failed redundancy mode.
  • Failed redundancy failing.

Related:

Outlook Web Access did not initialize.A forms registry file is not valid %1 Line number = %2 Position = %3. The value %4 that is specified for the IsRichClient attribute is not a valid Boolean value. Change this property in the registry to contain True or False.The forms registry is a critical component of Outlook Web Access. If this error is not addressed, users might be unable to access the Outlook Web Access client. For more information about how to troubleshoot the forms registry, see the Help and Support Center.

Details
Product: Exchange
Event ID: 55
Source: MSExchange OWA
Version: 8.0
Symbolic Name: FormsRegistryInvalidUserOfIsRichClient
Message: Outlook Web Access did not initialize.A forms registry file is not valid %1 Line number = %2 Position = %3. The value %4 that is specified for the IsRichClient attribute is not a valid Boolean value. Change this property in the registry to contain True or False.The forms registry is a critical component of Outlook Web Access. If this error is not addressed, users might be unable to access the Outlook Web Access client. For more information about how to troubleshoot the forms registry, see the Help and Support Center.
   
Explanation

This error indicates that the value for the IsRichClient attribute in the specified forms registry is not valid.

   
User Action

To resolve this error, do one or more of the following:

  • Open the specified forms registry and edit the value for the IsRichClient attribute to either true or false, as required by your organization.

  • If you have difficulty resolving the issue, contact Microsoft Customer Support. For information about how to contact support, visit Microsoft Help and Support.

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 file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume %2.

Details
Product: Windows Operating System
Event ID: 55
Source: ntfs
Version: 5.2
Symbolic Name: IO_FILE_SYSTEM_CORRUPT_WITH_NAME
Message: The file system structure on the disk is corrupt and unusable.
Please run the chkdsk utility on the volume %2.
   
Explanation

The file system structure on the volume listed in the message might be corrupt because of one or more of the following reasons:

  • The disk might have bad sectors.
  • I/O requests issued by the file system to the disk subsystem might not have been completed successfully.
   
User Action

Check the state of the file system and repair it if necessary.

To check the state of the file system

  1. Click Start, click Run, and then, in the Open box, typecmd
  2. To determine whether the volume is corrupt, at the command prompt, typechkntfs Drive:
  • If the message “Drive_letter: is dirty” is displayed, the volume is corrupt. In this case, repair the file system.
  • If the message “Drive_letter: is not dirty” is displayed, the volume is not corrupt and no further action is required.

To repair the file system

  1. Save any unsaved data and close any open programs.
  2. Restart the computer.The volume is automatically checked and repaired when you restart the computer.

Alternatively, you can run the Chkdsk tool from the command prompt without shutting down the computer first.

  1. Click Start, click Run, and then typecmd
  2. At the command prompt, type
  3. chkdsk /X Drive:Chkdsk runs and automatically repairs the volume.

If the following message appears, type Y.

“Cannot lock current drive. Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts?”

The next time the computer is started, Chkdsk will automatically run.

If the NTFS 55 message appears regularly, for example daily or weekly, run Chkdsk using the /R command-line option. This option allows Chkdsk to locate bad sectors on the hard disk.

Related:

NTFS – File system corrupt

Details
Product: Windows Operating System
Event ID: 55
Source: ntfs
Version: 5.2.3790.1830
Message: NTFS – File system corrupt
   
Explanation

The file system on the volume might be corrupt due to one or more of the following reasons:

  • The disk might have bad sectors.
  • I/O requests issued by the file system to the disk subsystem might not have been completed successfully.

Cause

  • The disk might have bad sectors.
  • I/O requests issued by the file system to the disk subsystem might not have been completed successfully.
   
User Action

Check the state of the file system and repair it if necessary.

To check the state of the file system

  1. At a command prompt, type chkntfs <drive letter>:
  2. Check the message from chkntfs.
  • If chkntfs displays the message “<drive letter>: is dirty”, the volume is corrupt. In this case, repair the file system using the chkdsk /r command.
  • If chkntfs displays the message “<drive letter>: is not dirty”, the volume is not corrupt and no further action is required.

To repair the file system

  1. Save any unsaved data, close any open programs, and restart the computer.
  2. Microsoft® Windows® automatically runs chkdsk /r on “dirty” (corrupt) volumes to check and repair them.

You can also run chkdsk manually using the following steps.

  • At a command prompt, type chkdsk /x <drive letter>:Chkdsk runs and automatically repairs the volume.
  • If chkdsk displays the following message, type Y. “Cannot lock current drive. Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts?”Windows will automatically run chkdsk the next time the computer is started.

If you regularly see NTFS Event ID 41 or Event ID 55 in Event Viewer, run chkdsk using the /r option. This option allows chkdsk to locate bad sectors on the hard disk.

Related Resources

For more information about the chkdsk /c and /i options, see Knowledge Base article 187941 “An Explanation of CHKDSK and the New /C and /I Switches” at http://go.microsoft.com/fwlink/?LinkId=25770.

For more information about NTFS recoverability, see Knowledge Base article 101670 “Transaction Log Supports NTFS Recoverability,” at http://go.microsoft.com/fwlink/?LinkId=25981.

Related: