Symptoms
- Vehicles not showing up on the map
- Just added a vehicle, but I dont see it on the map.
- Can't see my vehicles on map on my phone.
- Can't see vehicles on the map on my browser, its like I dont have an account.
- I can't see the vehicles live on my map
- I can't see vehicles on the database
- I haven't been able to see my vehicles on the map
- Can't see all vehicles on the map
- Registered trackers not showing up on map
- Device not showing location
- unable to see vehicles in Geotab
Resolution Path
Reason #1 | Device/GPS not communicating |
Resolution #1 | How to troubleshoot a GO device not communicating (while you are at the vehicle) |
Reason #2 | Prevent access to shared data is turned on for your user |
Resolution #2 |
Reason #3 | The user does not have data access to the group containing the vehicles |
Resolution #3 | Unable to see some vehicles or users in MyGeotab because of data access |
Reason #4 | No vehicles are selected to be viewed |
Resolution #4 |
Reason #5 | The devices you are looking for have not been added to the database |
Resolution #5 | Device not showing up on the map because it hasn't been added to the database |
Reason #6 | The devices you are looking for have not communicated to the database yet (devices not activated) |
Resolution #6 |
Reason #7 | The database entered is incorrect (the URL is incorrect) |
Resolution #7 | Login Error: Incorrect Username or Password because database name is incorrect |
Reason #8 | Customer has more than 50 devices on their database |
Resolution #8 | All vehicles do not auto populate on map when there are more than 50 devices in a database |
Reason #9 | Vehicle was made historical | |
Resolution #9 |
Reason #10 | There is a problem with the current browser configuration |
Resolution #10 | Try accessing the database from a different browser or contact internal IT department. |
Reason #11 | User may also be logged into the wrong database as a reason (Could be personal data base) |
Resolution #11 |
Reason #12 | Vehicle name does not match |
Resolution #12 | Ensure the device is associated to the correct vehicle. |
Reason #13 | User may be lock out |
Resolution #13 |
Related Questions
Below are more resolution path options that do not have public visibility:
Reason #12 | Enterprise Vehicle didn’t successfully share with the database |
Resolution #12 |
Reason #13 | Vehicles in question have a different database owner |
Resolution #13 | Communicating device not showing up on map because device is communicating to the wrong database |
Reason #14 | Vehicle is not showing on the map due to suspend mode |
Resolution #14 |