Home » KBArticles » Page 2

Category: KBArticles

Citrix Storefront Upgrade Failure 2.x to 3.9


When trying to Upgrade our Citrix storefront servers from a 2.x version to 3.9 of storefront we encountered the following error: This meant the installation failed with the previous storefront version removed completely, and all configuration lost, and we were then unable to install any further version of Citrix Storefront.

Application Log Error, Source: Citrix Extensible Meta-Installer EVENTID: 0
Timestamp: 05/07/2017 19:04:43
Category:Error, WinError
Message:Unexpected exception. Message: Exception has been thrown by the target of an invocation.. Stack Trace =    at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
  at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at Citrix.Cxmi.CustomSandbox.ManagedDllLoader.CallStaticMethod(String typeName, String methodName, Dictionary`2 methodParams)
   at Citrix.Cxmi.Workflow.ExecuteTask.Execute()
   at Citrix.Cxmi.Workflow.WorkflowSequence.Execute()
   at Citrix.Cxmi.Workflow.WorkflowSequence.Execute()
   at Citrix.Cxmi.Workflow.WorkflowExtension.Run()
   at Citrix.Cxmi.Core.Engine.Run()
   at Citrix.Cxmi.Core.Program.Main(String[] args).

Things Tried:

Deletion of all local temp files – Failed

Complete uninstall and reinstall of Storefront versions – Failed

Reinstall of old version 2.x – Failed

Install of new 3.x  version as different user – failed

We had no choice but to revert the VM snapshot to recover the production Web server.


Upgrade to Storefront 3.0 First, then attempt to upgrade to a higher version.

Azure Active Directory synchronisation attempts failing

Unhealth identity synchronization notification.

Azure Active Directory did not register a synchronization attempt from the identity synchronization tool in the last 24 hours for <Company>


There are a large number of reasons why this might be affecting you, however in this specific instance we needed to ensure the Microsoft Azure Active Directory Connect was not stuck at ‘required to upgrade’ screen.

Connect to the AD where you have installed the Sync tool and confirm.

Perform the upgrade as necessary

I then had to spend nearly as hour trying to discover what username / password was configured on this damned account as it was not working with my Azure portal login (portal.azure.com).

As this was a partner subscription from the Microsoft Action pack the original configuration was setup under portal.office.com, also as password synchronisation was setup as part of the AD sync, the previously updated on prem passwords had not synced with Office – so no one could log in with their new passwords.


  1. I ran password recovery for the @xxx.onmicrosoft.com account
  2. Accessed the portal.office.com and confirmed all else was ok with the subscription

  3. Setup On Prem AD Sync again with the recently reset user and password.

  4. Finally we can complete the upgrade.
  5. Upgrade completed


Azure Source Anchor Upgrade from objectGUID

Post setup (or reconfiguration) of Azure AD Synchronization there is a prompt

Azure Active Directory is configured to use AD attribute objectGUID as the source anchor attribute. Its strongly recommended that you let Azure manage the source anchor for you. Please run the wizard again and select Configure Source Anchor.

Why should we do this?

Upgrading this from objectGUID to ms-DS-ConsistencyGUID is best practise and allows for easy recover of accidentally deleted on-premise user accounts.

Walk Through Steps

  1. Run the Azure AD Connector Wizard and select the Source Anchor option
  2. Select Configure Source Anchor

  3. Click ‘Configure’ to commit the settings appropriately

  4. Success


Microsoft Azure Virtual Network Gateway Deletion Failing

You may be frustrated at Microsoft Azure’s lack of ability to power off the Network gateways especially when they are chewing up resources and $. Unfortunately Azure provides no current way to power the gateways down so the only current solution is to delete them, however you need to delete them in the right order to remove the service pre-requisites.


Failed to delete virtual Network Gateway

Failed to delete virtual network gateway 'UKSouthGateway'.
Error: Gateway /subscriptions/xxxxx-xxxx-xxx-xxxx-xxxxxxx/resourceGroups/


The gateway devices must be deleted in a specific order

  1. Connections (both sides)
  2. Local Network Gateway (both sides)
  3. Virtual Network Gateways (both sides)
  4. IP Ranges (only if necessary)

Citrix Cloud Connector Installation Unsuccessful on Windows Server 2016


After multiple attempts to install the Citrix Cloud Connector software we continued to receive even after mutiple reboots.

Installation was unsuccessful. See below for details.
A system restart is pending. The system must be restarted before any products can be installed.


Simple delete / clear the windows registry entry in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations


How to stop WhatsApp sharing your details with Facebook

If, like me, you have recently wondered how to stop WhatsApp sharing your details with Facebook well the team at WhatsApp seem to have already provided this (we hope). So lets us put aside our thoughts of deleting whatsapp entirely, for now, and whilst some of us have paid for a lifetime of “private, no-ads” service, it is still early days yet and this option maybe enough to give us some level of comfort..? Maybe??

Process to stop the data sharing

  1. Dont immediately agree to the ‘policy change’ when you see it in whatsapp
  2. Click the  “read more about the key updates to our Terms and Privacy Policy”
Whatsapp Agreement screen 1 select 'read more' to unshare data with facebook
Whatsapp Agreement Change Aug 2016 – Screen 1

3) Untick the “share my whatsapp account information with Facebook to improve my Facebook ads and product experiences.” (because, you know, our facebook experiences are already so awesome that we would willingly sign up for more targeted advertisements etc)

Whatsapp Agreement screen 2 to unselect the sharing of data to facebook
Whatsapp Agreement Change Aug 2016 – Screen 2


I just received the above messages today on my android phone EE network in the UK (26/08) however it only prompted me after a phone restart.


Unable to downgrade Google Apps for Work trial


A customer had upgraded their free Google Apps to Google apps for Work Trial and wanted to cancel the trial 5 days before the trial ended. In the process of attempting to cancel the trial they were unable to downgrade from ‘Google Apps for Work Trial’ to ‘Google Apps’. There was no option to downgrade back to Google Apps, rather a ‘Cancel and Delete everything’.

Google Apps for work downgrade option not available
Google Apps for work downgrade option not available


During the trial the customer had added some additional domains which were preventing the downgrade option being available, as soon as the additional domains were removed the downgrade option appeared.

This can also happen if the primary domain is changed during the trial as well.

Google Apps downgrade option available
Google Apps downgrade option available

Netscaler MAS Error when adding Netscaler Instance


We received the following Netscaler MAS Error when adding Netscaler Instance to be monitored by the NMAS.

1 Error: Licence cannot be retrieved. Either the Netscaler is unresponsive or the login credentials are incorrect.

Screen Shot 2016-08-17 at 22.20.13


There are a number of reasons this may come up

  1. you are not running an enterprise or platinum licence on the Netscaler appliance.
  2. you have connected to the SNIP and not the NSIP of the netscaler device
  3. you are blocked from communicating with the netscaler NSIP by network firewall etc
  4. you do not have SNMP enabled on the NSIP – so get this enabled


WD MyCloud External USB Drive showing 0Kb


A Client had an network attached WD MyCloud 3TB Drive and had attempted to attach an external 3TB disk (re-purposed with an external JMicron Hard drive caddy)

Regardless of formatting it as NTFS, exFAT  -the JMicron controller was being recognised but the 3TB Disk partition swasnt


Attach the disk to windows and ensure an EFI partition has not been created.

If an EFI partition exists, remove it using diskpart from an elevated command prompt.

(use command: delete partition override as the EFI partition will be marked as protected)

This is what worked for us in this instance and hope it helps others.

Issue with VMWare workstation network bridging

We found a network bridging issue for a client running VMWare workstation 10. The VM would ‘sometimes’ connect to the production / corporate network and obtain a DHCP address. Othertimes it would not and it would get an APIPA address instead. (169.254.x.x)

Various internet posts suggested

  • Disconnecting the Virtual nic – NO SUCCESS
  • Upgrade the VM tools – NO SUCCESS

couldn’t even mount the ISO for some reason, so the .iso’s are located here(“C:\Program Files (x86)\VMware\VMware View\Client\Local Mode”) for future reference so you can extract and then manually run the installation.

  • Remove and re add the NIC  – NO SUCCESS


Turns out that when bridging mode is set to ‘automatic’ VMWare workstation will bind to any and all available network cards. (Bluetooth, wifi, other VMNics, Virtual box etc) So its a bit of pot luck when it connect to the production network and not the others.

  • Open the Virtual Network editor
  • Edit the appropriate ‘bridged’ network and select the appropriate NIC to bridge

  • Be sure the configuration of the VM’s NIC is set to BRIDGED or is bound to the VMNetX that is configured for bridging.

Note: Besure to run the Virtual Network Editor as an administrator else you will not be able to change settings.

Non Admin