Thanks for your prompt reply. The patch script you linked certainly fixed Issue#4 for us. I think we should be fine to push forward with 4.7.3 as it looks like all the issues have now been resolved. Thanks for linking through that knowledge base article. I'll be sure to have a look through the knowledge base articles before any future upgrades.

As per email response: Try upgrading to 3.6.5 first, then to 4.6.4.

We don't have a formal EoL policy, but as long as you're current on support (which, just checked, you guys are), we'll do our best to provide support for whatever version you are on. Of course, please understand that, a lot of times, the answer may just be "upgrade to a new version", and we most likely will be unable to provide a hotfix. I suggest you upgrade to v4.6 (we can provide assistance in this as well), and then schedule a routine upgrade/maintenance window (monthly, bi-monthly, etc) so that you can try to keep current. We put a lot of effort into making sure everything is backwards-compatible, and in the event something breaks, you can rollback... or we have the capability to ship a new release within hours.

Looks like this has been fixed in 3.2.0. Thanks guys!

Thanks for the report - this should be fixed on the server end now, and you should be able to see the release notes on your end.

I'm not using Windows authentication, so user rights aren't the issue. The very first thing I did was to simplify the password, and that didn't work either. I know that the connection string works, because both the web application and the service function fine. I ended up doing a manual install of 2.2.10 to get me up and running (I needed the fix for NuGet 2.8).

I've installed 3.0.6 successfully now (I think).

If you run the command: sc config inedobmwebsrv depend= / for the web server or: sc config inedobmsvc depend= / on the server with admin privileges, the dependency should be removed.