Event ID 1014 — Windows Installer Service Availability

Event ID 1014 — Windows Installer Service Availability

Updated: December 16, 2008

Applies To: Windows Server 2008 R2

The Windows Installer service is an operating system component that centrally manages application installation and configuration tasks, and also the process of uninstalling applications.

Event Details

Product: Windows Installer – Unicode
ID: 1014
Source: MsiInstaller
Version: 5.0
Symbolic Name: EVENTLOG_TEMPLATE_INCORRECT_PROXY_REGISTRATION
Message: Windows Installer proxy information not correctly registered

Resolve
Reregister the Windows Installer service

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

To reregister Windows Installer:

Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.

  1. Locate the following registry key in the Windows registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer
  2. Verify that the ImagePath string contains the correct path for the Msiexec.exe file: Drive:\Windows\System32\Msiexec.exe /V, where Drive is the drive where Windows is installed.
  3. Restart Windows in safe mode, and then register the Msiexec.exe file by typing msiexec /regserver at an elevated command prompt.
  4. Shut down Windows, and then restart it in standard mode.

Verify

To verify that Windows Installer is available on your computer:

  1. Click Start, click Control Panel, double-click Administrative Tools, and then double-click Services.
  2. Look for Windows Installer in the list of results displayed in the Services window. The presence of Windows Installer in this list indicates that Windows Installer is indeed installed and available on your computer.

Related Management Information

Windows Installer Service Availability

Windows Installer Service

Related:

Event ID 1014 — RemoteApp and Desktop Connection Configuration

Event ID 1014 — RemoteApp and Desktop Connection Configuration

Published: January 8, 2010

Applies To: Windows Server 2008 R2

RemoteApp and Desktop Connection is configured by using the Control Panel.

Event Details

Product: Windows Operating System
ID: 1014
Source: Microsoft-Windows-RemoteApp and Desktop Connections
Version: 6.1
Symbolic Name: TSWORKSPACE_SETUP_PERMISSION_DENIED_ERROR
Message: The credentials that were used to connect to %1 did not work.Connection name: %1Connection URL: %2Error code: %3, %4″

Resolve
Provide proper credentials

When configuring a RemoteApp and Desktop Connection, you must have proper credentials to access the RD Web Access server.

To provide proper credentials:

  1. On the client computer, if you are prompted for credentials, you must enter the appropriate user name and password.
  2. In the User name box, type the user name of a user account who has the appropriate credentials to the RD Web Access server.
  3. In the Password box, type the password of the user account.
  4. Click OK.

Verify

To verify that RemoteApp and Desktop Connection is configured correctly, you should start a RemoteApp program that is published by using RemoteApp and Desktop Connection.

To start a RemoteApp program that is published by using RemoteApp and Desktop Connection:

  1. On a client computer, click Start, point to All Programs, point to RemoteApp and Desktop Connections, point to Enterprise Remote Access, and then click a RemoteApp program.
  2. Verify that the RemoteApp program opens successfully.

Related Management Information

RemoteApp and Desktop Connection Configuration

Remote Desktop Services

Related:

The UM worker process (UMWorkerProcess.exe) encountered an unhandled exception “%1” during an incoming call with ID “%2”. The call was disconnected.

Details
Product: Exchange
Event ID: 1014
Source: MSExchange Unified Messaging
Version: 8.0
Symbolic Name: ExceptionDuringCall
Message: The UM worker process (UMWorkerProcess.exe) encountered an unhandled exception “%1” during an incoming call with ID “%2”. The call was disconnected.
   
Explanation

This Error event indicates that an unhandled exception occurred in the Microsoft® Exchange Server 2007 Unified Messaging (UM) worker process (UMWorkerProcess.exe) during an incoming call. As a result, the incoming call was disconnected. This event may occur if the following conditions are true:

  • An unexpected error is generated within the UM worker process.

  • There is no mechanism defined by the UM worker process to handle the error.

   
User Action

To resolve this error, follow one or more of these steps:

  • Restart the Microsoft Exchange Unified Messaging service.

  • Restart the Unified Messaging server.

If this error frequently occurs, contact Microsoft Product Support. For contact information, visit the Microsoft Help and Support Web site.

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:

Process %1 (PID=%2). Failed to read from metabase. Metabase object %3 can not be found. OAB synchronization suspended.

Details
Product: Exchange
Event ID: 1014
Source: MSExchangeFDS
Version: 08.01.0106.000
Symbolic Name: MetabaseOperationFailedExistsObject
Message: Process %1 (PID=%2). Failed to read from metabase. Metabase object %3 can not be found. OAB synchronization suspended.
   
Explanation

This Error event indicates that the Microsoft File Distribution service could not find one or more offline address book objects in the metabase. The metabase contains configuration information about the offline address book virtual directory that links to the offline address book objects. The File Distribution service requires offline address book virtual directory information to distribute offline address book files.

This event may occur because of corrupted metabase or configuration problems in offline address book virtual directory.

   
User Action

To resolve this error, follow these steps.

  • Open the Internet Information Services (IIS) Manager console.

  • Expand the Web Sites container and then expand Default Web Site.

  • Make sure that the Default Web Site container has the OAB virtual directory. If the OAB virtual directory does not exist, you can create a new virtual directory using New-OABVirtualDirectory Exchange Management Shell command.

You may have to re-associate existing offline address books with the new OAB virtual directory. This process is also referred to as enabling Web-based distribution.

  • Review the Application event log for related events. These related events may indicate a corrupted metabase. If the metabase is corrupted, you must restore the metabase. For more information, see Working with the Metabase (IIS 6.0) on Microsoft Windows Server 2003 TechCenter.

Note  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:

Failed to copy the user default profile to a local copy for user %1.

Details
Product: Windows Operating System
Event ID: 1014
Source: Winlogon
Version: 5.0
Component: Application Event Log
Symbolic Name: EVENT_COPY_USER_DEFAULT_FAILED
Message: Failed to copy the user default profile to a local copy for user %1.
   
Explanation

The user default profile is the standard Windows 2000 profile. The user can modify this profile, and save it as the user’s personal profile. This event record indicates that the changes that the user made to the default profile were not copied to the local system. The user will have to use the user default profile at the next logon session.

Related:

An error occurred calling into the Microsoft Exchange Information Store service: the call to %1 failed with error %2.

Details
Product: Exchange
Event ID: 1014
Source: IMAP4SVC
Version: 6.5.7596.0
Message: An error occurred calling into the Microsoft Exchange Information Store service: the call to %1 failed with error %2.
   
Explanation

This Error event indicates that users using Internet Message Access Protocol version 4rev1 (IMAP4) clients are unable to access their mailboxes or public folders on the Exchange 2003 Server.

This event may be caused by of one of the following factors:

  • The IMAP4 service is not enabled on the front-end or back-end Exchange 2003 servers

  • Users cannot log on to the Exchange server

  • The Exchange Information Store service takes a long time to start

Note   The IMAP4 Internet-based protocol engine enables Internet-based clients, such as Microsoft Outlook Express, to communicate with Exchange 2003. Microsoft Exchange IMAP4 enables mail access with some advanced features, such as folder synchronization and browsing subjects before downloading messages to the client.

   
User Action

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

  • Check to see whether IMAP4 service is enabled on the front-end or back-end servers

  • Check the application event log for information on the Exchange Information Store service (MSExchangeIS).

For more information see the following articles:

Related:

An interoperability error occurred with entity {object name}. Association error, Session Protocol Data Unit (SPDU) length exceeds the total chunked data. Missing data length: {value}, Control Block index: {index name}. Contact Microsoft Technical Support. [{value}{value}{value}{value}] (14)

Details
Product: Exchange
Event ID: 1014
Source: MSExchangeMTA
Version: 6.0
Component: Message Transfer Agent
Symbolic Name: MTA01014
Message: An interoperability error occurred with entity {object name}. Association error, Session Protocol Data Unit (SPDU) length exceeds the total chunked data. Missing data length: {value}, Control Block index: {index name}. Contact Microsoft Technical Support. [{value}{value}{value}{value}] (14)
   
Explanation
The diagnostics logging levels of the message transfer agent (MTA) interface and interoperability categories should be increased to create interoperability logs.These logs are text logs that consist of the binary contents of communication among MTAs in different sites and between MTA and client applications within a site. They are stored in the \Exchsrvr\Mtadata directory. The current log is always named Bf0.log. Prior logs are named Bfx.log, where x increases as the age of the log increases.
   
User Action
To help Microsoft Product Support Services track down the problem, create log files. For more information, see Knowledge Base articles Q163032 and Q168906. To create Ap*.log files, in the Diagnostics Logging tab of the Server Properties dialog box, select MSExchangeMTA and set the logging level of the Interoperability and Interface categories to Maximum. To create Bf*.log files, set the logging level of the APDU and X.400 Service categories to Maximum.Save all MTA log files (Mtadata\*.log), Event Viewer output, and database files. Contact Microsoft Product Support Services.You can enable text event log files (Ev*.log) by modifying the Registry. Contact Microsoft Product Support Services for assistance.

Related:

The store driver failed to open the message item for event %1 mailbox %2 MDB %3. An NDR won’t be generated.

Details
Product: Exchange
Event ID: 1014
Source: MSExchange Store Driver
Version: 8.0
Symbolic Name: NoMessageForNDR
Message: The store driver failed to open the message item for event %1 mailbox %2 MDB %3. An NDR won’t be generated.
   
Explanation

The Warning event indicates that that the Microsoft® Exchange store driver attempted to open a message item, but that the action failed. Exchange was unable to generate a non-delivery report (NDR) because the message could not be located.

The store driver is a software component of the Hub Transport server role that delivers inbound messages to Exchange stores, the databases that contain public folder and mailbox stores. The store driver also retrieves messages from a user’s outbox and submits them for delivery. For information about the store driver component of Exchange transport, see Transport Architecture in the Exchange Server 2007 online Help.

   
User Action

To resolve this warning, use the Exchange Server 2007 message tracking feature to try to determine the root cause of this warning. For example, search the message tracking log files for messages delivered to the mailbox specified in the event description. For more information about tracking messages, see Managing Message Tracking in the Exchange Server 2007 online Help.

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 Microsoft Exchange ActiveSync process has been shut down Process id: [%1]. This event typically results from a shortage of system memory from overload. If this event is logged frequently, review the Application log for related events. The Client Access Server that the Microsoft Exchange ActiveSync service runs on may need to be load balanced to reduce system overload.

Details
Product: Exchange
Event ID: 1014
Source: MSExchange ActiveSync
Version: 8.0
Symbolic Name: AirSyncUnloaded
Message: The Microsoft Exchange ActiveSync process has been shut down Process id: [%1]. This event typically results from a shortage of system memory from overload. If this event is logged frequently, review the Application log for related events. The Client Access Server that the Microsoft Exchange ActiveSync service runs on may need to be load balanced to reduce system overload.
   
Explanation

This Information event indicates that the Microsoft.Exchange.AirSync.dll has been unloaded. This event is logged under the following operating conditions:

  • If any required services have been shut down.

  • If the Internet Information Services (IIS) server has stopped.

  • If the Exchange ActiveSync Virtual directory is stopped.

  • If the application pool is stopped.

    If you have manually configured ActiveSync to shut down the worker process after it is idle for a specific number of minutes, this event may also be logged. In this scenario, if Exchange ActiveSync detects that the Exchange ActiveSync DLL has not been used in a specific period of time, it will unload that DLL.

   
User Action

If one of these conditions occurred during typical operations, you can safely ignore this event. If one of these conditions occurred outside typical operations, review the Application log for other related events. You may have to check your IIS configuration settings.

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: