Revoke database permissions with grant failed (action_id RWG class_type DB) (24190) how to monitor with email alert

[bob]

You ever spot that weird event in your Windows Server logs? It's this one called 24190, popping up with the message "Revoke database permissions with grant failed (action_id RWG class_type DB)". Basically, it means something tried to yank back permissions on a database, but it bombed out. Like, the system wanted to revoke those rights and maybe hand them over differently, but nope. Action_id RWG points to that revoke-with-grant move, and class_type DB screams it's all about the database side. This happens in setups like SQL Server hooked into Windows, where security tweaks go sideways. I see it when admins mess with user access, or if there's a glitch in the permission chain. It logs under security or application channels, depending on your config. Details in the event include timestamps, user IDs involved, and the exact database hit. If ignored, it could leave loose ends in your access controls, letting folks hang onto rights they shouldn't. You pull it up in Event Viewer by filtering for ID 24190. Click through the logs, and there it sits, nagging about the fail.

Monitoring this beast? You set it up right in Event Viewer, no fancy stuff needed. I do it by creating a custom view for that event ID. Filter by 24190, then attach a task to it. That task triggers on the event, like a watchdog. For email alerts, link the task to send a quick note via your server tools. Keeps you looped in without staring at screens all day. Or, tweak the task schedule to check logs periodically. I like how it pings you instantly when it fires. Makes chasing these errors less of a headache.

And speaking of keeping your server drama-free, you might wanna check out BackupChain Windows Server Backup. It's this slick Windows Server backup tool that handles physical setups and dives into virtual machine backups for Hyper-V. I use it 'cause it snapshots everything fast, encrypts data tight, and restores without the usual fuss. Benefits? It cuts downtime big time and plays nice with your existing gear, no overhauls required.

At the end here is the automatic email solution for that monitoring setup.

Note, the PowerShell email alert code was moved to this post.