has version 8.7.2.5 broken logging system?

Hi Oxa

Until a few days ago I was running the last stable version (8.6.1.4)

On installing the latest version I am now getting a recurrence of the 'Unable to start logging system' error.

This was discussed at length in this thread earlier this year:

https://community.welldonesoft.com/marketfeeder-troubleshooting/'unable-to-start-logging-system'-any-known-fixes/msg70380/#msg70380

The solution you came up with then of putting separate logger port numbers in each instance of mfp worked until I installed the latest version.  Now the error has resurfaced, always when trying to launch the 6th instance of mfp.

I have tried changing all the logger port numbers in the ini files but no success.  I have used a piece of software called tcpview to see if any other programs are using ports arounf 19004, but none seem to be.

Do you think anything in the new code could have broken this again? In summary, I use 9 versions of mfp running simultaneously and with the new version I can only run 5 before each new instance brings up the error message.

Thanks if you've got any suggestions.

Hi armarni
Just a thought, the latest version has a dedicated settings page for the logger. Have you tried entering the port numbers via the settings page rather than the .ini files?

Thanks Mark, that did the trick!

I checked the box to enter the logger port manually and I entered the same port numbers that I have in my ini files for each instance, and now they all launch without a problem.

Appreciate the help

Glad you sorted this out!

We introduced the separate logger settings to support our VPS offering which allows users to view their MarketFeeder Pro logs remotely. The ability to set the logger port manually is critical for remote servers where ports can be occupied with other services & system apps.