This page covers troubleshooting for environment-dependent problems. The scenarios below do not necessarily indicate a PowerOn Pro defect. Check PowerOn Pro: Open Logs for the failed operation and its error before choosing a workaround.
Remote Sym synchronization problems
If files are missing or a synchronization fails, check the selected connection, Remote Sym directories, and destination first. Review the output for transfer errors and check Source Control for incoming changes awaiting your choices.
Remote Sym synchronization downloads into a temporary staging directory before applying changes to the local workspace. The earlier report of files appearing and disappearing is not confirmed as a current defect, so do not assume it requires a WSL configuration change.
- Using SFTP: WSL is not involved. Check that VS Code can write to the local workspace and temporary directory, and that your AIX account can read the selected host directories.
- Using Rsync on Windows: check the default WSL distribution, installed tools, and its access to the Windows temporary directory used for staging. VS Code also needs write access to the destination workspace.
- Using Rsync on macOS or Linux: check local tools and directory permissions, plus host access. WSL settings do not apply.
See Remote change review for handling incoming changes and Setting up Rsync for dependency checks.
Windows Rsync permissions
Windows Rsync uses the default WSL distribution to access Windows drive paths. Confirm that the failing path exists, is available in WSL, and is writable by the Linux user running the transfer. The underlying Windows account must also have the required access.
WSL mount options can affect how Windows file permissions appear inside Linux, but enabling metadata or changing user IDs and permission masks is not a universal fix. Follow Microsoft's WSL file permissions guidance with your workstation administrator when the error points to a mount or permissions problem.
To use the default transfer method instead, set poweronPro.syncMethod to sftp and retry synchronization. This removes the WSL/Rsync dependency; it does not bypass local or host access controls.
Permission Denied
A permission error can come from different parts of the workflow. Check the failed operation and path in the logs:
| Where the failure occurs | What to check |
|---|---|
| Connecting to the host | The AIX account credentials, account status, and allowed SSH authentication. An authentication failure is different from a file permission error. |
| Reading or writing a host file | The AIX account's access to the target Sym directory, file ownership, permissions, and relevant SYM### group membership. |
| Running a Symitar operation | The selected Sym and the Symitar account's authorization for that operation. |
| Writing a local file or staging a download | The local filesystem permissions and available path. For Windows Rsync, also check WSL access to the staging path. |
The AIX and Symitar accounts have separate responsibilities. Membership in a Sym group may be necessary for file access, but it does not resolve every permission or authentication failure.
Checking your groups
Use your organization's approved SSH access method to sign in to the Symitar host with the same AIX account configured in PowerOn Pro. At the host shell, run:
id
groups
Ask your host administrator to confirm that the account has the required group membership and directory access for the target Sym. For example, access to Sym 627 may require membership in SYM627.
Updating your groups
Have your host administrator or hosting provider make any required AIX account or group changes while preserving existing memberships. The appropriate procedure depends on how your organization manages accounts; see IBM's AIX chuser reference.
After an access change, disconnect and reconnect in PowerOn Pro so the new session can pick up the updated permissions, then retry the failed operation.
Host validation still requires access to the host. Realtime diagnostics run locally, but they do not replace host validation or fix host permissions.