Troubleshooting

This section provides a list of some of the common problems that may occur while working with Microsoft Dynamics Mobile - Server Components and Mobile Sales. Each error situation states the problem and explains the nature of the problem, and suggests a workaround to continue the work.

The errors are categorized for easier identification. You may find a solution to your problem in one of the following categories:

  • Installation

  • Deployment

  • Synchronization

  • Operation

  • Integration with Microsoft Dynamics AX

Installation

Problem Cause Workaround

Uninstalling older versions of Mobile Device SDK.

When you uninstall an older version of Mobile Device SDK, an error message may appear that tells you that another version of the product is already installed. The error is not specific to a particular product. The following article explains the global problem. For more information on how to resolve the issue, go to the Macrovision Knowledge Base: http://support.installshield.com/kb/view.asp?articleid=Q105462.

  1. From the command prompt, run the following command:

    MsiExec.exe /I "Mobile Development Tools – Framework Components.exe" REINSTALLMODE=voums REINSTALL=ALL
    
  2. Then run the installation file Mobile Development Tools – Framework Components.exe again.

    You can download the latest version from PartnerSource.

Error while trying to deploy to the mobile device.

The following error message displays:

An error message cannot be displayed because an optional resource assembly containing it cannot be found.

The error may occur during the initial setup of the deployment and during normal activity, such as sending a request document. If the transaction fails, the preceding error message displays.

Verify that you have the latest version of the .NET Compact Framework .CAB file. This file is required to enable deployment to mobile devices. If you have a device that runs Microsoft Windows Mobile 5.0, you will need to download the most recent .CAB file. Mobile devices that run Microsoft Windows Mobile 6.0 have this file as part of the standard software.

You can download the latest version from the following site:

.NET Framework 2.0 Software Development Kit (SDK) (x86)

For more information on prerequisite files, see the topic How to: Install Prerequisite Software on Mobile Devices Before Deploying Applicationment.

Click the following link to review blog entries posted on the .NET Compact Framework Team blog. For more information see .NET Compact Framework Team MSDN blog.

Deployment

Problem Cause Workaround

Mobile device is unable to receive files.

The standard security settings on the mobile device may block the system administrator from sending application files through the deployment service to the mobile devices.

Download the Security Configuration Manager tool, which enables you to:

  • See the current security configuration on your connected device (including certificates).

  • See the policies and certificates for standard security configurations.

  • Check the signature on a file.

  • Deploy the development certificates or a standard security configuration to your connected device (if you have rights to do so).

You can download the Security Configuration Manager from the following site:

Device Security Manager .

Unable to deploy new mobile applications created using Mobile Device SDK.

The following error message may appear if you attempt to deploy a new mobile application:

Cannot load the type: Microsoft.Dynamics.Mobile.Components. component name .

The new mobile application is built using an older version of Mobile Device SDK, which makes it incompatible.

Install the latest version of Mobile Device SDK.

You can download the latest version PartnerSource.

Synchronization

Problem Cause Workaround

Error while synchronizing.

The following message displays when you run the synchronization process:

Last execution failed with the error: An internal error happened in SqlCereplication: The connection is already open (state = open).

Check the connection for the mobile device to the network and repeat the synchronization.

Error while synchronizing to Web server.

This is a common error that may occur when you try to send request documents, retrieve data, or monitor the activities on mobile devices. These actions take place using the Web services.

When you try to connect to your Web server, the following message may appear:

Last execution failed with the error: A request to send data to the computer running IIS has failed. For more information, see HRESULT.

  1. Verify the definition for the URL to your IIS server in the app.config file. To test the connection to the IIS, type the URL in the Internet Explorer browser on your desktop.

  2. Open the web.config file for the Web service that fails and verify that the database connection string is correct. For more information, see How to: Specify Database Connection Strings in a web.config File of the Mobile Web Services.

  3. When you are connected to the network, verify that Active Sync is working. You may have to change the connection type to Reconnect.

Operation

Problem Cause Workaround

Using Intermec Devices with a Barcode Scanner.

If you use the barcode scanner on an Intermec device without all of the prerequisite components, the result is an unhandled exception.

When the barcode scanner is enabled in the preloadDlls section in the app.config file, and you create an order in Mobile Sales, the following error message displays:

An unexpected error occurred while running Microsoft Dynamics Mobile Framework Runtime. The application will terminate. Please contact your administrator if the error persists.

Cannot load the type Microsoft.Dynamics.Mobile.Components.Services.BarcodeScanning.Intermec.ScannerDevice, Microsoft.Dynamics.Mobile.Components.Services.BarcodeScanning.Intermec.

Stacktrace:

at Microsoft.Dynamics.Mobile.Framework.Configuration.ConfigurationManager.GetSectionFromXml()

at Microsoft.Dynamics.Mobile.Framework.Configuration.Configuration.GetSection()

at Microsoft.Dynamics.Mobile.Framework.Configuration.ConfigurationManager.GetSection()

at Microsoft.Dynamics.Mobile.Framework.Runtime.ServiceFactory..ctor()

at Microsoft.Dynamics.Mobile.Framework.RolePadApplication.AddServices()

at Microsoft.Dynamics.Mobile.Framework.CompositeUI.CabApplication`1.Run()

at Microsoft.Dynamics.Mobile.Framework.RolePad.RolePadClient.Main()

  1. Verify that the barcode assembly is present on the computer. Locate the following assembly under the Mobile Device SDK installation folder: Microsoft.Dynamics.Mobile.Components.Services.BarcodeScanning.Intermec.

  2. Enable the itcscan.dll assembly in the preloadDlls section in the app.config file. The assembly is the barcode driver for Intermec devices.

  3. Copy the Intermec.DataCollection.CF2.dll file to the Application folder that is located under the Client folder for the Mobile Sales installation. By default, the Application folder contains the tasklets, the userrole.xml file and the app.config file. The Intermec.DataCollection.CF2.dll assembly is part of the Intermec Development Library.

Using Symbol Devices with a Barcode Scanner

If you use the barcode scanner on a Symbol device without all of the prerequisite components, the result is an unhandled exception.

When the barcode scanner is enabled in the preloadDlls section in the app.config file and you create an order in Mobile Sales, the following error message displays:

Cannot load the type: Microsoft.Dynamics.Mobile.Components.Services.BarcodeScanning.Symbol.ScannerDevice, Microsoft.Dynamics.Mobile.Components.Services.BarcodeScanning.Symbol.

The error may occur because the assembly files Symbol.Barcode.dll and Symbol.dll are not present.

Verify that the two barcode assemblies Symbol.Barcode.dll and Symbol.dll are present on the computer. You can download the assemblies from the Symbol Mobile Developer Kit (SMDK) v1.5 for .NET from the following location: http://support.symbol.com/support/search.do?cmd=displayKC&docType=kc&externalId=10598&sliceId=&dialogID=16346770&stateId=0%200%201115944.

The application cannot create a secure Transport Layer Security (TLS) or Secure Socket Layer (SSL) connection.

The certificates may be invalid or have expired.

Verify that the device is set to the correct date and time.

An error message appears that states no error message can display because the resource collection with the error message could not be found.

This error can be caused by one of the following:

  • The user has changed the regional settings of the device to something other than the locale of the operating system. For example, the locale is English (US), and the user sets the regional settings to Danish.

  • The resource localization assembly System.SR.dll is not found on the device.

On the device, execute the Microsoft .NET Compact Framework 2.0 .cab file that resets the system locale for your operating system locale, and then perform a soft reset.

For example, to reset to the English (US) locale, run the System_SR_ENU.CAB file on the device, and then perform a soft reset.

The default location of the .cab files on a computer that has Microsoft .NET Compact Framework 2.0 SDK installed is C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\CompactFramework\2.0\v2.0\WindowsCE\Diagnostics.

For more information about the resource localization assembly, see

http://msdn2.microsoft.com/en-us/library/t7htf230(VS.80).aspx.

Integration with Microsoft Dynamics AX

Problem Cause Workaround

Error while starting Microsoft Dynamics AX.

An error occurs when you start Microsoft Dynamics AX and the telephony integration configuration key is not configured correctly. The error message displays the following text: “INI-file corrupt.”

By default, the configuration key for telephony integration is set to enabled. The error occurs if you do not have the necessary hardware and software to support the telephony integration configuration key.

You have the following options:

  • Create a new location.

  • Change the configuration in Microsoft Dynamics AX.

To create a new location:

  1. In the Control Panel, select Phone and Modem Options.

  2. Create a new location.

To change the configuration:

  1. Open Microsoft Dynamics AX.

  2. In the Administration menu, select Setup, System, Configuration.

  3. Expand the CRM Series folder and clear the box for the Telephony integration key.

See Also

Community Additions

ADD
Show: