Event ID 26 — WUA Update Detection

Event ID 26 — WUA Update Detection

Updated: December 13, 2007

Applies To: Windows Server 2008

The Windows Update Agent Update Detection is designed to check for updates and install them on a daily basis. Windows Update Agent can be configured to detect and install updates automatically or can be set to detect updates and manually install them.

Windows Update Agent detects updates every day at user configured scheduled time or at 3:00 A.M. by default and installs them if Automatic Updates is turned on.

Event Details

Product: Windows Operating System
ID: 26
Source: Microsoft-Windows-WindowsUpdateClient
Version: 7.0
Symbolic Name: VISTA_MSG_DETECT_SUCCEEDED
Message: Automatic Updates Agent sucessfully found %1 updates.

Resolve

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

Related Management Information

WUA Update Detection

Windows Update

Related:

Event ID 26 — Remote Desktop Services Client Access License (RDS CAL) Availability

Event ID 26 — Remote Desktop Services Client Access License (RDS CAL) Availability

Published: January 8, 2010

Applies To: Windows Server 2008 R2

When a client—either a user or a device—connects to a Remote Destkop Session Host server, the RD Session Host server determines if a Remote Desktop Services client access license (RDS CAL) is needed. The RD Session Host server then requests an RDS CAL from a Remote Desktop license server on behalf of the client attempting to connect to the RD Session Host server. If an appropriate RDS CAL is available from a license server, the RDS CAL is issued to the client, and the client will be able to connect to the RD Session Host server.

RDS CALs are installed onto a license server by using the Remote Desktop Licensing Manager tool.

Event Details

Product: Windows Operating System
ID: 26
Source: Microsoft-Windows-TerminalServices-Licensing
Version: 6.1
Symbolic Name: TLS_W_REMOVELICENSES
Message: All available “%1!s!” Remote Desktop Services client access licenses (RDS CALs) for product “%2!s!” on Remote Desktop license server “%3!s!” have been removed. Use RD Licensing Manager to re-register the RDS CALs.

Resolve
Reinstall the RDS CALs onto the license server by using the telephone method

To resolve this issue, reinstall the Remote Desktop Services client access licenses (RDS CALs) onto the Remote Desktop license server by using the telephone method. When you call the Microsoft Clearinghouse, ensure that your License Purchase Agreement information is readily available.

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

To reinstall RDS CALs by using the telephone method:

  1. On the license server, open Remote Desktop Licensing Manager. To open Remote Desktop Licensing Manager, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Licensing Manager.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
  3. In the left pane, click All Servers, click the name of the license server, and then on the View menu, click Properties.
  4. On the Connection Method tab, in the Connection method list, select Telephone.
  5. In the Select Country or Region list, select the appropriate country/region.
  6. Click OK to close the Properties dialog box.
  7. Right-click the license server and then click Install Licenses.
  8. Click Next.
  9. On the Obtain client license key pack page, use the telephone number that is displayed to call the Microsoft Clearinghouse, and give the representative your Remote Desktop license server ID and the required information for the licensing program through which you purchased your RDS CALs. The representative then processes your request to install RDS CALs, and gives you a unique ID for the RDS CALs. This unique ID is referred to as the license key pack ID.

    Important:  Retain a copy of the license key pack ID. Having this information with you will facilitate communications with the Microsoft Clearinghouse should you need assistance with recovering RDS CALs.

  10. In the Install Licenses Wizard, on the Obtain client license key pack page, enter the license key pack ID provided by the representative into the boxes provided, and then click Next. The RDS CALs are installed onto the license server.
  11. To complete the process, click Finish. The license server can now issue RDS CALs to clients that connect to a Remote Desktop Session Host server.

Verify

To verify that Remote Desktop Services client access licenses (RDS CALs) are installed and available on the Remote Desktop license server, use the Remote Desktop Licensing Manager tool.

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

To verify that RDS CALs are installed and available:

  1. On the license server, open Remote Desktop Licensing Manager. To open Remote Desktop Licensing Manager, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Licensing Manager.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
  3. In the left pane, expand All Servers, and then click the license server. In the right pane, the type, version, and number of RDS CALs installed on the license server is listed.

Note:  To verify that the Remote Desktop Session Host server can contact a Remote Desktop license server with the appropriate type of RDS CALs, use Licensing Diagnosis in the Remote Desktop Session Host Configuration tool on the RD Session Host server.

Related Management Information

Remote Desktop Services Client Access License (RDS CAL) Availability

Remote Desktop Services

Related:

Event ID 26 — Volume Shadow Copy Service Operations

Event ID 26 — Volume Shadow Copy Service Operations

Updated: January 27, 2011

Applies To: Windows Server 2008

The Volume Shadow Copy Service (VSS) provides the ability to create a point in time image (shadow copy) of one or more volumes that can be used to perform backups. The service is also used during restores of applications.

Event Details

Product: Windows Operating System
ID: 26
Source: VSS
Version: 6.0
Symbolic Name: VSS_ERROR_EVENTSYSTEM_DISABLED
Message: Volume Shadow Copy Service error: Either the COM+ Event System service (EventSystem) or the COM+ System Application service (COMSysApp) is disabled. Please enable the service and try again. %1

Resolve
Ensure that the COM+ Event System service is started

You should check whether the system is running in Safe mode. When your computer is in safe mode, you will see the words Safe Mode in the corners of the display. If it is in Safe mode, restart it in Normal mode. If it is not in Safe mode, you should check whether the COM+ Event System is running.

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

To check that the COM+ Event System service is started:

  1. Click Start, click Administrative Tools, and then click Services.
  2. In the results pane, double-click COM+ Event System.
  3. In Service status, make sure that the status is Started. If the status is not Started, click Start.
  4. Make sure Startup type is set to Automatic.
  5. Click OK.

Verify

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

To verify that the Volume Shadow Copy Service is started:

  1. Click Start, point to Administrative Tools, and then click Services.
  2. In the results pane, double-click Volume Shadow Copy.
  3. In Service status, make sure that the status is Started. If the status is not Started, click Start.
  4. Make sure Startup type is set to Manual.
  5. Click OK.

Related Management Information

Volume Shadow Copy Service Operations

File Services

Related:

Unable to Load Device Driver : device driver could not be loaded.

Details
Product: Windows Operating System
Event ID: 26
Source: Application Popup
Version: 5.0
Symbolic Name: status_log_hard_error
Message: Unable to Load Device Driver : device driver could not be loaded.
   
Explanation

The program could not load a driver because the program user doesn’t have sufficient privileges to access the driver or because the drive is missing or corrupt.

   
User Action

To correct this problem:

  • Reinstall the program to restore the driver to the correct location.

If these solutions do not work, contact Product Support Services.

Related:

An error occurred processing the remote operation finite state machine (FSM). Connection control block: index name. FSM event: name. FSM state: name. [namevaluevaluevaluevalue] (12)

Details
Product: Exchange
Event ID: 26
Source: MSExchangeMTA
Version: 6.5.0000.0
Message: An error occurred processing the remote operation finite state machine (FSM). Connection control block: index name. FSM event: name. FSM state: name. [namevaluevaluevaluevalue] (12)
   
Explanation
The association will be stopped and restarted if necessary. Associations are paths that are opened to other systems. Each association is contained within a connection and is used to transfer messages to a system. You may have multiple associations in each connection.
   
User Action
Use network Monitor to capture Network Traces, then view these traces from Network Monitor for network issues.

If the error persists, stop and restart the message transfer agent service.

If the error still persists, restart Microsoft Exchange Server.

Related:

The driver has detected that device %1 has old or out-of-date firmware. Reduced performance may result.

Details
Product: Windows Operating System
Event ID: 26
Source: Various
Version: 5.0
Component: System Event Log
Message: The driver has detected that device %1 has old or out-of-date firmware. Reduced performance may result.
   
Explanation

The device and driver could run at a faster rate if upgraded firmware were provided.

   
User Action

There is no user action. However, you might want to contact the hardware manufacturer for an upgrade to the firmware for this device.

Related:

Application popup: %1 : %2

Details
Product: Windows Operating System
Event ID: 26
Source: Application Popup
Version: 5.2
Symbolic Name: STATUS_LOG_HARD_ERROR
Message: Application popup: %1 : %2
   
Explanation

The program could not load a driver because the program user doesn’t have sufficient privileges to access the driver or because the drive is missing or corrupt.

   
User Action

To correct this problem:

  • Ensure that the program user has sufficient privileges to access the directory in which the driver is installed.
  • Reinstall the program to restore the driver to the correct location.

If these solutions do not work, contact Product Support Services.

Related:

An error occurred processing the remote operation finite state machine (FSM). Connection control block: {index name}. FSM event: {name}. FSM state: {name}. [{name}{value}{value}{value}{value}] (12)

Details
Product: Exchange
Event ID: 26
Source: MSExchangeMTA
Version: 6.0
Component: Message Transfer Agent
Symbolic Name: MTA00026
Message: An error occurred processing the remote operation finite state machine (FSM). Connection control block: {index name}. FSM event: {name}. FSM state: {name}. [{name}{value}{value}{value}{value}] (12)
   
Explanation
The association will be stopped and restarted if necessary. Associations are paths that are opened to other systems. Each association is contained within a connection and is used to transfer messages to a system. You may have multiple associations in each connection.
   
User Action
Use network Monitor to capture Network Traces, then view these traces from Network Monitor for network issues. If the error persists, stop and restart the message transfer agent service. If the error still persists, restart Microsoft Exchange Server.

Related:

Outlook Web Access was unable to initialize..A base theme could not be found. The base theme must be in a folder with the name “%1”.

Details
Product: Exchange
Event ID: 26
Source: MSExchange OWA
Version: 8.0
Symbolic Name: NoBaseTheme
Message: Outlook Web Access was unable to initialize..A base theme could not be found. The base theme must be in a folder with the name “%1”.
   
Explanation

This Error event indicates that Microsoft® Office Outlook® Web Access did not initialize because the Outlook Web Access base themes folder referenced in the event description does not exist. The base folder contains images and cascading style sheets that are used to control the default appearance of Outlook Web Access for your organization. The base folder is also used by other custom Outlook Web Access themes if they are installed. By default, the base folder is located in C:\Program Files\Microsoft\Exchange Server\ClientAccess\Owa\<version> hemes\.

   
User Action

To resolve the error, replace the base folder and its contents with the files and folders that are located on the Microsoft Exchange Server 2007 DVD. By default, the base folder is located in the \Setup\ServerRoles\ClientAccess\owa\version hemes folder of the Exchange 2007 DVD.

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: