| Event Information | According to Microsoft :
Cause :
This event is logged when Windows Servicing identified that package is not applicable for this computer.
Resolution :
Obtain a valid package or check the logs
The package might not be applicable to this computer. To resolve this problem, do the following: - To determine whether this computer supports the package:
- First search online for information about any dependencies and architecture requirements. You should check the requirements on the Web site you downloaded the package from. You can also search the Microsoft Knowledge Base for a KB article for the package. You can often find the Knowledge Base number in the .mum file of the package (search for KB ), or in the error message.
- Look at the last error in the Component-Based Servicing (CBS) log (located at %windir%\logs\cbs\cbs.log) and ensure that Applicability:4 is specified in the message. If the applicability attribute is not 4, then the package does not apply to this computer.
- Install any dependencies that the computer is missing, or obtain a valid package. If you think the package is applicable, download the package again.
- Try the operation again.
If you determine that the package is applicable to the computer, but you continue to receive this error, then you have encountered a more complex issue. In this case, you may need to call Customer Service and Support (CSS) in order to resolve the problem. If you want to try to determine the cause yourself, you can diagnose the Windows Update log (%windir%\WindowsUpdate.log), the Component-Based Servicing log (%windir%\logs\cbs\cbs.log), and driver logs. - Windows Update log (%windir%\WindowsUpdate.log)
- Component Based Servicing log (%windir%\logs\cbs\cbs.log)
- Windows Side-by-Side Pending log (%windir%\winsxs\pending.xml)
- Windows Side-by-Side Pending Bad log (%windir%\winsxs\pending.xml.bad)
- Pending Operations Queue Exec log (%windir%\winsxs\poqexec.log)
- DPX Setup Act log (%windir%\logs\DPX\setupact.log)
Verify :
If you did not receive a message in the user interface that confirmed that the package was installed or uninstalled, then you may have to try several methods to confirm that the package is installed or uninstalled. Use the following methods in the specified order.
Method 1
If you were installing or uninstalling an optional component (that would appear in Windows Features) using OCsetup or Package Manager, open Control Panel, click Programs , and under Programs and Features , click Turn Windows features on or off . Verify that the component is listed or not listed.
Method 2
If you were installing or uninstalling a package using Package Manager then in Control Panel, click Programs , and under Programs and Features , click View installed updates . Verify that the item is either listed or unlisted. For example, if you are installing an update associated with a Microsoft Knowledge Base article, then the KB number will be listed.
Method 3
Open Event Viewer and verify that Component-Based Servicing (CBS) raised one of the following events. - Event 4373: Windows Servicing successfully set package () state to ()
- Event 4372: Windows Servicing is setting package () state to ()
- Event 4371: Windows Servicing started a process of changing package () state from () to ()
Note : If you receive Event 4376 ( Servicing has required reboot to complete the operation of setting package () into () state ), then the package may be reported as installed even though you still need a restart the computer to complete the installation.
Method 4
If you know the assemblyIdentity name of the package (you can find this in the .mum file—for example, SQL-Server-2005-Embedded-Edition-Windows-Package ), then use Registry Editor (Regedit.exe) to check the installation status of that package under the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages . - If you were installing, check that your package is listed and that the value for the CurrentState key is one of the following: 7 (installed), 6 (installation is pending a reboot), or 4 (all of the manifests and files are present on the computer, but the files have not been projected and are not being used by the computer).
- If you were uninstalling, check that your package is not listed, or that it is listed and the value for the CurrentState key is 0 (absent) or 5 (removal is pending a restart).
Method 5
- Use the Windows Management Instrumentation (WMI) event handler. For more information, see Win32_QuickFixEngineering
|