Hi Louis,
I think it's a BUG. Big Bug. Here is my test result.
Environment:
CA SM 17.1
SDM and DB are different server.
If DB TCP listening port is the default port 1433, then it is ok to just enable TCP/IP and disable named pipe. SDM works normally.
If DB TCP listening port is not default port (e.g 1561 per customer policy), then I have to enable both TCP/IP and named pipe, to make SDM work.
From my obversation, SDM is using below command to connect to the database.
sqlcmd -S demodb -U *** -P ***
I think SDM incorrectly ignored the DB port config (neither the port I inputted in pdm_configure screen or in the @NX_DB_PORT of nx.env).
To repeat this issue:
Test#1
1. In DB server, in Sql Server Configuration Manager, modify the protocols of mssqlserver.
TCP/IP: Enabled. IPALL TCP Port = 1433
Named PIPE: Disabled
restart sql server service.
2. In SDM server, modify nx.env
@NX_DB_PORT=1433
restart sdm service.
3. Login SDM successful.
Test#2
1. In DB server, in Sql Server Configuration Manager, modify the protocols of mssqlserver.
TCP/IP: Enabled. IPALL TCP Port = 1561
Named PIPE: Enabled
restart sql server service.
2. In SDM server, modify nx.env
@NX_DB_PORT=1561
restart sdm service.
3. Login SDM successful.
Test#3
1. In DB server, in Sql Server Configuration Manager, modify the protocols of mssqlserver.
TCP/IP: Enabled. IPALL TCP Port = 1561
Named PIPE: Disabled
restart sql server service.
2. In SDM server, modify nx.env
@NX_DB_PORT=1561
restart sdm service.
3. Cannot start SDM. Cannot access SDM login page. sql connection error found in stdlog.
Please help to contact technical team to confirm this bug and provide fix.
Thanks.
Regards,
Chison Cai
chison.cai@igsl-group.com