...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Excerpt |
|---|
Here you can find common error messages and known solutions to them. |
...
| width | 11 |
|---|
...
| Column | ||
|---|---|---|
| ||
|
Login errors
See I can't log in from mobile device
Runtime errors
See Error and Performance Troubleshooting Checklist
See also
| Filter by label (Content by label) | ||||||
|---|---|---|---|---|---|---|
|
...
|
...
|
Installation and Upgrade errors
Error Message | Solution | Link |
|---|---|---|
"Profile Update Failed: Error Details: Details: |
...
 | A new Mobile Document Type has been added called "GetLocalizationData"
| See also Mobile Document Types (6/10) |
Your program license does not allow you to publish 'MOB Print Setup' | Please make sure you have downloaded an updated license for BC, from PartnerSource. Check the license includes both these modules:
| |
Your program license does not allow you to publish 'MOB Ns Resp Buffer' | The license file is missing "ISV Insert rights". In the very last step when creating the License, you have to set this to YES. |
...
 | ||||
AL0185, Extension Compilation Failed [Object] ...does not exist in the current context [Object] ...for the extension object is not found [Object] ...is missing | This is a symptom of symbols for has not been generated in your database. Perhaps you are using a hybrid On-Prem installation where CAL changes have been made. See link - Way two, command:
| |||
The property 'ExtendedDatatype' can only be set if the the property 'Type' is set with any of the values of ... | You may be deploying to an unsupported Platform 13 version. Solution: Upgrade to platform 13.5 (BC13 CU5) | |||
failed to compile.Extension compilation failedobjects/Codeunit/Cod81288.MOB%20Common%20Mgt.al(15,32): error AL0133: Argument 1: cannot convert from 'Record TempBlob' to 'var Codeunit "Temp Blob"' | A version of Mobile WMS Compatible with the next release of Business Central has not been deployed to the customers tenant. | |||
A package with publisher 'Microsoft', name 'System', and a version compatible with '13.0.0.0' could not be loaded. Symbols for the requested app Application by Microsoft 13.0.0 | This is a symptom that symbols for AL development has not been generated in your database. | You need to complete your upgrade. You might be missing step task 12 in this guide: | ||
error AL1024: A package with publisher 'Microsoft', name 'Application', and a version compatible with '13.0.0.0' could not be loaded. Symbols for the requested app Application by Microsoft 13.0.0 | This is a symptom that symbols for AL development has not been generated in your database. Common troubleshooting regarding this topic is very well explained in the following Blog posts: | |||
AL0104, AL0183, AL0198, AL0183 Syntax error, '}' expected | You are running a BC version earlier than the supported 13.5 Please upgrade to a supported version | |||
The application extension with app id 'a5727ce6-368c-49e2-84cb-1a6052f0551c' is already configured for use by the global tenant. | You are trying to publish an app to SaaS with the same GUID as our AppSource app. When installing in SaaS you should simply install via AppSource Marketplace | See also Installation Guide. Download from http://university.taskletfactory.com/ | ||
Receive error: The Bin does not exist. Identification fields and values: Location Code='XXX', Code='' | You may be posting a receipt setup for Cross-Docking, but with no "Cross-Dock Bin Code" populated at the location. | Populate the Location."Cross-Dock Bin Code" field or disable Location."Use Cross-Docking" for the location. If you enabled Cross-Docking you must recreate existing Warehouse Receipts (or manually update Warehouse Receipt Lines Cross-Dock Bin Codes) for the location setup change to take effect. | ||
Internal Error Invalid language ID Supplied | You are missing the "Windows Language ID" in the standard BC "Language" table. | |||
The Code field in the Mobile Language table contains a value (DAN, ENU, DEU) that cannot be found in the associated (Language) table | You are missing the "Windows Language ID" in the standard BC "Language" table. Make sure you have the following languages and language IDs.
| |||
The requested operation cannot be performed in this context | Please check the "Mobile Document Types" setup Page. Ensure that the correct "Processing Codeunit ID" is set up for the "Document Type "involved in the transaction. (The "Document Type" can be found in the "Mobile Dokument Queue" Page) | |||
Sorry, the current permissions prevented the action. (TableData MOB Setup Read: Mobile WMS) Different versions got different variants of the above. | After a new installation: The user needs the MOBWMSUSER permissions set. Please add it the user for all or the current company. After an update to version 5.40 or 5.41 using BC21 or newer: The upgrade code in version Version 5.40 and 5.41 did not handle the change of scope for the MOBWMSUSER permission set if it was included in a different permission set. You will therefor need to find the permissions sets including MOMWMSUSER and delete the inclusion and include it again pointing to the MOMWMSUSER user with the new scope. The problem has been solved from version 5.42 but you will need to solve it manually if you installed 5.40 or 5.41. |
Posting Errors
Area | Document Type | Error Message | Possible Solution | Link/Screenshot |
|---|---|---|---|---|
Printing | PostPickOrder | Order posted successfully. | The error is caused by custom code that attempts to perform Report.Print() to the printername, which does not exist. Write code to check the printer name is correct. | |
Receive | PostReceiveOrder | Sorry, the current permissions prevented the action. | The user has a non-Premium license (i.e. Essential license). There are Records in the Prod. Order Component -table. During Receive, Cross Docking (base code, not Tasklet) will access this table. Is has to be empty for non-Premium uses to post Warehouse Receipts. | |
Receive | PostReceiveOrder | You are not allowed to register multiple bins on Receive orders. | Splitting of purchase lines is not supported by NAV/BC (only one bin can be registered on the mobile device). Workaround: See You are not allowed to register multiple bins on Receive orders | You are not allowed to register multiple bins on Receive orders |
PutAway | PostPutAwayOrder | Qty. to Handle must not be Qty. Outstanding in Warehouse Activity Line Activity Type='Put-away',No.='PU000004',Line No.='20000'. | You may be posting more than 14 different LotNo/SerialNo/ToBin to the same Warehouse Activitity Line. Renumbering activity lines during putaway posting with SplitLine is not supported until standard BC build 13.5.29483.0 and MOB5.11. Workaround: Never scan and register more than 14 different LotNo/SerialNo/ToBin at the same orderline at the mobile device at the same time. Instead, register the ~10-14 order lines you have scanned, then repeat to scan the next batch of lines. Solution: Update to standard application 13.5 (or newer) with MOB5.11 (or newer). | |
Count | PostCountOrder | Phys.Inventory must be equal to 'Yes' in Item Journal Line....Current value is No | You have manually entered a journal line. Journal lines should be calculated.
Use action "Whse. Calculate Inventory" to generate the warehouse journal lines for counting. "Phys. Inventory Journals": Use action Prepare > "Calculate Inventory" to generate the journal lines for counting. | |
Unplanned Move, | PostAdhoc | "Expiration Date must not change for an Item tracked by Lot Number." | With the release of BC 23.2 Microsoft introduced new validation code on the Warehouse Journal, that resulted in problem with our features, Unplanned Move, Adjust Qty. and Unplanned Count. Because of Microsoft changes the Error message "Expiration Date must not be changed for an Item tracked by Lot Number." will occur if Location is setup with "Directed Put-away & Pick" and "Skip Whse. Unpl. Count Item Journal Post" disabled. Extension version 5.45 fixes this | Release Notes (Business Central)#,%5BNTW%2D2300%5D,-Error%20%22Expiration%20Date |
Runtime Errors
Area | Document Type | Error Message | Possible Solution | Link/Screenshot |
|---|---|---|---|---|
Posting | Bulk Move and more | Whse. Document No. must be equal to 'Txxxxx' in Warehouse Journal Line: Journal Template Name=RECLASS, | Remove the number series from the Template Batch. Go to "Warehouse Journal Templates" Go to action "Related" > "Template" > "Batches" | |
ReferenceData | GetReferenceData | Getting Reference data failed. Server response: Microsoft.Dynamics.Nav.Runtime.NavXmlCData variable not initialized | The current Mobile User is not associated with any Mobile Group. | |
Get | Any | Unable to convert from Microsoft.Dynamics.Nav.Runtime.NavInteger to System.String | New Accessor Tables doesn't work on BC 13.0 platform due to FldRef.Value() function working differently on the old platform. Solution: Either (1) Upgrade to platform 14 (or newer) (2) Upgrade to MOB5.11 (or newer) (3) manually modify code:_ local procedure GetValueByFieldNo(var RecRef: RecordRef; FieldNo: Integer): Text | |
Action | Any | No document hander is available for Lookup::Attachments. or Empty Register Images Reference ID field. | Register Images and Attachment actions are included in Mobile App version 1.5.0+. But you need Mobile WMS Extension v.5.17+ to use these features. |
...
 | |||
Unplanned | Unplanned Move | There is not MOB NS Request Element within the filter. Filters: Name: NewLocation | You have changed the setting "Unplanned Count Warning" in Mobile WMS Setup. When changing this, you have Log out of the mobile device and in again. |
...
  | |||
Permissions | Any | You do not have the following permissions on TableData Warehouse Receipt Header : Modify To view details about your permissions, see Effective Permissions page. To report a problem, refer to the following server sessions ID: "xx". | You are using Device SL for BC. We do not sell Device SL. It is something that the partner buys and configures. Please follow the link for reference to how to set this up: |
...
 | ||||
Webservice | Any | Parameter mobileUserID in method ProcessRequest in service MOB_WS_Dispatcher is null! |
| |
Webservice | Any | The metadata object CodeUnit 0 was not found. | The problem was is by not having the standard WMS group and not running the Create Document Types action on Mobile WMS Setup after having created bespoke groups. |
...
 | ||||
Posting | Any | Posting Problem: A problem arose when trying to post the order. Retyr now or try again later. Error details:Request Entity Too Large | The server rejected the mobile response. Increase the "Max message size" on the Service Tier | |
Posting | Production Consumption | Handled must not be No in Mobile WMS Registration Type='Production Consumption',Order No.='xxxx',Line No.='10000',Registration No.='1' |
To resolve the issue:
|
...
 | |||
Webservice | Login/Any | Function ID -1164226044 was called. The object with ID 8703 does not have a member with that ID. |
If this does not work, then use the Repair-NAVApp command from PowerShell. Repair-NAVApp -ServerInstance 'MY_INSTANCE' -Name 'Mobile WMS' -Version 5.42.0.0 |
...
 |
Cloud Print Errors
| Anchor | ||||
|---|---|---|---|---|
Error Message | Explanation | Solution |
|---|---|---|
"A call to System.Net.HttpWebRequest.GetResponse failed with this message. The remote server returned an error (401) Unauthorized. | This is a known issue related to a move to TLS version 1.2. | Download updated NAV Objects version MOB4.60.1
Follow the instructions in the ReadMe.txt file.
|
NAV MOB4.60.1 | This is a known quirk. You have to press "Test Connection" one more time. | |
NAV MOB4.60.1 | You need to run Upgrade Codeunit 6181390 | |
NAV MOB4.60.1 | Incorrect Tenant and/or Username and Password | |
"A call to System.Net.HttpWebRequest.GetResponse failed with this message. The operation has timed out | Incorrect Template Paths | |
An empty response was received from the online print service. | Request data ïs invalid. The cloud service was not able to generate a label based on the Request from Business Central. Ask TF Support to input the data manually into the Designer to determine why not output could be generated. | |
Error in XML. Unable to deserialize XML, hexadecimal value 0x1D, is an invalid character. | You are scanning a barcode from a label. The GS1 barcode contains an "Item Cross Reference" in AI91 with more than four alphanumeric characters. This is a quirk of ZebraPrinter-generated GS1 barcodes. | Option A Contact TF Support to have "forceInterpretation" enabled in start.cfg <dataMatrixenabled="true"forceInterpretation="true"> Option B Use GTIN or a longer "Item Cross Reference" barcodes |
Print problem: Could not connect to device: Failed to connect to /192.168.0.10 (port 6101) from /192.168.172.77 (port 35810) after 15000ms: isConnected failed: ECONNREFUSED (Connection refused) | The printer could be using another port than standard 6101. The printer network cannot be accessed from the Wi-Fi network mobile device uses. | Verify the port number Verify the network routing |
Print problem: Could not connect to device: com.zebra.sdk.comm.ConnectionException | Bluetooth is turned off | Turn ON Bluetooth |
Business Central Report Printing Errors
Error Message | Explanation | Solution |
|---|---|---|
The User Personalization does not exists. | Printing BC Report during Mobile posting fails. | If you try to actively print of standard BC Report as part of a posting routine done from the Mobile device, you need to check the following requirements.
|
Nothing is printed and error message when printing from Mobile on BC On-Prem | The printer might be unknown to the user account, running the Service Tier for Web Service (Mobile communicates with Business Central using this service tier) | Log into the Windows server, with the user account, that runs the service tier for Web Service Install the printer in Windows Printer |
Pack & Ship
Error Message | Explanation | Solution |
|---|---|---|
"The length of the string is 21, but it must be less than or equal to 20 characters. Value: SHIPIT365-1-SADDLEBAG" The above or similar errors might appear during posting, where the "1" and "SADDLEBAG" may contain other values. | Package Codes in Pack & Ship support up to 100 chars, but a function called during posting is unfortunately limited to 20 chars. This is expected to be solved in a future version. | Ensure the package codes in Transsmart have a maximum of 8 chars to limit the total length of package codes to a maximum of 20 chars. |
...
See also
...