Argh - File not found (80070002) error on DLL object instantiation!

[Henry Rollins]

This is driving me nuts.

I have created a Class Assembly in .NET C# which is to be used by
traditional ASP pages. I registered it just fine with the regASM command
and it work - about 2/3 of the time. The rest of the time I launch the
site and the following error is generated:

'80070002'
And that's it. No name of which file isn't found, etc. The line on which
this occurs is the Server.Createobject command - so I'm assuming, of
course, that the DLL is what ASP can't find. I'm moved it around and re-
registered it in several locations - system32, system, windows, etc. The
system could NEVER find the dll when it was placed in the applications
"bin" directory.

Is this correct? What the hell is going on? This problem didn't show
until we moved to production and the inconsitency of its appearance is
infuriating, as is the nearly complete lack of error reporting.

Anyone who knows what is happening here, please help!!

[Dan C]

I just ran in to this problem when we moved some sites to
a different server. spent a while looking for answers
until I realized that I had just forgotten to add the
assembly to the "Assembly Cache".

it may not be the same problem, I was getting the error
every time.

-----Original Message-----
This is driving me nuts.

I have created a Class Assembly in .NET C# which is to be used bytraditional ASP pages. I registered it just fine with the regASM commandand it work - about 2/3 of the time. The rest of the time I launch thesite and the following error is generated:

'80070002'
And that's it. No name of which file isn't found, etc. The line on whichthis occurs is the Server.Createobject command - so I'm assuming, ofcourse, that the DLL is what ASP can't find. I'm moved it around and re-registered it in several locations - system32, system, windows, etc. Thesystem could NEVER find the dll when it was placed in the applications"bin" directory.

Is this correct? What the hell is going on? This problem didn't showuntil we moved to production and the inconsitency of its appearance isinfuriating, as is the nearly complete lack of error reporting.
Anyone who knows what is happening here, please help!!
.