Home » RDBMS Server » Enterprise Manager » Add Target Using Wrong Port (Enterprise Manager Windows 2016)
Add Target Using Wrong Port [message #682328] Fri, 16 October 2020 07:57
Messages: 2
Registered: October 2020
Junior Member
Enterprise Manager installed on Windows 2016. We installed an agent on a Windows 2008 server on port 1830, uninstalled and reinstalled on 2889. Agent is reporting as running ok and on port 2889, its monitoring the host and we can see CPU and RAM usage.
If we try and add a database target using Guided Process it fails with 'Unable to connect to the agent at //servername:1830/emd/main connection refused' - so still using the old port for the agent. Uninstalled and re-installed the agent a number of times and everytime it appears to be running on port 2889, but the guided process always reports back a failure on the old port.

Any thoughts or anyone had the same issue?

Previous Topic: Connection refused when trying to start Database Instance
Next Topic: please help me to find solution for this error
Goto Forum:

Current Time: Tue May 28 23:36:04 CDT 2024