| FYI: 'Execution guard failed...' error resolved! I was also getting the 'Execution guard failed to check the script due to internal error' from SSMSBoost 3.0 beta after upgrading SSMS2016 this week (and some other seemingly harmless 'Object not set' errors). However, when I viewed the error details from the popup it shows several ApexSQL errors, so apparently there's a conflict between the two addins w/latest SSMS2016 build. (I also installed the latest ApexSQLComplete2017 this week) I uninstalled ApexSQLComplete2017 and the errors went away. |
 |