Need help with FSUIPC error

[macwino]

I am having a problem running Google Earth with MyFsGoogleEarth over my registered copy of WideFS. I am using the very latest versions of FSUIPC and WideFS. I am posting here because I am getting the following error message from MyFsGoogleEarth when I try and track a plane in Google Earth:

[initFs2] Error opening FSUIPC connection: 14

This error message is accompanied by a Google Earth error message that "Fetch of the NetworkLink failed." Do you have any idea what the FSUIPC error means and how I might eliminate the error?

I use WideFS for a moving map program with a null modem cable connection and it works just fine. But this Google Earth connection is an ethernet connection and doesn't seem to be working. What's most frustrating is that I had this working a few weeks ago. Then, I did a defrag of my hard drive on the main FS9 machine, and this appears to have changed the IP address for my FS9 machine - or that's my best guess as to what caused the change. I made the necessary corrections in Google Earth's settings for the new IP address, but I now get this error referring to FSUIPC. My WideFS ini file makes no reference to IP addresses since I understand this to no longer be necessary. So I'm at a loss as to what the problem might be.

Thanks, Robert

[Pete Dowson]

[initFs2] Error opening FSUIPC connection: 14

This error message is accompanied by a Google Earth error message that "Fetch of the NetworkLink failed." Do you have any idea what the FSUIPC error means and how I might eliminate the error?

It isn't an error message from either WideFS or FSUIPC, but the number 14 probably comes from the interface in the program you are using. If they are using the code I provide in the FSUIPC software kit, then "14" means "Maybe running on WideClient, but FS not running on Server, or wrong FSUIPC".

I use WideFS for a moving map program with a null modem cable connection and it works just fine.

WideFS doesn't use COM ports and a null modem cable, unless that's how you Networked your PCs (very unlikely, far too slow). You must mean GPSout, not WideFS?

... appears to have changed the IP address for my FS9 machine - or that's my best guess as to what caused the change. I made the necessary corrections in Google Earth's settings for the new IP address

Why would Google Earth want your FS IP address? If you are using WideFS it is WideFS which talks to FS, not Google Earth's interface. You sound very confused.

So I'm at a loss as to what the problem might be.

Does the WideClient title bar say it is Connected? If not you have a Network problem -- look at the WideClient and WideServer log files.

If it does, then the most likely thing wrong is an illegal or otherwise bad FSUIPC or WideFS user registration key. Have you got more than one email address, as I cannot find the one you use here amongst the valid registrations? ZIP up your FSUIPC.KEY file and send it to me at petedowson@btconnect.com and I'll check it.

Regards,

Pete

[macwino]

Hi Peter,

I wish I'd posted 3 hours earlier. Your analysis pointed me in the direction to fix the problem. Thanks so much.

First, you're right - I was very confused - but you straightened me out. Yes, I'm using GPSOut for the moving map, not WideFS; however, I've been launching WideFS for years whenever I used the moving map because I thought I had to. Dumb!

Second, I found that WideClient wasn't receiving any info from the FS9 machine; it was indeed disconnected. But I suppose it was connecting a few weeks ago when I had this working. So something messed up the connection. In any event, I read the manual and added the line you suggested to the WideClient.ini referencing the IP address of the FS9 machine. Once I did that, all was working fine.

Finally, I have valid registrations for both FSUIPC and WideFS. The email address used by my simFlight Network forum registration is a real old one and is not the one I used when I registered the programs. I'll email you the registration info shortly just to confirm this, and I'll try and change my email address with the forums so all is up to date.

Thanks again for all the help, and especially for explaining to me just what was going on here.

Robert

[Pete Dowson]

I wish I'd posted 3 hours earlier. Your analysis pointed me in the direction to fix the problem. Thanks so much.

Ah. Good.

In any event, I read the manual and added the line you suggested to the WideClient.ini referencing the IP address of the FS9 machine. Once I did that, all was working fine.

Well, in general it is usually better to provide the ServerName rather than the IPaddress, as you are less likely to change that.

What version of WideFS are you using? Are both Server and Client running WinXP? With the current version of WideFS and XP all round you should never need to specify server name, IP address, ort anything.

Finally, I have valid registrations for both FSUIPC and WideFS. The email address used by my simFlight Network forum registration is a real old one and is not the one I used when I registered the programs. I'll email you the registration info shortly just to confirm this

No, there's no need, thank you all the same.

Regards,

Pete

[macwino]

Quote:

Well, in general it is usually better to provide the ServerName rather than the IPaddress, as you are less likely to change that.

What version of WideFS are you using? Are both Server and Client running WinXP? With the current version of WideFS and XP all round you should never need to specify server name, IP address, ort anything.

----------------

I'm running v6.5.1 of WideFS. Your advice about using the server name instead of the IP address is well taken. I just didn't know my server name right off the bat and I did know the IP address. I've since changed the entry to the Server Name. I know this should have worked automatically as I'm running XP on both machines, but for some reason it apparently connected automatically at first, but sometime during the past 2 weeks it stopped connecting and needed the Server Name entry to reconnect.