IIS Bug and PATH

[Alhambra Eidos Development]

Hi all,

in this post, http://forums.asp.net/t/939729.aspx,

there is this comment:


IIS has a bug!!

If you are trying to use IBM.Data.Informix (Client 2.81 TC3, 2.9, 3.5, etc.)
from IIS, and you still have this problem, I have a solution. I found that
IIS 5.1 has a bug!!. IIS cannot read the entire PATH environment variable if
it’s too long (my PATH has 1364 characters). So if your informix dir is near
the end of your PATH and your PATH is too long, IIS will never read your
informix dir ("C:\Program Files\IBM\Informix\Client-SDK\bin"). Just put your
informix dir at the beginning of your PATH variable, and very important
execute an "iisreset" and the issue will gone away. I don't know if this bug
remains in IIS 6.0 or later. But you can try this.

If I'm correct this will help to solve other problems when you're trying to
access unamanaged dlls from IIS:
"Unable to load DLL 'foo.dll': The specified module could not be found."

====================

any comments about it ? in IIS 6.0 , MS dont' solve this error ?? and IIS
7.0 ??

any solutions, better solutions than change location of a dir in the PATH ??

Thanks in advanced.

Greetings.

 

[Patrice]

According to http://www.lindersoft.com/forums/showthread.php?p=4978 the
limit was 1024. So :
- either this is an OS dependent limit and you'll have this as well in other
programs
- or it has been hard coded for this limit (in which case trying to go under
1024 should allow to be on the safe side).

If I remember the search path could be also set using the registry (not sure
if it the same mechanism than PATH or if it something that comes in addition
in which case you could move some path from the environment variable to the
registry).

--
Patrice

"Alhambra Eidos Development"
<[email protected]> a écrit dans le message
de groupe de discussion :
(e-mail address removed)...