I’ve just had an insane 2 weeks with work but I did manage to get my site updated to the technical refresh and would have forgotten about my birthday if it wasn't for my friends at the SAJ;-).
MOSS allows you to run side by side with WSS v2 but the final TR patch process (psconfig.exe) will try to patch the WSSv2 config database which it should not try to do unless you specify this in a registry key. They error in the log is
[FarmSequence] [DEBUG] [9/18/2006 8:39:04 PM]: Initializing old farm - Server=community;Database=wssv2config;Trusted_Connection=yes;App=SharePoint Portal Server;
[SPManager] [ERROR] [9/18/2006 8:39:04 PM]: CanUpgrade [SPFarm Name=SharePoint_Config] failed.
[SPManager] [ERROR] [9/18/2006 8:39:04 PM]: Invalid object name 'dbo.PortalGlobals'.
Your Database name will be different (I have so many databases that the default names just make it too confusing for me to figure out what they are for).
But why would you want to run WSSv2 on the server when v3 is soo much better? Maybe you have Project Server 2003, VSTS or a 3rd party solution built on tom of WSSv2 that can’t be upgraded to v3 yet (and this is your dev/test server as you wouldn't install a beta product on a production server, would you).
I had to remove WSSv2 from the server, re run pscong, then re-install WSSv2 and restore my stsadm backups.