Potential issues and resolutions
Get a session ID
If you encounter a problem with the mobile app, you can help Microsoft troubleshoot the problem much more effectively if you provide them with a session ID for that problem.
From the navigation bar, select > Settings.
Select About and then you will see the Sesson ID.
Troubleshoot We can’t find any apps for your role error message on Dynamics 365 for phones and tablets.**
When using Dynamics 365 for phones and tablets, you encounter the following message:
We can’t find any apps for your role. To check for recently-added apps, select Refresh.If you can’t find your app, change your search criteria and try again.
For more information see, Troubleshoot "We can’t find any apps for your role" error message.
Troubleshoot issues where user does not have the Dynamics 365 for mobile privilege
Make sure you have these required privileges before using the mobile app.
Troubleshoot error code 800c0019 on Windows Phones
If you get error code 800c0019 when you try to sign in to your Microsoft account while using the Dynamics 365 for phones or CRM for phones express apps, chances are that you have the wrong date and time settings on your Windows 8 phone. This can occur after updating your Windows 8 phone, removing and replacing the battery, or after a time change.
In most cases, your phone’s date and time is set automatically by your mobile operator. If it’s not, you need to set it manually so you can sign in to your Microsoft account successfully. Here’s how:
On Start, flick left to the App list and tap Settings.
Turn off Set automatically.
Set the correct values for Time zone, Date, and Time.
Troubleshoot a Windows app start-up error
If you receive this error:
Additional steps may be needed to configure Dynamics 365 for Customer Engagement for this organization. Please contact your system administrator.
If you’re using a computer or tablet
|Users:||Notify your administrator that you received this error.|
|Admins:||To enable the Dynamics 365 for Windows 8.1 app for Dynamics 365 Customer Engagement (on-premises) deployments, you need to make some configuration changes. More information: Set up Dynamics 365 for phones and tablets
|Important: Customer Engagement (on-premises) deployments require Windows 10 and the Dynamics 365 apps for Windows app built for Windows 10.|
If you’re using a Windows phone
You received this error because you’re trying to connect to a Customer Engagement (on-premises) deployment, which is not supported for your version on Windows Phones. Windows Phone connection to Microsoft Dynamics 365 on-premises requires the Dynamics 365 apps for Windows app built for Windows 10. More information: Support for Dynamics 365 for phones and tablets
Error message: Your device configuration is preventing sign-in
If you receive this message it means that your IT administrator is using Microsoft Intune and requires you to sign-in securely using an authenticator app, but your device configuration is blocking the Dynamics 365 for phones and tablets app from launching the authenticator app installed on your device.
Steps to resolve the issue are device manufacturer-specific and depend which authenticator app you have installed. Microsoft authenticator apps are Authenticator and Company Portal. Your company may also use a third-party authenticator app. If you are unsure, ask your IT administrator which authenticator app you should be using and then follow the instructions below.
For Huawei and Honor device, do the following:
- Go to Settings > Battery > App launch.
- Under Manage automatically for the authenticator app set the toggle switch to OFF.
- On the Manage manually screen ensure that Secondary launch / Can be launched by other apps is enabled. This will allow Dynamics 365 for phones and tablets can launch the app.
For Vivo device, do the following:
- Go to Settings > More Settings > Applications > Autostart.
- Set the toggle switch to ON for the authenticator app.
For other device manufacturers, please email Dynamics 365 Mobile Support email@example.com and include your device make and model and quote the error message above.
Error message: This record is unavailable
If this message appears when a user starts the mobile app, taps the Home button, or selects Dashboards from the menu, the user likely doesn’t have access to the expected dashboards.
If you’re an admin, you can avoid users getting this error by making sure all mobile users have access to the sales dashboard:
In the web app, go to Settings > Customizations > Customize the System.
Select Sales Dashboard.
Click Enable Security Roles.
Select Display to everyone and then click OK. If you prefer to display only to select security roles, be sure to select your user’s security role.
Have your user close and open the mobile app so your dashboard changes will download.
If you’re an end user and you’re seeing this message on your home page, you can choose a different dashboard and set it as your home page:
From the mobile app, tap the menu and then tap Dashboards.
On the command bar, tap Select Dashboard and then select the dashboard you would like to use as your home page.
On the command bar, tap Set as Home.
If you’re an end user and you’re seeing this message on the dashboards page, you can create a personal dashboard through the web app and enable it for mobile:
In the web app, go to Sales > Dashboards.
Enter a name for your dashboard and select Enable for mobile.
Add the components you want on your dashboard and click Save.
In the mobile app, follow the previous procedure to select your new dashboard and set it as your home page.
Error message: Your server is not available or does not support this application
Cause 1: The Dynamics 365 server is down. Verify that the server is on and connected to your network.
Sample Trace Message for Cause 1:
“Dynamics CRM [Error] | Connection error: 404”
Cause 2: Your Dynamics 365 apps version is not supported. See What's supported for version support information.
Cause 4: This error can also occur if you enter an invalid URL. Make sure the same URL you have provided works to access Dynamics 365 for Customer Engagement in your browser on your device.
Sample Trace Messages for Cause 4:
“XMLHttpRequest: Network Error 0x2ee7, Could not complete the operation due to error 00002ee7.”
“Dynamics CRM [Error] | Connection error: 0”
Error message: You haven't been authorized to use this app. Check with your system administrator to update your settings
Cause 1: Verify that your Dynamics 365 for Customer Engagement security role includes the Use Dynamics 365 for tablets privilege. See "Required privileges" in Get started with Dynamics 365 for phones and Dynamics 365 for tablets.
Cause 2: This error can occur if you have a Dynamics 365 for Customer Engagement organization and your user has not been assigned a Dynamics 365 for Customer Engagement license. If you add a Dynamics 365 for Customer Engagement subscription to an existing Office 365 tenant, your user may not have a Dynamics 365 for Customer Engagement license assigned. If the user has the Global Administrator or Service Administrator role in the Microsoft Online Service Portal, you’re able to sign in to the Dynamics 365 for Customer Engagement web application to perform certain administrative actions, but you can’t perform end user tasks, such as creating records (for example, accounts, contacts, and leads) or configuring Dynamics 365 for tablets. When you sign in to the web application, you may notice that not all areas appear within the navigation (for example, Sales and Marketing are missing):
Access the Users and Groups section within the Microsoft Online Service Portal and verify you have a Dynamics 365 for Customer Engagement license assigned to your user record.
Error message: You need an internet connection to use this app. Reconnect and try again
Cause 1: This error can occur if you do not have an Internet connection. Verify you are connected to the Internet and can access the same URL in your web browser.
Cause 2: Check if you are using a preview build of Windows 8.1. So far this issue has only been reported with the preview version of Windows 8.1.
Error message: Sorry, something went wrong while initializing the app. Please try again, or restart the app
Cause 1: Permissions might not be set properly. See "Required privileges" in Get started with Dynamics 365 for phones and Dynamics 365 for tablets.
Cause 2: See the following KB article:
An error occurs in the Dynamics 365 for Customer Engagement app for users in child business units. For more information, see Sorry, something went wrong while initializing the app.
Sample Trace Message for Cause 2:
Error Message:System.NullReferenceException: Object reference not set to an instance of an object.
at System.Linq.Enumerable.Any[TSource](IEnumerable1 source, Func
at Microsoft.Crm.Application.WebServices.ApplicationMetadataService.UserRolesChanged(Guid clientUserRoles, DateTime syncTime, ExecutionContext context)
at Microsoft.Crm.Application.WebServices.ApplicationMetadataService.RetrieveUserContext(UserContextRetrieveRequest userContextRetrieveRequest)
Cause 3: This can occur if the download of the metadata failed. The next attempt to connect will fully regenerate the metadata and successfully connect. Microsoft is aware of an issue where metadata may fail to download due to a timeout and plans to address this issue in a future update.
Sample Trace Messages for Cause 3:
“Error occurred during complete refresh of Application/Entity/Attribute metadata”
“XMLHttpRequest: Network Error 0x2ef3, Could not complete the operation due to error 00002ef3.”
Error message: The language installed on your company’s system isn’t available on the app. Please contact your system administrator to set up a supported language
Cause: This error will occur if one of the supported languages is not enabled in Dynamics 365 for Customer Engagement. For more information on the supported languages, see Dynamics 365 for tablets: Set up and use and expand What you need to use Dynamics 365 for tablets and Supported Languages.
Error message: The process assigned to this record is unavailable or has been deleted
If you receive this message for a record which has a non-deleted process assigned to it, you should manually synchronize Dynamics 365 for tablets with your Dynamics 365 for Customer Engagement data. Close the Dynamics 365 for tablets app, reopen, and then choose to download the latest customizations. This procedure forces Dynamics 365 for tablets to check for updated customizations. Recently viewed data while you were connected is cached and synched. Record data like Accounts or Contacts are not synched. You can’t choose which data synchronizes to the device like you can with Microsoft Dynamics 365 for Outlook.
Error message: This operation failed because you’re offline. Reconnect and try again
This error may occur for the following scenarios when you are using a Windows 8 device and you have a Dynamics 365 for Customer Engagement organization that uses Microsoft account (formerly named Live ID). This issue doesn’t occur for organizations provisioned through Office 365.
Cause 1: You are automatically authenticated as a different Microsoft account that is not a member of the Dynamics 365 for Customer Engagement organization. This may happen if you sign into your Windows 8 device and your domain account is connected to a Microsoft account. For example: you sign in to your device as <userid>@contoso.com (your domain account) and that account is connected to <userid>@live.com (a Microsoft account). If your connected account (for example, <userid>@live.com) is not a member of the Dynamics 365 for Customer Engagement organization, you will encounter this error. In this scenario, the error occurs after providing your URL, but you are never prompted for credentials. When you connect your domain account to a Microsoft account, that account will be used to automatically sign in to apps and services that use Microsoft account for authentication. If you’re using a Windows 8 device, use the steps listed here to check if your domain account is connected to a Microsoft account. If you’re using a Windows RT device, see the Windows RT section.
Swipe from the right side of the screen to access the charms bar and then tap Settings.
Tap Change PC settings.
Check to see if under the Your Account section it says “This domain account is connected to <Your Microsoft account>”
If you are using a Windows RT device and need to authenticate as a Microsoft account that is different than the one you use to log on to your device, you must create another account and switch to that account when using the app. For example: you currently sign in to your Windows RT device as <userid>@live.com, but want to access your Dynamics 365 for Customer Engagement organization via the tablet app as <userid>@outlook.com. For more information on how to create a new account on your device, see Video: Create a user account.
Sample Trace Message for Cause 1:
The app couldn’t navigate to https://port.crm.dynamics.com/portal/notification/notification.aspx?lc=1033&organizationid=<OrganizationId> because of this error: FORBIDFRAMING.
Cause 2: This error may occur if you previously authenticated to the app as a different Microsoft account and chose the option “Keep me signed in”. Even after uninstalling and reinstalling the app, the token for the previous credentials is still stored on your device. If you are trying to connect as a different user, you will need to remove the token. To completely clear the app, after you uninstall the app, you must clear the Indexed DB folder (Drive:\Users\%USERNAME%\AppData\Local\Microsoft\Internet Explorer\Indexed DB). You may have to sign in as a different user and use the command prompt as an administrator to clear the Indexed DB folder. That is because some files in this folder can be held by the Host Process for Windows Tasks. Once the token is successfully removed, you should see the sign-in page after you enter your URL in the app.
The same error as Cause 1 may be found in the traces.
Cause 3: You have not accepted your invitation to the Dynamics 365 for Customer Engagement organization. If you attempt to access the same URL through your browser, you see a notification that you are invited to the organization but need to accept the invitation. Once you accept the invitation, you are able to configure the app successfully.
Sample Trace Message for Cause 3:
The app couldn’t navigate to https://port.crm.dynamics.com/portal/response/Response.aspx?token=KFES-CK5C-NL8R-X1U0&expiration=635211904207200000&cs=Lkya6zs9EeOtJXjjtRc6AeZa5xqt94YAppfqrXFgZa5slinq2iaabTmwfX0AR4HLGvz&cb=invite&cbcxt=invite&wlid=<username>%40live.com&lc=1033 because of this error: FORBIDFRAMING.
For each of the causes listed previously, you may also see the following event logged in the traces:
“Authentication: Failed - cookie setup”
Cause 4: If you connect to a Dynamics 365 for Customer Engagement organization on an Android device, this error can occur if the certificate from the Dynamics 365 for Customer Engagement website or the federated server, such as AD FS, is not trusted by the device. To avoid this scenario, make sure to use a publicly trusted certificate or add the Certificate Authority certificate to the device. For more information, see KB article: While configuring Dynamics CRM for phones and tablets, you receive an error message.
Error message, Dynamics 365 for Good: We’re sorry. Your server is not available or does not support this application
Users must update to the latest version of the Dynamics 365 for Good application prior to updating to Dynamics CRM Online 2015 Update 1. On the Apple App store, the version the users need is 1.1. On the Good Dynamics Marketplace or (Good Control Console), the version needed is listed as 1.1.0.
Users who have not updated their app prior to connecting to Dynamics CRM Online 2015 Update 1, will likely see the following error approximately 2 minutes after connecting to Dynamics CRM Online 2015 Update 1.
Error: We’re sorry. Your server is not available or does not support this application.
To fix this error, the user must uninstall and reinstall the Dynamics 365 for Good app using the version listed above.
Event 10001 messages appear in the Event Log when you run Dynamics 365 for Windows 8
The following event may be recorded multiple times to the Event Log, when Show Analytic and Debug Logs is enabled, on the device where Dynamics 365 for Windows 8 is running. Notice that, by default, Show Analytic and Debug Logs is disabled in Event Viewer and these messages won’t be recorded. More information: Enable Analytic and Debug Logs
Event Id: 10001
SEC7131 : Security of a sandboxed iframe is potentially compromised by allowing script and same origin access.
Verify the source of the messages. If the source is Dynamics 365 Server, these events don’t pose a security threat and can be ignored.
By design: “—d” added to URL
For Dynamics 365 for Customer Engagement users
To improve the reliability of DNS resolutions to Dynamics 365 for Customer Engagement organizations, Dynamics 365 for tablets modifies the organization URL used when signing in. When a user signs in, Dynamics 365 for tablets adds “—d” (two dashes + d) to the URL. For example, if the organization URL is https://contoso.crm.dynamics.com, Dynamics 365 for tablets will change the URL to https://contoso--d.crm.dynamics.com.
If a user needs to retry signing in, they’ll see “—d” in the web address. They can sign in with the modified URL or reset it to the URL normally used.
After providing credentials the app appears to load indefinitely and never completes
This can occur if the time on the device is not within a certain variance of the Dynamics 365 for Customer Engagement server. For example: you may encounter this issue if the time on the server is 2 PM on November 11th but the device is set to 2 PM on November 12th.
You may see events like the following logged multiple times in the trace files:
Dynamics CRM [PAL] | Authentication: Token Expired with Token Timeout value (-255674015) --- Retrieving new Auth Token from shim
Dynamics 365 for tablets users are repeatedly prompted for sign-in credentials and can’t sign in
Cause: This can occur if certain directories under the Dynamics 365 for Customer Engagement website have Windows Authentication enabled. For Dynamics 365 for tablets to successfully connect to a new deployment of Dynamics CRM Server 2013 or Dynamics CRM Server 2015, you must run a Repair of Dynamics CRM Server 2013 or Dynamics CRM Server 2015, on the server running IIS where the Web Application Server role is installed after the Internet-Facing Deployment Wizard is successfully completed.
To resolve this issue by running Repair, the Dynamics 365 for Customer Engagement deployment must already be configured for claims-based authentication and IFD.
When the logon prompt appears, it is an Active Directory logon prompt instead of the sign-in page of your Secure Token Service (STS) such as Active Directory Federation Services (AD FS). The prompt looks like the one shown here.
After you tap Cancel or enter credentials 3 times, you see the correct sign-in prompt.
Redirected URLs do not work when you configure Dynamics 365 for tablets or Dynamics 365 for phones
URLs that redirect, such as IIS host headers or link-shortening websites such as tinyurl or bitly, do not work when you use the URL in the Dynamics 365 apps web address field with Dynamics 365 for tablets or Dynamics 365 for phones during configuration.
For example, an https://www.contosocrm.com host header for a Dynamics 365 apps online website URL that is actually https://crm.contososerver001.com, will not work and will display an error message. To work around this behavior, you must enter the actual web address for the Dynamics 365 for Customer Engagement organization. When this issue occurs and you have enabled logging, the information logged is similar to the following. Notice that the URLs in lines 2 and 3 are different. That difference indicates a redirected URL.
User entered URL: https://URL_entered
Constructed server URL: https://URL_after_CRMforTablets_processing
HTTP Response location: https://URL_that_the_response_came_from
Users not getting customizations
Users will not get customizations made to Dynamics 365 apps if there are draft records present. Users should be encouraged to save records as soon as they go online.
Data cached for offline viewing remains after the entity is no longer enabled for Dynamics 365 for tablets
In Dynamics 365 for tablets, record data is cached as the user visits the record so the user can access the data when going offline.
This cached data persists after the entity is no longer enabled for Dynamics 365 for tablets (Settings > Customizations > Customize the System > [select an entity] > under Outlook & Mobile, deselect Dynamics 365 for tablets).
To remove the cached data, the user must sign out of Dynamics 365 for tablets, or Dynamics 365 for tablets must be reconfigured or uninstalled.
Customization changes do not appear in Dynamics 365 for tablets
Cause 1: The customizations (metadata) from your Dynamics 365 for Customer Engagement organization are cached on your device. The app checks for updated metadata after 24 hours or any time you reopen the app. For customization changes to become available immediately, you must completely close and then reopen the app. If new metadata is found, you will be prompted to download it. For more information on how to completely close an app, refer to the help for your operating system or reference one of the articles provided:
Windows 8: How do I close an app?
iPad: Force an app to close
Android: How to force close Android apps
Cause 2: You may be seeing a different form than the one you customized. If you have multiple forms for an entity, you will see the first form in the form order that you have access to. This is different than the web application where you see the last form you used and have the ability to change between forms.
Private Browsing not supported in Safari
If you enable Private Browsing on your iPad in your Safari browser, you will see the following error message when you attempt to connect to your Common Data Service environment or Dynamics 365 Customer Engagement (on-premises) organization: “[Dynamics 365 has encountered an error.” You will need to disable Private Browsing. Tap the address bar, and then tap Private.
Web app differences in mobile browsers
For differences you can expect to find in the web app when you’re accessing it from a mobile device, see Support for Dynamics 365 for phones and Dynamics 365 for tablets.
Clipboard data – available to admins and customizers
Dynamics 365 for Customer Engagement System Administrators or System Customizers can access other users’ Clipboard data for users of Windows 8 and 8.1 devices.
Users can view queue items in another person’s queue
A user viewing records in Dynamics 365 for tablets can view records in another user’s queue.
Update the Dynamics 365 for Good app before updating to Dynamics CRM Online 2015 Update 1
Users must update to the latest version of the Dynamics 365 for Good application prior to updating to Dynamics CRM Online 2015 Update 1. On the Apple App store, the version the users need is 1.1. On the Good Dynamics Marketplace or Good Control Console, the version needed is listed as 1.1.0.
Users who haven’t updated their app prior to connecting to Dynamics CRM Online 2015 Update 1, will likely see the following error approximately 2 minutes after connecting to Dynamics CRM Online 2015 Update 1.
Error: We’re sorry. Your server is not available or does not support this application.
To fix this error, the user must uninstall and reinstall the Dynamics 365 for Good app using the version listed previously.
App restart required after reconfiguring Dynamics 365 for Good
After you reconfigure Dynamics 365 for Good, the app can get stuck in a loop. You need to close and reopen the app.
On your iPad, press the Home button two times quickly. You'll see small previews of your recently used apps.
Swipe to find the Dynamics 365 for Good app.
Swipe up on the app's preview to close it.
Tap the Dynamics 365 for Good app icon to launch the app and configure for the new org.
Prevent click for mapping and Dynamics CRM Online 2015 Update 1
For users of version 1.0 (1.0.0) of the Dynamics 365 for Good app that have updated to Dynamics CRM Online 2015 Update 1, note that the Prevent click for mapping setting does not work.
To prevent click for mapping in version 1.0 (1.0.0), admins should enable the Require a secure browser for opening URLs setting in the Good Control server, as shown here.
The Prevent click for mapping setting works as expected in Dynamics 365 for Good app version 1.1 (1.1.0). We recommend updating to the latest version of the Dynamics 365 for Good app rather than applying this workaround.
Issue still not resolved?
The following are some suggested details to provide:
What are the specific symptoms you encounter? For example, if you encounter an error, what is the exact error message?
Does the issue only occur for users with certain Dynamics 365 for Customer Engagement security roles?
Does the issue only occur on certain devices but works correctly for the same user on another device?
If you attempt to connect to a different Dynamics 365 for Customer Engagement organization that does not include your customizations, does the same issue occur? If the issue only occurs with your customizations, provide a copy of the customizations if possible.
Does the issue still occur after uninstalling the app and reinstalling it?
- What type of device (ex. iPad 4th Generation, Microsoft Surface, etc…) are you using and what is the version of the operating system (ex. iOS 6.0, Windows 8, etc…)?