Skip to main content

Troubleshoot without losing work

Guide home · Find a task

This guide helps diagnose common Sambafied issues. Always preserve your work before attempting repairs.

Cannot connect or sign in​

  1. Check the connection name, Author address and DAM root with your administrator.
  2. Check network access and whether the session expired.
  3. Retry sign-in from the affected connection and inspect the account name.
  4. If it still fails, retain the sanitized error and contact your support contact.

Browser sign-in does not always mean the desktop application can access assets. Never share passwords, cookies or tokens.

Certificate or proxy error​

Ask your administrator to check the certificate chain and supported proxy route. Retain the error with private addresses redacted. Do not disable certificate validation or change trust settings as an improvised fix.

Asset is missing or denied​

Check the connection, folder, query, filter and whether more results remain to load. Refresh and read the error. A filtered or denied asset is not necessarily deleted. Ask your administrator about permissions or expired-asset policy.

Download or upload fails​

Check disk space, network and the item in Transfers. Some files can finish while others fail. Check any unknown server result before retrying. Server processing can continue after transfer completion.

Saved edits do not appear in AEM​

Open Edited locally and inspect the saved copy. Saving locally differs from Upload Changes. Check completion, processing and separate check-in. A later save may remain unuploaded after an earlier copy finishes.

Linked assets are missing​

Preserve the creative document. Check related downloads, permissions, application support and stable paths. Use the application's supported relink tools with care. See creative applications.

Window is blank or unresponsive​

Record the version, last action and visible error. Use supported close or restart controls if available. After reopening, inspect local work and pending transfers. Preserve edits before considering reinstalling; do not delete the cache as a shortcut.

Error message reference​

These messages may appear in the application window or console output.

Authentication errors​

MessageCauseFix
login declinedUser cancelled the sign-in flowRetry sign-in if you want to connect
default browser unavailableCould not open the system browserCheck default browser settings
invalid public clientClient configuration errorCheck login config file
file audience scopes requiredMissing required OAuth scopesContact administrator
configured file root unavailableThe AEM root is not accessibleCheck AEM permissions

Connection errors​

MessageCauseFix
generation reconciliation requiredProfile was created with different server stateRe-authenticate or create new profile
profile directory must be absoluteInvalid path specifiedUse full absolute path
login callback port unavailablePort 8788 is in useClose other applications using the port

File operation errors​

MessageCauseFix
Sambafied window preferences could not be readPreferences file corruptedDefaults will be used; reset preferences
Sambafied sort preference could not be readSort preference corruptedDefault sort will be used
Sambafied item-opening preference could not be readPreference corruptedDefault will be used
Sambafied account status stoppedBackground status service endedRestart the application

Windows-specific errors​

MessageCauseFix
WinFsp helper failedVirtual drive mount failedCheck WinFsp is installed
Invalid vault credentialStored credential corruptedRe-authenticate

Log locations​

Logs help diagnose problems. Sambafied outputs to the terminal when run from command line.

  • Console output from Command Prompt or PowerShell
  • Profile data in AppData

Collect support information​

Reproduce safely without exposing passwords, tokens or asset contents.

  1. Note the action you took and any message shown.
  2. Record the application version supplied with your build.
  3. Record connection type, time, action, expected result and actual result.
  4. Copy a sanitized error message (remove paths with usernames).
  5. Review any logs before sharing.

Exclude cookies, request headers, signed links and private asset data.

Illustrative sample: Check app health displays diagnostic information in About

Illustrative sample. Check app health displays diagnostic information in About.