- May 7, 2013
- 10,400
Okay, no problem!
[SOLVED] Unable to install SNMP on Windows server 2012/2012 R2
- Thread starter Scar_UY
- Start date
Scar_UY
Well-known member
- Oct 2, 2019
- 77
Restarted the server, waited 15 minutes, run the Dism command and got the same error, so I restarted again, waited a couple of hours, tried again and the very same result.
I've attached said log just in case it's of any use.
Code:
Lista de características del paquete : Microsoft-Windows-ServerCore-Package~31bf3856ad364e35~amd64~~6.3.9600.16384
Nombre de característica : NetFx4ServerFeatures
Estado : Habilitado
Error: 3017
Error en la operación solicitada. Se requiere un reinicio de sistema para revertir los cambios realizados.
El archivo de registro de DISM se encuentra en C:\Windows\Logs\DISM\dism.log
Last edited:
- May 7, 2013
- 10,400
From the DISM.log:
Could you please provide the CBS hive of this server?
Export CBS hive
Please ensure that the file is a registry hive file.
Rich (BB code):
2022-08-13 00:37:23, Info DISM DISM Package Manager: PID=4056 TID=4068 Feature NetFx4ServerFeatures with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 7(DISM_INSTALL_STATE_INSTALLED) - CDISMPackageFeature::LogInstallStateMapping
2022-08-13 00:37:23, Error DISM DISM Package Manager: PID=4056 TID=4068 Failed to get the State of the Feature - CDISMPackageFeature::Internal_GetCbsState(hr:0x80070bc9)
2022-08-13 00:37:23, Error DISM DISM Package Manager: PID=4056 TID=4068 Failed to get the CBS State of the Feature - CDISMPackageFeature::get_State(hr:0x80070bc9)
2022-08-13 00:37:23, Error DISM API: PID=3960 TID=4052 Failed to get feature state - DismFeature_InternalToPublicEx(hr:0x80070bc9)Could you please provide the CBS hive of this server?
Export CBS hive
- Click on the Start button and in the search box, type regedit
- When you see regedit on the list, right-click on it and select Run as administrator.
- When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing - Once selected, click File > Export....
- Change the Save as type: to Registry Hive Files (.).
- Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
- Right-click on the saved file and choose Send To -> Compressed (zipped) Folder.
- Attach the .ZIP file to your next post.
- If the file is too large to upload here, upload to Dropbox or OneDrive or SendSpace and just provide the link here.
Please ensure that the file is a registry hive file.
Scar_UY
Well-known member
- Oct 2, 2019
- 77
Here it goes: ComponentBasedServicing.7z
- May 7, 2013
- 10,400
Thanks, I can't see anything immediately wrong so let's attempt to gather a little more information using Process Monitor.
Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try DISM /Online /Get-Features just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square icon on the toolbar as shown below.
4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or WeTransfer.
Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try DISM /Online /Get-Features just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square icon on the toolbar as shown below.
4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or WeTransfer.
Scar_UY
Well-known member
- Oct 2, 2019
- 77
- May 7, 2013
- 10,400
Rich (BB code):
2022-08-13 19:51:54, Info CBS Failed to get applicability on updates [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
2022-08-13 19:51:54, Error CBS Failed to call external evaluate applicability on package: Package_4_for_KB4534309~31bf3856ad364e35~amd64~~6.3.1.8, Update: 4534309-9_neutral_GDR [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
2022-08-13 19:51:54, Info CBS Failed to evaluate external applicability for package update: 4534309-136_neutral_PACKAGE [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
2022-08-13 19:51:54, Error CBS Failed to call external evaluate applicability on package: Package_for_KB4534309_RTM_GM~31bf3856ad364e35~amd64~~6.3.1.8, Update: 4534309-136_neutral_PACKAGE [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
2022-08-13 19:51:54, Info CBS Failed to evaluate external applicability for package update: 4534309-242_neutral_PACKAGE [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
2022-08-13 19:51:54, Error CBS Failed to call external evaluate applicability on package: Package_for_KB4534309_RTM~31bf3856ad364e35~amd64~~6.3.1.8, Update: 4534309-242_neutral_PACKAGE [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
2022-08-13 19:51:54, Info CBS Failed to evaluate external applicability for package update: 4534309-243_neutral_PACKAGE [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
2022-08-13 19:51:54, Error CBS Failed to call external evaluate applicability on package: Package_for_KB4534309~31bf3856ad364e35~amd64~~6.3.1.8, Update: 4534309-243_neutral_PACKAGE [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
2022-08-13 19:51:54, Info CBS Failed to call EvaluateApplicability on internal CBS package. [HRESULT = 0x80070bc9]
Rich (BB code):
2022-08-13 19:51:53, Info CBS Failed to evaluate applicability [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
2022-08-13 19:51:53, Info CBS Failed to get applicability on updates [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
2022-08-13 19:51:53, Error CBS Failed to call external evaluate applicability on package: Package_2_for_KB4088879~31bf3856ad364e35~amd64~~6.3.1.4, Update: 4088879-2_neutral_GDR [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
2022-08-13 19:51:53, Info CBS Failed to evaluate external applicability for package update: 4088879-294_neutral_PACKAGE [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
2022-08-13 19:51:53, Error CBS Failed to call external evaluate applicability on package: Package_for_KB4088879_RTM_GM~31bf3856ad364e35~amd64~~6.3.1.4, Update: 4088879-294_neutral_PACKAGE [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
2022-08-13 19:51:53, Info CBS Failed to evaluate external applicability for package update: 4088879-568_neutral_PACKAGE [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
2022-08-13 19:51:53, Error CBS Failed to call external evaluate applicability on package: Package_for_KB4088879_RTM~31bf3856ad364e35~amd64~~6.3.1.4, Update: 4088879-568_neutral_PACKAGE [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
2022-08-13 19:51:53, Info CBS Failed to evaluate external applicability for package update: 4088879-569_neutral_PACKAGE [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
2022-08-13 19:51:53, Error CBS Failed to call external evaluate applicability on package: Package_for_KB4088879~31bf3856ad364e35~amd64~~6.3.1.4, Update: 4088879-569_neutral_PACKAGE [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
2022-08-13 19:51:53, Info CBS Failed to call EvaluateApplicability on internal CBS package. [HRESULT = 0x80070bc9]FRST Registry Search
1. Click your Start button and type in cmd.
2.After you find the Command Prompt, right click on it and select Run as Administrator.
3. Copy and paste the following into the Command Prompt:
reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
4. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
5. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
6. Copy and paste KB4534309 into the Search box and click the Search Registry button.
7. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.
Please repeat the same instructions for the second update as well, which is KB4088879.
- May 7, 2013
- 10,400
One thing which may be worthwhile trying is the following, please boot into the Windows RE and then enter the following command:
Please change the partition letter C:\ if is different for your system.
If successful, then you should see something similar to the following:
Otherwise, please also check that the following file exists and attach it your next post: %systemroot%\WinSxS\pending.xml.
Rich (BB code):
DISM /Image:C:\ /Cleanup-Image /RevertPendingActionsPlease change the partition letter C:\ if is different for your system.
If successful, then you should see something similar to the following:
Rich (BB code):
Reverting pending actions from the image...
The operation completed. Any revert of pending actions will be attempted after reboot.
The operation completed successfully.Otherwise, please also check that the following file exists and attach it your next post: %systemroot%\WinSxS\pending.xml.
Scar_UY
Well-known member
- Oct 2, 2019
- 77
Attached are the requested files, restarting in to Win RE is out of the question at least until tomorrow night, but doable then, there is in fact a file "%systemroot%\WinSxS\pending.xml" in this server.
- May 7, 2013
- 10,400
Thanks for the other two files, could you please provide the pending.xml file? Ideally, we'll want to run the /RevertPendingActions command, but in the meantime, it will be worth taking a look at what is requiring a reboot to take place.
- May 7, 2013
- 10,400
Thanks, it seems like it's trying to revert the changes to the SNMP service but for some reason has got stuck? Could you please provide the COMPONENTS hive for this particular server?
Scar_UY
Well-known member
- Oct 2, 2019
- 77
- May 7, 2013
- 10,400
Thanks, I can't see anything immediately wrong - best to wait and see if the suggested DISM command works.
Scar_UY
Well-known member
- Oct 2, 2019
- 77
This might take a few days, I believe I won't be able to have a chance to do that until saturday, sorry
- May 7, 2013
- 10,400
No worries, just strange that it worked previously and then all of a sudden it's got stuck on reverting back. It's attempting to revert for the same reasons as the other two servers: the service is timing out when it attempts to start automatically.
Scar_UY
Well-known member
- Oct 2, 2019
- 77
After a long wait (last weerend the sales team was going to be working extra so the server couldn't be shutdown, but today it's independence day in my country so I came here to do it) I booted into Windows RE and run the comand, twice:
First time got a warning about scratchdir, so I added the required argument but got the same error 0x8000ffff, dism.log is attached.
- May 7, 2013
- 10,400
Unfortunately, there hasn't been anything particularly useful logged to your DISM.log other than the issues with the feature enumeration which was due to the pending operations regarding the SNMP service. Could you please provide the CBS logs to see if anything more useful has been written to that?
- May 7, 2013
- 10,400
I would change the service start type back to it's default value and see if that makes a difference. Otherwise, we can try and delete the pending.xml file, however, I would rather take that as a last resort and after you've created a backup of the server.
Has Sysnative Forums helped you? Please consider donating to help us support the site!