'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix SQL Server 2022 Computer Account Login Error in SolarWinds
Question details
The user needs to know if a SolarWinds server requires its own SQL login when connecting to SQL Server 2022 via a service account.
- Product
- SQL Server 2022 / SolarWinds
- Device & OS
- not provided
- Scenario
- Connecting a SolarWinds server to a SQL Server 2022 database instance using a Windows service account.
- Observed behavior
- The connection fails with the error message 'Could not find a login matching the name provided.'
Ensure you have sysadmin or securityadmin privileges on the SQL Server 2022 instance so you can view and modify server-level logins.
Verify and Add the Computer or Service Account in SQL Server Logins
This solution ensures that the specific account used by SolarWinds (whether a domain service account or a machine account) is explicitly granted login rights in SQL Server.
When an application runs under a context like 'Network Service' or 'Local System' and connects over a network, it authenticates using the computer's machine account (Domain\ComputerName$). If a dedicated domain account is used, that exact account must be registered in SQL Server.
Launch SSMS and connect to your SQL Server 2022 instance using an account with administrative privileges.
In the Object Explorer, expand the 'Security' folder, right-click on 'Logins', and select 'New Login' from the context menu.
In the Login name field, enter the exact name of the account. If SolarWinds runs as a machine account, enter it in the format 'Domain\ComputerName$'. Click 'Search' to validate the name against your Active Directory.
Navigate to 'Server Roles' and 'User Mapping' on the left panel to grant the necessary database permissions required by SolarWinds documentation, then click 'OK' to save.
Escalate the Issue to Microsoft Q&A Experts
If standard login configurations do not resolve the authentication error, consult the official Microsoft community for advanced SQL Server troubleshooting.
Analyze SQL Server Data Efficiently with WPS Office
While troubleshooting SQL Server 2022 connection errors, you may need to export error logs or query configurations. WPS Office provides a free, lightweight suite to open database exports, analyze CSV files, and document server settings without consuming heavy system resources.
- 1. Export SQL Logs: Save your SQL Server error logs from SQL Server Management Studio as a CSV file.
- 2. Open in WPS Spreadsheet: Launch WPS Office and open the exported CSV file directly.
- 3. Analyze and Filter: Use built-in data filters in WPS Spreadsheet to isolate 'Login failed' events and identify the exact account name causing the issue.
Frequently Asked Questions
Does a computer account need a SQL login if connecting via Network Service?
Yes. If an application service runs as 'Network Service' or 'Local System' and connects to SQL Server over a network, it authenticates using the machine account (e.g., Domain\ComputerName$). You must explicitly add this computer account to SQL Server logins.
Why does SQL Server return 'Could not find a login matching the name provided'?
This error triggers when SQL Server receives a connection request from a Windows account or SQL Auth credentials that have not been created under the SQL Server Security > Logins directory. The connecting account must match an existing entry exactly.
Can I use SQL Server Authentication instead of a Windows service account for SolarWinds?
Yes. SolarWinds supports both Windows Authentication and SQL Server Authentication. If domain authentication continues to fail, you can create a dedicated SQL server login (with a username and password) and configure SolarWinds to use those specific credentials.
How do I check which account SolarWinds is using to attempt the connection?
You can check the Windows Services application (services.msc) on the SolarWinds server. Right-click the primary SolarWinds service, select 'Properties', and look at the 'Log On' tab to see exactly which account is initiating the service.
