solidDB server startup fails with authentication errors
Symptom
The solidDB server startup fails with the following type of errors in solmsg.out and solerr.out:
UNICOM soliddb process has encountered an internal error is unable to continue normally. External authentication requires Crypto to be enabled. ... Server emergency shutdown.
UNICOM soliddb process has encountered an internal error is unable to continue normally. Crypto enabled, but failed to load the Crypto library. Check the library path. ... Server emergency shutdown.
Causes
If there is only one database administrator account and the account is externally authenticated and General.UseCryptoLib is set to no, the solidDB server startup fails with the error External authentication requires OpenSSL to be enabled.
If the database administrator account is authenticated internally but other users are authenticated externally, solidDB server will start even if General.UseCryptoLib is set to no. However, connections for externally-authenticated users fails with error Error 08004: Server rejected the connection.
If General.UseCryptoLib is set to yes and solidDB cannot load the OpenSSL libcrypto library, the solidDB server startup fails with the error crypto enabled, but failed to load the OpenSSL library. Check the library path.
Recovery
1 Check that OpenSSL is installed on the server computer.
2 Check that server-side solid.ini file contains the following parameter settings: