Jump to content
The simFlight Network Forums

Recommended Posts

*** Moved from User Contributions ***

Hi,

after I got the following error message

         "FS Eliminator for FSUIPC client application

FS Eliminator for FSUIPC client application no longer works"

WideFS does not connect the client PC to the FSUIPC server PC. After WideFS has started via the auto start menu folder I have to close this application and start WideFS again.

Then erverything works fine. The error occurs ervery time I have shut down the PC Network and start it again after a couple of time.

Thanks for your support in advance

Peter

 

 

 

Share this post


Link to post
Share on other sites

Hi Peter,

6 hours ago, FS4U said:

WideFS does not connect the client PC to the FSUIPC server PC.

Presume you mean WideClient, which is part of WideFS.  It may be that the network (or other services) may not be available yet when auto starting. Do you have anything in your event log?

Could you also try adding
    Log=Debugall
to the [user] section of your WideClient.ini (or add the [user] section if not already there). Then post the log when you get the crash. The log file may be quite large but zips up nicely.

John

 

Share this post


Link to post
Share on other sites

Thanks for your quick response, I will check the event log

Kind regards

Peter

 

Share this post


Link to post
Share on other sites

Hello John,

I can`t see the WideClient.log files in the WideFS Folder as well there are no log files in the Prepar3D Modules folder. Attachetd youn will find the WideCleint.ini.

The error occurs the first time after I restarted the network PCs few times. Since 4 Years I had never  had a problems with the WideClient.

Kind regards

 

Peter

 

 

WideClient.ini

Share this post


Link to post
Share on other sites

Hi Peter,

the log files are probably hidden by windows. Got to Control Panel -> Appearance and Personalization -> Folder Options and make sure that you have 'Show hidden files and folders' selected.

John

P.S. And don't forget to check the event log!

Share this post


Link to post
Share on other sites

Sorry, I'm referring to the Windows event log. Start the Event Viewer (you can find it from the search box in the Start menu) and look under Windows Logs -> Application. There should be an Error event there at the time of the WideClient crash, and possibly some other events at the same time. Copy any events at the time of the crash and post them.

Oh, and for the WideClient log, ignore my previous advice (wrong option, sorry!), you want to enable Hide extensions for known file types in your folder options.

John

Share this post


Link to post
Share on other sites

Hello John,

hope I did it right and you can see something that would help to fix the bug. Further more the are no log files in the WideFS folder.

Kind regards

Peter

 

Share this post


Link to post
Share on other sites

... may be the resolution is too bad to see details. If possible I would send you files with a better resolution via e-mail.

Bild7.jpg

Share this post


Link to post
Share on other sites

There only 3 window error messages related to a failed update attempt.

Kind regards

Peter

 

Share this post


Link to post
Share on other sites

Start a command prompt, change directory to your WideClient folder, then list the contents of that directory.

There must be a log file there, as well as an ini.

Share this post


Link to post
Share on other sites

Sorry John,

it seems that I am a little bit in the "windows off". Command prompt is clear: windows+r,  but how can I change the directory to my WideClient?

Kind regards

Peter

 

 

 

 

Share this post


Link to post
Share on other sites

Click your start menu, in the search box, type 'command' - the top option will be 'Command Prompt' (or something similar, depends on Windows version and what you have installed). Select the 'Command Prompt' option. A window should open. In that window, type 'cd <your install directory>', whatever your install directory  fore WideClient is, use that (is it 'C:\Users\Peter\Downloads\WideFS'? Are you running from your download directory?).

When you are in the directory, type 'dir' to get the folder contents.

Anyway, its really a lot easier using Windows Explorer. Did you try changing your folder options to see hidden file types?

Google is your friend in these matters!

John

Share this post


Link to post
Share on other sites

Sorry John that I waste your time with this windows problems, folder options "see hidden file types" is enabled. Shame on me, I did a stupid mistake (no space bar after "cd") sorry for that. I will send you the WideClient log file as soon as possible.

Kind regards

Peter

 

Share this post


Link to post
Share on other sites

Log files 1 and 3 are as expected. Log file 2 shows it did connect but took quite a while. Could it have been waiting for P3D to start, or was it already fully up and running when you started WideClient? Did you get the '...no longer works' message?

 

Share this post


Link to post
Share on other sites

Hi John,

WideClient was up and waiting for P3D to start and I didn´t get the ...no longer works' message.

Kind regards

Peter

 

Share this post


Link to post
Share on other sites

Hi Peter,

12 hours ago, FS4U said:

WideClient was up and waiting for P3D to start and I didn´t get the ...no longer works' message.

...and the log indicates that it connected when P3D started. Was this not the case?

I need to see the log generated when you get the message that message that WideClient has stopped working, or when it fails to connect to P3D when you start it. 

The log files you have posted so far don't show any issues!

Regards,

John

Share this post


Link to post
Share on other sites

Okay John, but I get no message that WideClient has stopped working. The only different that I can see in the log files is that SIOC is only runing when I restart the WideClient. So I thing we should close this topic and wasting your time. I will delete WideClient.exe from the auto start folder and in the future I will start it manuel when Prepar3D is running. So everything will work fine.

Thanks for your efforts and kind regards

Peter

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.