There appear to be a few cases where having BizTalk 2004 and the .NET
2.0 framework installed on the same machine may cause you some difficulty. I'm
not sure why this might be - and it works fine in my environment. However, I've
seen a few cases where the BizTalk service will not start...or where the BizTalk 2004
process is loading (gulp) the 2.0 runtime(so says Process
Explorer.) This latter behavior will result in the VS2003 debugger not attaching
correctly (among other things...)
To fix this, you can modify the BTSNTSvc.exe.config file (for BT2004) to include the
following (after 'configSections'):
<startup>
<supportedRuntime version="v1.1.4322"/>
</startup>