Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
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

Config Archive Job Invalid Directory

Since the upgrade to NCM 7.2 my weekly export of the config database has been failing. I was using an UNC path to it. Now it fails with the following error "Invalid config archive directory". Has anyone else had this issue?

Find more posts tagged with

Accepted answers

All comments

andy_h

Anytime I've seen this, it's always a Windows permission issue with the UNC path. Sure fire way to test this, is to set the group EVERYONE to have full access to that path and then check to see if NCM will validate. I realize that might be a bit overkill, it probably needs either NETWORK SERVICE or SYSTEM to have read/write access to that path. The alternative is to store it locally on the NCM server and then share that path instead.

tgoyette

I am also having the same issue after upgrading to the latest release. For security reasons we don't want to grant access to the directory and we also don't want to keep it on the local server for disaster recovery reasons. Is there not a way to control what domain account is being used to authenticate to the remote server?

wfordham

Same issue. Any solution yet?

mezdem

not sure if this covers ncm folders, but run the OrionPermissionChecker.exe and this fixed similar issues for me.

EchoDelta

I found that when leveraging a UNC to export configs, you need to add the AD computer identity of your NCM box to the UNC share rights.

specifically to that folder only.

mine is \\server\network\configs\, where the NCM server is a R/W/M member of the "configs" directory only

tuttlejs

This worked for me too. thank you!

malmodovar

I am having the same issue. This seems to occur every time we update NCM/NPM. I wrote up a how-to a while ago when we did these upgrades, but I was different from your solution. Previously I would just have to go to the Windows archive server, run services.msc, look for the SolarWinds Job Engine v2 or the SolarWinds Information Service Agents, hit properties and ensure we were using the proper AD service account for the job. Once we verified that it would start working again.

Unfortunately, I am not seeing either one of these agents in the services window (Win 2k8 R2 Standard SP1).

I tried your approach of providing permissions to the NCM server to the archive folder path (providing Full Control, Change and Read access) but I still get the same message in NCM when validating: Invalid config archive directory

Anyone else have a clue?

erickv

Are you guys saying that the network drive where I am backing up the configs needs to be in AD, We try to keep this specific drive out of AD for security reasons. So my question is does the external back location need to be in AD, or can I do it with local credential specific for solarwinds to login via a specific path?

Thanks

EchoDelta

When I set mine up, the way the process ran the AD machine account was the most reliable authenticator.

You could add a credential from one box to another, workgroup style...

If you have a domain CA things get a little more complicated...

Every machine behaves like a standalone domain (when not joined) so the same method should apply.

Erik