Applications Systems
How to run a repair on SAM
This article overviews how to run a repair on SAM if for some reason SAM is not functioning properly
First published date
Last published date
Overview
You can try to repair the SolarWinds Server & Application Monitor if you encounter any of the following issues:
- Missing or corrupt SAM dlls/files
- SAM is not functioning properly
- Missing SAM objects from the Web Console
[STP OneTimeJobResult Thread #0] ERROR SolarWinds.APM.BusinessLayer.JobResultProcessing.JobTypes.OneTimeJobProcessor - Unable to get OneTimeJob result.
Job result error: SolarWinds.JobEngine.WorkerProcess.JobExecutionException: System.TypeInitializationException: The type initializer for 'SolarWinds.APM.Probes.OneTimeJob.ProcessesSnmpOneTimeJob' threw an exception. ---> System.IO.FileNotFoundException: Could not load file or assembly 'SolarWinds.Net.SNMP, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
This is a SAM error found in the SAM BusinessLayer logs for a file general Orion file not being found.
SAM BusinessLayer logs (APM.BusinessLayer.log) are under the C:\ProgramData\SolarWinds\Logs\APM directory.
This is indicating problems with the SAM product.
Product section
Cause
Resolution
- Open Programs and Features
- Find SolarWinds Server and Application Monitor
- Right-click and hit Repair
- Click through the defaults of the Configuration Wizard that pops up and run Configuration Wizard.