0x80010119 -- The dreaded "Security must be initialized before any
interfaces are marshalled or unmarshalled"

I think at this point you're probably going to have to wait for v2.  
There is a race condition related to v1's use of .NET on top of some of
the other components that we use.  There is a very small minority of
people who hit this, but they seem to hit it consistantly.  Our only
reliable repro of this bug was achieved bu running a Danish language
version of Windows on a virtual PC.  A fairly contrived scenario.

The last person who I helped with this problem was hitting it on a dual-
proc hyper-threaded machine. One theory that he helped me work through
was that we could get the problem to go away by turning off
hyperthreading.  Unfortunatly, it didn't help.  I didn't have the heart
to ask him to disable the additional CPU and turn off hyperthreading to
see if going back to a single CPU and a single active thread ended the
race condition.  I'd still be interested in hearing the outcome of that
experiement.  However, the answer would only be academic as we aren't
going to be putting out a patch for v1 to fix this issue.

We did try to do the investigation on equivalent hardware to look for a
workaround. I was never able to repro the problem either. <sigh>.

It won't be possible for v2 to have this problem.  I can't say exactly
why until we make more broad announcements about the v2 release (sorry).  
When we get ready to do the v2 beta, I'll post an announcement here
looking for volunteers to participate in the beta.  I'd be particulary
interested in having some of the folks who were affected by this bug
take part in the beta.

Sorry,