How do I change the Port Number for SQL Monitor?
jasonhurley
Posts: 7 Bronze 3
Previously the URL for accessing our Redgate Monitor was:
http://{internal server IP}:8080/
I just installed updates to SQL Monitor and now it's:
http://{internal server IP}:8070/
How can I update the Port Number so that our users don't have to change the URL they use?
http://{internal server IP}:8080/
I just installed updates to SQL Monitor and now it's:
http://{internal server IP}:8070/
How can I update the Port Number so that our users don't have to change the URL they use?
Tagged:
Best Answer
-
Russell D
Posts: 1,324 Diamond 5
First stop the basemonitor, then you need to edit the RedGate.Response.UI.Server.Service.exe.config, in C:\Program Files\Red Gate\SQL Monitor\Web\. Find the portNum setting in the serverSettings tags:
<serverSettings portNum="8080" serviceType="network">
<website path="C:\Program Files\Red Gate\SQL Monitor\Web\Website\"/>
</serverSettings>
then restart both the SQL Monitor Basemonitor and the SQL Monitor Web Service services.Have you visited our Help Centre?
Answers
Hi @hurleystylee
It depends on whether you are using the built in webserver or IIS. I imagine you are using the built in webserver as it would be harder to accidentally change the port in IIS
For the built in webserver:
If you haven't opened as an admin it will not let you save it. The line will look like:
If you are using IIS you will need to edit the port the site in IIS is bound to.
I hope that helps!
Kind regards,
Alex
Have you visited our Help Center?
Yes, I'm using the built in webserver, but I've got slightly different values than what you pointed out.
1. In %ProgramData%\Red Gate\SQL Monitor\, that applicationhost.config file doesn't exist. All that's there are 2 folders - BaseMonitor and Web. However, in the Web folder, there's an applicationhosttemplate.config file
2. That applicationhosttemplate.config file has the following line in it:
<binding protocol="http" bindingInformation="*:{PORT}:*"/>Although I didn't think it would work, I went ahead and changed that line to match what you suggested, then restarted the Web Service. No luck.
It sounds like you're looking in the %ProgramFiles% folder (the install directory which has BaseMonitor and Web or Website depending on whether you have IIS or built in webserver) not the %ProgramData% folder (the hidden folder for data relating to the program that isn't user specific).
Copy and paste the folder path and it should take you to the right place - though thinking about it just now, you may be able to change this working directory when you install.
Can you confirm whether you are looking at the correct folder above?
Kind regards,
Alex
Have you visited our Help Center?
Thank you for your continued help! I apologize for being in the wrong folder before - that was dumb. I'm in the ProgramData folder now and have found the config file in question.
I'm able to modify the binding protocol line in Admin mode, I close it and then reopen it to verify the change was saved (it was), then I restart the SQL Monitor Web Service. Nothing appears to have changed , plus the value in the config file reverts back to 8070.
Thank you!
Jason
Not a problem it happens to us all
This is quite odd - what version of SQL Monitor are you using? If you stop the webservice first and then try editing it and start the service again does it still do this?
Kind regards,
Alex
Have you visited our Help Center?
This all started because I opened up SQL Monitor and it prompted me to update to the latest version. So, that's what version I'm on now! (Web Server and Base Monitor versions of 7.1.12.9668)
I liked the idea of stopping the service, changing the value, and starting the service. However, that didn't work either! It keeps reverting the value back to 8070!
Thanks,
Jason
Thanks for helping out with this too!
I was able to change the portNum value in that config file from 8070 to 8080 and the value "stuck" when I restarted the basemonitor.
However, the Monitor is still only working with the URL of 8070 and not 8080.
http://localhost:8070/GlobalDashboard/ --> Works
http://localhost:8080/GlobalDashboard/ --> Doesn't work