SDP Help Center
News
SDP Help Center
News
Troubleshoot: Spirion Agent is installed but not visible on the Agent Management page
Popular
Architecture and High-level Information
Scans
Agents
How to Use Dashboards
How to Use Data Asset Inventory
How to Install\Uninstall and Set Up Spirion Sensitive Data Platform
How to Use Logs
How to Manage Users and Roles
Reports
Settings and Resources
Additional Resources
Release Notes
Reporting API
Customer Support Articles
Endpoint for Windows Configuration Reference GuideEndpoint Software Command Line InterfaceBasic Troubleshooting Steps (Enterprise Console)Endpoints or Results Fail to be Displayed in the ConsoleMongoDB and TLS 1.3SQL Client SQL Exception ErrorHow to Troubleshoot Spirion Client Search Failures and How to WhitelistCustomer Notice – Spirion Agent Update & Security Assessment for PostgreSQLHow to Enable Verbose/Debug Logging for the Endpoint ServiceHow can I monitor the status of a queue job?Can I monitor the job queue status automatically?Troubleshooting: "Unable to find job queue: search_queue"How to Verify the Discovery Agent's StatusHow to check if port 6433 is open on your networkWhat is the SDM Translator Service?Can Spirion Sensitive Data Platform be integrated with Microsoft Active Directory?Windows ARM SupportFrom Discovery to Action: Maturing Sensitive Data Risk RemediationCPU/Chipset SupportEnhancing Data Protection: 7 FAQs on Spirion and MPIP IntegrationDoes your DLP solution protect data using a Zero Trust model?What is DLP as a service and when is it right for your organization?Spirion Sensitive Data Platform Installation Errors: Error code 1723Spirion Sensitive Data Platform for Linux: Tips and TricksComplete Your Microsoft 365 Data Protection StackSpirion Sensitive Data Platform Console MaintenanceSpirion Customer Support site has moved to archTIS Help CenterHow to Create a Single Tenant App for OneDrive and Exchange Online SearchesHow to Configure Spirion for Sybase DiscoveryHow to Use Certificates to Authenticate with SharePoint OnlineHow to Quarantine to a Remote Location Using Spirion Sensitive Data PlatformA Server Error has Occurred: How to use the Chrome Developer ToolsWhy doesn't my Oracle 19c Database scan?How to Enable Full Disk Access on a Mac AgentWhy is My Scan Node Running Out of Disk Space?What to do about Message Processing and Delays, also known as 'Lag,' in SpirionDetails About the Box API used by Spirion to Search Box AccountsHow to Build a Mac Package (PKG)How to Sanitize AgentsHow to Set User and Role AccessHow to Enable SSL Communication between Linux Agents and the Spirion ConsoleHow to Enable HTTPS for the Spirion ConsoleHow to Search BoxFAQ: How do I avoid being prompted to re-login to the Spirion console?Spirion Sensitive Data Platform Scan PerformanceHow to Authenticate to SharePoint On-PremiseHow to Configure Spirion Sensitive Data Platform to Connect to an Oracle DatabaseFAQ: Linux 12.5 Client Package Build WorkaroundTroubleshoot Exchange Online Using Microsoft Graph ExplorerFAQ: What to do when an agent will not start the discovery team scan?Required SQL Server PermissionsHow to Scan Microsoft Teams with Spirion Sensitive Data PlatformField Input Using Linux Machines Anti-virus Alerts Received during Spirion SearchVersion 13.6 MSI Installation Issues - Exe file not signedWhat are common firewall rules needed for distributed scans?How do I create a custom regex for medical record numbers?

Spirion Sensitive Data Platform Installation Errors: Error code 1723

This article describes the 1723 error code, possible root causes and provides an example 1723 error code with the suggested fix.

What is Error 1723

Error 1723 is a Windows Installer error, not a Spirion-specific one. It means:

"There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run."

The full message typically reads:

"Spirion -- Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor."

Possible Root Causes

  1. Corrupt or missing installer DLL — A .dll file that the MSI package calls as a custom action during install/uninstall is missing, blocked, or corrupted on the target machine.
  2. Previous installation remnants — A prior Spirion installation left behind a broken or partially-uninstalled state. The installer tries to call a DLL from the old install path that no longer exists.
  3. Antivirus/security software blocking the DLL — Endpoint security tools (e.g., CrowdStrike, Defender) may block execution of the installer's custom action DLL.
  4. Insufficient permissions — The installer is not running with sufficient privileges to execute the DLL (not running as Administrator).
  5. Corrupted MSI download — The installer package itself is damaged.

Example Error 1723

In our example installing Spirion Sensitive Data Platform (using the default Spirion provided .MSI) produces the following error:

Note: 1: 1723 2: GetAdobeInstallDir 3: GetAdobePlugInPath 4: C:\Users\csscs\AppData\Local\Temp\MSI6383.tmp Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action GetAdobeInstallDir, entry: GetAdobePlugInPath, library: C:\Users\csscs\AppData\Local\Temp\MSI6383.tmp

Error 1723 is triggered because the Windows Installer lacks full administrative permissions to execute a required configuration script inside your local user account's Temp directory.

The setup file ( in this example:MSI6383.tmp) is blocked from launching its built-in Adobe setup plugin (GetAdobePlugInPath).

Follow these targeted troubleshooting sequences to resolve the issue:

Fix Temp Folder Security Permissions

Your active user account or the default Windows System profile might lack explicit full authorization privileges over your temporary cache folder.

  1. Press the Windows Key + R simultaneously to invoke the Run prompt.
  2. Input %temp% and strike Enter to directly open your local temporary file store.
  3. Move backward by one folder tier inside the navigation address bar, or click Local in the path hierarchy to locate the parent Temp directory.
  4. Right-click the Temp folder icon and choose Properties from the context options.
  5. Access the Security tab interface, then choose the Edit action button.
  6. Click on your active Windows username profile within the selection list box.
  7. Mark the checkbox labeled Full Control inside the Allow column block.
  8. Ensure absolutely zero boxes are marked under the Deny column block.
  9. Select the SYSTEM entry name within that identical profile box list and verify it also possesses Full Control rights.
  10. Click Apply, confirm with OK, reboot your desktop system, and re-run the Adobe setup package installer app execution.

Re-register the Default Windows Installer Service

Corrupt background engine processing pipelines can block execution parameters belonging to third-party installations.

  1. Open your Windows search bar, type cmd, right-click on Command Prompt, and select Run as Administrator.
  2. Input msiexec.exe /unregister and press Enter to release current engine hooks.
  3. Input msiexec.exe /regserver and press Enter to rebuild execution registry flags.
  4. Run the installation package again.

Note: Working versus Non-working Machines

If this error occurs on some machines, but not others in your organization, pay special attention to the installation prerequisites.

The likely cause of the error is that the failing machines do not contain the necessary required software to support the successful installation of Spirion Sensitive Data Platform.

Was this article helpful?

Powered by Product Fruits