We get this a lot, but usually if you’re running into initialization problems for more than 2 hours or so, something has gone wrong.
I’ve written an internal facing guide on how to fix this and I’m working with our documentation team to come up with a more public facing document… but TYPICALLY the stuff that you see when you run into the initialization problem are:
- Connectivity to the database from the remote WebUI box isn’t good (ports, firewalls, proxies, IPSes)
- The database credentials are wrong
- The database credentials were correct, but they’ve changed recently
- The database credentials are correct but don’t have the necessary privileges for the WebUI to do everything
- You’re running MSSQL and you have encryption turned on
** If that’s you, just turn on this client setting on the WebUI box: _WebUIAppEnv_MSSQL_CXN_ENCRYPT = 1
A lot of this you can verify yourself by testing on something like ODBC from the remote WebUI box. We’re working on a database connectivity tester tool built in to the WebUI so that when you run into the initialization problems, you aren’t off wondering what’s up.
Let me know if those suggestions help you out. If there’s something else going on, then we have something really interesting on our hands and i’m happy to help.