MapInfo Pro can rarely assign X and Y coordinates to all of your records on the first try, especially when geocoding to street level. It is not uncommon to have a geocoding hit rate of under 50% on your first attempt. The information in your database may not exactly match the information in the search table. MapInfo Pro-based maps are updated regularly, but may not include the most recent changes (for example, new subdivisions or postal code boundaries).
And there can be other problems. The abbreviations that you use in your table may not match the abbreviations that MapInfo Pro recognizes. For example, the records in your table may use abbreviations like Circ. for Circle and Pl. for Plaza. MapInfo Pro only recognizes Circle or Cir for Circle and Plaza or Plz for Plaza. When it cannot match an abbreviation, it does not geocode the record.
That is why MapInfo Pro gives you the option of geocoding your database interactively. There are a number of methods for geocoding records that do not have an exact match. The following is a list of potential geocoding pitfalls and how to avoid or rectify them.