MMT Android Troubleshooting
KadriLenk
2015/09/03 14:41	

Table of Contents
Error “No connection” 	 # 
Message “Error. Connection timed out” 	 # 
Message “ Necessary permits missing “ 	 # 
Message “User locked or closed “* 	 # 
Message “Filtering error. Packet filtering has caused an error” 	 # 
Message “Document processing error” 	 # 

Error “No connection”
Message “Error. Connection timed out”
Message “Necessary permits missing”
Message “Incorrect username or password”
Message “User locked or closed”*
Message “Filtering error. Packet filtering has caused an error”
Message “Document processing error”
Error “Message. No data”
Error occurs when updating data.
Cause	Solution	
User has no clients assigned to him/her in Telema database.	1. Contact your company Key User to review master data documents	
	2. Contact Telema (if Key User could not handle the problem)	

Error “No connection”
Error occurs when updating data and sending documents.
Cause: No internet connection
Solution:  Enable device’s data connection via mobile network or restart it: press Menu button of the device > go to Settings > Wireless & Networks (or similar) > Mobile networks > check “Data enabled” option (or uncheck and check) i f this does not help restart the device.

Message “Error. Connection timed out”
Error occurs when updating data and sending documents.
Cause: “Connection timed out” refers that the device has internet connection (it is possible to browse the internet) but MMT cannot establish connection with Telema server within given time. At the same time everything is working in wifi. Thus the problem is in data connection settings. 
Solution: Check the data connection settings:
Press Menu button of the device > go to Settings > Wireless & Networks (or similar) > Mobile networks > Access Point Names (or similar) >  ”EMT Internet” must be selected. Change if necessary > Quit settings, and try update data or send documents in MMT again.

Message “ Necessary permits missing ”
Error occurs when updating data and sending documents.
Cause: S ome compulsory permit is missing.
Solution: Check user permits in Telema Admin Web.

Message “ Incorrect username or password ”
Error occurs when updating data and sending documents.
Cause: Incorrect username or password set in MMT application.  
Solution: Check and reset the user credentials in MMT settings: Press devices menu button in MMT main menu screen > Settings > make necessary changes > Save > Update data
* If previous steps did not help then do as follows:
    1. Browse to Telema Portal https://service.telema.com/service/. On the log-in page click on “Forgot your password?” link, insert the required data and system will send the password reset link to your e-mail.
    2. Log in to MMT with new credentials

Message “User locked or closed ”*
Error occurs when updating data and sending documents.
Cause: U ser is locked or closed. 
Solution: Check user status in Telema Admin Web.

Message “Filtering error. Packet filtering has caused an error”
Error occurs when updating the application.
Cause: The device is unable to download newer MMT version.
Solution: Empty the folder “Downloads” from all MMT installation files: Applications> Downloads> Make a check mark next to all the MMT installation files > tap on the Delete button.  
After this, make a restart to the device and try to upgrade Telema MMT program again. If that fails, the application must be  removed  and  reinstalled .

Message “Document processing error”
Error occurs when sending a document.
Cause: Telema EDI system did now accept the sent document. There is some error inside the document.
Solution: First, make sure the user uses MMT version 1.82.14 or newer. If the MMT version is older and user created the document based on another document, it is probably a duplicate document. Ask the user to update MMT version and also to create the document again.
Other cases for this error message can be invalid product or user data (GTIN is a text, username too long, ...). You can check the error log and ask system administrator for more details to find out the exact reason for this error.