SEQ_OS issues should happen with a MS SQL db for 1.5.0, and was fixed in 1.5.1 and newer.
Appliance for 5.1.2 shouldn't have this problem, since it's on the newer code base.
Just make sure to note, the appliance is not for production purposes and has some limitations.