Gen 8.6 Windows SQL Server CSE configuration completes successfully but loadschema.log shows errors
search cancel

Gen 8.6 Windows SQL Server CSE configuration completes successfully but loadschema.log shows errors

book

Article ID: 135857

calendar_today

Updated On:

Products

Gen

Issue/Introduction

Using default SQL Server instance, the CA Gen 8.6 Windows SQL Server CSE Configuration utility (cse_config.exe) ends successfully with "Configuration Complete" but log file "C:\ProgramData\CA\Gen 8.6\logs\CSE\loadschema.log" shows these errors:

====

Load Schema Server_Name Data_Source_Name Userid Password

load schema90 SASC

SQLState = 37000, NativeError = 4060

Error = [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Cannot open database "Data_Source_Name" requested by the login. The login failed.

SQLState = 28000, NativeError = 18456

Error = [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Login failed for user 'Userid'.

load schema90 SDIV

SQLState = 37000, NativeError = 4060

Error = [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Cannot open database "Data_Source_Name" requested by the login. The login failed.

SQLState = 28000, NativeError = 18456

Error = [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Login failed for user 'Userid'.

...

load schema92 STRG

SQLState = 37000, NativeError = 4060

Error = [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Cannot open database "Data_Source_Name" requested by the login. The login failed.

SQLState = 28000, NativeError = 18456

Error = [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Login failed for user 'Userid.

Load Schema Done

====

Environment

Release : 8.6
Component : CA Gen Client Server Encyclopedia

Cause

The script "C:\Program Files (x86)\CA\Gen86\CSE\cse_msqls\loadschema.cmd" is using the Data Source Name (DSN) as the Database Name when executing the bcp commands to load the schema tables. In this case the Encyclopedia DSN had been defined with a different name to the actual Encyclopedia Database Name which caused the bcp commands to fail.

Resolution

After changing the Encyclopedia DSN to match the Database Name the problem was resolved on the next run of the CSE Configuration utility. 

Additional Information

 

The DSN matching Database Name requirement is documented here under "Create Microsoft SQL Server CSE Database"

CA Gen -8.6 > Encyclopedia > Client Server Encyclopedia > Using the Client Server Encyclopedia > Installing and Configuring CSE > Configure Databases

Create Microsoft SQL Server CSE Database

...

The ODBC Data Source Administrator panel opens. 

10. Select the System DSN tab and click Add. The Create New Data Source panel opens. 

11. Select SQL Server and click Finish. 

12. In the next dialog, type the database name in the Name field, Description, Which SQL Server (local), and click Next. 

...