
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-28-2018 03:10 PM
I am hosting LanSweeper locally on my PC. I am getting "Package Timeout" errors with my Deployment and I am not sure why. I have done silent install deployments before, but this timeout is a first.
1. Is there an issue with my XML code?
2. Is my Adobe Reader .msi file correct? I ran it through Adobe's Acrobat Customization Wizard, but it has the default msi file name.
XML :
1. Is there an issue with my XML code?
2. Is my Adobe Reader .msi file correct? I ran it through Adobe's Acrobat Customization Wizard, but it has the default msi file name.
XML :
<?xml version="1.0" encoding="utf-8"?>
<Package>
<Name>Adobe Reader Installer</Name>
<Description>It will install Adobe Reader DC onto the PC.</Description>
<ShutdownOption>0</ShutdownOption>
<ShutdownTime>0</ShutdownTime>
<MaxDuration>1500</MaxDuration>
<Rescan>False</Rescan>
<RunMode>-1</RunMode>
<Steps>
<Step>
<Nr>1</Nr>
<Name>Send Start Message</Name>
<Type>2</Type>
<ReturnCodes>0,1641,3010</ReturnCodes>
<Success>2</Success>
<Failure>-3</Failure>
<Path></Path>
<Parameters></Parameters>
<MSIParameters></MSIParameters>
<MSIName></MSIName>
<MSIVersion></MSIVersion>
<Command>msg.exe /TIME:60 * Installing Adobe Reader remotely. Please do not turn off your PC/laptop.</Command>
<EditMode>False</EditMode>
<Conditions />
</Step>
<Step>
<Nr>2</Nr>
<Name>Check .exe File Exists</Name>
<Type>5</Type>
<ReturnCodes></ReturnCodes>
<Success>-2</Success>
<Failure>-1</Failure>
<Path></Path>
<Parameters></Parameters>
<MSIParameters></MSIParameters>
<MSIName></MSIName>
<MSIVersion></MSIVersion>
<Command></Command>
<EditMode>False</EditMode>
<Conditions>
<Condition>
<Type>1</Type>
<SpecOne>C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader</SpecOne>
<SpecTwo>AcroRd32.exe</SpecTwo>
<Operator>1</Operator>
<Value></Value>
</Condition>
</Conditions>
</Step>
<Step>
<Nr>3</Nr>
<Name>Install Adobe Reader</Name>
<Type>1</Type>
<ReturnCodes>0,1641,3010</ReturnCodes>
<Success>4</Success>
<Failure>5</Failure>
<Path>{PackageShare}\Installers\Reader\AcroRead.msi</Path>
<Parameters>/ForceInstall /Printername="Adobe Reader" /VERYSILENT /NORESTART</Parameters>
<MSIParameters>/i /qn /norestart</MSIParameters>
<MSIName></MSIName>
<MSIVersion></MSIVersion>
<Command>msiexec.exe /i "{PackageShare}\Installers\Reader\AcroRead.msi" /norestart /qn /ForceInstall /Printername="Adobe Reader" /VERYSILENT /NORESTART</Command>
<EditMode>False</EditMode>
<Conditions />
</Step>
<Step>
<Nr>4</Nr>
<Name>Finish Message</Name>
<Type>2</Type>
<ReturnCodes>0,1641,3010</ReturnCodes>
<Success>-2</Success>
<Failure>-1</Failure>
<Path></Path>
<Parameters></Parameters>
<MSIParameters></MSIParameters>
<MSIName></MSIName>
<MSIVersion></MSIVersion>
<Command>msg.exe /TIME:30 * Installation finished. Thank you.</Command>
<EditMode>False</EditMode>
<Conditions />
</Step>
<Step>
<Nr>5</Nr>
<Name>Error Message</Name>
<Type>2</Type>
<ReturnCodes>0,1641,3010</ReturnCodes>
<Success>-2</Success>
<Failure>-3</Failure>
<Path></Path>
<Parameters></Parameters>
<MSIParameters></MSIParameters>
<MSIName></MSIName>
<MSIVersion></MSIVersion>
<Command>msg.exe /TIME:30 * Error installing Adobe Reader. We apologize for the inconvenience.</Command>
<EditMode>False</EditMode>
<Conditions />
</Step>
</Steps>
<SoftwareVersion>6.0.130.40</SoftwareVersion>
</Package>
Labels:
- Labels:
-
General Discussion
4 REPLIES 4

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-04-2018 06:49 AM
Are you doing any configuration etc. We are installing it using the default settings with the following command.
msiexec.exe /i "\\SERVERNAME\Software\Applications\Adobe\AcroRdrDC1500720033_en_US\AcroRead.msi" /norestart /qn
msiexec.exe /i "\\SERVERNAME\Software\Applications\Adobe\AcroRdrDC1500720033_en_US\AcroRead.msi" /norestart /qn

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-29-2018 01:28 PM
Your deployment logs should display the step which returned that error. Try testing the steps manually as I explaining in my last reply. If you can find the step which does not finish executing, you can look more closely as to why it is not finishing.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-28-2018 04:33 PM
The Result was this:
Result: Package timeout reached. Stopping deployment executable: Successful. Timeout: (2700sec). Credential: (Service account - NT AUTHORITY\SYSTEM). ShareCredential: (domainx\userx).
Result: Package timeout reached. Stopping deployment executable: Successful. Timeout: (2700sec). Credential: (Service account - NT AUTHORITY\SYSTEM). ShareCredential: (domainx\userx).

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-28-2018 03:27 PM
I don't see anything obviously wrong with the package. I can't say much about the MSI file or the parameters used as they are specific to the Adobe software.
I presume the package gets the timeout at step 3, which is installing the software. In general, reaching the package timeout just means that the maximum duration you configured (in this case 25 minutes) was reached before the whole package completed. In some cases it is simply because the package requires more time to finish. Another common cause is that the package requires user input on the asset which is preventing it from continuing.
I would recommend testing your deployment package steps. For testing the commands:
I presume the package gets the timeout at step 3, which is installing the software. In general, reaching the package timeout just means that the maximum duration you configured (in this case 25 minutes) was reached before the whole package completed. In some cases it is simply because the package requires more time to finish. Another common cause is that the package requires user input on the asset which is preventing it from continuing.
I would recommend testing your deployment package steps. For testing the commands:
- Copy the Result command of the failed deployment package.
- Use the exact path defined under Deployment\Security options.
- Paste the command into the command prompt of a machine where the deployment failed.
- This should help you identify the cause of the issue. Only when the command works in Command Prompt will it work in Lansweeper as well.
- If the command worked then we recommend that you check that the command has been added correctly to your package and the parameter are also correctly added to the parameter field.
