This topic helps you solve app deployment problems with Microsoft Intune.
If this information does not solve your problem, see How to get support for Microsoft Intune to find more ways to get help.
Typical app deployment problems
If you can’t log in to the Microsoft Intune company portal
Check to see if your account exists in the Office 365 portal or if it is disabled.
Make sure that you are provisioned on this account in the Office 365 portal.
In the Office 365 portal, make sure that you are using the right user name and password to log in to Intune and that it is in the format: firstname.lastname@example.org.
If the Contact IT information is missing in the company portal
In the Intune admin console, choose Admin > Company Portal.
Set the Contact IT details.
If you can’t see specific apps in the list
Make sure you are checking the list of apps for a user or device to which the app was deployed.
Make sure that the device meets the requirements for the app.
If you get an error while downloading an app
Make sure there isn't more than one concurrent download per user. Each user can download one app at a time.
Make sure there are not too many concurrent downloads per account. Wait a few minutes and then try again.
If you receive an iOS native message that you can't install, that the installation is canceled or that you need to retry, it might be due to high traffic. Wait a few minutes and then try again.
If the iOS app download progress bar is complete but the app installation fails, something might be wrong with the app files that you provided.
If an iOS app link takes you to a previous location in the iTunes App Store
The current iTunes App Store session is opening to the previous app page.
Close the iTunes App Store on the device and retry the link.
If you receive an error while launching an iOS app
- The expiration date of the app might not be valid.
If your app is stuck “in progress” while uploading
When uploading an app, first the metadata is added, followed by the app package. After the metadata has been uploaded, the app will appear in progress. If you see that your app is in the in-progress state for an unusually long time, delete the app and then upload it again.
Make sure not to manage the deployment of the app while it is in the “in progress” state.
If you encounter a failure when installing an iOS app
Make sure that your organization’s firewall allows access to the Apple provisioning and certification web sites.
For more information, view the Apple developer documentation.
Error: Publisher does not exist
You use Add Other Software Agreement to add a 3rd party license agreement. You try to add the publisher from the Other software licensing agreement page. The page provides a list with the existing publishers in alphabetical order. You enter the missing publisher but receive the error Publisher does not exist.
This is by design. Intune provides license tracking only for popular software titles. Intune requires that at least 4 separate accounts report the software before it is made available as a choice in the licensing workload.
If managed apps are not reporting installation status
Installation status was not collected for managed app installations prior to the Microsoft Intune service update in November 2014. For devices that installed managed apps prior to this service update, update each associated app deployment with the appropriate deployment action (for example, Available install). Each device will update the app during the automatic check for available apps. For more information, see Update apps using Microsoft Intune.
The following table lists common errors that may occur during Intune app deployment, the likely causes, and possible solutions to help you troubleshoot them.
|Error code||Possible problem||Suggested resolution|
0x80CF201C (client error)
|To install this app, you must have a sideloading-enabled system.||Make sure that the app package is signed with a trusted signature and installed on a domain-joined device that has the AllowAllTrustedApps policy enabled, or a device that has a Windows Sideloading license with the AllowAllTrustedApps policy enabled (applied when a Windows RT device is enrolled).|
|0x80073CF0||The package could not be opened.||Possible causes:
- The package is unsigned.
- The publisher name does not match the signing certificate subject.
Check the AppxPackagingOM event log for more information.
|0x80073CF3||The package failed update, dependency, or conflict validation||Possible causes:
- The incoming package conflicts with an installed package.
- A specified package dependency is not found.
- The package does not support the correct processor architecture.
Check the AppXDeployment-Server event log for more information.
|0x80073CFB||The provided package is already installed, and reinstallation of the package is blocked||You might receive this error if you are installing a package that is not identical to the package that is already installed. Confirm the digital signature is also part of the package. When a package is rebuilt or re-signed, that package is no longer bitwise identical to the previously installed package. Two possible options to fix this error are as follows:
- Increment the version number of the app, then rebuild and re-sign the package.
- Remove the old package for every user on the system before you install the new package.
|0x87D1041C||Application installation succeeded but application is not detected.||- User installed app from company portal, then uninstalled directly from the device. Reinstall app from the company portal.
- You may have a mismatch between the version number of a line-of-business app as recognized by Intune, and the version installed on the device. Ensure Intune has the correct version and reinstall the app.
If this troubleshooting information didn't help you, contact Microsoft Support as described in How to get support for Microsoft Intune.