all groups > dotnet distributed apps > july 2006 >
You're in the

dotnet distributed apps

group:

"Couldn't install assembly as a COM+ component" Error Message


"Couldn't install assembly as a COM+ component" Error Message OliviuG
7/3/2006 3:21:02 PM
dotnet distributed apps:
We use serviced components and we've changed the transaction settings on the
componets from [TransactionAttribute(TransactionOption.Supported)] to
[TransactionAttribute(TransactionOption.RequiresNew,
Isolation=TransactionIsolationLevel.ReadCommitted)]
..

We get the error I mentioned in the subject when we install the new version
of the components, but not in all test environments.

Is there an extra assemblyn depency which we've introduced.
RE: "Couldn't install assembly as a COM+ component" Error Message OliviuG
7/3/2006 3:29:01 PM
Just to clairy the issue is reproducing on some test environments, while it
works on others.

[quoted text, click to view]
RE: "Couldn't install assembly as a COM+ component" Error Message OliviuG
7/4/2006 10:36:02 AM
Thanks for the reply. Found the issue to be caused by the presence of the
..net 2.0 on the machine.

The installer was registering the assembly in the com+ catalog using the
System.EnterpriseServices.RegistrationHelper COM objects(from vbscript), so
it picking up the 2.0 version.

Thanks.

[quoted text, click to view]
RE: "Couldn't install assembly as a COM+ component" Error Message Michael Nemtsev
7/4/2006 5:26:05 PM
Hello OliviuG,

Does error arise only during install? Does it Server component? Strong named?
VS 2005?

O> Just to clairy the issue is reproducing on some test environments,
O> while it works on others.
O>
[quoted text, click to view]
---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsch

AddThis Social Bookmark Button