SQL error 53: Named Pipes Provider: Could not open a connection to SQL Server[53] during Solution Manager Managed System Configuration

[Former Member]

I created SQL server login(PRD_SAPMonitor) in SQL server 2012(SAP Note 1458291 - SolMan 7.1 Database Warehouse & Alerting for MSSQL

).

Creating a SQL Server login.

These instructions are for SQL Server 2008.  Other releases are very similar.

1. NOTE: This login must be created in the target SQL Server instance that you want to monitor. If your SolMan system runs on SQL Server, do *not* create this login in the local SolMan system.
2. In SQL Server Management Studio, open Object Explorer and expand the folder of the server instance in which to create the new login.
3. First make sure the SQL Server is configured for SQL Server authentication.  Right-click on the server, choose Properties and then click on Security.  Choose "SQL Server and Windows Authentication mode". Click OK.
4. Right-click the Security folder, point to New, and then click Login.
5. On the General page, enter a name for the new login in the Login name box.
6. Select SQL Server Authentication and enter a password for the login. Select the password policy options that should be applied to the new login.
7. Choose the database you want to monitor as the default database.
8. Choose the Server Roles page and check "sysadmin".
9. Choose the User Mapping page and select the database you want to monitor and select the db_owner role membership for the database.
10. Click OK.

I am able to login using PRD_SAPMonitor(SQL Authentication) in SQL Server 2012

Then, I setup DBA Cockpit in Manage System Config.

But I encounter below error:

SQL error 53: Named Pipes Provider: Could not open a connection to SQL Server[53]

Please help.

Regards,

Fadzly Iqbal

[Former Member · Accepted solution]

From SAP:

Dear Fadzly,

I have checked the issue and I think there is a misunderstanding here for creating the user manually.

Usually the monitoring user, which usually has the name SAPMonitor or <(><SID>_SAPMonitor (in your case PRD_SAPMonitor) is created

automatically by the initiating process. The user, what needs to be created is only a temporary user with administration priviledge. You can use here an already existing

administrator e.g. the user sa, which has SQL Server Authentication possibility.

For more details please check the SAP KBA:

1904412 - DBA cockpit connection XXX cannot be established

I am suggesting also to upgrade the SAP_BASIS component to the latest version, because it contains Monitoring related corrections like:

1963503 - Objects erroneously dropped and created in the 'dbo' schema due to an error

Please update also the kernel and DBSL module to the latest patch level.

thank you for your feedback in advance

best regards

Sándor Szalina

SAP Product Support