Network Management

NCM Nodes fail with Permission denied during file transfer attempts with SolarWinds SFTP/SCP Server tool

This article discusses potential issues regarding why an NCM node fails to send a config file to the SolarWinds SFTP/SCP Server tool. It will go over what logs to review, troubleshoot and resolve the issue.

First published date

9/25/2025 1:57 PM

Last published date

7/29/2026 6:31 PM

Overview

NCM Nodes fail with Permission denied during file transfer attempts with the SolarWinds SFTP/SCP Server tool.

Check the Sftpserver.log file on the node's assigned polling engine under C:\ProgramData\SolarWinds and search for the failing node's IP for the most recent entries.

For the Potential SCP credential password authentication bug, log entries will appear as:

2025-08-08 17:46:13,750 [6] INFO  SolarWinds.Sftp.Service.Listener - LogonFail Unknown Authentication failed for user SCP-User from IP X.X.X.X; bad username or password.
2025-08-08 17:46:15,750 [6] INFO  SolarWinds.Sftp.Service.Listener - Logon Unknown Authenticated user SCP-User from IP X.X.X.X.

For destination filename or filepath issues, log entries will appear as:

2025-08-08 17:45:59,000 [6] INFO  SolarWinds.Sftp.Service.Listener - FileUploadFail Unknown File upload rejected; user nms-user from IP X.X.X.X; path "nd10tjtxh4f.config".
OR
2025-08-08 17:45:59,000 [6] INFO  SolarWinds.Sftp.Service.Listener - FileUploadFail Unknown File upload rejected; user nms-user from IP X.X.X.X; path "/nd10tjtxh4f.config".

Product section

Network Configuration Manager

Cause

For SCP credential authentication failure, the password set for the SCP User may contain ending ASCII characters that cause the issue.

There is currently a bug with the SolarWinds SFTP/SCP Server for passwords ending with characters from the list below:

, ] ^ _

For file upload rejected issues, the issue may be either:

Mismatched SolarWinds SFTP/SCP Server tool and NCM Settings > SCP Server Settings values for the root directory.

The device template contains either the "/" for the destination filename when not needed, or there is an extra "/".

 

Resolution

This issue has been addressed in NCM 2026.2. Consider upgrading your environment. If you cannot upgrade, use the workarounds below.

 

Workaround 1:

For SCP credential authentication issues that potentially has the bug where the password ends with the ASCII characters, log into the Polling Engines, open the SolarWinds SFTP/SCP Server tool, go to users and update the passwords on the SCP-User failing to not contain at the end with the following:

, ] ^ _

Afterwards, log in to the SolarWinds Web Console, navigate to Settings > All Settings > NCM Settings > SCP Server and update the password for the failing SCP-User.

Note: A future update to the SolarWinds SFTP/SCP Server tool will permanently fix the issue of allowing ASCII characters.

Workaround 2:

For file upload rejected issues, start by RDP to the Polling Engines, open the SolarWinds SFTP/SCP Server tool, under the General Tab review the "Root Directory" path.

Next, log in to the SolarWinds Web Console and navigate to Settings > All Settings > NCM Settings > SCP Server. Review the "Root Directory" path; both the SolarWinds SFTP/SCP Server tool and the NCM Settings must match for the root directory path.

If the file upload rejected log showed that the destination filename has at the beginning the "/" character (example: "/kdj2dkn3.config", review the assigned device template and confirm the command syntax.

Here is an example command for a Palo Alto PAN-OS device:

<Command Name="DownloadConfigIndirectSCP" ConfigType="Running" Value="${TransferProtocol} export configuration from running-config.xml to ${SCPServerUserName}@${SCPStorageAddress}:/${StorageFilename}${CRLF}${SCPServerPassword}"/>

In some cases, when testing directly from PuTTY, the "/" is not needed and can be removed.

In some cases, there are two "/" and one must be removed.