Re: CS0007: Unexpected common language runtime initialization error -- 'Class not registered '

From: alien2_51 (dan.billow_at_n.o.s.p.a.m.monacocoach.com)
Date: 06/10/03


Date: Tue, 10 Jun 2003 11:51:03 -0700


If you want to register your component with COM+ it must be signed with a
strong name and registered with COM+ using regsvcs

"xmax" <max@ati.com> wrote in message
news:#yqbwQ3LDHA.3088@TK2MSFTNGP10.phx.gbl...
> Hi,
>
> I've been using ASP.NET for a while now (WinXP, IIS5, .NET1.0 sp1) with no
> problems but yesterday after trying to convert one of components to a
> ServicedComponent (COM+) I started getting this error when trying to
> navigate to any ASP.NET page:
>
> CS0007: Unexpected common language runtime initialization error -- 'Class
> not registered '
>
> Not only did ASP.NET stop working regular .asp pages starting faulting as
> well with DCOM/COM+ errors being logged in Event Log. After uninstalling
and
> re-installing both ASP.NET and IIS the problem was still there. After much
> browsing I found the fix for regular .ASP problem
> (http://www.iisfaq.com/default.aspx?View=A318) which advised to set up
IUSR_
> and IWAM_ users as administrators and run SYNCIWAM script. It's not clear
> what exactly is wrong and being fixed but it worked fine for .ASP pages.
> ASP.NET pages still weren't working and whenever I ran APSNET_REGIIS to
> restore ASP.NET IIS settings it blew away the fix for regular .ASP.
>
> After investigating further I found out that running the same compiler
> (CSC.EXE) command line that is given in the ASP.NET error manually works
> just fine and a binary is produced. This as well as the nature of the fix
> for regular .ASP makes me think that for whatever reason the process that
> runs CSC.EXE does not permisisons either to read the registry or load COM
> classes. I've added ASPNET user to Administrators group and granted full
> permissions on HKEY_CLASSES_ROOT and HKEY_LOCAL_MACHINE but it doesn'
help.
>
> My question is:
> - Is there an equivalent of SYNCIWAM script that can do the same for
ASPNET
> user? If it worked for .ASP pages it just might work for ASP.NET. Also if
> someone can explain to me what exactly SYNCIWAM does it would be helpful a
s
> well (output from the script is at the end of the post).
>
> If anybody has any ideas on how this may be solved please post as well.
>
> Thanks,
> Max
>
> SYNCIWAM output:
>
> Microsoft (R) Windows Script Host Version 5.6
> Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
>
> IIS Applications Defined:
> Name, AppIsolated, Package ID
> w3svc, 0, {3D14228C-FBE1-11d0-995D-00C04FD919C1}
> ROOT, 2,
> IISHelp, 2,
> changelog, 0,
>
> Out of process applications defined:
> Count: 1
> {3D14228D-FBE1-11d0-995D-00C04FD919C1}
>
> Updating Applications:
> Name: IIS Out-Of-Process Pooled Applications Key:
> {3D14228D-FBE1-11D0-995D-00C04FD919C1}
>
>
>
>



Relevant Pages

  • Re: ASP.NET 2.0 control into classic asp?
    ... You have to register the DLL, then ASP uses it as a regular COM object. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: [OT] Thats a novel concept.
    ... register are regular users. ... but absolutely no indication of how much ... many users habits are only ...
    (uk.rec.motorcycles)
  • Re: Register .NET Dll for classic asp
    ... COM interop" to true. ... component not usable in ASP"); ... Override Uninstall: ... what would I do to register them? ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: .Net Assembly from Classic ASP and VB6
    ... You went right with the "Register with COM Interop" option. ... This is, of course, one of the symptoms of "DLL Hell" that .NET ... I'm not sure about why your ASP page couldn't find your assembly after ...
    (microsoft.public.dotnet.framework.interop)
  • RE: Call ASP.NET DLL from ASP 3.0 - Newbie
    ... ASP 3.0 would have to call the .NET component via a COM callable wrapper ... you would have to register the type library for the .NET ... >will not install a 3rd party COM component, ... >WITHOUT registering the .NET DLL? ...
    (microsoft.public.dotnet.framework.aspnet)