Comments
Sort by recent activity
Thanks Pete! The former will explain the situation for us - the encryption key was changed on these files a couple of weeks ago.
Perhaps this is something that ought to be noted in the UI when changing/setting an encryption key ie. if you set or change the encryption key, you will manually need to delete any back up files that used the old key because of this issue of not being able to read the headers.
And probably something in the log file that also points to the issue and thorws a warning ie. "Warning xxxx file was not able to be deleted as encryption key does match the key currently stored on the job" / comments
Thanks Pete! The former will explain the situation for us - the encryption key was changed on these files a couple of weeks ago.
Perhaps this is something that ought to be noted in the UI when chan...
Thanks Chris.
I can confirm that after re-installing the agent and updating it to use the correct account to run the service that the SQL Backup Pro UI now correctly shows in the properties as the "SQL Backup version" being '7.3.2.12'
Cheers
Joe / comments
Thanks Chris.
I can confirm that after re-installing the agent and updating it to use the correct account to run the service that the SQL Backup Pro UI now correctly shows in the properties as the ...
Hi Jason
Both of the base monitor servers I mentioned have the following specifications :
IBM X3550 M3 2.13Ghz 32GB RAM running Windows Server 2008 R2 Enterprise
They are "Jump" servers that are used by a number of our staff to grant them access to our production environments. The only tools that run on them aside from SQL Monitor are SSMS and a number of other bespoke internal very low impact applications.
They do not have SQL Server or any SQL instances hosted on them.
Cheers
Joe / comments
Hi Jason
Both of the base monitor servers I mentioned have the following specifications :
IBM X3550 M3 2.13Ghz 32GB RAM running Windows Server 2008 R2 Enterprise
They are "Jump" servers that are us...
Just to add some more information to this one. As of today, without any intervention on my part, the CPU and memory consumption on the problem base monitor has lowered - now the process is consumin approx 8GB memory and running between 5 and 20% CPU
Perhaps not coincidentally this morning I also received a number of very delayed emails for alerts that were generated 36 hours ago within SQL Monitor. We have confirmed from our SMTP message transfer logs that the emails were only delivered to the message transfer agent this morning despite the details of the alerts showing that they were from 36 hours ago.
This is reflected in what I now see in the "Alerts" page in SQL Monitor - these alerts were not visible here until this morning.
So this suggests to me some form of problem within the SQL Monitor application.
Interested to get some feedback from some at RedGate soon as we place a form of reliance on seeing these emails alerts for specific SQL events/issues and not having them delivered in a timely fashion obviously does not allow us to meet our customers expectations.
Cheers
Joe / comments
Just to add some more information to this one. As of today, without any intervention on my part, the CPU and memory consumption on the problem base monitor has lowered - now the process is consumin...
Hi Eddie
I have followed the instructions in your link to check WMI. (minus the screenshots) Testing WMI
At the command prompt, run:
wbemtest
In the Windows Management Instrumentation Tester dialog box, click Connect.
In the Namespace box, type \\myserver.example.com\root\cimv2 where myserver.example.com is the name of the
Windows server you are attempting to monitor.
Under Credentials, enter the Windows account you are using to monitor the server and the password. This is the account listed under Credentials on the Monitored serverspage in SQL Monitor (Configuration > Monitored servers).
Click Connect.
Click Query and enter the following query:
SELECT Name FROM Win32_Service
Click Apply. You should see a list of results similar to those shown below:
If connection fails and an "Access Denied" error message is displayed, see WMI Troubleshooting and WMI Isn't Working!.
I get exactly the same issue when I try these tests with the error:
"User credentials cannot be used for local connections"
So back to my question - is the issue that I cant have the Base Monitor running on a host server that belongs to an SQL cluster and use domain account credentials ie. the base monitor is running on the instance that I am monitoring and that instance is the member of a cluster.
Cheers
Joe / comments
Hi Eddie
I have followed the instructions in your link to check WMI. (minus the screenshots)Testing WMI
At the command prompt, run:
wbemtest
In the Windows Management Instrumentation Tester dialog ...
Can I please get an update on this question or a ticket logged ? / comments
Can I please get an update on this question or a ticket logged ?
Thanks for the reply Chris
I thought it might come down to something like this.
I will have to look at moving the base monitor setup to a server that is not part of the cluster.
Cheers
Joe / comments
Thanks for the reply Chris
I thought it might come down to something like this.
I will have to look at moving the base monitor setup to a server that is not part of the cluster.
Cheers
Joe
Thanks Chris
I can confirm that after installing this updated version, I no longer have this issue.
Cheers
Joe / comments
Thanks Chris
I can confirm that after installing this updated version, I no longer have this issue.
Cheers
Joe
Ahh... Thanks for this bit of information.. I did wonder why, after I had manually resolved some alerts for fragmentation on some of my MSDB that even a few days later the alert had not ended.
Agree with the once a week scanning on this due to the relative expensiveness of running the query to get these results. / comments
Ahh... Thanks for this bit of information.. I did wonder why, after I had manually resolved some alerts for fragmentation on some of my MSDB that even a few days later the alert had not ended.
Agr...
Thanks Raj. I have emailed you the required information. Looking forward to hearing back
Cheers
Joe / comments
Thanks Raj. I have emailed you the required information. Looking forward to hearing back
Cheers
Joe