inetserver asp components:
Greetings,
This seems to be the right group to ask this question however if anyone
can suggest a more appropriate group then please do so.
I have a script component that serves to proxy data from SQL Server
which works fine under Windows XP and Windows 2000 Server when attached
to an NT4 Domain. The component is called by several pages displayed in
a frame-set on the client (Internet Explorer only). The site uses BASIC
Authentication and NTFS permissions are used on the files and folders.
The same application, when installed on IIS on Windows 2000 Server
attached to an Active Directory Domain exhibits the following symptoms...
IIS session state turned off:
The component appears to execute successfully once, then all other
instances fail with the following error:-
Server object error 'ASP 0177 : 8007000e'
Server.CreateObject Failed
/getreport.asp, line 24
Ran out of memory
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.
"line 24" above contains only the call to Server.CreateObject which
instantiates the component. If I remove all of the component's code,
except the headers which describe it, the result is the same. Other
pages which use the component also fail on the same call to CreateObject.
Another script component, which does not connect to the database but
does create a recordset object, fails in exactly the same way. My gut
feeling is that we have a permissions issue but I can't prove it and am
at a loss as to how to track this down.
Please, does anyone have any insight that would help me to resolve this
issue?
--
Regards,
