nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
- SolarWinds Academy
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

SolarWinds console is inaccessible due to "solarwinds.apiproxyfactory.TransientApiProxyException"

gaba8696

Screenshot 2026-09-11 133813.png

The SolarWinds console was working fine until yesterday. Today, it became inaccessible due to an expired database password. The password has been reset, and database connectivity has been successfully verified.

However, the Configuration Wizard fails to complete after the password update. During troubleshooting with SolarWinds Support, it was identified that Windows Defender Antivirus may be blocking SolarWinds services from restarting. The vendor recommended configuring antivirus exclusions for SolarWinds files/directories and restoring any blocked or quarantined files.

Any suggestions on the root cause or additional troubleshooting steps would be greatly appreciated.

Find more posts tagged with

orion

npm

Accepted answers

mr.castaneda

Hi,

The TransientApiProxyException on the web console is a symptom of the backend services (particularly SolarWinds Information Service / SWIS) being down because the Configuration Wizard failed during the service restart phase.

Based on the screenshot showing "Unable to query the Service configuration" and the NCM folder creation warning, here are the most effective steps to resolve this:

1. Apply Antivirus Exclusions & Check Quarantined Files

If Windows Defender or your EDR is inspecting/blocking SolarWinds binaries or the Service Control Manager (SCM):

Add folder exclusions for:
- C:\Program Files (x86)\SolarWinds\
- C:\ProgramData\SolarWinds\
- C:\Inetpub\SolarWinds\ (or your website root)
Check Defender's protection history and restore any quarantined SolarWinds executables/DLLs.

2. Run the SolarWinds Permission Checker

The warning regarding C:\ProgramData\SolarWinds\NCM\Config-Archive indicates the wizard is running into file system permission blocks:

Navigate to C:\Program Files (x86)\SolarWinds\Orion\
Right-click OrionPermissionChecker.exe and select Run as administrator.
Click Check, and once completed, click Repair / Fix.

3. Check Windows Services Status

Open services.msc and verify that the SolarWinds Administration Service, SolarWinds Information Service (v3), and SolarWinds Orion Module Engine are not disabled or stuck in a Stopping / Starting state.
Kill any hanging SolarWinds.* processes via Task Manager if necessary.

4. Re-run Configuration Wizard as Administrator

Launch Configuration Wizard using Run as administrator.
Select Database and Services (and Website if needed) to complete the configuration cleanly.

If it still fails:
Check C:\ProgramData\SolarWinds\Logs\Orion\ConfigurationWizard.log around the timestamp of the failure—it will provide the exact exception thrown when querying the service manager.

Hope this helps!

All comments

mr.castaneda

Hi,

Based on the screenshot showing "Unable to query the Service configuration" and the NCM folder creation warning, here are the most effective steps to resolve this:

1. Apply Antivirus Exclusions & Check Quarantined Files

If Windows Defender or your EDR is inspecting/blocking SolarWinds binaries or the Service Control Manager (SCM):

Add folder exclusions for:
- C:\Program Files (x86)\SolarWinds\
- C:\ProgramData\SolarWinds\
- C:\Inetpub\SolarWinds\ (or your website root)
Check Defender's protection history and restore any quarantined SolarWinds executables/DLLs.

2. Run the SolarWinds Permission Checker

The warning regarding C:\ProgramData\SolarWinds\NCM\Config-Archive indicates the wizard is running into file system permission blocks:

Navigate to C:\Program Files (x86)\SolarWinds\Orion\
Right-click OrionPermissionChecker.exe and select Run as administrator.
Click Check, and once completed, click Repair / Fix.

3. Check Windows Services Status

Open services.msc and verify that the SolarWinds Administration Service, SolarWinds Information Service (v3), and SolarWinds Orion Module Engine are not disabled or stuck in a Stopping / Starting state.
Kill any hanging SolarWinds.* processes via Task Manager if necessary.

4. Re-run Configuration Wizard as Administrator

Launch Configuration Wizard using Run as administrator.
Select Database and Services (and Website if needed) to complete the configuration cleanly.

Hope this helps!

gaba8696

@mr.castaneda Thank you for sharing the suggestion. This will really help us resolve the issue. I will let you know if any further assistance is needed.

giovana.prado

you need to run the permission checker tool

gaba8696

@mr.castaneda - I checked with the Cybersecurity team, and they have added an exclusion for the Orion path temporarily. Following that, I completed the recommended troubleshooting steps and re-ran the Configuration Wizard with administrative privileges; however, the same error persists.

Additionally, I attempted to perform a repair of the SolarWinds Platform through Programs and Features, but the process failed with a separate error related to the SolarWinds Orion Module Engine. I also tried to manually restart the service, but it seems Orion module engine service is stuck.

Screenshot 2026-09-12 121526.png

chad.every

@gaba8696 , if this is a system down issue, please make sure you contact support. If you've already done that and have a case number. Please post that here so I can follow it internally.

The error solarwinds.apiproxyfactory.TransientApiProxyException is a generic error and you'll have to look in the logs and find the stack trace to get an idea of what is causing it.

The log file you need to look at is found in the following location:
C:\ProgramData\SolarWinds\Logs\Orion\OrionWeb.log

Can can search for the error in the log and then post the stack trace right after it. Depending on time and if the log has rolled over, it might be in OrionWeb.log.1, .2, .3, etc.