Bevan
> The search continues.... :)
did you nail this one yet?
if not here is another partially formed dim idea:
this problem has the odd feature that running
the programs first interactively as administrator
"latches" things so that they'll work.
is it possible that running the app from a logged
on session loads different DLLs than running
it via IIS impersonating the IUSR_ anonymous
user?
some kind of difference in "path" so that the
"first" load of the app determines which DLLs
you get? And once they're loaded, subsequent
loads reuse the already loaded ones?
it's not obvious to me what "DLL path" is in
effect when IIS runs an application - it doesn't
actually "log on" as the IUSR_ user - I think
it just uses it's ACL to access stuff.
i'd be tempted to try a few tests - like:
1. does running the app interactively first
(as IUSR_xxx instead of administrator) ALSO
"fix" the problem?
2. does changing the anonymous IIS user
to "administrator" (temporarily - just as
a test not forever) continue to fail in
same way?
sorry this isn't a more coherent attack ...
-ns
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
