SAGE Offline Configuration Tool — “Directory name invalid” on launch

Issue

After launching the SAGE Offline Editor and selecting a configuration, the tool returns “Directory name invalid”, even though the configuration file is in the same directory as the Editor executable. This occurs across multiple Windows versions and compatibility modes.

Product

SAGE RTU

SAGE Offline Configurator Tool (SOCT)

Environment

Windows workstations (various versions); configurations stored on local drives, network shares, or synced folders (e.g., OneDrive/SharePoint/Dropbox).

Cause

These errors are commonly triggered by folder access and path resolution issues—especially when the SOCT or configuration set is located on network-mapped drives, UNC paths, or cloud‑synced folders (e.g., OneDrive). In those scenarios, the tool may not have full access to enumerate the directory, or the path reported to the application is virtualized/sandboxed, causing a “Directory name invalid” response.

Resolution

Follow these steps in order:

1. Check the Run-App Directory
   Ensure both the SOCT and the configuration folder are on a local path (e.g., C:\Sage\OfflineEditor\ and C:\Sage\Configs\).
• Avoid UNC paths (e.g., \\server\share\...) and cloud‑sync locations (OneDrive/SharePoint/Dropbox).
• If needed, copy your configuration set from the network/synced folder to a local C:\ location and retry.
2. Run as Administrator
   Right‑click the SAGE Offline Configurator Tool executable and select Run as administrator.
• This often resolves permission/virtualization issues affecting directory discovery.
3. Check Folder Permissions
   Verify the configuration directory grants your Windows user Read/Write permissions.
• Right‑click folder → Properties → Security → confirm you have Modify/Write.
• Remove Read‑only attributes on the folder and contained files if set.
4. Use the Latest Version
   Install and use the latest available version, currently V2.1.1.7 (at Nov 25)
• If you’re upgrading, unblock the installer (Right‑click → Properties → Unblock), install to a local path, and relaunch as admin.

If the issue persists:

• Shorten overly long paths or remove special characters from folder names.
• Avoid spaces/unicode in top-level directory names as a diagnostic step.
• Test with a new, empty local folder (e.g., C:\Sage\TestConfig\) and a known‑good sample configuration.
• Check that antivirus/EDR isn’t sandboxing the executable; add a temporary allow‑list entry for the Editor and the config folder.

Опубліковано для: Schneider Electric Україна