TN - 1503 Historian Client Named Pipes Connection Error
Last updated: June 4th, 2026Description
- Author: Rich Brooks
- Published: June 4th, 2026
Details:
Description
This article from InSource shows how to resolve a Named Pipes Connection Error for AVEVA Historian Client.
- Author: Rich Brooks
- Published: 6/4/2026
- Applies to: AVEVA Historian Client 2023 R2 SP1 P04 and higher
Details
Following an upgrade of the Historian, you may encounter the following popup message when attempting to connect from the Historian Client.

You may also see messages in the Log Viewer as shown below.

There is a problem with the linked server “INSQL”. The linked server is found in SQL Server Management Studio under Server Objects.

The linked server may be deleted and rebuilt. Right-click on the “INSQL” under Linked Servers to select Delete. Run the following from a new query window to rebuild the linked server.
USE [master]
GO
/****** Object: LinkedServer [INSQL] Script Date: 6/4/2026 9:39:15 AM ******/
EXEC master.dbo.sp_addlinkedserver @server = N'INSQL', @srvproduct=N'', @provider=N'INSQL'
/* For security reasons the linked server remote logins password is changed with ######## */
EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'INSQL',@useself=N'True',@locallogin=NULL,@rmtuser=NULL,@rmtpassword=NULL
GO
EXEC master.dbo.sp_serveroption @server=N'INSQL', @optname=N'collation compatible', @optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @server=N'INSQL', @optname=N'data access', @optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @server=N'INSQL', @optname=N'dist', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'INSQL', @optname=N'pub', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'INSQL', @optname=N'rpc', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'INSQL', @optname=N'rpc out', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'INSQL', @optname=N'sub', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'INSQL', @optname=N'connect timeout', @optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @server=N'INSQL', @optname=N'collation name', @optvalue=null
GO
EXEC master.dbo.sp_serveroption @server=N'INSQL', @optname=N'lazy schema validation', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'INSQL', @optname=N'query timeout', @optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @server=N'INSQL', @optname=N'use remote collation', @optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @server=N'INSQL', @optname=N'remote proc transaction promotion', @optvalue=N'true'
GO
Recommended articles
[ISS Support Case] Hist client not connecting to server
When trying to logon to the sql server in remote clients auth fails. Configured for non-CNA account. Tested in SSMS - windows auth works, sql auth failed. Changed pw - sql auth worked, client connected.
Read More[ISS Support Case] No Tag Information in Historian Client Trend
After connecting, tags are not available in the tag picker. Message states "Impossible, the server was not added"
Read More[ISS Support Case] Historian missing data
A month ago they changed the network acct utility. Missing data from 9/7 - 10/30, data starting coming in after they re-ran the change network acct utility again. ?Using tiered historian.
Read More