We moved to email, but the next version of MangoNoSql, 3.5.1, will improve the handling of corruption in the database that is to be merged. This is what caused the buffer overflow exception at the end of the log, and the returning to IDLE state before finishing all the data points.

Sorry I keep pasting the entire file within the post, if there's a better way to share it please let me know.

Tis better to log the whole log than no log at all!

Hi Phil - thanks for the prompt response.

I have a new finding. I now get a response when accessing the http page via command line from the server ( using the wget -p http://localhost:8080 command), but can't access it from any of our other servers running in the same LAN. So now I no longer think this is an issue with the Mango instance, but rather a network/firewall issue most likely.

I will look further into it and report back with my findings after the weekend. Thanks again for the prompt response!

The data source only supports reading the curValue into a data point. It does check if curStatus is ok, if it is not OK the data point is marked as being "unreliable". You should see the unreliable status as a little red warning icon next to any point value displays in the UI. The unreliable status is not trended however.

It will probably be easier if we can work directly with you on getting this set up on both sides. If you contact me directly I can set up a web meeting and help you get it up and running. Joel.