Deploying software should be smooth sailing. But sometimes, a stubborn error code appears and stops you in your tracks. Error 1620 is one such roadblock that can frustrate even seasoned IT professionals.
What Is Going On?
Error 1620 can occur when you attempt to deploy software or patches using an .msi installer through Lansweeper On-Premises. The installer usually fails because it cannot locate or access the .msi file from the target computer.
Why Does This Happen?
Error 1620 signals a file access problem. The target machine cannot reach the .msi file stored in your package share. Several culprits may cause this issue:
- The package share location is unreachable from the target computer.
- Credentials lack proper permissions on the share or the .msi file.
- Network connectivity issues block the path between machines.
- Firewall rules prevent access to the shared folder.
When Lansweeper initiates a deployment, it uses scanning credentials to create a task on the target machine. That task then uses share credentials to access files stored in your package shares. If either credential fails, the deployment crumbles.
How Can I Fix This?
Follow these clear steps to resolve Error 1620:
Step 1: Verify Share Accessibility
Log into the target computer using your deployment credential. Navigate to the package share location:
\\srv-lansweeper\DefaultPackageShare$\Installers
If you cannot access this folder, the target machine has connectivity problems. Check network paths and DNS resolution.
Step 2: Confirm Credential Permissions
Both deployment and package share credentials need Read & Execute permissions on the .msi file. Share credentials are stored in encrypted format on target computers. For security, use accounts that only have Read & Execute access to your shares.
Step 3: Check Your Share Configuration
The Lansweeper installer creates a default share at Program Files (x86)\Lansweeper\PackageShare as DefaultPackageShare$. You can manage additional shares in the Deployment > Security options section of the web console.
Step 4: Review Firewall Settings
Ensure the target computer's firewall permits access. Enable the Remote Scheduled Tasks Management rule if needed.
With these steps, your MSI deployments will flow like a river again. Happy deploying!
