December 9, 2017 at 5:49 am
I am getting this error when trying to setup a Notify operator task on a SQL2016 server
Property IsMailHost is not available for Database '[msdb]'. This property may not exist for this object, or may not be retrievable due to insufficient access rights. (Microsoft.SqlServer.Smo)
We have .Net Framework 3.5 installed
Current SQL version is SP1 CU6. I know there was a fix for this issue in CU2, should the installs of CUs have been in order or would it have been fine just to run CU6 , seems not to be needed though.
I have also run
sp_configure 'Database Mail XPs' ,1
GO
RECONFIGURE
GO
I can send a test email and the profile is the default mail profile
December 11, 2017 at 12:19 pm
Andre 425568 - Saturday, December 9, 2017 5:49 AMI am getting this error when trying to setup a Notify operator task on a SQL2016 serverProperty IsMailHost is not available for Database '[msdb]'. This property may not exist for this object, or may not be retrievable due to insufficient access rights. (Microsoft.SqlServer.Smo)
We have .Net Framework 3.5 installed
Current SQL version is SP1 CU6. I know there was a fix for this issue in CU2, should the installs of CUs have been in order or would it have been fine just to run CU6 , seems not to be needed though.I have also run
sp_configure 'Database Mail XPs' ,1
GO
RECONFIGURE
GOI can send a test email and the profile is the default mail profile
Try setting the profile to public if it isn't already.
And also check if you have enabled mail and the mail profile in the Agent Properties for the Alert System.
Sue
December 11, 2017 at 3:15 pm
All done thanks originally, also receiving test mails
December 12, 2017 at 12:19 pm
Andre 425568 - Monday, December 11, 2017 3:15 PMAll done thanks originally, also receiving test mails
It could just be bugs with SSMS as you've noted and I'm not sure that it's actually been really fixed. I know people have tried different versions of SSMS and that hasn't worked either. And others can't reproduce it on the same versions
So maybe try from a different PC? If it works for some and fails for others on the same version of SSMS then I would think it's some type of configuration issue related to whatever is on that server or PC where the issue comes up.
Sue
December 13, 2017 at 9:51 am
I'm dealing with same issue and yes, it would be nice to make use of this great documentation feature. However, my work around is making use of the Job Properties/Alerts or Notifications.
December 22, 2017 at 1:09 am
Thanks guys. I have tried recreating it on other VMs, get the same issue every time SSMS version 17.4
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply