When creating a new CI, the error message "AHD05519: Error in MDB Registration. (Cora not initialized yet!)" appears and it fails to be created and the following error messages are written in a stdlog.
> From the stdlog.x,
11/15 11:17:13.51 <SDM_SV> mdb_registration_nxd 6544 ERROR mdb_registration.c 935 Unable to initial CORA API. RC: 470200
11/15 11:17:13.54 <SDM_SV> mdb_registration_nxd 6544 ERROR mdb_registration.c 937 CORA Error Message:Cora not initialized yet!
11/15 11:17:13.55 <SDM_SV> mdb_registration_nxd 6544 ERROR mdbreg.c 160 ca_reg_init failed (Cora not initialized yet!)
11/15 11:17:13.57 <SDM_SV> spelsrvr 9744 ERROR cmdb_api.spl 622 api::checkCIExists3100 AHD05519:Error in MDB Registration: (Cora not initialized yet!)
SDM 17.x
"\\default" is specified as an instance name of SQL server in NX.env, e.g. "<SQL Server>\\DEFAULT,14000".
When you use a default instance, i.e. "MSSQLSERVER" is displayed as an instance name of SQL server service in Windows Service list and "\\default" is specified as an instance name, CORA fails to connect to a database because in CORA, we use SQLNCLI 11 which does not support providing \\DEFAULT instance name in the connection string. It does accept instance names, but NOT the default instance name. If we use "default" instance, we must not provide instance name to connect a database. The instance name must be provided only if the instance is NOT the default one. Please refer to the following web page for more information regarding the DB connection.
Connection string for default instance like for named instance
If you use a default instance, please do not specify the instance name "\\default" because SQLNCLI 11 used by CORA fails to connect the database. It is a limitation of the SQL API not a limitation of CORA.
If the database is on the SQL named instance, you may need to specify "\\<instance name>", and CORA also would work.