Issue
The PME installer fails on the Configure Network Settings step with an error message indicating: "A connection could not be established to the Database server. Ensure the server is running and accepting connections."
Product Line
Power Monitoring Expert 7.2.x
Power Monitoring Expert 8.x
Power Monitoring Expert 9.0
Power Monitoring Expert 2020
Power Monitoring Expert 2021
Power Monitoring Expert 2022
Power Monitoring Expert 2023
Environment
PME Secondary Server Installer
Cause
The secondary server is unable to connect to the database instance.
Resolution
To verify that the secondary server cannot connect to the database instance, attempt saving a UDL file on the desktop. If the file cannot be saved, an error will appear indicating that a connection to the SQL Server failed.
Attempting to test a database connection using a UDL file prompts the error “SQL does not exist or access denied”. This clearly indicates that the secondary machine cannot connect to the database instance.
Once verified that this is the issue, follow the steps below to resolve the connection issues.
If the issue still exists, make sure that hat the SQL server accepts remote connections. Please refer to the link below for assistance with configuring SQL for remote connections.
Additionally, if a firewall is used on the Primary / Database / Secondary server then certain ports will need to be included in the exception list for opening. Search the SE Asset Guide hereto find your version of PME's port requirements.
The PME installer fails on the Configure Network Settings step with an error message indicating: "A connection could not be established to the Database server. Ensure the server is running and accepting connections."
Product Line
Power Monitoring Expert 7.2.x
Power Monitoring Expert 8.x
Power Monitoring Expert 9.0
Power Monitoring Expert 2020
Power Monitoring Expert 2021
Power Monitoring Expert 2022
Power Monitoring Expert 2023
Environment
PME Secondary Server Installer
Cause
The secondary server is unable to connect to the database instance.
Resolution
To verify that the secondary server cannot connect to the database instance, attempt saving a UDL file on the desktop. If the file cannot be saved, an error will appear indicating that a connection to the SQL Server failed.
Attempting to test a database connection using a UDL file prompts the error “SQL does not exist or access denied”. This clearly indicates that the secondary machine cannot connect to the database instance.
Once verified that this is the issue, follow the steps below to resolve the connection issues.
- On the Database server, type Server Configuration Manager in the Windows start menu and open the application.
- Expand SQL Server Network Configuration and select Protocols for ION.
- Click on the Named Pipes Protocol Name and change the status to Enabled.
- Restart the SQL server service for the changes to take effect.
If the issue still exists, make sure that hat the SQL server accepts remote connections. Please refer to the link below for assistance with configuring SQL for remote connections.
Additionally, if a firewall is used on the Primary / Database / Secondary server then certain ports will need to be included in the exception list for opening. Search the SE Asset Guide hereto find your version of PME's port requirements.