Skip to main content

DCA Installation Fails: Access Denied, Error 1603, or Installer Blocked

Installing the Print Tracker DCA returns "Access is denied," Exit Status 1603, a 403 or 500 error from the download link, or the installer fails silently. Step-by-step causes and fixes.

Written by Joshua Kern

Use this article when the DCA installer will not complete. Work through the steps in order: the first two resolve the large majority of cases.

Common Error Messages and Their Causes

Error Message

Likely Cause

Access is denied

Installer not run as administrator

Exit status 1603

Windows Installer conflict, permissions issue, or a prior failed install

msiexec.exe: Access denied

Group Policy or AppLocker restriction preventing install

Error 403 or 500 from the download link

Network security policy or web filter blocking the download URL

Installer downloads but nothing happens

Antivirus silently blocking execution

PowerShell command completes but nothing installs

PowerShell window was not opened as administrator, which fails silently

Installer completes but the DCA never appears in Web Admin

Agent was never registered, wrong datalink code, or outbound port 443 blocked

Installation prevented on Windows 10 or 11

The machine is in S Mode. See DCA Installation Blocked by Windows S Mode.

macOS: "the .pkg cannot be opened"

Gatekeeper. Print Tracker is not distributed through the Apple App Store. See Installing and Managing Agents.

Step 1: Run the Installer as Administrator

This is the most common cause of installation failure. Right-click the installer file and select Run as administrator. Do not simply double-click it as a standard user, even if the account appears to have admin rights, because some configurations require the explicit elevation.

If you are installing from the command line, the same rule applies: the PowerShell window must be opened as an administrator. If it is not, the installation fails silently with no error at all.

Step 2: Use the Generic Installer Instead of the One-Click Installer

Print Tracker offers several deployment methods, and some are more prone to antivirus and web filter interference than others. One-click installers are generated on the fly for a specific entity, and that is exactly the behavior security tooling tends to flag. The generic installer is a static, well-known file and is let through in many cases where the one-click installer is not.

If the one-click installer link from Web Admin returns a 403 or 500 error, or is blocked, download the generic installer directly from printtrackerpro.com/download and run it manually.

The generic installer does not register itself automatically, so you will need the entity's datalink code. After installation, open localhost:1301 on the host machine, enter the datalink code, and click Register.

If the download URL itself is being blocked by a web content filter, whitelist printtrackerpro.com in the filter policy.

Step 3: Temporarily Disable Antivirus or EDR Software

Security software such as Sophos, CrowdStrike Falcon, Norton, Malwarebytes, and Windows Defender can silently block the installer or quarantine the executable after installation. To test:

  1. Temporarily disable real-time protection on the host machine.

  2. Run the installer as administrator.

  3. Re-enable protection immediately after the installation completes.

  4. Add Print Tracker to the allowlist so this does not recur. See Antivirus or EDR Software Blocking the DCA for product-specific exclusion paths.

Adding the exclusions is not optional cleanup. If you skip it, the installation may succeed and then the DCA will be quarantined days later, which presents as an install that mysteriously went offline.

Optionally you can pre-emptively make the necessary exclusions needed for the app found in Antivirus or EDR Software Blocking the DCA

Step 4: Check Group Policy or AppLocker Restrictions

On domain-joined or MDM-managed machines, software restriction policies may block unlisted installers. Signs of this include a silent failure with no error, or an "Access is denied" message even when running as administrator.

Have the customer's IT administrator check:

  • Windows AppLocker policies (Local Security Policy, then Application Control Policies)

  • Group Policy Software Restriction Policies

  • Any MDM or RMM tool policies (Intune, ConnectWise Automate, and similar) that may restrict installer execution

The Print Tracker installer needs to be whitelisted, or the installation should be performed by the IT administrator with elevated domain rights. Check our article Antivirus or EDR Software Blocking the DCA for a full list of exclusions needed.

Step 5: Clean Up a Failed Previous Install

If an earlier attempt partially completed, Windows Installer may block a new attempt, or corrupted folders may remain. To clean up:

  1. Open Add or remove programs from the Start menu.

  2. Search for Print Tracker Pro and uninstall it if it appears.

  3. Check for a Print Tracker Pro folder in C:\Program Files (x86) and delete it if found.

  4. Reboot the machine.

  5. Run the installer again as administrator.

Step 6: Verify the DCA Registered Successfully

After a successful install, the DCA should appear in Web Admin under Installs for the entity within 5 to 10 minutes. If it does not appear:

  • Confirm the agent was actually registered. An agent that is installed but never registered will not appear in Print Tracker at all. Open localhost:1301 on the host, enter the datalink code, and click Register.

  • Confirm the correct datalink code was used. A code from the wrong entity binds the DCA to that entity instead. See Installing and Managing Agents for how to correct this.

  • Confirm outbound TCP port 443 is open from the host machine to *.printtrackerpro.com.

  • Check the Windows Services list for Print Tracker Pro Watcher and verify it is running.

Contacting Support

If the installation continues to fail, contact Print Tracker support with the full error message, the Windows version and edition, whether the machine is domain-joined, and the name of any endpoint security software installed.

Did this answer your question?