Probable Cause: 

• Desktop app was installed and then user was granted new roles & newly assigned roles are not installed.

Probable Solution:

• Verify if the newly assigned roles have been installed.
  • Login to Platform on Web
  • Click on Compass and select the "newly assigned role"
  • Click on the small down arrow (Chevron) beside any native app, For example - Assembly Design or Part Design

  • Check if there is a message to "Install Roles" or a option in green which says "New Roles Available" or in Orange "Update Available"

    

Before: App could not be launched - KO

After: App can be launched - OK

Probable Cause:

• Please ignore the level and release of Desktop app in the screenshot and notice that when clicking on the down arrow besides the app, there is no blue line visible which suggests that the option is not selected. (screenshot 1)
• Therefore the platform is not able to find the installation. 

Probable Solution:

• Select the option (click on it) which will then have the blue line and then try to launch the app. 

Probable Cause:

• This message appears when you have a license expired on the tenant mention in error and the role is still assigned.
• Note that tenant mentioned in the warning/error is a Where Used (WU) tenant and is usually numbered +1 your Where Access (WA) tenant. 
• Ex: if WA tenant id you know is R1132100000123 then WU tenant would be R1132100000124. (This is true in most of the cases)

Probable Solution:

• If the WA tenant is still active, Contact Administrator of the tenant to remove the role which is expired.
• If the tenant is not active : Open a SR with below information
  • Error message attached to the SR
  • Tenant id and username shown in error message
  • If there are multiple error messages, Include all the screenshots of each error message

Probable Cause:

• This is as per the design specification. 
• You cannot use a desktop app license on multiple machines at a time, 
• To use desktop app on another machine you should end all the processes involving 3DExperience native app from machine 1 (or shut down machine 1) and wait for 30min to 2hrs to be able to use the license on machine 2.

Note: If the machine name mentioned in error is the same as you are working on then please open a SR.

Probable Cause:

• As the error suggests you dont have access to at least 1 collab space or some of the licenses on your tenant are expired.

Probable Solution:

• User facing the issue should contact the administrator to make sure they have access to at least 1 collab space
• Check if there are enough licenses on the tenant for all users.
• If there are not enough licenses for all users on the tenant, please order the missing license 
• If the number of licenses are enough for all users on the tenant, then an SR shall be open to investigate further.

Probable Cause:

The error shown below appears most commonly due to 2 reasons while launching Desktop Application

• User does not have access to any Collaborative Space (3DSpace app >> Confirm user has access to at least 1 Collab Space)
• The Desktop Application has not been updated even after the 15 day grace period is over after the FD upgrade

Probable Solution:

• Contact your administrator to allow access to at least 1 collab space or create your own collab space.
• Make sure that your desktop application is updated to the latest HF.

Reference: QA00000055307

Probable Cause:

• As an administrator of the tenant, you might have chosen a different location for the "Native Apps Environment Configuration file"
• After a Release upgrade (Ex: 3DEXPERIENCE R2024x to 3DEXPERIENCE R2025x) this file becomes obsolete and needs to be updated.
• Configuration file is not updated after a Release upgrade, you will not be able to launch the desktop application.

Probable Solution:

• Make sure you have a valid "Native Apps Environment Configuration file". 
• The easiest solution is to Empty "Native Apps Environment Configuration file" field. By doing so the platform will use the default path "%Install-Root%\\CATEnv".

Reference: QA00000059072

Probable Cause:

• This is due to connection error between the client machine launching the app and DS License Server (DSLS)

Probable Solution:

• Check the knowledge article to fix the issue.
• QA00000030462: DSLS connection error when launching 3DEXPERIENCE Native Apps on the Cloud