03-07-06 10:54 PM
I believe path resolution is documented to be changed on Windows Server 2003
for security reasons.
I'm not certain that system32\inetsrv matters because it's not in the PATH.
ISAPI Extension runs as impersonated identity (comes from authentication -
see my blog entries in the prior response) so all your DLLs need to be
accessible to that identity.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Laco" <LSopko@1024Informatica.com> wrote in message
news:1141722850.215368.140070@z34g2000cwc.googlegroups.com...
> Thx, for respond.
>
> Nop, it is not a ISAPI fiter. It is regular ISAPI extension, Which use
> other regular dlls for its internal data processing. There is no
> problem to load ISAPI from IIS. it work fine, problem starts later,
> when loaded ISAPI need to call one regular dll ( i wrote it ) and this
> dll use third party dlls to work on images.
>
> Let me explain better. I have ISAPI: HxIMGServerISAPI.dll just
> extend IIS for WebGis procesing
> then i have HxJPGServer.dll which i use in all my programs for JPG
> management (not only web based) this dll call
> many others dlls when work with images.
>
> When i call HxIMGServerISAPI.dll, to process my request, it load
> HxJPGServer.dll. Then HxJPGServer.dll loads all other dlls to work.
>
> I wanted to put my HxJPGServer.dll with other dlls in one dir (
> different from ...\system32\intesrv) to have some order in things on my
> server. And it wan't work, only if all dlls are in ..\system32\inetsrv
> it works fine. It seems that command LoadLibrary, which i call to load
> HxJPGServer.dll dont make search in dirs which are in PATH system
> variable.
>
> laco.
>
[ Post a follow-up to this message ]
|