-
タイトル
Using a Windows AD functional account fails on "MS SQL Server" platform -
説明
Connection to a Micorosft SQL 20xx server fails to connect when using a Active Directory functional account "Use Domain Account"
"Test System" shows the following error:
[DD/MM/YYYY HH:MM:SS] Gathering the information necessary to perform a check of SQLSERVER...
[DD/MM/YYYY HH:MM:SS] Checking the MS SQL Server Database SQLSERVER(SQL2008R2.yourdomain.com)...
[DD/MM/YYYY HH:MM:SS] Connecting with Windows functional account yourdomain.com\tpamsql
[DD/MM/YYYY HH:MM:SS] Unable to connect to SQLSERVER to perform the check. Verify the network address, port, and Functional Account settings for the system.
[DD/MM/YYYY HH:MM:SS] Error: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to
allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
[DD/MM/YYYY HH:MM:SS] Processed the system check on SQLSERVER in 17.6679688 seconds -
原因
On 2.5.919 and below when using a Domain Account for the functional account TPAM uses Named Pipes to connect to MS SQL. -
対策
WORKAROUND
Enable Name Pipes on the SQL server.
- From the SQL Server Configuration Manager | SQL SQL Network Configuration | Enable Named Pipes. If the setting is changed a reboot or restart of SQL is required.
STATUSIssue fixed in 2.5.920. This allow sfor TCP connections for MS SQL Server when using Windows functional account.