«

This is not a pure Perl problem but is to do with the running of Perl
on IIS.

I now have two scripts that run without errors (I'm using strict) but,
for some reason, will not display the simple 'Done!' page built into
the script. Instead the server gives me 'The page cannot be
displayed'.

I have run it on a local IIS set up with no problems but on the main
server I continue to get this error. As I have no error messages other
than page not displayed I'm not sure what I can tweak to get it to
work. Maybe there's an error log I could look at?

I need to get a HTML page displayed at the end so I can then do futher
steps but so far cannot.

I'm running ActiveState Perl 5.8 with IIS 5 on a Windows 2000 box.

Any help appreciated.

Stew Dean

(stew dean) wrote in
news: om:

> This is not a pure Perl problem but is to do with the running of Perl
> on IIS.
>
> I now have two scripts that run without errors (I'm using strict) but,
> for some reason, will not display the simple 'Done!' page built into
> the script. Instead the server gives me 'The page cannot be
> displayed'.

And we are supposed to divine what is going on without seeing a line of
code?

> I have run it on a local IIS set up with no problems but on the main
> server I continue to get this error. As I have no error messages other
> than page not displayed I'm not sure what I can tweak to get it to
> work. Maybe there's an error log I could look at?

There probably is. Why don't you look at it?

> I need to get a HTML page displayed at the end so I can then do futher
> steps but so far cannot.

....

> Any help appreciated.

To get any help, you'll need top provide some information. Also, make
sure this is not a web server configuration or CGI issue. Please refer to
the posting guidelines for this group at

http://mail.augustmail.com/~tadmc/cl...uidelines.html

Without at least seeing a short example script that illustrates the
problem you are having, it is impossible to say anything.

Sinan.

On 21 Oct 2003 03:53:24 -0700
(stew dean) wrote:

> This is not a pure Perl problem but is to do with the running of
> Perl on IIS.
>
> I now have two scripts that run without errors (I'm using strict)
> but, for some reason, will not display the simple 'Done!' page built
> into the script. Instead the server gives me 'The page cannot be
> displayed'.
>
> I have run it on a local IIS set up with no problems but on the main
> server I continue to get this error. As I have no error messages
> other than page not displayed I'm not sure what I can tweak to get
> it to work. Maybe there's an error log I could look at?

This questions begs one to ask - "Did you read the documentation for
IIS?". Errors from your script _should_ be there for you to examine.

>
> I need to get a HTML page displayed at the end so I can then do
> futher steps but so far cannot.
>
> I'm running ActiveState Perl 5.8 with IIS 5 on a Windows 2000 box.
>
> Any help appreciated.

Please start by RTM Also, run the script at the command line.
Any errors should show there - and be identical (with all things being
equal) to the error messages in the error log.

HTH

--
Jim

Copyright notice: all code written by the author in this post is
released under the GPL. http://www.gnu.org/licenses/gpl.txt
for more information.

a fortune quote ...
In English, every word can be verbed. Would that it were so in
<our programming languages.

(stew dean) wrote in message news:<. com>...
> I now have two scripts that run without errors (I'm using strict) but,
> for some reason, will not display the simple 'Done!' page built into
> the script. Instead the server gives me 'The page cannot be
> displayed'.

Perhaps the server is not configured to run scripts? Or, if you know
that the scripts are running, the page won't display, you must have a
problem with formatting (maybe you're not sending the "text/html"
prologue?).

In that case, try shift-clicking the link that launches the scripts,
so you can save the output to a file, then peruse the file. Name it
with a .html extension and try to load it directly.

"A. Sinan Unur" <> wrote in message news:<Xns941B70CB78211asu1cornelledu@132.236.56.8> ...
> (stew dean) wrote in
> news: om:
>
> > This is not a pure Perl problem but is to do with the running of Perl
> > on IIS.
> >
> > I now have two scripts that run without errors (I'm using strict) but,
> > for some reason, will not display the simple 'Done!' page built into
> > the script. Instead the server gives me 'The page cannot be
> > displayed'.
>
> And we are supposed to divine what is going on without seeing a line of
> code?

The code it's self, although clunky no doubt compared to the abilities
of many, works fine. It's processing a large XML file and spitting out
webpages. With a smaller XML file it displays Done - with a larger one
it apears to time out. I've checked it for errors by putting a dummy
error in there but it only shows up that error.


> > I have run it on a local IIS set up with no problems but on the main
> > server I continue to get this error. As I have no error messages other
> > than page not displayed I'm not sure what I can tweak to get it to
> > work. Maybe there's an error log I could look at?
>
> There probably is. Why don't you look at it?

I don't know if there is an error log or where it would be if there
was. Any suggestions suggested.

> > I need to get a HTML page displayed at the end so I can then do futher
> > steps but so far cannot.
>
> ...
>
> > Any help appreciated.
>
> To get any help, you'll need top provide some information. Also, make
> sure this is not a web server configuration or CGI issue. Please refer to
> the posting guidelines for this group at
>
> http://mail.augustmail.com/~tadmc/cl...uidelines.html
>
> Without at least seeing a short example script that illustrates the
> problem you are having, it is impossible to say anything.

The script is fine. I have many scripts running quite happily except
for the two hardest working scripts, both are fine when you give them
a short XML file but large ones cause problems. The server is hefty
enough to handle them (memory etc is all fine) so I'm thinking it's a
set up issue with IIS.

I'm looking to see if anyone else has a similair problem.

Stew Dean

James Willmore <> wrote in message news:< lphia.net>...
> On 21 Oct 2003 03:53:24 -0700
> (stew dean) wrote:
>
> > This is not a pure Perl problem but is to do with the running of
> > Perl on IIS.
> >
> > I now have two scripts that run without errors (I'm using strict)
> > but, for some reason, will not display the simple 'Done!' page built
> > into the script. Instead the server gives me 'The page cannot be
> > displayed'.
> >
> > I have run it on a local IIS set up with no problems but on the main
> > server I continue to get this error. As I have no error messages
> > other than page not displayed I'm not sure what I can tweak to get
> > it to work. Maybe there's an error log I could look at?
>
> This questions begs one to ask - "Did you read the documentation for
> IIS?". Errors from your script _should_ be there for you to examine.

The errors for the script are not going to be in the documentation. I
have a rather hefty manual I could spend a few weeks reading but I
very much doubt it will resolve my issue.

> >
> > I need to get a HTML page displayed at the end so I can then do
> > futher steps but so far cannot.
> >
> > I'm running ActiveState Perl 5.8 with IIS 5 on a Windows 2000 box.
> >
> > Any help appreciated.
>
> Please start by RTM Also, run the script at the command line.
> Any errors should show there - and be identical (with all things being
> equal) to the error messages in the error log.

When it comes down to the combination of technolgies i'm using the
manuals don't cut it. The perl ones are aimed at Unix users and the
IIS help files don't (help that is). I have some heft books on IIS
and, quite frankly, it's a soul destoying paper chase form tech term
to tech term.

I've been online for about nine years now - the interweb superexpress
freeway always delivers answers that dead tree media often cannot. I
wouldnt ask if it the solution was in the pile of vegetable cells on
my desk.

Stew Dean



>
> HTH
>
> --
> Jim
>
> Copyright notice: all code written by the author in this post is
> released under the GPL. http://www.gnu.org/licenses/gpl.txt
> for more information.
>
> a fortune quote ...
> In English, every word can be verbed. Would that it were so in
> <our programming languages.

(stew dean) wrote in
news: om:

> James Willmore <> wrote in message
> news:< lphia.net>...
>> On 21 Oct 2003 03:53:24 -0700
>> (stew dean) wrote:
>>
>> > This is not a pure Perl problem but is to do with the running of
>> > Perl on IIS.
>> >
>> > I now have two scripts that run without errors (I'm using strict)
>> > but, for some reason, will not display the simple 'Done!' page
>> > built into the script. Instead the server gives me 'The page cannot
>> > be displayed'.
>> >
>> > I have run it on a local IIS set up with no problems but on the
>> > main server I continue to get this error. As I have no error
>> > messages other than page not displayed I'm not sure what I can
>> > tweak to get it to work. Maybe there's an error log I could look
>> > at?
>>
>> This questions begs one to ask - "Did you read the documentation for
>> IIS?". Errors from your script _should_ be there for you to examine.
>
> The errors for the script are not going to be in the documentation. I
> have a rather hefty manual I could spend a few weeks reading but I
> very much doubt it will resolve my issue.

The manual would tell you where to find the error logs so you can find
out what is wrong, and maybe give us a clue. That is not too much to ask.

> I've been online for about nine years now - the interweb superexpress
> freeway always delivers answers that dead tree media often cannot. I
> wouldnt ask if it the solution was in the pile of vegetable cells on
> my desk.

So, you cannot be bothered to check the error logs, and tell us what is
in there, but somehow we are supposed to divine what is going on ...
Interesting attitude.

In the time you took to type up all these replies as to why you won't
check the error logs, you could have checked the error logs, and posted
some information that could have been helpful in figuring out the
problem.

--
A. Sinan Unur

Remove dashes for address
Spam bait: private.php?do=newpm&u=

On 22 Oct 2003 04:27:54 -0700
(stew dean) wrote:
> James Willmore <> wrote in message
> news:< lphia.net>...
> > On 21 Oct 2003 03:53:24 -0700
> > (stew dean) wrote:
<snip>

What happened when you ran the script at the command line? There is
_little_ difference between running the script on the command line and
running it through the web server - especially if you use the CGI
module (hint - '-debug').

Where is the code you speak of? You have yet to post any offending
code.

The documentation for _Perl_ (specifically, perlfaq9) gives a tip or
two on debugging a buggy Perl CGI script.

And yes, I was insulting to you. Sorry for the transgression. By the
same token, if you run a web server, you should at least know where
the logs are located - or you shouldn't be a web server admin or even
touch a web server for development purposes. I may not agree with
some of the admins or the developers where I work, but at least they
know where the logs are located

For the time being - and to give a hint - try using CGI::Carp (just
not in a production environment).

HTH and have a nice day

--
Jim

Copyright notice: all code written by the author in this post is
released under the GPL. http://www.gnu.org/licenses/gpl.txt
for more information.

a fortune quote ...
People usually get what's coming to them ... unless it's been
<mailed.

(stew dean) wrote:

: The code it's self, although clunky no doubt compared to the abilities
: of many, works fine.

Then the Perl problem has been solved. Yay team!

: I'm thinking it's a set up issue with IIS.

You are probably right.

Since Perl is not IIS, an IIS-oriented newsgroup would be a more
appropriate place to seek help than a Perl newsgroup. The readers there
will at least be able to guide you to the location of the server's error
log.

Right now, the only thing known about the error is that it exists. That
is not enough information to begin diagnosis.

"A. Sinan Unur" <> wrote in message news:<Xns941C6F2D4438Easu1cornelledu@132.236.56.8> ...
> (stew dean) wrote in
> news: om:
>
> > James Willmore <> wrote in message
> > news:< lphia.net>...
> >> On 21 Oct 2003 03:53:24 -0700
> >> (stew dean) wrote:
> >>
> >> > This is not a pure Perl problem but is to do with the running of
> >> > Perl on IIS.
> >> >
> >> > I now have two scripts that run without errors (I'm using strict)
> >> > but, for some reason, will not display the simple 'Done!' page
> >> > built into the script. Instead the server gives me 'The page cannot
> >> > be displayed'.
> >> >
> >> > I have run it on a local IIS set up with no problems but on the
> >> > main server I continue to get this error. As I have no error
> >> > messages other than page not displayed I'm not sure what I can
> >> > tweak to get it to work. Maybe there's an error log I could look
> >> > at?
> >>
> >> This questions begs one to ask - "Did you read the documentation for
> >> IIS?". Errors from your script _should_ be there for you to examine.
> >
> > The errors for the script are not going to be in the documentation. I
> > have a rather hefty manual I could spend a few weeks reading but I
> > very much doubt it will resolve my issue.
>
> The manual would tell you where to find the error logs so you can find
> out what is wrong, and maybe give us a clue. That is not too much to ask.

That's my problem - the script is producing no errors as in the script
if fine, it runs without producing an error, that's why I think it's a
server related problem.

>
> > I've been online for about nine years now - the interweb superexpress
> > freeway always delivers answers that dead tree media often cannot. I
> > wouldnt ask if it the solution was in the pile of vegetable cells on
> > my desk.
>
> So, you cannot be bothered to check the error logs, and tell us what is
> in there, but somehow we are supposed to divine what is going on ...
> Interesting attitude.

I don't even know if there is an error log.

> In the time you took to type up all these replies as to why you won't
> check the error logs, you could have checked the error logs, and posted
> some information that could have been helpful in figuring out the
> problem.

So you know where the error log is then? Look I know you want to help
but you're not helping me.

I'm now going to try and find an error log that may or may not exist
(I have already spent an hour trying to find if one exists).

Stew Dean