"Navigator TCP Connection Fail" message after updating to Navigator 19

[myurkoski]

Sorry to be the only guy that reports bugs!

Just updated to Navigator 19, and I'm constantly getting a "Navigator TCP Connection Fail" message. It was working great previously, so I'm not sure whats changed between the two.

The PC had a network connection. I'm running CF 4.4.9 on Windows 10 (with latest updates 1909). Any idea on how to suppress this?

[johnjore]

Message is by design when it can't connect to Mapfactor Navigator. Probably you only need to enable the TCP connection in Navigator.

It's required for the plugin to work under CF.

---

From: myurkoski notifications@github.com Sent: 25 November 2019 10:22 To: johnjore/Centrafuse-MapFactor-Navigator Cc: Subscribed Subject: [johnjore/Centrafuse-MapFactor-Navigator] "Navigator TCP Connection Fail" message after updating to Navigator 19 (#2)

Sorry to be the only guy that reports bugs!

Just updated to Navigator 19, and I'm constantly getting a "Navigator TCP Connection Fail" message. It was working great previously, so I'm not sure whats changed between the two.

The PC had a network connection. I'm running CF 4.4.9 on Windows 10 (with latest updates 1909). Any idea on how to suppress this?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/johnjore/Centrafuse-MapFactor-Navigator/issues/2?email_source=notifications&email_token=ADC2CIVXOSWOBQ7JS3D2HTLQVMEDFA5CNFSM4JRBRQSKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H3VG4JQ, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADC2CISDDUFKYTECH4QGUFTQVMEDFANCNFSM4JRBRQSA.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/johnjore/Centrafuse-MapFactor-Navigator/issues/2?email_source=notifications\u0026email_token=ADC2CIVXOSWOBQ7JS3D2HTLQVMEDFA5CNFSM4JRBRQSKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H3VG4JQ", "url": "https://github.com/johnjore/Centrafuse-MapFactor-Navigator/issues/2?email_source=notifications\u0026email_token=ADC2CIVXOSWOBQ7JS3D2HTLQVMEDFA5CNFSM4JRBRQSKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H3VG4JQ", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[myurkoski]

Well I looked all over for such a setting, but I couldn't find one, so I launched CF again and mercifully, my PC was slow enough that the initial splash allowed me enough time to select language for interface and voice and accept the warning. Now I no longer receive this warning.

I'm not recalling having to do this before in 18, so was there something i did that was of similar effect, or is this a new behavior in 19?

[johnjore]

This is documented on the first page and is for all Navigator versions. Must complete first run settings before using it under CF.

---

From: myurkoski notifications@github.com Sent: 25 November 2019 12:37 To: johnjore/Centrafuse-MapFactor-Navigator Cc: John Jore; Comment Subject: Re: [johnjore/Centrafuse-MapFactor-Navigator] "Navigator TCP Connection Fail" message after updating to Navigator 19 (#2)

Well I looked all over fir such a setting, but I couldnt find one, so I launched CF again and mercifully, my PC was slow enough that the initial splash allowed me enough time to select language for interface and voice and accept the warning. Now I no longer receive this warning.

I'm not recalling having to do this before in 18, so was there something i did that was of similar effect, or is this a new behavior in 19?

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/johnjore/Centrafuse-MapFactor-Navigator/issues/2?email_source=notifications&email_token=ADC2CIQOYRKZXUCW7U7SVCLQVMT43A5CNFSM4JRBRQSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFA3MOQ#issuecomment-557954618, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADC2CISBMRBRYUEGM6IR3DLQVMT43ANCNFSM4JRBRQSA.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/johnjore/Centrafuse-MapFactor-Navigator/issues/2?email_source=notifications\u0026email_token=ADC2CIQOYRKZXUCW7U7SVCLQVMT43A5CNFSM4JRBRQSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFA3MOQ#issuecomment-557954618", "url": "https://github.com/johnjore/Centrafuse-MapFactor-Navigator/issues/2?email_source=notifications\u0026email_token=ADC2CIQOYRKZXUCW7U7SVCLQVMT43A5CNFSM4JRBRQSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFA3MOQ#issuecomment-557954618", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[myurkoski]

Ahhh, thank you. I had omitted this because I merely upgraded from 18 to 19, but it appears they are entirely different, with new install locations and everything. Whats funny is that it immediately asked me to find the new exe which I pointed it at, but that didn't prompt me to do the re-setup. I loaded up Nav 19 outside of CF and got it all squared away, but apparently when CF runs it it carries its own settings/options so it ignored that setup. CF must be launching it as a different user or something making it treat the CF version separately from a user directly launching Nav19 from their desktop.

Closing ticket.