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:43Category:Error, WinErrorMessage: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).
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 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.
I ran password recovery for the @xxx.onmicrosoft.com account
Accessed the portal.office.com and confirmed all else was ok with the subscription
Setup On Prem AD Sync again with the recently reset user and password.
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
Run the Azure AD Connector Wizard and select the Source Anchor option
Select Configure Source Anchor
Click ‘Configure’ to commit the settings appropriately
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
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
Dont immediately agree to the ‘policy change’ when you see it in whatsapp
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)
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.
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’.
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.
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.