Lowell, thanks for the quick reply. However, the error message occurs due to the trigger failing to execute properly. I failed to mention that.

If I test the trigger through a .Net application where a db does not require encryption and the connection is not encrypted, the same message is displayed.

So, for both the true and false condition you get the same results.

I know that the message appears for the dbs that we require encryption for when testing through SSMS and I'm fairly confident that the trigger works fine in SSMS.

Thanks, again.