SSMS 2022 Unable to Connect to SQL Server: Fix Error Code 87 on Windows

Many users install SQL Server Management Studio (SSMS) 2022 successfully but get stuck at the login screen with errors like “Error code 87 – The parameter is incorrect.” This issue is common on fresh setups and usually happens due to a misunderstanding between SSMS and the SQL Server Database Engine.

This guide explains why the error occurs and how to fix it correctly on a local Windows laptop.

Why SSMS 2022 Fails to Connect on a Local Laptop

SSMS is only a management tool. It does not include the SQL Server engine itself. If the database engine is missing, stopped, or addressed incorrectly, SSMS cannot connect.

Most common causes

• SQL Server Database Engine is not installed
• SQL Server service is not running
• Wrong server name format for a default instance
• Confusion between default and named instances

Step 1: Check Whether SQL Server Is Installed

Before changing anything in SSMS, confirm that SQL Server actually exists on your system.

How to check

1. Press Win + R
2. Type services.msc
3. Press Enter
4. Look for SQL Server (MSSQLSERVER)

What the result means

What you see	Meaning	Action
SQL Server (MSSQLSERVER) – Running	Server installed correctly	Go to Step 2
SQL Server (MSSQLSERVER) – Stopped	Server installed but inactive	Right-click → Start
SQL Server not listed	Only SSMS installed	Install SQL Server Engine

SSMS alone cannot accept connections. You must install SQL Server 2022 Database Engine separately.

Step 2: Use the Correct Server Name (Most Important Fix)

If your SQL Server instance name is MSSQLSERVER, you are using a default instance.

Default instances do not require the instance name in the Server name field.

Do not use

[Computer Name]\MSSQLSERVER

Use any one of the following

.
(local)
localhost
[Computer Name]

Recommended:
Use . or (local) with Windows Authentication.

The screenshot below shows the correct SSMS 2022 settings for a local SQL Server connection.

Default vs Named Instance Login Reference

Instance type	Instance name	Correct login
Default	MSSQLSERVER	.
Default	MSSQLSERVER	(local)
Named	MSSQLSERVER5	.\MSSQLSERVER5
Named	SQL2019	FDAYTALK\SQL2019

Dot (.) works only for the default instance. Named instances always require the instance name.

Step 3: Choose the Right Authentication Mode

For a local laptop setup:

• Use Windows Authentication first
• Avoid SQL Login until the server connection is confirmed

Windows Authentication works automatically when SQL Server is installed and running correctly.

Step 4: Verify SQL Server Network Settings (If Needed)

If SSMS still cannot connect after using the correct server name:

1. Open SQL Server Configuration Manager
2. Go to SQL Server Network Configuration
3. Select Protocols for MSSQLSERVER
4. Ensure TCP/IP is Enabled
5. Restart SQL Server (MSSQLSERVER) service

Then try connecting again using:

localhost

Step 5: When You Must Install SQL Server Engine

If SQL Server (MSSQLSERVER) does not appear in Services, you need to install the database engine.

What to install

• SQL Server 2022 (Developer or Express edition)
• Select Database Engine Services during setup

After installation

• Restart the system
• Open SSMS
• Connect using . or localhost

Correct SSMS 2022 Settings to Connect to SQL Server on Windows

• Server name: .
• Authentication: Windows Authentication
• Service: SQL Server (MSSQLSERVER) running

Most SSMS 2022 login errors happen because users install only SSMS or use the wrong server name for a default instance. Once the SQL Server Database Engine is installed and running, connecting locally becomes straightforward.