Structure of the installation
Scopevisio consists of three layers, all located in the user profile (no admin rights, no registry, no system-wide components):
Native launcher (
Scopevisio.exe/Scopevisio.app/Scopevisio): sets up the Java runtime, manages the environment configuration and startscom.scopevisio.launch.jar: loads the client's program components into a cache and updates them on every start, and startsthe Scopevisio client (Java/Swing): sign-in window and application.
What | Windows | macOS | Linux |
Launcher folder: |
|
|
|
Client cache: |
| same folder as above | same folder as above |
Personal client settings: email, customer number, language, proxy (including password in plain text), window position, UI scaling |
|
|
|
"Automatic sign-in" token |
|
|
|
Client logs (2 days) |
|
|
|
Optional proxy file (read-only, format see below) |
|
|
|
Shortcuts (created by the client on first login) | Desktop |
| The client's |
Program | where it was downloaded (usually |
| anywhere |
Stored on the server and not affected by a local reset: layout, menus, application settings, all data.
Note on Windows folder names:ScopevisioLauncher and Scopevisio must have exactly these names; the client counts running instances through them. Please do not rename them while Scopevisio is running.
Custom base folder (SCOPEVISIO_BASE_DIR)
If the environment variable SCOPEVISIO_BASE_DIR is set (typical on Citrix/terminal servers, e.g. D:\ScopevisioData\%USERNAME%), the launcher folder and client cache are located there instead of in the profile; the folder names below stay the same (<base>\ScopevisioLauncher, <base>\Scopevisio). .erpclient.properties, .svautologin.properties and svproxy.txt still remain in the classic user profile. The folder actually in use is shown by Scopevisio.exe --print-config ("Base Folder: … (platform default | configured via SCOPEVISIO_BASE_DIR)"). Details: help article "Scopevisio on Citrix: direct start by customer number & setting the data folder yourself".
Performing a reset
Principle: back up → reinstall → delete the backup after success. Nothing is deleted immediately; every step can be undone.
Manually
Windows (PowerShell, as the affected user)
# Scopevisio must be closed
$ts = Get-Date -Format "yyyyMMdd_HHmmss"
$base = if ($env:SCOPEVISIO_BASE_DIR) { [Environment]::ExpandEnvironmentVariables($env:SCOPEVISIO_BASE_DIR) } else { $env:LOCALAPPDATA }
foreach ($p in "$base\ScopevisioLauncher", "$base\Scopevisio", "$env:APPDATA\Scopevisio",
"$env:USERPROFILE\.erpclient.properties", "$env:USERPROFILE\.svautologin.properties") {
if (Test-Path $p) { Rename-Item $p ("{0}_backup_{1}" -f $p, $ts) }
}
Get-ChildItem "$env:USERPROFILE\Desktop", "$env:PUBLIC\Desktop" -Filter "*Scopevisio*.lnk" -ErrorAction SilentlyContinue |
Rename-Item -NewName { $_.BaseName + "_backup_$ts" + $_.Extension }
Then download the client again from the customer portal (right environment!), start it, sign in. Afterwards delete the *_backup_* objects, or start the reset tool: it recognizes this naming pattern and offers to delete them. The tool replaces the former internal PowerShell script (ScopevisioClientReset.ps1 / …_DryRun.ps1, June 2026) and covers everything it did; the script remains only for environments where the EXE must not run.
macOS / Linux (terminal)
ts=$(date +%Y%m%d_%H%M%S)
# macOS:
base="$HOME/Library/Application Support/Scopevisio"
# Linux:
# base="$HOME/.scopevisio"
[ -n "$SCOPEVISIO_BASE_DIR" ] && echo "Warning: SCOPEVISIO_BASE_DIR=$SCOPEVISIO_BASE_DIR – adjust base folder there"
for p in "$base" "$HOME/.erpclient.properties" "$HOME/.svautologin.properties"; do
[ -e "$p" ] && mv "$p" "${p}_backup_$ts"
done
# macOS: launcher per customer number and app
ls -d "$HOME"/Applications/Scopevisio* 2>/dev/null && mv "$HOME"/Applications/Scopevisio* ~/.Trash/
mv /Applications/Scopevisio.app ~/.Trash/ 2>/dev/null
# Linux: menu entries
rm -f ~/Desktop/*Scopevisio*.desktop ~/.local/share/applications/*Scopevisio*.desktop
Reinstall, test, then remove *_backup_*.
What a reset does not touch
svproxy.txt(the IT department's proxy configuration) – deliberately kept.Server-side user settings.
With
SCOPEVISIO_BASE_DIR: the old profile folder, if the variable was only set later (nothing is migrated).
Diagnosis before the reset
Symptom | Likely cause | Check |
"The customer number you entered is unknown in the selected environment" | Client for the wrong environment (Standard ↔ C5) | Ctrl + click on "Settings" → "Server" field: |
Program does not start at all, no message (with a shortcut using | Customer number does not exist in the environment of the download |
|
"The Scopevisio servers are currently unreachable …" / "Proxy not found" / "Proxy sign-in failed" | Proxy/firewall | Allow the domains (below); proxy in the sign-in window under "Settings" or via |
Start window: "Error: The application is no longer available" | Proxy responds 407 or instance URL 404 |
|
Start window: "Error: Directory permissions missing" / "No write permissions"; dialog "The configured base folder cannot be used" | Base folder not writable (Citrix, restricted profile) |
|
Dialog "Failed to prepare the Scopevisio environment." | Java runtime could not be loaded (network, proxy, disk space) |
|
Dialog "Timeout while preparing the Scopevisio environment …" | Launcher waits > 20 min for launch.jar | Proxy/network |
Dialog "Update available" | Native launcher older than the minimum version | Download the client again from the customer portal |
Logs: launcher …\ScopevisioLauncher\log\svlaunch*.log (7 days), launch.jar …\Scopevisio\launch.log (overwritten on every start), client ~\.erpclientlogs\. SV_LOG_FILE=<path> redirects the launcher log to a fixed file. In the start window, "?" opens a debug window; the s key writes environment variables and system properties to the log.
Network (firewall/proxy allowlist):account.scopevisio.com (portal), appload.scopevisio.com (Standard) or appload.c5.scopevisio.com (C5) for downloads, Java runtime, program components and application; Linux additionally corretto.aws (Java runtime). All HTTPS/443. Status: status.scopevisio.com, status.c5.scopevisio.com.
svproxy.txt (in the user profile, read by launcher and launch.jar):
proxyhost=proxy.company.local
proxyport=3128
proxyuser=…
proxypass=…
Without this file, the system proxy settings are used.
Distribution and direct start
The client needs no installer and no admin rights; for terminal servers, a central location for the EXE plus
SCOPEVISIO_BASE_DIRwith a%USERNAME%placeholder is recommended.Start directly into an instance:
Scopevisio.exe --public-id=<customer number>; the environment is stored in the download. Details in the help article "Scopevisio on Citrix …".Scopevisio.exe --print-configshows environments, the path ofenvironments.jsonand the base folder.The shortcuts point to a copy of the launcher in the client cache:
%LOCALAPPDATA%\Scopevisio\cache\<host>\clientx\<cid>\scopevisio_<customer no.>.exe.
