Re: Client error code

Justin/Evan,

Thought I'd respond to both mails at once. It turned out to be the LANSA
configuration that hadn't been set up properly, but this has been corrected
and everything now seems to be fine.

Thankyou both very much for your help.

Adam Driver
Technical Consultant
Kaz Computer Services
Level 7
66 Wentworth Ave
Sydney NSW 2010
Australia
Phone: +61 2 9844 0386
Fax: +61 2 9844 0333

A division of Kaz Group Limited - visit our website at www.kaz.com.au




Message: 2
From: "Justin & Michelle Houchin" <jhouchin9@charter.net>
To: <web400@midrange.com>
Subject: Re: [WEB400] Client error code
Date: Sun, 14 Apr 2002 13:38:16 -0500
Reply-To: web400@midrange.com

Do you have a map, pass statement before your exec statement, this would
explain why your CGI's do not work. but if you cannot pull up your welcome
page, I still think there is a problem with the map statement

Justin







Message: 3
Date: Mon, 15 Apr 2002 07:41:14 +1200
From: Evan Harris <spanner@ihug.co.nz>
Subject: Re: [WEB400] Client error code
To: web400@midrange.com
Reply-To: web400@midrange.com

Hi Adam

do you have any logging running that will help you identify whats happening
? The Map/pass suggestion as a place to look elsewhere sounds likely. I am
not proficient enough with the syntax to give you an example off the top of
my head and I'm at home right now :)

You should also probably go back and verify the host name/IP address you
have spcified in your server config and check that you have an entry  in
your DNS or hosts table to enable you to find it. You may be able to check
that the system is listening where you expect it to be by having a browse
through the NETSTAT option 3 output.

Also, be aware that HTTP the server might require the case of file name to
match. Make sure the extension matches as well.

If you strip your config file down to absolute basics this may help isolate
the problem. If you post it here someone will probably be able to diagnose
the problem for you.

If you concentrate on getting a page you know is in your root directory to
display (like the index page) even if you have to actually specify the name
in your browser request then once that is working you can knock off the
other problems one by one :)

I'm not sure about the LANSA user profile - it strikes me that for just
HTTP this should not be an issue, although I guess it could mean that if
there is an authoring tool then it will have problems accessing/overwriting
the file. It would seem to have more relevence when you get to doing CGI.

Sounds like it would be a good idea at this point to crack the LANSA
manuals at least. For whatyou need to do the V4R5 manuals for the HTTP
Serve should be OK (corrections accepted :))_

Good luck

Regards
Evan Harris