Diagnostics and Troubleshooting Software Delivery › Virtual Application Software Package Deployment Fails

Virtual Application Software Package Deployment Fails

Symptom:

When I attempt to deploy a virtual application software package, the deployment fails and I receive the following error message: "ERROR (number) Install package_name failed.” What do I do now?

Solution:

To troubleshoot an error while deploying a virtual application software package, perform the following steps:

1. Navigate to the Computers and Users, All Computers, computer_name, Jobs, Software Jobs folder.

   The right pane displays the available software delivery jobs.

2. Select the job that failed, right-click, and select Properties.

   The Job Properties dialog appears.

3. View the Status Message on the Computer Job tab.
4. Open the Job Output tab and view the trace information.

   Note: There is no trace information shown if the deployment is successful.

5. Scroll down to the Starting postprograms section.

   This section displays information related to virtual application package installation.

6. View the postprogram return code. The following list includes all return codes and their meanings:

   -1

   Indicates an internal error with wrong or incomplete parameters (install script not executed).

   0

   Indicates successful termination (no error).

   1

   Indicates that the process could not find the DSM installation (files, directories, registry keys, or environment were not found).

   2

   Indicates that the process could not create or remove files or folders.

   3

   Indicates that the process could not find required files for the package (for example, .sft files for Microsoft App-V packages).

   4

   Indicates that the creation or removal of net shares failed.

   5

   Indicates that the process could not restart App-V services.

   6

   Indicates that the execution of sftmime.exe (App-V) or ThinReg.exe (VMware ThinApp) failed. These required tools create or remove links (icons) on the desktop and entries in the Start > Programs menu.

   7

   Indicates that the process failed to connect to the ThinApp streaming server.

7. View the command line that caused the deployment failure in the Action output of installation section of the trace information. Scroll right to view the command line parameters and return code.
8. Determine the cause of the error and fix the problem.
9. Redeploy the virtual application software package.

Network Installation of MSI Package Fails

Symptom:

When I perform a network installation of an MSI package on Windows Server 2008, the installation fails with an error "1619: This installation package could not be opened". How do I fix this problem?

Solution:

The network installation of an MSI package fails with the error code “1619: This installation package could not be opened” when both the scalability server and the agent are installed on Windows Server 2008, Windows Vista SP2, or Windows 7 operating environments and are part of a WORKGROUP rather than a domain.

To perform a successful network installation of an MSI package, disable SMB2.0 and restart the scalability server.

To disable SMB2.0 on the scalability server, do the following:

1. Open Registry Editor and navigate to HKLM,System, CurrentControlSet, Services, LanmanServer, Parameters.
2. Create a DWORD Value and name it smb2
3. To disable SMB2.0,set the value of smb2 to 0.

   Note: To enable SMB2.0, set the value to 1.

4. Restart the scalability server

   SMB2.0 is disabled on the scalability server.

SD Agent Does not Start after a CAF Restart

Valid on Windows and UNIX

Symptom:

When you start CAF, the SD agent does not initiate automatically. Hence, the SD job check does not run on CAF restart.

Solution:

Do the following:

• On the CAF Scheduler, change the default value of the random now time field to 0 seconds.
• Verify that the default value of the CAF: Enable registration on start-up configuration policy is true.

Note: On UNIX, CAF register does not run all the plug-ins. Use the CAF register all command to run all the plug-ins.

Variables in debconf Parameters are not Preseeded

During deployment, the software delivery agent preseeds the debconf parameters with the values you specify during the creation of wrapper packages. The agent does not preseed debconf parameters when you assign them variables such as ${choices}.

Perform the following steps to preseed a variable with known values:

1. Navigate to DSM Explorer, Computer, Software, Software Package Library, All Software, Debian wrapper package, Source, New Volume, debWrpMetadata.wdp.
2. Double-click and edit the wdp file as required.

Installation of Debian Wrapper Package Fails

Symptom:

When I install a Debian Wrapper package, installation fails with the following error:

WARNING: The following packages cannot be authenticated!

Solution:

Perform one of the following steps:

• Create a configuration file for APT commands to allow unauthenticated packages to be installed. On the agent computer, add the following text in one of the APT configuration files or create a new file under /etc/apt/apt.conf.d:

  APT {
  

     Get {
  

  	AllowUnauthenticated "true";
  

     };
  

  }
  

• Import the public key to the agent computer using the apt-key add command. For a large-scale import of the key, create a software delivery package.

Debian Wrapper Package Fails to Install

Symptom:

I installed a Debian wrapper package but the package failed to install.

Solution:

Do the following:

• Verify that the package size or hash is not changed from the index file.
• Verify that the package is present in the repositories mentioned in sources.list.
• Verify that all package dependency is fulfilled.
• Verify that runtime errors do not appear during installation.