Comments
Sort by recent activity
When I attempt to open Tab History, this is the error I'm getting: '{DependencyProperty.UnsetValue}' is not a valid value for property 'OpacityMask'. SSMS: Microsoft SQL Server Management Studio 11.0.5058.0 / comments
When I attempt to open Tab History, this is the error I'm getting:'{DependencyProperty.UnsetValue}' is not a valid value for property 'OpacityMask'.SSMS: Microsoft SQL Server Management Studio 11.0...
CraigEddy said:
When I attempt to open Tab History, this is the error I'm getting: '{DependencyProperty.UnsetValue}' is not a valid value for property 'OpacityMask'.
SSMS: Microsoft SQL Server Management Studio 11.0.5058.0
This is fixed in 9.5.23.12091. Thanks! / comments
CraigEddy said:
When I attempt to open Tab History, this is the error I'm getting:'{DependencyProperty.UnsetValue}' is not a valid value for property 'OpacityMask'.
SSMS: Microsoft SQL Server...
@Tianjiao_Li I was able to get the Web folder deleted by first un-installing IIS Express, then deleting the folder, and then using the installer again. I'll probably pursue using IIS soon, when I find time to get it configured on that machine. Thanks for your help. Craig / comments
@Tianjiao_Li I was able to get the Web folder deleted by first un-installing IIS Express, then deleting the folder, and then using the installer again.I'll probably pursue using IIS soon, when I fi...
Tianjiao: I'm getting a similar error with SQLMonitorWeb_8.0.17.16240.exe but now it's about the C:\Program Files\Red Gate\SQL Monitor\Web\Website\Scripts folder. I uninstalled the SQL Monitor Web Services and tried the installer with the same result. / comments
Tianjiao: I'm getting a similar error with SQLMonitorWeb_8.0.17.16240.exe but now it's about the C:\Program Files\Red Gate\SQL Monitor\Web\Website\Scripts folder. I uninstalled the SQL Monitor Web ...
Yes, that worked like a champ! Thank you! / comments
Yes, that worked like a champ! Thank you!
Wow! I think version 2.0.23 has fixed this. Thanks! [image] / comments
Wow! I think version 2.0.23 has fixed this. Thanks!