Table of Contents

Testing and troubleshooting

Test every add-in script with a small set of files before enabling it for production users.

  1. Build and test the .pdmshell script outside the add-in.
  2. Add the script in the Script Editor.
  3. Enable Always show condition test message while validating conditions.
  4. Configure permissions for a small administrator group.
  5. Enable a command menu or trigger point.
  6. Test against known files and folders.
  7. Expand permissions after the automation behaves as expected.

Common issues

Symptom What to check
Menu command does not appear Confirm the script is enabled, Menu is enabled, command menu text is not empty, and the current user passes permissions.
Menu command or trigger change does not appear after saving If the Script Editor showed the menu and hook changes prompt, restart Windows Explorer or log out and back in to the vault so PDM reloads the add-in menus and command hooks.
Script does not run from a trigger Confirm the trigger point is selected and the add-in was reloaded after changing trigger configuration.
Conditions do not match Enable the condition test message and verify the resolved placeholder and variable values.
Script runs against the wrong item Check the PDM command context and whether the event supplies files, folders, or command-only data.

Installation and registration

Symptom Next check
Class ID not found, class not registered, or failed to extract add-in Confirm you are installing the dedicated add-in package, not the standalone DLL directory. Record the exact named DLL, PDM version and app version for support. A dependency DLL is not necessarily an add-in entry point.
A check failed and installation cannot proceed Use 4.0.90 or newer and review the explicit Repair installation option. A failed inspection means the installed version is unknown; it does not prove the add-in is absent. Permission and package checks still apply.
Repair completed but verification failed Treat the outcome as unverified. Record the failing stage, worker, HRESULT and any dependency filename; do not assume rollback or repeatedly install without reviewing the result.
File-copy error contains Blue%20Byte%20Systems Update standalone PDMShell to 4.0.84 or newer, which fixes the escaped installation path. Other copy failures still need their paths and error codes checked.
Add-in still loaded during an update Close affected clients through your maintenance procedure. Version checks are isolated in 4.0.81 and newer; they do not unload another application's add-in.
Task still runs old code Reimport the file or saved vault script and save task properties. The task holds a snapshot, not a live link.
No Edit Scripts menu Expected in 4.0.83 and newer. Launch standalone PDMShell and use New/Open > Vault script.

Do not delete the PDM plug-in cache or change COM registration blindly. Back up configuration and coordinate client restarts before repairing a production installation.

Standalone installer errors such as Failed to remove existing application directory are a different workflow. See Processes blocking installation for the updater's process list and confirmed close/restart actions.

Edit this page