When WideServer starts on Prepar3D, ErrorMsg: Unable to serve (see logs)

[rolakon]

Hi Pete,

 

I use FSUIPC 4.928 on my fs-pc. Installed is FSX and on a different hdd a version of P3D 1.4.

On a second pc I run the wideclient to use different help programs (i. e. moving map, weather, etc).

Both pc's run on win7 with fixed ip-adresses in the same network. With FSX there is no problem.

But when I start P3D and the WideServer runs up, it tells me: "Unable to serve (see logs)" in the

top of the fs-window for a very short period of time (< 1 sec.).

Then it shows ".......waiting for clients". But a connect is not possible.

My logfiles are attached.

Can you see where my error is? I can't find out.

 

Thanks for your help in advance.

 

Best wishes Roland

Logs.rar

[Pete Dowson]

I use FSUIPC 4.928 on my fs-pc. Installed is FSX and on a different hdd a version of P3D 1.4.

On a second pc I run the wideclient to use different help programs (i. e. moving map, weather, etc).

Both pc's run on win7 with fixed ip-adresses in the same network. With FSX there is no problem.

But when I start P3D and the WideServer runs up, it tells me: "Unable to serve (see logs)" in the

top of the fs-window for a very short period of time (< 1 sec.).

 

None of the logs are finished. You need to close things down before copying the logs, otherwise essential information is lost.

 

One strange thinge which doesn't make total sense is that when the message "Unable to serve (see logs)" is displayed, either it is preceded by a message box entitled "WideServer Error" which you have to "OK" to get out of, or, simultaneously, the explanatory message is written to the log -- yet in your case the server log shows nothing.  However, maybe the error was so transient that this got overridden by subsequent events.

 

Three questions rise:

 

1. Is the FSUIPC4.KEY file in the P3D Modules folder identical to that in the FSX Modules folder?

2. Are you possibly using anything else on P3D which might be taking the main port used by WideFS -- 8002?

3. Could your firewall be allowing FSX.EXE through but not Prepar3D.exe? That would explain it for sure.

 

Regards

Pete

[rolakon]

Thank you for this quick reply.

I've checked the firewall for sure.

But I was to blind to see, that access to the public network only was granted.

After granting rights to the local network, everything works fine.

Thanks again....

 

Regards

Roland