Unable to install Citrix Components with the error code 1714 – (Failing action was “RemoveExistingProducts”)

While performing a upgrade by uninstalling the previous version of a Citrix Component and installing the newer version, it fails with the following error being logged in the Installation Logfile.

$ERR$ : XenDesktopSetup:CitrixProductHere failed to install, with internal error code 1714, failing action was “RemoveExistingProducts”

Related:

  • No Related Posts

Error: “AddOrRemoveSSONProvOrder: Could Not Open Key for Access” While Installing Receiver 14.4.1

Uninstalled traces of Receiver using Receiver Cleanup Utility.

Checked HKEY_LOCAL_MACHINESYSTEMServicesPnSson.

This key cannot be removed or accessed or read.

Checked HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlNetworkProviderOrder

and set “ProviderOrder”=”RDPNP,LanmanWorkstation,webclient,PnSson”

Restart client machine and attempt to install receiver.

Receiver 4.4.1 installation was successful.

Related:

  • No Related Posts

VDA Installation Fails With “Installation of the VDA Monitor Plug-in failed with error code 1603.”

  • VDA installation fails with error “Installation of the VDA Monitor Plug-in failed with error code 1603.”

  • In XenDesktop Installation.log saved at C:Users<Install User>AppDataLocalTempCitrixXenDesktop Installer, the below failure was seen.

20:21:46.5890 : XenDesktopSetup:Process completed with error code 0x00000643

20:21:46.5900 $ERR$ : XenDesktopSetup:Installation of MSI File ‘VdaMonitorPlugin_x64.Msi’ failed with code ‘InstallFailure’ (1603).

20:21:46.5920 $ERR$ : XenDesktopSetup:InstallComponent: Failed to install component ‘VDA Monitor Plug-in’. Installation of MSI File ‘VdaMonitorPlugin_x64.Msi’ failed with code ‘InstallFailure’ (1603).

In MSI logs created for VdaMonitorPlugin_x64 the below error got logged:

MSI (s) (28:E4) [20:21:46:564]: Note: 1: 1708

MSI (s) (28:E4) [20:21:46:564]: Product: Citrix Monitor Service VDA Plugin — Installation failed.

MSI (s) (28:E4) [20:21:46:223]: Product: Citrix Monitor Service VDA Plugin — Error 1920. Service ‘Citrix Desktop Service’ (BrokerAgent) failed to start. Verify that you have sufficient privileges to start system services

  • As per procmon logs we saw ACCESS DENIED for BrokerAgent.exe (which runs under NT AUTHORITYNETWORK SERVICE) on file

C:WindowsMicrosoft.NETFramework64v4.0.30319Configmachine.config.

00:51:15.7172558 BrokerAgent.exe 13728 CreateFile C:WindowsMicrosoft.NETFramework64v4.0.30319Configmachine.config ACCESS DENIED Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Open No Recall, Attributes: n/a, ShareMode: Read, AllocationSize: n/a NT AUTHORITYNETWORK SERVICE 0

Related:

How to Remove Files Remaining on System after Uninstalling Receiver for Mac

After uninstalling the Receiver and rebooting the system, ensure that the files or folders listed in this section have been removed from your system. If they still exist, remove them manually.

  1. /Applications-

    Citrix Receiver.app

  2. /Library

    – /Internet plug-ins/CitrixICAClientPlugIn.plugin

    – /LaunchAgents/com.citrix.AuthManager_Mac.plist

    – /LaunchAgents/com.citrix.ServiceRecords.plist

  3. /Users/Shared

    – /Citrix/Receiver Integration (entire folder)

  4. ~/Library

    – /Internet plug-ins/CitrixICAClientPlugIn.plugin

    – /Application Support/Citrix Receiver

    – CitrixID

    – Config

    – Module

    – /Preferences/com.citrix.receiver.nomas.plist

    – /Preferences/com.citrix.receiver.nomas.plist.lockfile

    – /Preferences/com.citrix.ReceiverFTU.AccountRecords.plist (added in 11.6)

    – /Preferences/com.citrix.ReceiverFTU.AccountRecords.plist.lockfile (added in 11.6)

  5. ~/Applications

    – Under this folder, you can delete any applications you previously added via the Receiver UI.

  6. /private/var/db/receipts

    – com.citrix.ICAClient.bom

    – com.citrix.ICAClient.plist

Important Notes

  • A tilde (~) placed at the beginning of a folder path refers to that folder’s location within the user profile. For example, ~/Library/Preferences/ refers to the Preferences folder within the user’s Library folder (e.g. /Users/<username>/Library/Preferences/). A path without a tilde refers to the system-wide version of that folder at the root of the system (e.g. /Library/Preferences/).

  • Note that certain folder mentioned in the list can be hidden directories on the system.

  • It is important to remember that certain items mentioned in this article might not exist on your system depending on the Receiver version(s) you previously installed.

Follow Me Data Notes

In version 11.6, the Follow Me Data feature is integrated into the Citrix Receiver for Mac. The files and folders that are compatible with this feature are listed.

You can remove the files that were not properly cleaned up by the uninstaller. You can also keep the user data that was previously synchronized on your system by Follow Me Data.

  1. The following locations should be cleaned up after running the uninstaller utility:

    – ~/Applications/Citrix/FollowMeData (this is a hidden folder that contains the application binary)

    – ~/Library/Application Support/ShareFile (contains user specific configurations)

    – /Library/PreferencePanes/FMDSysPrefPane.prefPane

  2. Installation information files that are okay to remove after uninstall:

    – /private/var/db/receipts/com.citrix.ShareFile.installer.plist

    – /private/var/db/receipts/com.citrix.ShareFile.installer.bom

File not cleaned up during uninstall that you may or may not want to delete depending on your needs:

– ~/ShareFile (contains the user data synchronized by Follow Me Data)

– /private/var/db/receipts

– com.citrix.ShareFile.installer.plist

– com.citrix.ShareFile.installer.bom


If you are Unable to find the Citrix WorkSpace App running on your MAC and if you want to forcefully quit

Press Cmd + Alt + Escape to see the Force Quit Applications menu.

This will show running apps, and lets you force-quit them if necessary – just highlight the Citrix WorkSpace App and click Force Quit.

Related:

Symantec DLP Network prevent for mail Installation

I need a solution

I’m going to install a detection server (Network prevent for mail ) v15.1 (forword mood) and this is the first time to me and I would like to ask about the problems that could face me while the installation and what should i do to prebare for this installation (the pest practise configuration )

and what about the configuration on the Exchange at the down time ?

0

Related:

  • No Related Posts

Symantec Management Agent error (Failed to restore the certificate to XXXX store, no backup date, error: The system cannot find the file specified (0x00000002).

I need a solution

During the install of the Symantec Management Agent (SMA) to a new computer, the agent installation log shows errors when validating certificate stores.

<event date=’01/23/2020 10:20:55.7190000 -05:00′ severity=’4′ hostName=’jima’ source=’Agent’ module=’AeXNSAgent.exe’ process=’AeXNSAgent.exe’ pid=’14756′ thread=’19548′ tickCount=’58669140′ >
  <![CDATA[Agent is starting. CEM mode is ‘Disabled’, registration status is ‘Not registered’]]>
</event>
<event date=’01/23/2020 10:20:55.7190000 -05:00′ severity=’4′ hostName=’jima’ source=’Agent’ module=’AeXNSAgent.exe’ process=’AeXNSAgent.exe’ pid=’14756′ thread=’19548′ tickCount=’58669140′ >
  <![CDATA[Validating certificate store ‘AeXNSClientPersonal’, restoring the missing certificates from the backup]]>
</event>
<event date=’01/23/2020 10:20:55.7190000 -05:00′ severity=’4′ hostName=’jima’ source=’CertificateManager’ module=’AeXNSAgent.exe’ process=’AeXNSAgent.exe’ pid=’14756′ thread=’19548′ tickCount=’58669140′ >
  <![CDATA[Failed to restore the certificates to ‘AeXNSClientPersonal’ store, no backup data, error: The system cannot find the file specified (0x00000002)]]>
</event>
<event date=’01/23/2020 10:20:55.7190000 -05:00′ severity=’4′ hostName=’jima’ source=’Agent’ module=’AeXNSAgent.exe’ process=’AeXNSAgent.exe’ pid=’14756′ thread=’19548′ tickCount=’58669140′ >
  <![CDATA[Validating certificate store ‘Local ComputerPersonal’, restoring the missing certificates from the backup]]>
</event>
<event date=’01/23/2020 10:20:55.7350000 -05:00′ severity=’4′ hostName=’jima’ source=’CertificateManager’ module=’AeXNSAgent.exe’ process=’AeXNSAgent.exe’ pid=’14756′ thread=’19548′ tickCount=’58669156′ >
  <![CDATA[Failed to restore the certificates to ‘Local ComputerPersonal’ store, no backup data, error: The system cannot find the file specified (0x00000002)]]>
</event>
<event date=’01/23/2020 10:20:55.7350000 -05:00′ severity=’4′ hostName=’jima’ source=’Agent’ module=’AeXNSAgent.exe’ process=’AeXNSAgent.exe’ pid=’14756′ thread=’19548′ tickCount=’58669156′ >
  <![CDATA[Validating certificate store ‘Trusted Root Certification Authorities’, restoring the missing certificates from the backup]]>
</event>
<event date=’01/23/2020 10:20:55.7410000 -05:00′ severity=’4′ hostName=’jima’ source=’CertificateManager’ module=’AeXNSAgent.exe’ process=’AeXNSAgent.exe’ pid=’14756′ thread=’19548′ tickCount=’58669156′ >
  <![CDATA[Failed to restore the certificates to ‘Trusted Root Certification Authorities’ store, no backup data, error: The system cannot find the file specified (0x00000002)]]>
</event>
<event date=’01/23/2020 10:20:55.7410000 -05:00′ severity=’4′ hostName=’jima’ source=’Agent’ module=’AeXNSAgent.exe’ process=’AeXNSAgent.exe’ pid=’14756′ thread=’19548′ tickCount=’58669156′ >
  <![CDATA[Validating certificate store ‘Client Authentication Issuers’, restoring the missing certificates from the backup]]>
</event>
<event date=’01/23/2020 10:20:55.7410000 -05:00′ severity=’4′ hostName=’jima’ source=’CertificateManager’ module=’AeXNSAgent.exe’ process=’AeXNSAgent.exe’ pid=’14756′ thread=’19548′ tickCount=’58669156′ >
  <![CDATA[Failed to restore the certificates to ‘Client Authentication Issuers’ store, no backup data, error: The system cannot find the file specified (0x00000002)]]>
</event>
<event date=’01/23/2020 10:20:55.7410000 -05:00′ severity=’4′ hostName=’jima’ source=’Agent’ module=’AeXNSAgent.exe’ process=’AeXNSAgent.exe’ pid=’14756′ thread=’19548′ tickCount=’58669156′ >
  <![CDATA[Validating certificate store ‘Intermediate Certification Authorities’, restoring the missing certificates from the backup]]>
</event>
<event date=’01/23/2020 10:20:55.7410000 -05:00′ severity=’4′ hostName=’jima’ source=’CertificateManager’ module=’AeXNSAgent.exe’ process=’AeXNSAgent.exe’ pid=’14756′ thread=’19548′ tickCount=’58669156′ >
  <![CDATA[Failed to restore the certificates to ‘Intermediate Certification Authorities’ store, no backup data, error: The system cannot find the file specified (0x00000002)]]>
</event>

Questions

1. Why are the certificates missing in the first place? Is it because the SMA has never been installed and the certificates are provided as a part of the install of the SMA?
2. Where is the so-called backup that the agent is going to restore these missing certificates from?
3. Why do i not have any backup data? 
4. What can’t the SMA install find the files it needs? error: 0x00000002
5. What should i do to resolve this issue? 
6. Is there a way to completely disable HTTPS and not require ceritifcates in the first place? I already unchecked HTTPS in every place possible i could find but i might be missing places?  Or do certiicates have to be validated even if HTTPS isnt enabled?

Thank You!

0

Related:

How to Install new ver SMG on Oracle VM

I need a solution

Hello everybody!

We initially installed the SMG ver.10.6.5-1 system on Oracle VM 3.4.
Everything works.
However, we were not able to upgrade to 10.6.6-5.
Now, installing the latest version 10.7.3 also failed.
We tried updating and reinstalling.
Does anyone have experience installing SMG other than on Vmvare?

0

Related:

Driver Disk for Qlogic fastlinq qede 8.42.10.0 – For Citrix Hypervisor 8.x CR

Who Should Install this Driver Disk?

Customers running a Citrix Hypervisor 8.x Current Release who use Qlogic’s fastlinq driver and wish to use the latest version of the following:

Driver Module Version
fastlinq (qede) 8.42.10.0

Issues Resolved In this Driver Disk

Includes general enhancements and bug fixes.

Installing the Driver Disk

Customers should use the Citrix Hypervisor CLI to install this update. Once the driver has been installed, the server must be restarted. As with any software update, Citrix advises customers to back up their data before applying this driver disk.

Please note that the attachment to this article is a zip file. It contains both the driver disk ISO mentioned below, and the source code for the driver. The zip file should be unzipped (to produce the driver disk ISO image), before carrying out the steps below. The source code file is not necessary for driver disk installation: it is provided to fulfill licensing obligations.

Installing as Part of a Clean Citrix Hypervisor Installation

  1. After you have selected your keyboard layout at the first installer prompt, you will be presented with a welcome screen. At this point, press F9 on your keyboard, and insert the CD with the driver disk in it, or use one of the other methods such as installation over the network.

    Note: If installation over HTTP or FTP is to be used, the ISO image must be unpacked at that location (i.e. the installer expects to find the contents of the ISO at that network location, not the ISO itself).

  2. The installer will proceed to attempt to load the driver. If this is successful, you can continue with the installation as normal. Near the end of the installation, you will be prompted to re-insert the driver disk (otherwise known as a Citrix Hypervisor supplemental pack) so that the driver can be installed onto disk. You must re-supply the driver disk at this point. Failure to do so will mean that the installation will not contain the new drivers. After this step, no further action is required.

If the installer fails to load the new driver from the driver disk, it is likely to be because an earlier version of the driver has already been loaded. In general, this is because a hardware component is present that is supported by the version of the driver that ships as part of XenServer (even if another component is present that requires a newer version of the driver). To avoid the existing driver being loaded, use the following procedure.

  1. Reboot the host, leaving the Citrix Hypervisor installation CD-ROM in the drive.
  2. At the boot: prompt, type:

    shell

  3. You will now be presented with a command prompt. Type the following:

    rmmod qede

    rmmod qedf

    rmmod qedi

    rmmod qedr

    rmmod qed

    If this succeeds (i.e. there are no error messages printed), the installer’s versions of the drivers have been unloaded. If error messages are presented, it is likely that other drivers depend on one or more of the drivers you are attempting to unload. If this is the case, please contact Citrix Technical Support.

  4. Type

    exit

    or press Control+D on your keyboard, to return to the installer.

  5. Use the procedure described above to provide the driver disk to the installer, which should now load correctly.

Installing the update by using the xe CLI

Perform the following steps to install the update remotely using the xe CLI:

  1. Download the update to a known location on a computer that has XenCenter installed.
  2. Upload the update:

    xe update-upload file-name=driver-qlogic-fastlinq-8.42.10.0.iso

    Note: The UUID of the update is returned when the upload completes.

  3. Apply the update:

    xe update-apply uuid=b733d754-725f-4b31-9995-4b2badd1a3a4

  4. To complete the installation, restart the host. This ensures that the driver loads correctly.

Files

Update Files

Component Details
Filename driver-qlogic-fastlinq-8.42.10.0.iso
File sha256 12a6f4ad0136ef862269b96fb4a8113fbc2e0e363ad35fb1f7c1a9d91f17dfd3
Source Filename driver-qlogic-fastlinq-8.42.10.0-sources.iso
Source File sha256 d9fb75cbbd261653517ffd849799c8fb95aac1f9a2aa5a00cf0084a789c391bb
Zip Filename driver-qlogic-fastlinq-8.42.10.0.zip
Zip File sha256 e87e29f8b69d0a69d7c9c81cf8a148c42dc49ffcf795a97f468ba12d58a25f8e
Size of the Zip file 168.03 MB

RPMs Provided

RPM Name
qlogic-fastlinq-8.42.10.0-3.el7.centos.x86_64.rpm

More Information

For a list of the driver versions and the latest driver disk updates available, see Driver versions for XenServer and Citrix Hypervisor.

If you experience any difficulties, contact Citrix Technical Support.

For information on how to build driver disks, refer to Citrix Hypervisor Supplemental Packs and the DDK Guide .

Related: