NodeJS应用连接SQL Server报错：无法查找实例DESKTOP-N5***R/ONEJOHI

Hey there, let's work through this connection issue you're facing. That "Failed to look up instance on DESKTOP-N5***R/ONEJOHI" error typically stems from misconfigured instance settings or incorrect connection string formatting in your Node.js code. Here are the key steps to troubleshoot:

1. Verify Your SQL Server Instance Name #

First, double-check that you're using the correct instance name:

• Open SQL Server Configuration Manager
• Navigate to SQL Server Services
• Look for the service named SQL Server (ONEJOHI) – the text in parentheses is your instance name (confirm it's exactly ONEJOHI)
• Note: If you're using the default SQL Server instance, you don't need to append an instance name; just use the server name DESKTOP-N5***R alone.

Also, watch out for slashes: In connection strings, you need to use a backslash (\) instead of a forward slash (/). In JavaScript, you'll need to escape it with a second backslash (\\) or use a template literal with a single backslash.

2. Ensure SQL Server Browser Service is Running #

Named instances rely on the SQL Server Browser service to broadcast their location over the network. If it's stopped, your Node.js app won't be able to find the instance:

• In SQL Server Configuration Manager, go to SQL Server Services
• Find SQL Server Browser – make sure its status is "Running"
• Set its startup type to "Automatic" so it starts with Windows, avoiding future issues.

3. Fix Your Connection String Format #

Let's make sure your config object is set up correctly for the mssql library. Here's a working example tailored to your setup:

// Example config.js content
module.exports = {
    user: "your_sql_username",
    password: "your_sql_password",
    server: "DESKTOP-N5***R\\ONEJOHI", // Double backslash for JS escape
    database: "your_target_database",
    options: {
        encrypt: false, // Disable encryption for local SQL Server instances
        trustServerCertificate: true // Skip certificate validation for local dev
    }
};

If you prefer template literals, you can write the server string as DESKTOP-N5***R\ONEJOHI without escaping.

4. Check Firewall Settings #

Even for a local connection, Windows Firewall might block traffic to SQL Server:

• Open Windows Defender Firewall > Advanced Settings
• Ensure there are inbound rules allowing traffic to:
  • SQL Server (default port 1433, or your custom port if you changed it)
  • SQL Server Browser (UDP port 1434)

5. Test Connection with SSMS First #

To rule out SQL Server itself being the issue, try connecting to DESKTOP-N5***R\ONEJOHI using SQL Server Management Studio (SSMS). If SSMS can't connect either, the problem is with your SQL Server instance configuration (not your Node.js code).

Start with these steps – most "failed to look up instance" errors get resolved by fixing the instance name or enabling the SQL Server Browser service. Let me know if you hit any snags along the way!

内容的提问来源于stack exchange，提问作者Onejohi_