CODEWITHSUNDEEP
sql-serverdatabase-connectioninstance
limitIntegral314
limitIntegral314

Reputation: 154

SQL Server doesn't get its naming right

When I installed a new instance of SQL Server, I specifically named it MSSQLSERVER01. Indeed, after everything was completed, the following folder had been created.

C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER01

However, Microsoft SQL Server Management Studio was unable to connect to DESKTOP-MHK0JT6\MSSQLSERVER01. I am able to connect to DESKTOP-MHK0JT6 and DESKTOP-MHK0JT6\, but that's not what I want.

When trying to connect to MSSQLSERVER01 from R using odbc::dbConnect, it says that the server either doesn't exist or that access was denied.

Why is this happening? Surely the server exists, because otherwise, the folder would not have been created. (The folder is not empty, by the way, it contains the non-empty folder MSSQL and R_SERVICES.)

Any help is greatly appreciated.

EDIT: The following lines, among others, are found in the log.

The service account is 'NT Service\MSSQLSERVER'.
Server name is 'DESKTOP-MHK0JT6'.
Server is listening on [ 'any' <ipv6> 1433].
Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
Server is listening on [ ::1 <ipv6> 1434].
Server is listening on [ 127.0.0.1 <ipv4> 1434].
The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/DESKTOP-MHK0JT6 ] for the SQL Server service.
The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/DESKTOP-MHK0JT6:1433 ] for the SQL Server service.

Upvotes: 0

Views: 1294

Answers (1)

Geovanny Hernandez
Geovanny Hernandez

Reputation: 237

You should open MMC (SQL Configuration Manager), in there you can see SQL Server Services and the names of configured instances too.

enter image description here

Upvotes: 1

Related Questions