Haha...good question...but seriously, two different applications, two different dbs, two different installer types, etc. Meaning...and if your 'feeling' my 'two' point...it comes down to two different development teams, in particular when TMSPE was born. However, we have been and are begining to rope the teams together now and this is one particular area of improvement. That's why I've said improvements are being done in future release
Sorry, forgot to mention that in my earlier 'word dump'
But this "Cannot read current settings" is a defect that we've fixed in the next major release of TMS, i.e. due out in April. I don't have defect reference for it just yet, but I can get one.
The problem itself is that when you select "Provisioning Extension Database Connection Settings" in TMS Tools, the issue is that TMS Tools does not look at the proper registry locations for 32 or 64-bit Java install meaning it cannot find where Java was installed.
A possible work around to the issue would be to set a proper JAVA_HOME, i.e. environment variables > system variables on the host machine. For example, could be pointing to something that doesn't exist.
The fix in the code is that we obviously now correctly read both the 32 and 64 bit registry locations when we're trying to find where Java is on the host machine.