ASP Developer Network - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com

ASPDeveloper

ASPDeveloper.Net / VirtualServerFAQ.COM

Make sure you go to our home page for:

* Virtual Server 2005 FAQ
* ASP.Net 2.0 Information
* ASP.Net 2.0 Streaming Tutorials
* ASP.Net 2.0 HTML based Tutorials

Made possible by Business Internet Technology Shop (BitShop)

Virtual Server 2005

Recent Virtual Server 2005 posts

* Virtual server does not see new network card
* Virtual Machine Boot Failure: virtual hard disk could not opened with read-write access
* How to use IVMVirtualMachine::AttachScriptToEvent?
* Losing virtual machine from Virtual Server 2005
* Anyone proved StarWind works. Need for Exchange restore (ARCServe)
* VSMT ramdisk error on PXE source server
* VS 2005 R2 guests and access from other subnets
* Virtual PC or Server for SBS2003 and XP Pro test environment
* VS R2 - Redhat Linux
* Error 1068
* phisical folder
* VSMT migrating SBS 2003
* Virtual Machine user account?
* Unable to use network share for .VHD location!
* VS on XP pro without IIS?
* Virtual Machine can only see host, not network
* Re: scsi vs non scsi disk performance
* scsi vs non scsi disk performance
* tools to trasfer floppy to vfd?
* multiple fllopy and CDrom possbile?

Add Solution

CoInitializeSecurity from a C# app fails with error 0x80010119, on chinese and japanese Win2003

Source: microsoft.public.virtualserver
Sent: 02/01/2006
From: "Gaurav Lochan" <(email address - cut out)>
Message:

Hi,

I've got a C# application that uses the Virtual Server COM API, and so
based on their sample code, the first thing my application does is call
CoInitializeSecurity with the specified parameters. I'm using
VS2003.NET and .NET 1.1 to develop the application.

This has worked fine on english systems (Win2003, Windows XP) but when
i tried this on a chinese or a japanese system, the app gets this error
code (0x80010119, RPC_E_TOO_LATE) from CoInitializeSecurity. I've
searched for this and found that people have hit this problem since the
CLR is calling CoInitializeSecurity on its own which prevents our app
from calling it again with the correct parameters.

I've seen that when i try to run my app over and over again, i hit this
problem the first 3-4 times, but then it works. And after that, i dont
hit the exception again !

I'm trying to find the answers to the following questions:
1. Why am I hitting this on the international OS's only ?
2. Why does this happen the first 3-4 times, and then go away ?
3. Is there a solution for this ? I cant just catch and ignore the
exception since i need to set the right parameters to work with Virtual
Server's COM API.

Thanks,

Gaurav

Post Reply | This is Spam! | Mark as Spam

Related Messages

Re: CoInitializeSecurity from a C# app fails with error 0x80010119, on chinese and japanese Win2003

Sent: 02/01/2006
From: Richard Cardona <(email address - cut out)>
Message:

In i18n development I find that keyboard input method support usually
triggers a different initialization profile. When you say you have a C#
app is output type console or Windows/Windows Form? The latter will
initialize more subsystems.

You might try setting some of the culture attributes of your assemblies
to see if .NET initializes your app like on a US system or set the
runtime cultureinfo of your startup thread to en_US.

Without actually trying any of this, I'm speculating here.

Gaurav Lochan wrote:

Show quoted text

> I've got a C# application that uses the Virtual Server COM API, and so
> based on their sample code, the first thing my application does is call
> CoInitializeSecurity with the specified parameters. I'm using
> VS2003.NET and .NET 1.1 to develop the application.
>
> This has worked fine on english systems (Win2003, Windows XP) but when
> i tried this on a chinese or a japanese system, the app gets this error
> code (0x80010119, RPC_E_TOO_LATE) from CoInitializeSecurity. I've
> searched for this and found that people have hit this problem since the
> CLR is calling CoInitializeSecurity on its own which prevents our app
> from calling it again with the correct parameters.
>
> I've seen that when i try to run my app over and over again, i hit this
> problem the first 3-4 times, but then it works. And after that, i dont
> hit the exception again !
>
> I'm trying to find the answers to the following questions:
> 1. Why am I hitting this on the international OS's only ?
> 2. Why does this happen the first 3-4 times, and then go away ?
> 3. Is there a solution for this ? I cant just catch and ignore the
> exception since i need to set the right parameters to work with Virtual
> Server's COM API.

Post Reply | This is Spam! | Mark as Spam

Other groups

Virtual PC (Mac)(3592)	Virtual PC(12844)	Virtual PC (French)(496)
Virtual Server 2005(6245)

Our Sponsors

Virtual Server 2005 Info Here!
http://www.aspdeveloper.net

Wiki

Blogs

Articles

Image galleries

File galleries

Forums

Maps

Directories

ASP Developer Network (since 1996) - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com
Copyright © 1997-2005 by BitShop, Inc. All Rights Reserved.
No content may be reproduced in any form without written permission from BitShop, Inc.
We will be honored to assist with reproduction rights on our material if you contact us.
We also can provide print articles for your magazine, private training seminars at your site, and conference presentations.
Thank you for visiting. Please bookmark our site if you found it useful!
If you wish to make a donation it will help further the development of these free resources: