- Check if the dbserver.exe is running. Go to Task Manager > Details.
-
Check whether the SQL server can be connected. Here's an example for ofcserver.ini:
[DBServer] SQLType=0 PoolMinimum=10 PoolMaximum=15 ConnectionString=Provider=SQLNCLI11; Server=CL-HQ-OFFSRV Database=CL-HQ-OFFSRV-ApexOne ConnectionParameterString= User=!CRYPT!1053B87F2B9E589F0D83C5A4E0F PWD=!CRYPT!20F5FC063AB7D52B8B328819460DBE526461F566708 SQLAuthMode=5020 LogAccessorInstance=2 ConnectionTimeout=60 CommandTimeout=60 SQLServerVerInfo=13.0.5101.9;SP2;Standard Edition (64-bit) [INI_DBE_ENGINE_SECTION] DBE_ENGINE=1002 SQLDBThreadingMode=1 SQLDBThreadCount=20 SQLCmd_path= ExpressEdition=0
DBE_ENGINE=1001 means CodeBase (only support OSCE XG) DBE_ENGINE=1002 means SQL Server SQLAuthMode=5020 means SQL server account SQLAuthMode=5030 means windows account
Next Steps
- If the server uses the codebase (OSCE XG only), copy the file and restore it to your testing environment to verify it.
- If the server uses the SQL server, refer to the KB article: Creating a data link (UDL) file and testing the connectivity to a Microsoft SQL server to verify the SQL connection.
- If the dbserver.exe service crashed, export the customer DB and use the following KB to collect application dump: Collecting Log Dumps when System and Applications encounter hang and crash issues.