Comments
3 comments
-
This is a good call. I ran in to exactally this, this morning. Was curious if anyone else had. -
Hi @DonFerguson,
Thank you for pointing that out! I will work to get the v14 migration guide updated (as it will impact any users updating from v13 to 14.0.3 using https with the Kestrel webservice and storing the cert in that folder, and also see about a note added to the release notes as well.
Kind regards,
Alex -
Hi all,
I have added a note to the bottom of the "Configuration files and query search data location" section of the Migration guide to version 14 documentation indicating the rename of the previous SQL Monitor folder from version 14.0.3 onwards and its particular impact on configuration files that were manually updated with that path (e.g. when enabling https).
Kind regards,
Alex
Add comment
Please sign in to leave a comment.
Fortunately, I was able to find the issue in the log found in the path C:\ProgramData\Red Gate\Logs\Redgate Monitor\
Here is the significant portion of the issue in the log.
The reason for this failure is because Redgate renamed the SQL Monitor folder as documented in the release notes.
https://documentation.red-gate.com/monitor14/redgate-monitor-14-0-release-notes-240977444.html
Changes
- Rename the redundant folder of "SQL Monitor" from the ProgramData folder left after upgrade from v. 13 to avoid future confusion.
The problem: If you set up SSL, part of the setup is to edit the Webserver.Kestrel.config file with the path to the cert file. This file was not automatically updated to reflect the new C:\ProgramData\Red Gate\Redgate Monitor path.The fix: Edit and update C:\ProgramData\Red Gate\Redgate Monitor\Webserver.Kestrel.config, Replace references of SQL Monitor with Redgate Monitor to reflect the correct path.
Do this before you upgrade.
Hopefully this post will help others avoid the surprise failure I had to troubleshoot.