Would a packet collision cause this on the plant wide intranet/internet

The nature of how TCP works means that it is not really possible for packet loss, packet collision (is this the 90s?) or other network 'interference' to cause you to read a one as a zero.

I think it is far more likely that your script (or maybe some sneaky code in your PLC) is setting the bit to zero.

I am having to go and "set" my 1's (reset) as they occasionally just zero off for no apparent reason

So Mango can write to these points too? Is that necessary for your plant to function? Is it possible to make the point read-only and see if the issue still occurs?

It means there is an error in the start up process. Could be a port conflict, cant' find your JAVA_HOME environmental variable or a database connection issue.

If you open the terminal from the start menu: search for CMD on the start menu > right click and run as administrator.

Then CD <your mango install folder> now you can type ma-start.bat and if it errors it won't close so you can see the error in the terminal. You can copy and past if here if you can't figure out what is causing it. You can also look in your /logs/ma.log file and it should contain the error from the last start up attempt.

Joe.