Troubleshooting
Fix InTouch 2023 Test Connection failure to Historian
Short answer
Test Connection from InTouch 2023 to a remote Historian fails for two reasons: the Historian node's firewall blocks the SQL Server listener even though ping works, and the Distributed Name Manager history provider does not support Windows credentials. Prove TCP reachability, then use a SQL Server login stored in Credentials Manager.
On this page
- Separate the provider test from the trend
- Read the failure mode before changing anything
- Prove the TCP path before touching credentials
- Why Windows credentials fail in the 2023 provider
- Enable SQL Server authentication on the Historian node
- Pick the login: sa proves, a dedicated login serves
- Worked example, illustrative values
- The order to work it
- Questions asked
Test Connection in InTouch 2023 fails against a remote Historian for two reasons, and one deployment can carry both: the Windows firewall on the Historian node is still active and blocks the SQL Server listener while ping keeps working, and the Distributed Name Manager (DNM) history provider in the 2023 release does not support Windows user credentials — AVEVA's support position is that only a SQL Server login works there. Prove the TCP path first with Test-NetConnection against the SQL Server port, then enable SQL Server authentication on the Historian node, restart the service, and point the provider at a low-privilege SQL login stored in Credentials Manager. Test Connection then succeeds.
Separate the provider test from the trend #
If Test Connection fails while you add the Distributed History Provider in the Distributed Name Manager, the fault is in the provider connection — network path or credentials — and the checks below apply. If the provider saves and Test Connection succeeds but a trend stays empty, the fault has moved to the tag names or the trend component. Confirm the tag exists in the Historian and that acquisition is active; PLC tag collection troubleshooting covers the collection side. Historian trend client connection failures covers the display side before you touch the provider again.
InTouch logging and Historical Logging do not need to be enabled for this scenario. Those features make InTouch a source of historical data; retrieval from an existing Historian is configured on the consuming component, such as a trend. When Historian collects through its own data acquisition — a remote IDAS to a DAS, for example — WindowViewer does not have to be running for collection to continue. Window Maker will let you enable InTouch History (.lgh files through the DNM) and logging to Historian together; treat them as mutually exclusive, and with logging to Historian, manage alarm logging separately.
Read the failure mode before changing anything #
| What you see | Layer at fault | Next check |
|---|---|---|
| Test Connection hangs, then times out | Network path or SQL Server listener | Firewall and port test on the Historian node |
| Credentials rejected immediately — domain admin or hostname\administrator alike | Authentication type | SQL Server login |
| SQL login accepted, provider saves, trend shows nothing | Tag or trend configuration | Tag path and trend component |
Ping proves ICMP and nothing else. It says nothing about the SQL Server listener, so a timeout with a working ping is the signature of a host firewall that is still active.
Prove the TCP path before touching credentials #
On the Historian node, run Get-NetFirewallProfile | Select Name, Enabled and read all three profiles: Domain, Private and Public. A rebuilt machine, or one new to the domain, can land in a profile nobody expected, and a line on a setup checklist is not evidence of the firewall's state.
From the InTouch node, run Test-NetConnection -ComputerName HIST1 -Port 1433, where HIST1 stands for the Historian node. TCP 1433 is the default-instance SQL Server port; a named instance listens on its own port, so test the configured one, not the default.
Decide on the result. TcpTestSucceeded : False while ping succeeds means the listener is blocked or SQL Server is not listening on TCP: open the required port in the active profile — or correct the profile — and repeat. If TCP connects and Test Connection still fails, the network is cleared and the cause is authentication.
Why Windows credentials fail in the 2023 provider #
In the 2023 release the DNM history provider rejects Windows credentials outright. Domain admin, hostname\administrator, every user-name pattern tried: all refused, on machines that accept the same accounts elsewhere. AVEVA support's position, returned on a ticket raised for exactly this fault, is that Windows user credentials are not supported in the Distributed Name Manager for the Historian connection, and that integrated security there would need an enhancement request. The credential type is what is unsupported, not the way the name is typed.
The newer Credentials Manager does not change this. From Application Manager, Tools, it will store a credential of the domain user name and password type — and the provider rejects that stored credential exactly the same way. The same steps worked on a 2014 application, and the dialog looks nearly identical, which is why this reads as a regression. The supported path in 2023 is a SQL Server login.
Enable SQL Server authentication on the Historian node #
SQL Server ships with Windows-only authentication, so the SQL login path needs one change on the Historian node. Install SSMS if it is not there; configuring SQL Server without it is impractical.
- In SSMS, open the server properties, go to Security, and set SQL Server and Windows Authentication mode.
- Restart the SQL Server service — Microsoft's documented requirement is that the mode change takes effect only after the restart, and a running SQL Server Agent must be restarted as well.
- Create or enable the SQL login and set its password.
- Re-run Test Connection from the DNM with that login.
Mixed mode widens the instance's attack surface, so record the change in the security baseline and keep the login's rights as small as the connection allows.
Pick the login: sa proves, a dedicated login serves #
| Login | Scope | Use |
|---|---|---|
| sa | The whole instance, every database | Proves the path on a bench; do not leave in service |
| aaUser | Existing account without full SQL Server access | Verify its rights on the Runtime database first |
| Dedicated SQL login | Runtime database access only | Preferred for continuous service |
Store the login you keep in Credentials Manager rather than typing it into the provider each time: Application Manager, Tools, Credentials Manager, credential type User name and password — not domain user name and password — then select the stored credential in the DNM provider setup. The stored value is not kept in clear text; the encryption strength is not documented, so treat it as better than plain text, not as a security control.
Worked example, illustrative values #
HMI1 is the InTouch node and HIST1 the Historian node; the hostnames are illustrative, the cmdlets are the actual ones, and the results show how this fault reads.
- Ping HMI1 to HIST1: 4 sent, 4 received, so 4 − 4 = 0 lost — 0% loss. ICMP is fine.
Test-NetConnection -ComputerName HIST1 -Port 1433from HMI1:PingSucceeded : True,TcpTestSucceeded : False. TCP blocked while ICMP passes points at the host firewall or a listener that is not listening.Get-NetFirewallProfile | Select Name, Enabledon HIST1: Domain False, Private False, Public True. The adapter landed in the Public profile when the machine was rebuilt, and one enabled profile of three blocks the port.- Open the SQL Server port in that profile and repeat the test:
TcpTestSucceeded : True. Network layer cleared. - Test Connection with domain\administrator: rejected immediately. TCP works, so credentials are the remaining cause.
- Mixed mode enabled, SQL Server service restarted, sa enabled: Test Connection succeeds, proving the path end to end.
- Replace sa with a dedicated SQL login holding Runtime database access only, stored in Credentials Manager: Test Connection still succeeds.
Decide every case the same way: a timeout with working ping is the firewall or the listener; an immediate rejection of a Windows account is the provider's credential type; a saved provider with an empty trend is tag or trend configuration.
The order to work it #
- Confirm where it fails: Test Connection inside the DNM is the provider; a saved provider with an empty trend is tag or trend configuration.
- Test the SQL Server port from the InTouch node and read the firewall profiles on the Historian node.
- Open the port in the active profile and repeat until
TcpTestSucceededis True. - Accept the 2023 limitation: Windows credentials are unsupported in the DNM history provider, typed or stored.
- Enable SQL Server and Windows Authentication mode, restart the SQL Server service — and Agent if it runs — and prove the path with sa once.
- Move to a dedicated SQL login with Runtime database access only, store it as a User name and password credential, and select it in the provider.
Questions asked
Does storing a Windows account in Credentials Manager fix the Test Connection failure?
No. The Distributed Name Manager history provider rejects Windows user credentials at the connection itself, so a stored domain user name and password credential fails the same way as typing the account into the provider. The rejection is about the credential type, not the format of the user name. Use the user name and password credential type with a SQL Server login instead.
Is testing TCP 1433 enough when SQL Server runs a named instance?
No. Port 1433 belongs to a default instance. A named instance listens on its own port, dynamic by default unless an administrator fixed it, so Test-NetConnection against 1433 can legitimately fail while the real listener answers elsewhere. Read the configured port from the SQL Server network configuration and test that port from the InTouch node.
Can the sa account stay in service once Test Connection succeeds?
No. Use sa once on a bench to prove the path, then change the password or disable it and move the provider to a dedicated SQL login granted access to the Runtime database only. sa carries full control of the whole instance, including every database on it, which is far more exposure than a trend connection needs.
Do InTouch logging or Historical Logging need to be enabled to trend Historian data?
No. Those features make InTouch a source of historical data. Retrieving data an existing Historian already collected is configured on the consuming component, such as the trend. When Historian collects through its own data acquisition, InTouch WindowViewer does not even have to be running for collection to continue.
Is a Distributed History Provider required to show Historian data on trends?
No. The .NET historical trend client can point directly at the Historian without a Distributed History Provider, which sidesteps the provider's SQL-login requirement entirely. Use that route when the only goal is displaying already-collected data; use the provider when classic components need the name it publishes.