Upgrade to 6014 - observations
I upgraded our production server from build 6010 to 6014 (using MySQL) a couple mights ago, and it appears to have completed successfully with no major hiccups, other than a couple techs experiencing some errors that disappeared after clearing their browser cache. Just wanted to offer a note of appreciation and to show others here that not all upgrades end in catastrophe.
The one curious thing I did run into though, was that after shutting down SDP and starting the upgrade process, the SDP service kept insisting on starting itself up, and attempted to do so about once a minute during the upgrade cycle. Of course it failed every time because the database was already running as part of the upgrade, but it was very annoying, and I kept having to kill the java.exe process it started because I was afraid it would interfere with the upgrade.
I'm thinking it was Windows itself that kept trying to restart the service. Perhaps if I had shut it down via the Windows services, it wouldn't have attempted to restart, but that always seems to cause an improper shutdown of SDP. You might want to try to make it so that shutting down the service without the SDP shutdown script doesn't cause it to crash and generate Windows event errors.
New to ADSelfService Plus?