CA Gen CSE configuration for SQL Server fails to load schema tables although "Configuration Completed" is reported
search cancel

CA Gen CSE configuration for SQL Server fails to load schema tables although "Configuration Completed" is reported

book

Article ID: 193708

calendar_today

Updated On:

Products

Gen

Issue/Introduction

Running CA Gen 8.6 CSE Configuration (cse_config.exe) for SQL Server reports "Configuration Completed" but file "C:\ProgramData\CA\Gen 8.6\logs\CSE\loadschema.log" shows messages:
===
Load Schema HOST_NAME DSN_NAME USER_ID PASSWORD
load schema90 SASC 
SQLState = 28000, NativeError = 18456
Error = [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Login failed for user 'USER_ID'.
...
===

File "C:\ProgramData\CA\Gen 8.6\logs\CSE\err_file.lst" also shows:
===
SQLState = 28000, NativeError = 18456
Error = [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Login failed for user 'USER_ID'.
===

Environment

Release : 8.6
Component : CA Gen Client Server Encyclopedia

Cause

The DB user's PASSWORD contains a caret character "^" and is not visible in the loadschema.log PASSWORD field.
The load schema tables are loaded using command file "C:\Program Files (x86)\CA\Gen86\CSE\cse_msqls\loadschema.cmd", which itself calls the SQL Server bcp.exe program.
Under Windows command line, a "^" is used as an escape character for the character immediately following it when that following character is special and needs to be interpreted literally. So the "^" in the password is itself is not interpreted literally and is effectively ignored in the bcp.exe password field.
NOTE: The "^" character does not cause any problems in the earlier CSE Configuration steps for DB connection and initialisation because they do not use .cmd files.

Resolution

After changing the password to not include the caret character "^", on re-run of the cse_config.exe program the load schema step runs successfully.