Problems installing Designer when logged into Virtual Machine as administrator

A user reported receiving an error message when trying to install an updated version of Designer from the FastStats Designer x64 Setup.msi onto their virtual machine whilst logged onto the virtual machine as an Administrative account.

We suggested that they try installing a different (non Apteco) program using an MSI file which they did, and this produced the same error:

They also tried an older version of Designer which had previously installed (but this time gave the same error).

After speaking to their 3rd party technical support, the issue was resolved: "The issue was fundamentally a permissions issue with the Administrator account on the VM. Shift-clicking the MSI installer and running it by signing in as our domain administrator allowed us to install Designer successfully."

• Related Articles

• Changing the default email address for the Orbit Administrator

  By default the Administrator user for each Orbit system is created with an email address of support@apteco.com This is done for assistance and reporting purposes e.g. for assistance when setting a new system up. A side effect of this is that any ...

• Admin User cannot see Users Explorer tab or Licences and Bundles screen in FastStats

  A user who believed they were set up as an admin user, reported logging into FastStats but not seeing either the Users tab or the Administration options. After checking the users settings were correct, we realised that in this case the issue was ...

• Issue with Environmental Variables within URLS in Designer build prior to Q2 2024

  A user reported an issue within the post-load action in Designer when upgrading their system from Q1 2023 to Q1 2024. The issue occurred where an environment variable name was included within a pathname of a post-load action. Designer was reporting ...

• Limits issue within FastStats

  We’ve found and fixed an issue with the query component, where in rare situations we didn’t fully clear the limit properties between queries. This could cause a query limit clause to be mistakenly applied to a subsequent query. To apply this fix: ...

• Problem using Post Load Action (Combine Categories) with data from Snowflake

  A user reported that they were in the process of rebuilding a system from a new ODS (Organisation Data Source) within Snowflake. The data contained 3 separate ID variables together with descriptions and the user was aiming to merge these as a ...