Unable to install SNMP on Windows server 2012/2012 R2

x BlueRobot · Jul 30, 2022

Not to worry and those errors are fine, the service shouldn't exist yet until DISM has fully enabled the feature. I just wanted to double check that there wasn't any remnants left behind which may have been preventing the service from starting. Here's some steps to carry out:

Reboot the server if possible - this has resolved odd issues similar to yours in the past
Provide the System and Application event logs
Provide the setupapi.dev.log which is available from %systemroot%\inf\setupapi.dev.log

To export the event logs quickly, then please open an elevated command prompt and enter the following commands:

Rich (BB code):

wevtutil epl SYSTEM %userprofile%\Desktop\Scar_UY_System.evt
wevtutil epl APPLICATION %userprofile%\Desktop\Scar_UY_Application.evt

Scar_UY · Jul 31, 2022

I restarted the server, got the logs you asked for, and tried dism again:

Code:

PS C:\Users\administrator> Install-WindowsFeature SNMP-Service -IncludeAllSubFeature -Verbose
DETALLADO: Instalación iniciada...
DETALLADO: ¿Desea continuar con la instalación?
DETALLADO: Procesamiento de requisitos previos iniciado...
DETALLADO: Requisitos previos procesados correctamente.
Install-WindowsFeature : Error en la solicitud para agregar o quitar características en el servidor especificado.
La operación no se puede finalizar porque es necesario reiniciar el servidor especificado.
En línea: 1 Carácter: 1
+ Install-WindowsFeature SNMP-Service -IncludeAllSubFeature -Verbose
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : DeviceError: (@{Vhd=; Credent...Name=localhost}:PSObject) [Install-WindowsFeature], Exce
   ption
    + FullyQualifiedErrorId : DISMAPI_Error__Failed_Reboot_Required,Microsoft.Windows.ServerManager.Commands.AddWindow
   sFeatureCommand

Success Restart Needed Exit Code      Feature Result
------- -------------- ---------      --------------
False   No             Failed         {}
DETALLADO: Instalación correcta.

Weird thing is, the server had been restarted less than 10 minutes before trying that, tell me if you need more logs, I'll be back at work in a few hours.

Events+setupapi.7z

x BlueRobot · Aug 1, 2022

Could you please provide the setupapi.dev.log? You've provided the setupapi.app.log.

x BlueRobot · Aug 1, 2022

Unfortunately, your event logs don't much useful information apart from the error message you've had and a timeout issue with starting the TrustedInstaller service. I wonder if your CBS log contains anything useful now? Could you please provide the CBS logs along with the setupapi.dev.log?

Scar_UY · Aug 1, 2022

Sorry about that log, here is the right one and CBS: setupapi.dev+CBS.7z

x BlueRobot · Thursday at 4:32 PM

The issue appears to not be with the installation of the associated components but rather with the starting of the SNMP service itself. It doesn't start in time and therefore ends up throwing a timeout error which causes the servicing stack to roll back the changes upon a reboot.

Rich (BB code):

2022-07-31 22:30:00, Info                  CSI    000000c9 Begin executing advanced installer phase 38 (0x00000026) index 24 (0x0000000000000018) (sequence 60)
    Old component: [l:0]""
    New component: [ml:322{161},l:320{160}]"Microsoft-Windows-SNMP-Agent-Service, Culture=neutral, Version=6.3.9600.16384, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    Install mode: install
    Installer ID: {51d504ad-4868-464c-a504-e6cc8a210a97}
    Installer name: [7]"Service"
2022-07-31 22:30:03, Error                 CSI    00000003 (F) Logged @2022/8/1:01:30:00.536 : [ml:98{49},l:96{48}]"Attempting to start service {SNMP} synchronously"
[gle=0x80004005]
2022-07-31 22:30:03, Error                 CSI    00000004 (F) Logged @2022/8/1:01:30:03.583 : [ml:230{115},l:228{114}]"Service did not run. Current state (1) Exit code (0) Service specific exit code (0) Check point (0) Wait hint (0) "
[gle=0x80004005]
2022-07-31 22:30:03, Error                 CSI    00000005@2022/8/1:01:30:03.599 (F) CMIADAPTER: Inner Error Message from AI HRESULT = HRESULT_FROM_WIN32(258)
 [
[53]"Tiempo de espera de la operaci\u00f3n de espera agotado.

"
]
[gle=0x80004005]
2022-07-31 22:30:03, Error                 CSI    00000006@2022/8/1:01:30:03.599 (F) CMIADAPTER: AI failed. HRESULT = HRESULT_FROM_WIN32(258)
    Element:
    [673]"<serviceData xmlns="urn:schemas-microsoft-com:asm.v3" name="SNMP" displayName="@%SystemRoot%\system32\snmp.exe,-3" errorControl="normal" imagePath="%SystemRoot%\System32\snmp.exe" start="auto" type="win32OwnProcess" description="@%SystemRoot%\system32\snmp.exe,-4" objectName="LocalSystem" startAfterInstall="synchronous" sidType="unrestricted" requiredPrivileges="SeChangeNotifyPrivilege,SeSecurityPrivilege,SeDebugPrivilege">

  <failureActions resetPeriod="86400">

    <actions>

      <action type="restartService" delay="60000" />

      <action type="restartService" delay="60000" />

      <action type="none" />

    </actions>

  </failureActions>

</serviceData>"
[gle=0x80004005]

The only thing I can suggest is to remove Symantec Endpoint Protection completely using the official removal tool and then checking if that makes any difference. The CleanWipe tool should have come bundled with endpoint protection.

Scar_UY · Monday at 8:55 AM

That was my first thought, since I saw the service in the services.msc but with missing tabs the first time I tried it.

I'll remove the AV, restart and try again as soon as I can work with the server and try again, I saw the same thing in the other two, It wouldn't surprise me if it was the same problem.

I'll report back as soon as Im able to try.

Scar_UY · Monday at 12:24 PM

Well, uninstalling the AV, restarting and trying again worked for one of the other two servers but not in the other, that's still good! I can't try on this one until the night, I'll report back then.

Scar_UY · 2022-08-09T09:18:16-0400

Sadly, after uninstalling the AV, restarting, waiting for 20 minutes to be sure the server is idle and trying again, I got the same result, I guess I should just give up on this server and focus on the other one?

x BlueRobot · 2022-08-09T11:45:43-0400

If one of the servers is now working correctly then it would suggest there must be something else with this particular one. Have you tried a repair install from the Windows 2012 Server R2 ISO? The ISO is still available from Microsoft Evaluation Center.

Scar_UY · 2022-08-09T12:17:54-0400

I'd try to avoid that route at all costs, since one of the servers that still won't install SNMP (the other one mentioned here: Unable to install SNMP on Windows server 2012/2012 R2) has a lot of stuff running and it'll be a p.i.a. to set it up again if something goes wrong (or restore it from a backup).

I can try that tho in a virtual environment, restore the server as a VM on an isolated network and try there, but I also seriously doubt my boss would let me try that in that server regardless of what the tests on a VM show.

If you still don't hate me too much and have the time, I can run the dism command on this other server with procmon running and upload the results...

Search

Search

Unable to install SNMP on Windows server 2012/2012 R2

x BlueRobot

Administrator, BSOD Academy Instructor, Windows Update Academy Instructor

Scar_UY

Well-known member

x BlueRobot

Administrator, BSOD Academy Instructor, Windows Update Academy Instructor

x BlueRobot

Administrator, BSOD Academy Instructor, Windows Update Academy Instructor

Scar_UY

Well-known member

x BlueRobot

Administrator, BSOD Academy Instructor, Windows Update Academy Instructor

Scar_UY

Well-known member

Scar_UY

Well-known member

Scar_UY

Well-known member

x BlueRobot

Administrator, BSOD Academy Instructor, Windows Update Academy Instructor

Scar_UY

Well-known member