Applies to
ApexSQL Monitor, ApexSQL BI Monitor, ApexSQL VM Monitor
Symptoms
The “Unable to open SQL Server connection” error appears in the Configuration step of the ApexSQL Monitor installation when the remote SQL Server instance is specified in the Server name field of the Central repository database section
Problem
During the ApexSQL Monitor installation process, the Configuration step requires selecting the SQL Server instance that should host the repository database. Additionally, this step requires entering the credentials for the Windows account that be used by the monitoring service.
When the user choses to host the repository database on a remote SQL Server instance in the Central repository database section, setting the adequate Windows account name and password in the Monitoring service section and pressing the Next button, after some 30 seconds the “Unable to open SQL Server connection” error message pops up.
Cause
The Windows account used in the Monitoring service section might be the correct one and with sufficient permissions on remote SQL Server, but the ApexSQL Monitor installer does not use that account to create the repository database on the remote SQL Server instance. The installer uses that account only for the ApexSQL Monitor service. Once the ApexSQL Monitor service is installed, it runs under that Windows account entered in the Monitoring service section
The installer itself is the one that creates the repository database on the remote SQL Server directly. The installer itself running under the Windows account that initiated the ApexSQL Monitor installation, which is the user that Windows OS is running under. If that Windows account does not have adequate permissions required for creating the repository database on the remote SQL Server instance, the “Unable to open SQL Server connection” error message appears
Solution
Make sure that the user that initiates the installation process has sufficient privileges on the remote SQL Server instance to create the repository database.
The following solutions are available:
Solution 1:
If it is possible, create the SQL login on remote SQL Server for the Windows user that should perform the ApexSQL Monitor installation. Make sure that the SQL login has CREATE DATABASE, CREATE ANY DATABASE, or ALTER ANY DATABASE permissions. Run the installation again
Solution 2:
In case the solution 1 is not possible or not allowed, then run the installer as a different user.
To do that:
Hold the Shift button and the mouse right click on the ApexSQL Monitor.exe installation file
Chose the Run as a different user command from the context menu. The Windows security Run as a different user dialog pops up
Now enter the user name and password for a Windows account with adequate permissions on target SQL Server and press the OK button
After the installation starts under the specified user, complete the installation as usual. The error should not appear again
Solution 3:
Log out from the current Windows session and log in to Windows again using the Windows account that has sufficient privileges on the remote SQL Server instance. Rerun the installation, and it will complete without error, and the repository database will be installed on the selected remote SQL Server
6.Optionally, perform the following tasks:•ClickSQL Database Unavailable Alert…toconfigurethe SQLdatabasenotificationsettings.For details, seeConfiguringthe SQL Database Unavailable Alert onpage 14-49.•ClickTest Connectionto verify the authentication credentials forthe existing SQL Server or database.7.ClickStartto apply theconfigurationchanges.Configuring the SQL Database Unavailable AlertApex One automatically sends this alert whenever the SQL database becomesunavailable.
Trend Micro Apex One™ Administrator's Guide14-50WARNING!Apex One automatically stops all services when the database becomesunavailable. Apex One cannot log agent or event information, perform updates,orconfigureagents when the database is unavailable.Procedure1.On the Apex One server computer, browse to <Server installation folder>\PCCSRV\Admin\Utility\SQL.2.Double-clickSQLTxfr.exeto run the tool.TheApex One SQL Server DatabaseConfigurationconsole opens.3.ClickSQL Database Unavailable Alert….TheSQL Server Unavailable Alertscreen opens.4.Type the email address(es) for the recipient(s) of the alert.Separate multiple entries using semicolons (;).5.Modify theSubjectandMessageas necessary.Apex One provides the following token variables:Table 14-18.SQL Database Unavailable Alert TokensVariableDescription%xThe name of the Apex One SQL Server instance%sThe name of theaffectedApex One server6.ClickOK.
Managing the Apex One Server14-51Apex One Web Server/Agent Connection SettingsDuring Apex One server installation, Setup automatically sets up a webserver that enables networked computers to connect to the Apex One server.Configurethe web server to which networked endpoint agents will connect.If you modify the web server settings externally (for example, from the IISmanagement console), replicate the changes in Apex One. For example, ifyou change the IP address of the server for networked computers manuallyor if you assign a dynamic IP address to it, you need toreconfigurethe serversettings of Apex One.WARNING!Changing the connection settings may result in the permanent loss ofconnection between the server and agents and require the re-deployment ofSecurity Agents.Configuring Connection SettingsProcedure1.Go toAdministration>Settings>Agent Connection.2.Type the domain name or IPv4/IPv6 address and port number of theweb server.NoteThe port number is the trusted port that the Apex One server uses tocommunicate with Security Agents.3.ClickSave.
Trend Micro Apex One™ Administrator's Guide14-52You canconfigureApex One to ensure that all communication between theserver and agents are valid. Apex One provides public-key cryptography andenhanced encryption features to protect all communication between theserver and agents.Server-Agent Communication
Upload your study docs or become a
Course Hero member to access this document
Upload your study docs or become a
Course Hero member to access this document
End of preview. Want to read all 253 pages?
Upload your study docs or become a
Course Hero member to access this document