I've now come across several issues, like the BizTalk service restarting all the time or not being able to run configureFramework.exe correctly.

After some searching & spelunking(tm) I've found the NT Eventlog to be the culprit!

As we all know Biztalk dumps tremendous amounts of logging information into the NT Eventlog. In certain circumstances (like configuring & un-configuring a number of times) the eventlog might run into its configured limit. When this happens Biztalk kind of chokes.

The error of not being able to write to the eventlog, is being written to the NT eventlog.

Ehhh.. anyone got a problem with that?

Just remember to set up your development system using a 'overwrite when needed' configured NT Eventlog