Troubleshooting Application Pack Deployments

Before you begin troubleshooting Application Pack deployments, it's important to first make sure that you're using the latest version of SmartDeploy. When you're logged in to the console, if you see the Update Available link in the top-right corner, click it to download and install the latest version of SmartDeploy.

You're welcome to submit a support ticket for help with your Application Packs. But you can troubleshoot some common issues related to Application Pack deployments.

How can I tell that my application is deploying?

After you deploy an Application Pack from the console, the message status under Message History should update with the current status of the deployment once the SmartDeploy Client checks in with the console.

You can view the Application Log in Event Viewer to confirm that the Application Pack is extracting and to confirm the correct command is being executed per your Application Pack configuration. To investigate further, such as why an application did not install, check the SmartDeploy Client log at C:\Program Files\SmartDeploy\ClientService\SDClientService.log.

The application deployment never starts; only a clock icon appears and never goes away

Two causes are covered here: the target client is not checking in with the console, or a previous application deployment appears to still be in process on the endpoint.

Client is not checking in

First, you'll want to confirm that your target client doesn't appear in gray or faded text in the Computer Management workspace. Gray text is an indication that the client has not checked in recently and is not checking for new messages. If this is the case, first restart the SmartDeploy Client service on the endpoint, and allow about 5 minutes for the service to start and the client to check in with your console. You'll also want to make sure that the required ports are open between your client and console host. For the ports SmartDeploy requires, see Which ports are required by SmartDeploy?.

A previous deployment is still in process

Application Pack deployments may also queue when a previous application deployment appears to be in process. On the target PC, delete the application pack folder from C:\ProgramData\SmartDeploy.

The application deployment appears to start, but the application never installs

We see this problem when the installation syntax that is set in the Application Pack is incorrect and the application installation has generated an error or some other prompt requiring user interaction. Because these application installations are run in the System context, you won't be able to see these prompts as a user, and the installation will remain hung in the background.

To resolve this, follow these steps:

  1. Use the Task Manager to end the installation process, or restart the client PC.
  2. Delete the SmartDeploy folder from C:\ProgramData\SmartDeploy if present.
  3. Revisit your Application Pack configuration to make sure that you have the correct syntax set in your command line arguments.

What should I do if a deployment is stuck in 'deployment scheduled' or 'pending' status?

If a deployment is stuck in the 'deployment scheduled' or 'pending' status, try these steps:

  1. Verify network connectivity to the target endpoint.
    1. For clients with a Local connection, see How can I check whether a client with a Local connection is able to communicate with the SmartDeploy Console?
    2. For cloud connected devices verify the "Last heartbeat" time in the Computer Management workspace to see when the machine reported to the console last.
  2. Cancel the pending job
  3. Restart the SmartDeploy Client Service on the target computer.
  4. Attempt the deployment again

If the issue persists, collect the client log from the target computer located in the path below for troubleshooting.

C:\Program Files\SmartDeploy\ClientService\SDClientService.log

Error: "The Application Pack failed to apply The data could not be decrypted with the supplied decryption password"

This error occurs when an Application Pack is over 5 GB in size. SmartDeploy does not recommend building an Application Pack for an application larger than 5 GB (see Create a Custom Application Pack). To avoid the error, store the installation files in a shared network location and add a step to the Application Pack that maps that location during deployment, or include only the files the installation needs.

What the error looks like

The console shows the message "The Application Pack failed to apply The data could not be decrypted with the supplied decryption password". The SmartDeploy Client log (C:\Program Files\SmartDeploy\ClientService\SDClientService.log) contains an entry like this:

Error Failed to export directory structure Xceed.Zip.InvalidDecryptionPasswordException: The data could not be decrypted with the supplied decryption password.
Type: Xceed.Zip.ZippedFile
FullName: \<Application Pack name>\Files\<path to a file inside the Application Pack>
Zip file: C:\ProgramData\SmartDeploy\<Application Pack name>.spk
---> Xceed.Compression.ZCryptException: Invalid decryption Password

 

Use a shared network location for the installation files

Instead of including the installation files in the Application Pack, place them in a shared network location. Then add a step to the Application Pack that maps the shared drive location during deployment and accesses the files from there.

Include only the files the installation needs

Where possible, make sure only the files used by the application installation are in the Application Pack folder. Keeping the folder as clean as possible reduces the size of the Application Pack.

Test your application installation as system

To test the installation of your application as system, follow these steps:

  1. Download the PsExec tool from Windows Sysinternals.
  2. Extract the PSTools Zip file to a convenient location.
  3. Open a command prompt as Administrator, and change directory to the folder that contains PsExec.exe.
  4. Run this command: psexec.exe -s -i cmd.exe
  5. Click Agree if you are prompted by the toolset.
  6. Run the command whoami to confirm that the command prompt is nt authority\system.
  7. Test your installation by using the command prompt that is running as nt authority\system.
Was this article helpful?