Having not looked too deeply into this, it appears the line that’s failing is complaining about an old protocol version. Is there any chance that you are or have run some processes with an old version (say, before 5.0) that may have some state lying around?
Also, is the version you are currently trying to run v6.0.18? That’s the version I used to get the backtrace, but if that’s not right it could change things.
Thanks for looking into it. I was running fdb 3.0 version earlier. As i couldn’t find a way to upgrade to 6.0 i have uninstalled 3.0 server,client packages and did a fresh install of 6.0 packages.
Glad you were able to get things working. Upgrades from 3.0 were supported in 5.0, and maybe sometime as late as 5.2, but they are not supported anymore in 6.0.
If you really needed to upgrade from an old version, it should be possible to do so by first upgrading to 5.0 and then from 5.0 to 6.0. Awkwardly, it doesn’t seem that there are download links for older versions on the website, so if you had such a need you’d probably need to build it yourself or maybe work with us to get a copy of the binaries.
Sorry i couldn’t make it work, i still get same error. In my earlier comment I meant: as i couldn’t find the upgrade path from 3.0 to 6.0, i have uninstalled 3.0 and installed 6.0 packages. Any way’s this issue can be closed as i have rebuilt entire setup with fdb 6.0 fresh install.
Deleting your 3.0 install and reinstalling 6.0 is certainly valid if you don’t care about your data. My comment was more to explain why the upgrade from 3.0 to 6.0 didn’t just work and how one might be able to do it if they didn’t want to lose existing data.
If you’re saying that you tried upgrading from 3.0 to 5.0 (rather than 6.0) unsuccessfully, that would be unexpected. It’s probably not an upgrade many people will be trying, but if you were running into trouble here and have details to share about how it failed, it may be helpful if something like this happens in the future.
If you only had problems upgrading directly from 3.0 to 6.0, then that is expected as described above.