Re: WSC CreateObject fails in ASP with 0177 error Ran Out of Memory

From: noonie (n00nie_at_bigpond.com)
Date: 02/24/04 

Date: Tue, 24 Feb 2004 20:33:45 +1100

noonie wrote:
> Greetings,
>

SNIP...

> If session state is enabled on IIS 5.0 then the other instances do not
> fail and the ASP's all behave as expected for that Authenticated user.
> However if another session is started with the same user credentials
> then the 'ASP 0177 : 8007000e' error appears again and the component
> remains unusable until IIS is reset.

ADDENDUM:

Setting IIS Server-Side Debug to "on" also resolved the problem for one
of the AD connected servers but not the other. In the first case session
state was no longer needed to avoid the error message.

For the application the problem is now solved. The WSC was ditched and
the component was re-written in C++.

Using a *real* component, as a compiled DLL, solved the issues but I
still would like to get a handle on what caused the problems as WSC is
such a good prototyping tool. 

-- 
Regards,
Neale NOON
Loading