Comments
6 comments
-
I'm also seeing these in the Base Monitor.log:
2020-05-04 17:37:31,273 [ 7] WARN RedGate.SqlMonitor.Engine.Monitoring.Core.Services.ActiveDirectoryConfigRepository - Failed to load credentials for domain hpl and no old-format entry was found. No Credential Manager entries were found for SQL_Monitor_AD_ServiceAccount_hpl or SQL_Monitor_AD_ServiceAccount. 2020-05-04 17:37:48,180 [ 92] WARN RedGate.SqlMonitor.Engine.Monitoring.Core.Services.ActiveDirectoryConfigRepository - Failed to load credentials for domain hpl and no old-format entry was found. No Credential Manager entries were found for SQL_Monitor_AD_ServiceAccount_hpl or SQL_Monitor_AD_ServiceAccount. 2020-05-04 17:37:48,243 [ 92] WARN RedGate.SqlMonitor.Engine.Monitoring.Core.Services.ActiveDirectoryConfigRepository - Failed to load credentials for domain hpl and no old-format entry was found. No Credential Manager entries were found for SQL_Monitor_AD_ServiceAccount_hpl or SQL_Monitor_AD_ServiceAccount. 2020-05-04 17:38:01,414 [ 21] WARN RedGate.SqlMonitor.Engine.Monitoring.Core.Providers.ProviderStatusLogger - Unknown error. HResult is -2146233088, status code is 5376 2020-05-04 17:38:05,149 [ 99] WARN RedGate.SqlMonitor.Engine.Monitoring.Core.Providers.ProviderStatusLogger - Unknown error. HResult is -2146233088, status code is 5376
-
Hi Mike,
When the activation fails, does it offer an alternative or manual activation process at all? If so, would you please try that? The below article contains some more info:
-
Martin, thanks for responding. I attempted this cut-over again today.
I couldn't find any alternate or manual activation instructions in the SQL Monitor UI.
I attempted the process in the link (e.g. navigating to the localhost:22221 address). This address is not active on the new server with only the new install of the Base Monitor Service on it. Attempting this on the original server that is hosting the SQL Monitor Web Service, gives me some options but none of them are for SQL Monitor, only for other RedGate products that are also installed on that server.
I may be able to open up ports, etc. for the new server to access the RedGate Licensing service directly.
What are the network access requirements necessary for the new Base Monitor server to be able to access the automatic RedGate Licensing service?
-Mike -
Hi Mike,
Unfortunately the localhost page will not work because SQL Monitor does not use the Redgate Client Service. However, you should be able to get to the manual activation page by copy/pasting the following URL:
(replace localhost:8080 with your sql monitor installation url and port).
-
Thanks Martin. Attempted this again today with your instructions for manual activation and it was successful.
-Mike -
Very glad to hear that! Please let us know if you run into anything else.
Add comment
Please sign in to leave a comment.
These steps seemed to work correctly. I then went back in to Configuration/Licenses and attempt to activate the product licenses. It gives me a "Failed to activate the License - The operation has timed out" error.
The Base Monitor log from the new server has this error:
I can switch the base monitor back to localhost and activate the license successfully so I'm apparently missing something on the new server. The new server is in a different sub-net but I think I've worked through all the firewall changes to give it access to the monitored servers.
What am I missing?