Event ID 1018 — Windows Installer Application Installation

Event ID 1018 — Windows Installer Application Installation

Updated: December 11, 2007

Applies To: Windows Server 2008

Microsoft Windows Installer is used to install applications on a computer.

Event Details

Product: Windows Installer – Unicode
ID: 1018
Source: MsiInstaller
Version: 4.0
Symbolic Name: EVENTLOG_TEMPLATE_APPHELP_REJECTED_PACKAGE
Message: The application ‘%1’ cannot be installed because it is not compatible with this version of Windows. Contact the application vendor for an update.

Resolve
Review the system log file

Microsoft Windows Installer encountered an error while installing, updating, or removing an application. For more information about the error, you will need to open Event Viewer and examine the System log file.

To review the system log file for Windows Installer events:

  1. Click Start, point to Administrative Tools, and then click Event Viewer.
  2. In the navigation pane, find the System event log.
  3. In the Actions pane, click Filter current log…
  4. In the Filter Current Log dialog box, select the Filter tab and then select MsiInstaller from the Event Sources drop-down.
  5. Review the most recent Windows Installer events to determine the cause of the issue. In addition to the Windows Installer events, you should also review the other system events to determine if a related issue may be the cause of the Windows Installer error.
  6. If you cannot resolve the issue based on the information in the event log, try reinstalling the application.

Note: If Windows Installer logging is not enabled, no information will be available in Event Viewer. For more information about Windows Installer logging, see http://support.microsoft.com/kb/223300.

Verify

You can use Programs and Features to verify an application is installed, uninstall applications, and change the application’s configuration by adding or removing options. If the application is not listed, it may not be configured properly or written for a different version of Windows. Reinstalling the application may resolve a configuration problem. To reinstall the application, consult the information that came with the application.

To verify the application is installed:

  1. Click Start, and then click Control Panel.
  2. Double-click Programs and Features.
  3. Verify the application appears in the list of installed programs.

Note: Only applications that are written for Windows will appear in Programs and Features. If you don’t see the application listed and you want to uninstall the application, check the information that came with your software, or go to the manufacturer’s website. Most programs install themselves in the C:\Program Files folder. Check this folder because some programs also include an uninstall program that you can use to remove the software.

Related Management Information

Windows Installer Application Installation

Windows Installer Service

Related:

Event ID 1018 — IIS W3SVC Performance Counter Availability

Event ID 1018 — IIS W3SVC Performance Counter Availability

Updated: March 24, 2009

Applies To: Windows Server 2008 R2

The Internet Information Services (IIS) World Wide Web Publishing Service (W3SVC) collects HTTP-specific performance counters for Web sites. The W3SVC initializes the counters and receives them from HTTP.sys, the protocol listener for HTTP. If W3SVC is not available, HTTP performance counter data cannot be gathered.

Event Details

Product: Internet Information Services
ID: 1018
Source: Microsoft-Windows-IIS-W3SVC
Version: 7.5
Symbolic Name: W3SVC_PERF_COUNTER_INITIALIZATION_FAILURE
Message: The World Wide Web Publishing Service was not able to initialize performance counters. The service will run without the performance counters. Please restart the World Wide Web Publishing Service to reinitialize the performance counters. The data field contains the error number.

Resolve
Restart W3SVC

If Web sites require updated performance counters, the World Wide Web Publishing Service (W3SVC) must be restarted.

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

To restart the W3SVC: 

  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 command prompt, type NET STOP W3SVC.
  3. At the command prompt, type NET START W3SVC.

Verify

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

To verify that a performance counter is functioning correctly:

  1. Click Start, Administrative Tools, Server Manager.
  2. In the left pane of Server Manager, expand Diagnostics, then expand Reliability and Performance.
  3. Expand Monitoring Tools, then click Performance Monitor. The Performance Monitor window appears in the middle pane.
  4. In the Performance Monitor toolbar, click the Add icon (the green plus sign.) The Add Counters screen appears.
  5. Under Available counters, select the counter you want to verify.
  6. On the bottom of the screen, click Add. In the right pane, the counter appears in the Added counters window.
  7. Click OK.
  8. At the bottom of the screen, the name of the counter should be visible in the Counter field.

    Note: If data for the counter does not appear, check the Application log for Event ID 2006 with source IIS-W3SVC-PerfCounters. You may receive this error if there is no data available for the counter.

Related Management Information

IIS W3SVC Performance Counter Availability

Internet Information Services (IIS) 7.5

Related:

An error occurred processing the meeting message with subject %1 in mailbox %2. Error: %3

Details
Product: Exchange
Event ID: 1018
Source: MSExchange Store Driver
Version: 8.0
Symbolic Name: ProcessingMeetingMessageFailure
Message: An error occurred processing the meeting message with subject %1 in mailbox %2. Error: %3
   
Explanation

This Warning event indicates that the store driver attempted to process a meeting request but that the action failed.

The store driver is a component of the Hub Transport server role that delivers inbound messages to Exchange stores and 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.

   
User Action

To resolve this warning, use the Microsoft 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.

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:

Event sink registration for SMTP virtual server failed. Error code is .

Details
Product: Exchange
Event ID: 1018
Source: MSExchangeMU
Version: 6.5.6940.0
Component: Microsoft Exchange Metabase Update
Message: Event sink registration for SMTP virtual server <instance> failed. Error code is <error code>.
   
Explanation

When a new Simple Mail Transfer Protocol (SMTP) virtual server is created, event sinks are registered for it. Occasionally, the metabase update service fails to register these event sinks and the SMTP virtual server does not work properly.

This event occurs at the time of the virtual server creation. You will receive the following phrase in the Event Description:

Event sink registration for SMTP virtual server [/LM/SMTPSVC/VS number] failed. Error code is [error number] (error text.). SMTP event bindings are missing from the virtual server entry in the metabase. As a result, the NTFS driver is failing to allocate a message.

The most common error codes noted in the Description section of the event are 80020005 (Type mismatch.) and 80041002.

   
User Action

Delete the new SMTP Virtual Server. Restart Exchange server. Recreate the SMTP virtual server for the event sink to register on the IIS metabase again.

Related:

Process %1 (PID=%2). Failed to connect to remote server %3. The remote server may be down, or its Server service may not be running.

Details
Product: Exchange
Event ID: 1018
Source: MSExchangeFDS
Version: 8.0
Symbolic Name: RemoteServerNotAvailable
Message: Process %1 (PID=%2). Failed to connect to remote server %3. The remote server may be down, or its Server service may not be running.
   
Explanation

This Warning event indicates that the Microsoft Exchange File Distribution service could not connect to the remote server specified in the event description. The File Distribution service synchronizes offline address book files between Exchange servers that have the Mailbox server role and the Client Access (CAS) server role installed, and where the Mailbox server is using the ExchangeOAB file share. This event may occur if the ExchangeOAB file share is not available or the server that has ExchangeOAB file share is down.

   
User Action

To resolve this Warning event, follow these steps:

  • Make sure that the remote server specified in the event description is working correctly. You can also use the Ping or PathPing command-line tools to test basic connectivity. For more information, see Microsoft Knowledge Base article 325487, How to troubleshoot network connectivity problems.

  • Make sure that the Windows Server service on the specified remote server is running. You can use Windows Services console to verify this step.

  • Make sure that ExchangeOAB file share on the specified remote server can be accessed from the Exchange server that logged this event.

  • Review the Application log for related events. Events that occur immediately before and after this event may provide more information about the root cause of this warning.

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 account ‘%1’ provided valid credentials, but it does not have submit permissions on Receive connector ‘%2’ and so authentication has failed.

Details
Product: Exchange
Event ID: 1018
Source: MSExchangeTransport
Version: 8.0
Symbolic Name: SmtpReceiveAuthorizationSubmitRejected
Message: The account ‘%1’ provided valid credentials, but it does not have submit permissions on Receive connector ‘%2’ and so authentication has failed.
   
Explanation

This Warning event indicates that the security principal that is trying to use the specified Receive connector does not have the Ms-Exch-SMTP-Submit permission assigned to it on the Receive connector. Security principals are user accounts, computer accounts, or security groups.

The Ms-Exch-SMTP-Submit permission allows the Receive connector to accept the SMTP MAIL FROM: command from the connecting messaging server.

Receive connectors grant permissions to security principals or to permission groups. Permission group members and their assigned permissions are not modifiable. All permission groups grant the Ms-Exch-SMTP-Submit permission on the Receive connector.

   
User Action

To resolve this warning, do one of the following:

  • Use the PermissionGroups parameter on the Set-ReceiveConnector in the Exchange Management Shell to assign the appropriate permission group to the Receive connector.

  • Use the Set-ADPermissions cmdlet in the Exchange Management Shell to grant the Ms-Exch-SMTP-Submit permission to an appropriate security principal, and then assign that security principal to the Receive connector.

For more information, see the following Microsoft Exchange Server 2007 Help topics:

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: