EventType clr20r3 on Workflow execution on Windows 2003 64bit

I have a program that runs on windows XP using .net 3.5 framework family. After many reinstalls using the redistributable package, the bootstrapper, and windows updates, when launching the program i get "".exe has encountered a problem and needs to close. Event viewer shows this:

.Net Runtime 2.0 Error

EventType clr20r3, P1 "".exe, P2 2010.1.1012.1, P3 4c6168a1, P4 system.configuration, P5 2.0.0.0, P6 4889de74, P7 277, P8 14, P9 ioibmurhynrxkw0zxkyrvfn0boyyufow, P10 NIL.

There are also these errors in event viewer, that only showed up after installing using Windows Updates.

.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Service reached limit of transient errors. Will shut down. Last error returned from Service Manager: 0x80029c4a.

I followed the advice in another msdn support request, http://social.msdn.microsoft.com/Forums/en-US/netfxsetup/thread/f56cc6e4-c2bf-490c-b87b-3e22b1e6b935 that suggested running:

%windir%\microsoft.net\framework\v2.0.50727\ngen.exe update

%windir%\microsoft.net\framework\v2.0.50727\ngen.exe executequeuedstatus

and

%windir%\microsoft.net\framework\v2.0.50727\ngen.exe queue status

and the requested output of the update command returns:

Error loading type library/DLL. (Exception from HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY))

On my old labtop (windows xp) I was using a SharePoint 2007 + Windows 2003 virtual machine (vhd)

(I was using the free Microsoft Virtual PC to use it) .But my labtop was very slow so I bought a new machine which has Windows 7 professional 64 bit.So how could I use my old vhd? I heard Virtual pc doesn't work on 64 bit windows.

After some search in google I read about VMWare Server which is free.I read v1 is better than v2.But I have no idea about it and didn't use it before is it safe?

Design patterns provide a common, repeatable approach to solving software development tasks, and many different patterns can describe how to accomplish a certain goal in code. When developers begin working with Windows Workflow Foundation (WF), they often ask about how to accomplish common tasks with the technology. This month's column discusses several design patterns used in WF.

Matthew Milner

MSDN Magazine August 2009

The heart of Windows Workflow Foundation is its declarative programming model. Here are some best practices to consider when using WF to realize software solutions in the real world.

Josh Lane

MSDN Magazine December 2008

State Machine workflows represent a different way of visualizing program logic. Rather than flowing from activity to activity like sequential workflows, State Machines transition from state to state. Learn about uses for State machines and see how to design and build a State Machine workflow with Windows Workflow Foundation.

Keith Pijanowski

MSDN Magazine February 2008

Matt Milner

MSDN Magazine March 2007

This article covers the core components required for building custom activities in Windows Workflow Foundation.

Matt Milner

MSDN Magazine December 2006

Windows Workflow Foundation supports virtually any scenario where human opera¬tors are involved. Learn how to use it to tame your workflows.

Dino Esposito

MSDN Magazine November 2006

Due to the distributed nature of a business process it makes sense for a workflow to be deployed as a distributed application. See how Windows Workflow and Web Services hold the key.

Israel Hilerio

MSDN Magazine October 2006

In last month's column, I presented a helpdesk workflow sample that focused on Windows® Forms client applications. This month I'll discuss ASP. NET workflow applications and the ability to expose a workflow as a Web service and invoke a Web service from a workflow.

Dino Esposito

MSDN Magazine April 2006

In the January 2006 issue, Don Box and Dharma Shukla introduced Windows® Workflow Foundation and discussed the overall architecture of the framework and its constituent components (see WinFX Workflow: Simplify Development With The Declarative Model Of Windows Workflow Foundation).

Dino Esposito

MSDN Magazine March 2006

Windows Workflow Foundation allows you to write workflow-based programs in terms of domain-specific activities that are implemented in CLR-based programming languages such as C# and Visual Basic. Here Don Box and Dharma Shukla get you started.

Don Box and Dharma Shukla

MSDN Magazine January 2006

There's a lot to say about Windows Server 2003. First of all, it's the first operating system with built-in .NET Framework support, and it's the first 64-bit OS from Microsoft. But wait, there's more! There are lots of new features and APIs in this version as well. For instance, Windows Server 2003 features Hot Add Memory and a number of other arcane new tidbits. There are new APIs for handling threads, directories, and files, and new features like the low fragmentation heap for managing memory and system information. There's vectored exception handling and new UI APIs as well.OS internals expert Matt Pietrek takes a look at the additions he finds most interesting and useful so you'll have a good place to start when you dive into Windows Server 2003.

Matt Pietrek

MSDN Magazine June 2003

Building Web sites that provide services external to the corporate firewall is tricky. Usually it's not desirable to grant corporate domain accounts to external clients, and from a purely practical standpoint Kerberos does not work well over the Internet due to the typical configuration of client-side firewalls.

Keith Brown

MSDN Magazine April 2003

Don Box

MSDN Magazine March 2000

I have an ASP.Net MVC application manages process of forwarding some business entities to one another partner.  At beginning of the process, the forwarding partner sends a request to every other partner.  There are many receiving partners for the forwarding request, but only the first partner who responds with ACCEPT token will enter into the contract with the sending partner.  When this happens, the process enters ACCEPTED state.  When the process goes into ACCEPTED state, the same request previously received by other partners will enter into Cancelled state.

I am thinking using Windows Workflow Foundation to do this, but I am not sure if I should use one flow or multiple flows associating with the forwarding request flow.  If multiple work lows are required, should they be all with the same structure, states, events, handlers, etc?  Any flow executes Accept method enters Accepted state, and triggers all other flows' Cancel events.

Can this be done?  Any other recommendation?  Thank you.