Home » Garmin talk

Mapsource problem

 
Mon, 02/22/2010 - 11:21pm

Started having a problem with Mapsource when retrieving data from my 265WT. It basically blows up with an error message and an option to copy it to the clipboard for inclusion in email to tech support (I'll paste it at the end of this post).

Tech support responded and indicated that I should empty my temp folder and update to latest version (done and done). Unfortunately the error persists. Mapsource had worked properly at one time. The only thing "different" is a map update has been released in the interim which I have chosen not to obtain yet.

It appears to be having trouble reading one of it's own tmp files.

Anyone seen this? Thanks in advance.

Ed

Here is the error:

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>

XML_DOMERRORHANDLER.CPP
62

Fatal Error:
File Path: d:\temp\MapSource\tmp233.tmp, line: 1, char: 56

Message: An exception occurred! Type:UTFDataFormatException, Message:irregular bytes í, ¶ of 3-byte sequence.

MapSource

6
15
11
0

Release
Jan 26 2010, 11:31:06
sqa

1033
006-A0041-00

Windows XP Service Pack 3
x86, Processor Level: 6, Processors:2, Model: 14 Stepping: 12
2087276

2010-02-22T22:20:56Z

‹ OK, I'm hooked Poiloader.exe and sox.exe ›
Mon, 02/22/2010 - 11:40pm

.

Update to the latest Sun Java may be a fix.

http://java.sun.com/j2se/1.4.2/docs/api/java/io/UTFDataForma...

--
nüvi 3790T | Those who make peaceful revolution impossible, will make violent revolution inevitable ~ JFK
Mon, 02/22/2010 - 11:49pm

Thanks for the suggestion.

Thanks for the suggestion. Java reports I am up to date.

Tue, 02/23/2010 - 10:23am

I had a similar experience...

when transferring tracks and waypoints from my nuvi255W - My error report was very similar to yours- except my error report said: "Message: Invalid character" instead of "Message:irregular bytes"

Garmin tech told me that a corrupt comment field in current.gpx was causing the error. One fix could be to delete the current.gpx (which I did not want to do) but that there was also a work around. They actually suggested converting it from gpx to gpx using gpsvisualizer.com (this did not work - gpsvisualizer.com did not recognize my current.gpx as a valid file - probably due to the corrupt comment field).

Anyway, realizing that I had only added a few favorites since the last mapsource transfer, I figured a new favorite could be the culprit. I opened the gpx with wordpad and searched for text to locate my newer waypoints - the corrupt data was easy to spot - it looked like Chinese characters where the State field should be. I changed the bad characters and saved the file. Mapsource was then able to read the file and transfer my tracks and waypoints.

The offending favorite turned out to be a pre-loaded POI that I had "saved" as a favorite (My family was meeting a Texas Roadhouse - I thought saving it would be a shortcut for accessing it later).

Not sure if any of this rambling helps your situation. But maybe if you look at the gpx, you maybe able to identify the bad bytes. Do you have a copy of an old current.gpx that perhaps you can compare to your current one?

--
Jan ~ Nuvi 255W
Thu, 02/25/2010 - 11:36pm

Bingo! A recently added

Bingo! A recently added Favorite had "|?|?" as the only characters in the address. Deleted that and good to go. I bet the | (pipe) was screwing up the works!

Thanks,
Ed

Fri, 02/26/2010 - 10:12am

Great!

edkrimmer wrote:

Bingo! A recently added Favorite had "|?|?" as the only characters in the address. Deleted that and good to go. I bet the | (pipe) was screwing up the works!

Thanks,
Ed

Glad to hear you found the problem. Just curious, how did you originally add that corrupt favorite? Did you Save a location or preloaded POI?

--
Jan ~ Nuvi 255W