| View previous topic :: View next topic |
| Author |
Message |
Mark Horrocks Guest
|
Posted: Mon Aug 01, 2005 5:27 am Post subject: windows server 2003 and isapi |
|
|
one of my customers is trying to install an app on win 2003 server but can't
get it to work
it runs a web broker isapi connecting to an app server exe and interbase.
IIS returns a 404 but it seems that the path is correct and the app
execution permissions are set to scripts and executibles. this app works
fine on an xp server. any ideas on what is wrong? is IIS 6 an issue here?
Mark
|
|
| Back to top |
|
 |
John Hair Guest
|
Posted: Tue Aug 02, 2005 11:28 am Post subject: Re: windows server 2003 and isapi |
|
|
Hi Mark,
| Quote: | one of my customers is trying to install an app on win 2003 server but
can't
get it to work
it runs a web broker isapi connecting to an app server exe and interbase.
IIS returns a 404 but it seems that the path is correct and the app
execution permissions are set to scripts and executibles. this app works
fine on an xp server. any ideas on what is wrong? is IIS 6 an issue here?
|
You have problably already tried this, but just in case in IIS have you
checked that Web Service Extensions that All Unknown ISAPI Extensions is set
to Allowed?
Cheers
John Hair
|
|
| Back to top |
|
 |
Mark Horrocks Guest
|
Posted: Tue Aug 02, 2005 12:30 pm Post subject: Re: windows server 2003 and isapi |
|
|
Thanks John,
This could be it, I did not know about this as I had not ever used IIS 6. I
wonder if there are any problems using IIS 6 with Windows XP?
Mark
"John Hair" <john.hair (AT) dsystems (DOT) co.uk.x> wrote
| Quote: | Hi Mark,
one of my customers is trying to install an app on win 2003 server but
can't
get it to work
it runs a web broker isapi connecting to an app server exe and interbase.
IIS returns a 404 but it seems that the path is correct and the app
execution permissions are set to scripts and executibles. this app works
fine on an xp server. any ideas on what is wrong? is IIS 6 an issue here?
You have problably already tried this, but just in case in IIS have you
checked that Web Service Extensions that All Unknown ISAPI Extensions is
set
to Allowed?
Cheers
John Hair
|
|
|
| Back to top |
|
 |
Mark Horrocks Guest
|
Posted: Tue Aug 02, 2005 12:59 pm Post subject: Re: windows server 2003 and isapi |
|
|
I use InternetExpress pages extensively in my web broker app and Microsoft
documentation states that relative paths are rejected by IIS 6 by default.
Does anyone know if there is a way round this?
|
|
| Back to top |
|
 |
Adge Guest
|
Posted: Tue Aug 02, 2005 6:13 pm Post subject: Re: windows server 2003 and isapi |
|
|
We had a problem with II6 and paths and got around it by using the full path
for all the links and redirects
/cgi-bin/mydll.dll/mypath
instead of /mypath
in the webpages served by the ISAPI we did the same for any links back to
the isapi
HTH
Adge
"Mark Horrocks" <markhorrocks@no spam sportdata.com.au> wrote
| Quote: | I use InternetExpress pages extensively in my web broker app and Microsoft
documentation states that relative paths are rejected by IIS 6 by default.
Does anyone know if there is a way round this?
|
|
|
| Back to top |
|
 |
Mark Horrocks Guest
|
Posted: Sat Aug 06, 2005 3:50 am Post subject: Re: windows server 2003 and isapi |
|
|
"Adge" <me (AT) nospam (DOT) com> wrote
| Quote: | We had a problem with II6 and paths and got around it by using the full
path
for all the links and redirects
That's what is says in the Microsoft Documentation but I need to distribute |
my app to customers using it on a network where I don't know the install
path. The app uses over 200 pages and has thousands of relative links for
internet express scripts, images, style sheet, custom javascripts, etc. I
think even some of the javascripts I didn't write have relative links. How
can I change all of this dynamically? Maybe I can put tags in every page at
the ../ and repalce them with the full path which my isapi gets anyway.
Would this be too extreme? Good palnning for IIS 6?
Mark
|
|
| Back to top |
|
 |
|