Did you restart IIS. With traditional COM, you have to restart the process,
as an earlier attempted call will lock things up. In some instances, you
even have to restart the entire service.

Signature
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
Subscribe to my blog
http://gregorybeamer.spaces.live.com/lists/feed.rss
or just read it:
http://gregorybeamer.spaces.live.com/
*************************************************
| Think outside the box!
*************************************************
>I might be in the wrong forum for this question, as it deals with ASP and
> .NET dll as opposed with strickly ASP.NET.
[quoted text clipped - 23 lines]
>
> Any help is greatly appreciated.
T McDonald - 27 Mar 2008 13:15 GMT
Thanks for the response.
I did restart both. No success. I notice that when I drop my test
application I built with the dll on the remote server, it cannot find the
dll's contents either.
I've also followed MS suggestions about creating a COM from here:
http://msdn2.microsoft.com/en-us/library/x66s8zcd(VS.80).aspx without
improved results. The dll is written in VB.Net if that makes any difference.
Again, any further insight is appreciated.
> Did you restart IIS. With traditional COM, you have to restart the process,
> as an earlier attempted call will lock things up. In some instances, you
[quoted text clipped - 30 lines]
> >
> > Any help is greatly appreciated.