Event ID 102 — Software Installation Processing

Event ID 102 — Software Installation Processing

Updated: September 21, 2007

Applies To: Windows Server 2008

The Software Installation client-side extension is responsible for installing software, applied through Group Policy, to both computers and users.

Event Details

Product: Windows Operating System
ID: 102
Source: appevt
Version: 6.0
Symbolic Name: EVENT_APPMGMT_INSTALL_FAILED
Message: The install of application %1 from policy %2 failed. The error was : %%%3

Resolve
Correct a failed MSI Group Policy software installation

Possible resolutions include:

Computer-assigned applications

  1. Ensure the computer account has read file permission to the software package assigned in the Group Policy object (GPO).
  2. If the software package is located on a Distributed File System (DFS) share, confirm that the computer account has Read NTFS and Share permissions in all root replicas of the DFS root and on all replica shares of the DFS link. Note: Computer-assigned packages cannot install from servers located in an Active Directory forest that is different from the computer’s forest.

User-assigned applications

  1. Ensure the user account has read file permissions to the software package that is assigned in the GPO.
  2. If the software package is located on a Distribute File System (DFS) share, confirm that the computer account has Read NTFS and Share permissions in all root replicas of the DFS root and on all replica shares of the DFS link.

Collect Software installation and Windows Installer debug logs

  1. Follow Microsoft Knowledgebase Article 249621 to enable Software installation debug logging.
  2. Follow Microsoft Knowledgebase Article 314852 to enable Windows Installer debug logging. Note: You may need to contact the application vendor if Windows Installer reports the error.

Verify

Group Policy Software Installation only occurs during computer startup and user logon. Software installation does not apply to computers or users during ther periodic background refresh. Therefore, you should reboot the computer or log off and log on to determine if Group Policy Software Installation is working correctly for the computer or user.

Group Policy Software Installation is working correctly if the last Group Policy Software Installation event to appear in the System event log has one of the following event IDs:

  • 201- 203
  • 301- 308

Related Management Information

Software Installation Processing

Group Policy Infrastructure

Related:

process name (process id) instanceThe database engine started a new instance (number).

Details
Product: Exchange
Event ID: 102
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: process name (process id) instanceThe database engine started a new instance (number).
   
Explanation
  • ESE event 102 is as follows: The database engine started a new instance (Instance #).
  • ESE event 103 is as follows: The database engine stopped the instance (Instance #).
  • ESE event 104 is as follows: The database engine stopped an instance (Instance #) with error (Error #).

There is only one Jet database engine, ESE.dll, per server. However, there can be one instance of Jet running per storage group. Event 102 signifies that an instance of Jet has started and indicates which instance has started. Event 103 indicates which instance has stopped. These events can occur in the normal scheme of Exchange operations, or they may be associated with errors. Event 103 never has an error mentioned in the Description section of the event.

Event 104 definitely indicates there is a problem and the named instance of Jet has stopped with a definite error associated with it, which is named in the Description section of Event 104.

Event ID 103 has many potential causes – check events in the Application log before and after Event 103 to determine which errors are mentioned in the Description section of other events. Known causes for the database instance stopping with event 103 are as follows:

  • Failing to apply an Exchange service pack for a reinstall or an Exchange-aware restore.
  • Running out of disk space.
  • Attempting to restore multiple storage groups simultaneously.
  • Applying an Exchange service pack, which resulted in the databases becoming inconsistent.

Event ID 104 has a definite set of potential causes. The most likely causes are indicated in the Description section of event 104:

  • Error -1090 = 0xfffffbbe = JET_errInstanceUnavailable = This instance cannot be used because it encountered a fatal error. If ESE encounters this error, it will not be able to roll back any transactions and it will dismount the databases in the Storage Group for that instance of Jet.
  • Error -1022 = 0xfffffc02 = 4294966274 = JET_errDiskIO = Disk IO error. A disk or controller failure has occurred, and access to the entire drive has been lost, sometimes temporarily. Check the System Log for I/O or drive errors near the time of the 439 Event. In this case, you may see Error -1022 in the description of Event ID 104. The -1022 error is a generic error that appears whenever a disk input/output (I/O) problem prevents Exchange from gaining access to a requested page in the database or to a transaction log. Permissions have been removed from the folder where the file resides. The file has been marked read-only. The folder containing the file has been renamed or deleted. Error -1022 can occur when Exchange cannot write to the hard disk, and generates an error message: Either software that has been installed has prevented the write operation or the hard disk itself is corrupted. The event message, which accompanies the error message, refers to an error 1022. This type of error occurs when there is a disk input/output (I/O) error: It may mean that the hard disk has been corrupted. An error 1022 is generated by Exchange whenever Exchange cannot write to the hard disk. Even though you may have a problem with the hard disk (for example, it has been corrupted), this type of error may also be a result of other software that is not compatible with Exchange, which prevents Exchange from writing to the hard disk. This issue can also occur because of incorrect permissions on the Exchsrvr folder structure.
  • Error -510 = 0xfffffe02 = 4294966786 = JET_errLogWriteFail = Failure when writing to log file. This error has both been seen in the Description of Event 104 and has been more commonly with an associated event. Error -510 can be caused by permissions issues, space issues, an
   
User Action
  • For ESE Event ID 103, the resolution depends on the error code in the Description of the associated events in the application log. In many cases, no user intervention will be necessary.
  • For ESE Event ID 104, run “chkdsk /f /r” (without the quotation marks). If chkdsk does not resolve the issue, examine the permissions on the Exchsrvr folder structure. Make sure that SYSTEM has full control of Exchsrvr and all subfolders on each partition that contains Exchange data. If you still cannot mount the databases, troubleshoot any Windows NT file-level antivirus software running on the Exchange server.

Related:

%1 (%2) %3The database engine (%5.%6.%7.%8) started a new instance (%4).

Details
Product: Exchange
Event ID: 102
Source: ESE
Version: 8.0
Symbolic Name: START_INSTANCE_ID
Message: %1 (%2) %3The database engine (%5.%6.%7.%8) started a new instance (%4).
   
Explanation

This Information event frequently occurs with two other related events. The following describes these three events.

  • ESE event 102: The database engine started a new instance (Instance #).

  • ESE event 103: The database engine stopped the instance (Instance #).

  • ESE event 104: The database engine stopped an instance (Instance #) with error (Error #).

There is only one ESE database engine, Ese.dll, per server. However, there can be one instance of ESE running per storage group. Event 102 signifies and indicates which instance of ESE has started. Event 103 indicates which instance has stopped. However, an error is never mentioned in the description section of event 103. Event 104 indicates a problem and that the named instance of ESE has stopped with a definite error associated with it. The error is named in the description section of event 104.

These events can occur in the ordinary operation of an Exchange Server environment, or they may be associated with errors.

   
User Action

To resolve ESE Event ID 102, examine related events in the Application log that occur before and after ESE event 103. These related events provide more information about the root cause of this error. The resolution of ESE event 102 depends on the error code in the description of the associated events.

For more information about ESE event 103, search for information about that event in the Errors and Events Message Center.

For more information about ESE event 104, search for information about that event in the Errors and Events Message Center.

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:

%1 (%2) %3The database engine started a new instance (%4).

Details
Product: Windows Operating System
Event ID: 102
Source: ESENT
Version: 5.2
Symbolic Name: START_INSTANCE_ID
Message: %1 (%2) %3The database engine started a new instance (%4).
   
Explanation
There is only one Jet database engine, ESE.dll, per server. However, there can be one instance of Jet running per storage group. Event 102 signifies that an instance of Jet has started and indicates which instance has started.
   
User Action
No user action is required.

Related:

%1 (%2) %3 The database engine started a new instance (%4).

Details
Product: Exchange
Event ID: 102
Source: ESE
Version: 6.5.7596.0
Message: %1 (%2) %3 The database engine started a new instance (%4).
   
Explanation

Event ID 102 frequently occurs with other related events. The following describes these three events.

  • ESE event 102   The database engine started a new instance (Instance #).

  • ESE event 103   The database engine stopped the instance (Instance #).

  • ESE event 104   The database engine stopped an instance (Instance #) with error (Error #).

There is only one Jet database engine, Ese.dll, per server. However, there can be one instance of Jet running per storage group. Event 102 signifies that an instance of Jet has started and indicates which instance has started. Event 103 indicates which instance has stopped. These events can occur in the ordinary operation of a Microsoft® Exchange Server environment, or they may be associated with errors. An error is never mentioned in the description section of event 103. Event 104 definitely indicates that there is a problem and that the named instance of Jet has stopped with a definite error associated with it. The error is named in the description section of event 104.

   
User Action

To resolve ESE Event ID 102, examine related events in the Application log that occur before and after ESE event 103. These related events provide more information about the root cause of this error. The resolution of ESE event 102 depends on the error code in the description of the associated events.

For more information about the related ESE event 103, search for information about that event in the Errors and Events Message Center.

For more information about ESE event 104, search for information about that event in the Errors and Events Message Center.

Related:

Exchange Search Indexer has failed to crawl the mailbox (%1) due to an exception (%2).

Details
Product: Exchange
Event ID: 102
Source: MSExchange Search
Version: 8.0
Symbolic Name: FailedToCrawlMailbox
Message: Exchange Search Indexer has failed to crawl the mailbox (%1) due to an exception (%2).
   
Explanation

This Error event indicates that the Microsoft Exchange Search service did not crawl the mailbox because the search service was unable to log on to the mailbox. The error can occur in the following conditions:

  • The mailbox is disabled or deleted

  • In a Move Mailbox operation, Active Directory replication has not yet occurred

The error means that an index for the mailbox is not created. Because of this error, search will be slower for the affected user. The event description will provide the affected mailbox GUID and the exception that caused the event for the specified mailbox.

   
User Action

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

  • Wait for Active Directory replication to occur.

  • Check the status of a disabled or deleted mailbox.

  • Look at the Application event log for a detailed description of the event.

  • Get additional help by posting the issue at Newsgroups: Exchange Server and Outlook.

  • Contact Microsoft Product Support Services with the error code. For more information, visit the Contact Us page of the Microsoft Help and Support Web site.

Note  If you aren’t already doing so, consider running the tools that 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 mailflow, and better manage disaster-recovery scenarios. Go to the Toolbox node of Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related: