FAQ and Troubleshooting guide for the Nodinite Database Monitoring Agent
Unlock the full potential of your database monitoring with the Nodinite Database Monitoring Agent. This guide provides actionable solutions and expert advice for common challenges, ensuring you maintain robust and reliable monitoring.
✅ Ensure secure and correct connection string configuration
✅ Resolve SQL Agent service issues quickly
✅ Access expert support for advanced troubleshooting
Below, you'll find clear solutions to frequently encountered problems and best practices for using the Database Monitoring Agent.
Connection String Issues
Password with Special Characters
If your password contains special characters (such as ; semicolon, = equals, or ' quotes), you may experience connection failures.
Tip
See the comprehensive solution: [Password with Special Characters][SQL Connection Strings] section in the SQL Server Connection Strings guide for:
- ✅ Best practice: Use Windows Authentication to avoid passwords entirely
- ✅ How to properly escape passwords with special characters
- ✅ Complete examples with troubleshooting
Quick fix: Enclose the password in single quotes:
❌ Incorrect:
Server=localhost;Database=MSDB;User Id=ServiceAccountName;Password=Da;Password;
✅ Correct:
Server=localhost;Database=MSDB;User Id=ServiceAccountName;Password='Da;Password';
Other Connection String Issues
For certificate validation errors, encryption settings, Azure SQL, and AOAG configuration:
[SQL Server Connection Strings Guide][SQL Connection Strings] – Complete troubleshooting and configuration reference
SQL Agent is Stopped or Disabled
If the SQL Agent service is not running, Monitor Views with the Nodinite Database Monitoring Agent will display a [Resource][Resources] error message:
Example error message for a stopped or disabled SQL Server Agent
The following LogText (in English) may appear, depending on your SQL Server language settings:
SQL Server blocked access to procedure 'sys.xp_sqlagent_enum_jobs' of component 'Agent XPs' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of 'Agent XPs' by using sp_configure. For more information about enabling 'Agent XPs', search for 'Agent XPs' in SQL Server Books Online.
To resolve this issue, you have two options:
- Start the SQL Agent Windows Service for the relevant SQL Server instance using Microsoft Services MMC (Recommended).
Starting the SQL Server Agent may trigger existing SQL Server jobs (including SSIS and maintenance plans) to run. - Enable Agent XPs via script if you cannot start the agent. This allows monitoring without starting the SQL Server Agent:
SP_CONFIGURE 'SHOW ADVANCE',1
GO
RECONFIGURE WITH OVERRIDE
GO
SP_CONFIGURE 'AGENT XPs',1
GO
RECONFIGURE WITH OVERRIDE
GO
Note
The SQL Server agent is not available in SQL Server Express editions.
Contact our support
If you have questions or need further assistance with the Nodinite Database Monitoring Agent, contact our support team at support@nodinite.com for expert help.
[Resources]:/Administration/2.%20Monitor%20Management/3.%20Resources/Features/What%20is%20a%20Resource.md[SQL Connection Strings]:/Install%20and%20Update/Troubleshooting/SQL%20Server/Connection%20Strings.md