Error “There is a problem with this Windows Installer package…….. Contact your support personnel or package vendor” when Installing Windows Receiver

Installation of Receiver fails with the following error,

“There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor”

Running Microsoft Fixit throws the following error,

“C:WindowsSystem32Rundll32.exe is missing”

\No Trolley Express log is generated under C:UsersusernameAppDataLocalTemp

In Event Viewer we see the following error from MsiInstaller,

Event 11721, MsiInstaller

Product Online Plug-in — Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: CtxCliLkdnInstallPerMachine.UID, location: C:Program FilesICA Client, command: rundll32.exe”C:Program FilesCitrixICA Clienticaconfs.dll”, ApplyConfigurationA import –replace -f -all “C:Program FilesCitrixICA ClientConfiguration” –RunAsAdmin.

Related:

Secure Mail Client displays “certificate might be invalid or inaccessible” error

Tradução automática

Эта статья была переведена автоматической системой перевода и не был рассмотрен людьми. Citrix обеспечивает автоматический перевод с целью расширения доступа для поддержки контента; Однако, автоматически переведенные статьи могут может содержать ошибки. Citrix не несет ответственности за несоответствия, ошибки, или повреждения, возникшие в результате использования автоматически переведенных статей.

Related:

  • No Related Posts

Latency seen on vServers, Netscaler Management when Signatures Bound to AppFW profiles

Tradução automática

Эта статья была переведена автоматической системой перевода и не был рассмотрен людьми. Citrix обеспечивает автоматический перевод с целью расширения доступа для поддержки контента; Однако, автоматически переведенные статьи могут может содержать ошибки. Citrix не несет ответственности за несоответствия, ошибки, или повреждения, возникшие в результате использования автоматически переведенных статей.

Related:

  • No Related Posts

Application Launch Error: “The Citrix server is unable to process your request to start this published application at this time.”

User-added image
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

Following are the possible solutions to troubleshoot the error:

Solution 1

In the PATH Environment variable, Move the location of the third party software variables after the XenApp variables. After the change, XenApp locates the correct version of cmstart.exe.

“%SystemRoot%system32;%SystemRoot%;%SystemRoot%System32Wbem;%SYSTEMROOT%System32WindowsPowerShellv1.0;C:Program Files (x86)Citrixsystem32;C:Program Files (x86)CitrixSystem32CitrixIMA;C:Program Files (x86)CitrixSystem32CitrixIMASubsystems;%SystemRoot%System32CitrixIMA;C:Program Files (x86)Citrixsystem32;C:Program Files (x86)Common FilesCitrixSystem32;C:Program Files (x86)ThirdPartyBin;C:Program Files (x86)Microsoft SQL Server100ToolsBinn;C:Program Files (x86)Microsoft SQL Server100DTSBinn;”

Solution 2

Complete the following steps to add values to the AppSetup String Value and resolve the issue:

Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.

  1. Open the Registry Editor and go to the following registry key:

    HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionWinlogon

  2. Double-click the AppSetup value.

  3. Add the data value cmstart.exe after Cmd separated by a comma.

  4. Add the data value CtxHide.exe before the data value UsrLogon.Cmd. There are no commas placed between CtxHide.exe and UsrLogon.Cmd.

    Note: In a XenDesktop 7 App Edition scenario on Windows Server 2012, CtxHide.exe will not be present on the system, and does not need to be included in this registry update.

Following is an example of the AppSetup Value Data: CtxHide.exe UsrLogon.Cmd,cmstart.exe

AppSetup Value Data: CtxHide.exe UsrLogon.Cmd,cmstart.exe.

Related:

How Do I Setup TLS_FALLBACK_SCSV On NetScaler?

Use Case

Protect server against POODLE attack by preventing the protocol downgrade attack.

Introduction to TLS_FALLBACK_SCSV

POODLE attack is a man-in-the-middle attack in which an attacker takes advantage of the fall back behaviour of clients (including browsers) to attack servers which support SSL 3.0 and CBC encryption mode.

User-added image

Most SSL/TLS implementations are backward compatible with SSL 3.0 to interoperate with legacy systems. A POODLE attacker leverages the fact that when a secure connection attempt fails, servers will fall back to older protocols such as SSL 3.0. He can trigger a connection failure and then force the use of SSL 3.0 and attempt an attack.

User-added image

To mitigate the POODLE attack, one approach is to completely disable SSL 3.0 on the client side and the server side. However, some old clients and servers do not support TLS 1.0 and above, so disabling SSL 3.0 might not be possible. The solution to this problem is that the browsers and servers should implement TLS_FALLBACK_SCSV which makes downgrade attacks impossible. This is how it works – browsers support a downgrade mechanism in the form of Signaling Cipher Suite Value (SCSV). After a session fails during the initial handshake, the browser will retry, but attempts on version one lower than before. For example, after failing to connect to a server with the max version set to TLS 1.1, the client would retry with the max version set to TLS 1.0. This mechanism basically ensures connectivity but lowers down the security and makes the session vulnerable.

The presence of this SCSV extension in the Client Hello indicates that the client is retrying to connect to the server by using a lower SSL version, after its previous attempt to communicate with a higher version failed. Therefore, if the server finds this extension in Client Hello and also finds that the client is proposing a version that is lower than the maximum version supported by the server, it is a likely indication of a “man in the middle attack” The server drops such handshakes.

Qualys SSL Labs, which test servers and browsers for SSL vulnerabilities, mandates a server to support TLS_FALLBACK_SCSV to get A+ rating.

Related:

Hotfix XS72E003 – For XenServer 7.2

Who Should Install This Hotfix?

This hotfix is for customers who use XenCenter as the management console for XenServer 7.2. It constitutes two deliverables:

File Name Description Download Link
XenServer-7.2.0-XenCenterSetup-7.2.1.msi This file updates the XenCenter installation on your Windows machine. DOWNLOAD
XS72E003.zip The download attachment issued with this hotfix updates the server-side copy of XenCenter in a XenServer 7.2 installation See the hotfix Download attachment

Note: Hotfix XS72E003 updates the version of XenCenter included in the XenServer 7.2.0 Base Installation ISO. This updated version of XenCenter MSI is the same as the latest version of XenCenter available to download from the XenServer 7.2 Product Download page. Note that updating XenCenter on your Windows machine does not replace the copy of XenCenter (v7.2.0) on the Control Domain (dom0) of the XenServer 7.2.0 host. Customers must install hotfix XS72E003.zip to update the copy of XenCenter installed on the dom0 of the XenServer 7.2.0 host.

Information About XS72E003

Hotfix Properties Details
Prerequisite: XenServer 7.2.0
Post-update action: None
Contains Live Patch: No
Revision History: Published on NOV 17, 2017

Issues Resolved In This Hotfix

This hotfix addresses following issues:

  • Fixed an issue to enable rolling pool update by using XenCenter from XenServer 7.1 Cumulative Update 1 to XenServer 7.2.
  • Fixed an issue where a local SR with VDIs on it might be destroyed when performing a host upgrade with a multipathed root disk.

Updating XenCenter on your Windows machine

  1. Download XenServer-7.2.0-XenCenterSetup-7.2.1.msi to a known location.
  2. Double click XenServer-7.2.0-XenCenterSetup-7.2.1.msi.
  3. Click Run to start the Citrix XenCenter Setup wizard.
  4. Click Next to continue and follow the instructions on the Setup wizard.
  5. When you have finished making any modifications to the installation directory settings, click Install to start the installation.
  6. Click Finish to exit the XenCenter Setup wizard.

Installing the Hotfix

Customers should use either XenCenter or the XenServer Command Line Interface (CLI) to apply this hotfix. When the installation is complete, see the Post-update tasks in the table Information About this Hotfix for information about any post-update tasks you should perform for the update to take effect. As with any software update, back up your data before applying this update. Citrix recommends updating all hosts within a pool sequentially. Upgrading of hosts should be scheduled to minimize the amount of time the pool runs in a “mixed state” where some hosts are upgraded and some are not. Running a mixed pool of updated and non-updated hosts for general operation is not supported.

Installing the Hotfix by using XenCenter

Choose an Installation Mechanism

There are three mechanisms to install a hotfix:

  1. Automated Updates
  2. Download update from Citrix
  3. Select update or Supplemental pack from disk

The Automated Updates feature is available for XenServer Enterprise Edition customers, or to those who have access to XenServer through their XenApp/XenDesktop entitlement. For information about installing a hotfix using the Automated Updates feature, see the section Applying Automated Updates in the XenServer 7.2 Installation Guide.

For information about installing a hotfix using the Download update from Citrix option, see the section Applying an Update to a Pool in the XenServer 7.2 Installation Guide.

The following section contains instructions on option (3) installing a hotfix that you have downloaded to disk:

  1. Download the hotfix to a known location on a computer that has XenCenter installed.
  2. Unzip the hotfix zip file and extract the .iso file
  3. In XenCenter, on the Tools menu, select Install Update. This displays the Install Update wizard.
  4. Read the information displayed on the Before You Start page and click Next to start the wizard.
  5. Click Browse to locate the iso file, select XS72E003.iso and then click Open.
  6. Click Next.
  7. Select the pool or hosts you wish to apply the hotfix to, and then click Next.
  8. The Install Update wizard performs a number of update prechecks, including the space available on the hosts, to ensure that the pool is in a valid configuration state. The wizard also checks whether the hosts need to be rebooted after the update is applied and displays the result.
  9. In addition, the Install Update wizard checks whether a live patch (this is an Enterprise Edition feature) is available for the hotfix and if the live patch can be successfully applied to the hosts. For more information, see Live Patching in XenServer in XenServer 7.2 Installation Guide.

    Follow the on-screen recommendations to resolve any update prechecks that have failed. If you want XenCenter to automatically resolve all failed prechecks, click Resolve All. When the prechecks have been resolved, click Next.

  10. Choose the Update Mode. Review the information displayed on the screen and select an appropriate mode. If the update contains a live patch that can be successfully applied to the hosts, it displays No action required on the Tasks to be performed screen.
  11. Note: If you click Cancel at this stage, the Install Update wizard reverts the changes and removes the update file from the host.

  12. Click Install update to proceed with the installation. The Install Update wizard shows the progress of the update, displaying the major operations that XenCenter performs while updating each host in the pool.
  13. When the update is applied, click Finish to close the wizard.
  14. If you chose to carry out the post-update tasks, do so now.

Installing the Hotfix by using the xe Command Line Interface

  1. Download the hotfix file to a known location.
  2. Extract the .iso file from the zip.
  3. Upload the .iso file to the Pool Master by entering the following commands:

    (Where -s is the Pool Master’s IP address or DNS name.)

    xe -s <server> -u <username> -pw <password> update-upload file-name=<filename>XS72E003.iso

    XenServer assigns the update file a UUID which this command prints. Note the UUID.

    5b49c861-f2ac-414f-af7e-e7e3049c07da

  4. Apply the update to all hosts in the pool, specifying the UUID of the update:

    xe update-pool-apply uuid=<UUID_of_file>

    Run the following command if you would like to apply the hotfix for a individual host

    xe update-apply host-uuid=<UUID_of_host> uuid=<UUID_of_file>

    Alternatively, if you need to update and restart hosts in a rolling manner, you can apply the update file to an individual host by running the following:

    xe update-apply host-uuid=<UUID_of_host> uuid=<UUID_of_file>

  5. Verify that the update was applied by using the update-list command.

    xe update-list -s <server> -u root -pw <password> name-label=XS72E003

    If the update is successful, the hosts field contains the UUIDs of the hosts to which this patch was successfully applied. This should be a complete list of all hosts in the pool.

  6. If the hotfix is applied successfully, carry out any specified post-update task on each host, starting with the master.

Files

Hotfix File

Component Details
Hotfix Filename XS72E003.iso
Hotfix File sha256 cf1dac45f5eebcf50835f04e5f80be238d1e437204b16820efc4447ba65df89f
Hotfix Source Filename XS72E003-sources.iso
Hotfix Source File sha256 d8175813afd1967a1fd535a1f97643e96f411c79c826d1fb87c1a092c1ea331b
Hotfix Zip Filename XS72E003.zip
Hotfix Zip File sha256 4c6a3f0d0730a467ae305c8630b90b6969159d14354fd6a6d06980bc529e3310
Size of the Zip file 51 MB

Files Updated

xencenter-7.2.1.5539-1.noarch.rpm

More Information

For more information see, XenServer 7.2 Documentation.

If you experience any difficulties, contact Citrix Technical Support.

Related:

A solution to VDA uninstallation failure with ERROR_SERVICE_DOES_NOT_EXIST (1060)

Tradução automática

Эта статья была переведена автоматической системой перевода и не был рассмотрен людьми. Citrix обеспечивает автоматический перевод с целью расширения доступа для поддержки контента; Однако, автоматически переведенные статьи могут может содержать ошибки. Citrix не несет ответственности за несоответствия, ошибки, или повреждения, возникшие в результате использования автоматически переведенных статей.

Related:

  • No Related Posts

App Layering: Host Not Accessible when Editing the CP

Tradução automática

Эта статья была переведена автоматической системой перевода и не был рассмотрен людьми. Citrix обеспечивает автоматический перевод с целью расширения доступа для поддержки контента; Однако, автоматически переведенные статьи могут может содержать ошибки. Citrix не несет ответственности за несоответствия, ошибки, или повреждения, возникшие в результате использования автоматически переведенных статей.

Related:

  • No Related Posts