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

Products

• Client Management Suite
• IT Management Suite

Issue/Introduction

Did an in-place OS upgrade on the SQL server (upgraded to Windows Server 2022) and also upgrade the SQL server to SQL Server 2022, and at the same time they did an in-place OS upgrade on the Task Server to Windows Server 2022.  After these upgrades, the managed Symantec Agent machines were no longer able to run jobs and tasks and other functionality that was working previously.

The NS logs show lots of the following SQL errors:

• SQL Exception details: code=2
• SQL Exception details: code=-1
• SQL Exception details: code=18456
• SQL Exception details: code=0
• SQL Exception details: code=4060
• SQL Exception details: code=-2146893055
• SQL Exception details: code=10054

The most common of these errors was:

SQL Exception details: code=2
The system cannot find the file specified

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)

Environment

ITMS 8.6

Cause

Confirmed that the Notification Server (NS) was unable to communicate with the SQL Server (under Configure Settings > Configure Database Settings) so needed to reconfigure this.

Resolution

Used the Symantec Installation Manager (SIM) tool and configured it to allow the NS to the SQL server referencing the correct database and using the correct credentials under Configure Settings > Configure Database Settings.