VRRP config be roughly the same across all versions, so it isn’t the issue here. But I guess my first advice be to update to version 7.15.2 if the routers are newish (/system/package). Or even if older router, if only for testing, you’d be better off to start with V7. All the docs and bugs focus on version 7 - you have an OLDER version 6. And also upgrade the firmware in /system/routerboard after upgrading the RouterOS version.
I don’t have time write a good example right now & my examples be from version 7. I’ll add to the queue to write an article on VRRP setup at some point - since most post are about some VRRP config errors.
In most cases, you want to use the /interface/bridge with vlan-filtering=yes. See Mikrotik’s docs on bridging and VLANs: https://help.mikrotik.com/docs/display/ROS/Bridge+VLAN+Table
@pcunite has a popular guide - with bridge+VLAN config examples here: http://forum.mikrotik.com/t/using-routeros-to-vlan-your-network/126489/1 You CANNOT [easily] troubleshoot VRRP issues and VLAN bridging issues at the same time. So get the bridge working first.
Once the VLANs are connected and IPs assigned, etc. Add the 2 VRRP /interfaces (and add /ip/address for each), listen on VLAN. VRRP needs to listen on the /interface/vlan in ALL cases. But it depends on things being bridged correctly. The VRRP part you seem to have/understand. But your method to deal with VLAN trucks/ports is not the “modern” way of doing it, so using new bridge vlan config is easier long-term.
The only subtlety in VRRP is /ip/dhcp-server - since “something” has to provide address when in on BACKUP VRRP router. And what’s odd in your photos is you’re showing a DHCP client one of the VLAN involved in VRRP. These should be static IP address for each VLAN, on each router - which you show. So I’m not sure where the dhcp-client is coming from since the RouterOS VLAN IP should be static. You show this in the diagram, but then show a screenshot of failed /ip/dhcp-client.