RE: HTTP server instance does not start

["JDE Temp 1" <JDETEMP1@xxxxxxxxxxxxx>]

Hello Brad, I do have the Port 80 in my HTTP config file. Please take a note 
that my *ADMIN can be started. Could this cause due to the fact that my TCP/IP 
environment is "Intranet", and we do not use an IP address yet by an ISP.

Thanks
Nimal

>>> "Stone, Brad V (TC)" <bvstone@taylorcorp.com> 03/21/00 03:18PM >>>
It seems you are specifying port 0 in your HTTP config.  Change this to 80
or any number above 1024.

Should look like this:
Port 80

Brad

-----Original Message-----
From: JDE Temp 1 [mailto:JDETEMP1@legacyptr.com] 
Sent: Tuesday, March 21, 2000 2:33 PM
To: MIDRANGE-L@midrange.com 
Subject: HTTP server instance does not start


Hello, 

Please help with following HTTP server instance issue.

We have an AS/400 720 with V4R4. We configured a server instance and trying
to start it. We have the following problem reported in the QSYSOPR message
queue. However, we do not have the server instance started. Please note that
*ADMIN server can be started. I also could use the *ADMIN server over the
browser.

We also have disabled the SSL keywords with "off" switch.

===================
Message ID . . . . . . :   TCP7422       Severity . . . . . . . :   10

 Message type . . . . . :   Information

 Date sent  . . . . . . :   03/20/00      Time sent  . . . . . . :
19:55:51   
 

 Message . . . . :   Failed to bind and listen on port 0.

 Cause . . . . . :   The server was not able to get ownership of the
specified  
   TCP port.

 Recovery  . . . :   Make the port available for use or try starting the
server 
   using a port other than port 0. If the AC1, AC2 or AC3 product is
installed  
   and ssl mode is on verify that the ssl port is not the same as the http

   port.


====================
 Message ID . . . . . . :   TCP7402       Severity . . . . . . . :   40

 Message type . . . . . :   Diagnostic

 Date sent  . . . . . . :   03/20/00      Time sent  . . . . . . :
19:55:51  
 

 Message . . . . :   HTTP server unable to start. Initialization errors were

   detected.

 Cause . . . . . :   The server detected initialization errors during
startup. 
 Recovery  . . . :   Check the previous messages to determine the specific

   error. Correct the error and try starting the server again.          

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com 
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com 
+---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---