Re: Error starting HTTP *ADMIN

We had a similar problem after doing an OS upgrade.  Installing the HTTP PTF group fixed this issue.  Those PTFs are not included in the regular PTF upgrade group.

I'd suggest getting current on HTTP PTFs first.

Rich Loeber
Kisco Information Systems
http://www.kisco.com[1]
-------------------------

Quoting Tom Hightower <tomh@xxxxxxxxxxx>:

I'm trying to start up the HTTP server instance *ADMIN and I'm getting this
error in the QEZJOBLOG:

From module . . . . . . . . :   QZSRSNDM

  From procedure  . . . . . . :   sendMessageToJobLog_CCSID

  Statement . . . . . . . . . :   27

  To module . . . . . . . . . :   MOD_SO

  To procedure  . . . . . . . :   load_module

  Statement . . . . . . . . . :   57

  Message . . . . :   The specified HTTP Server module cannot be added with

    LoadModule.

  Cause . . . . . :   The HTTP Server module

    /QSYS.LIB/QSYSDIR.LIB/QSVTAP22.SRVPGM specified on the LoadModule
directive
    cannot be added into the server.  The module name may be misspelled or

    another error may have occured while attempting to load the module.  For

    more information, see the previous messages in the job log. Recovery  . .
.
    :   This message may be a result of attempting to load a module that is
not
    compatible with the version of the HTTP Server (powered by Apache)
currently
    running on the system.  The version of the HTTP Server (powered by
Apache)
    is 20051115 . Contact the provider of the module for service. Technical

    description . . . . . . . . :   If you are the developer of the module,
look
    at member AP_RELEASE in file QHTTPSVR/H on the system the module was
built
    on.  The AP_RELEASE member contains the version number used by the
module.
    If the version number does not match the version of the HTTP Server
(powered
    by Apache), rebuild the module with the appropriate version of the header

    file. After performing the appropriate recovery, start the server again.


In the AP_RELEASE member, I see this:

/*-------------------------------------------------------------------*/
/* HISTORY:                                                          */
/*                                                                   */
/*                                                                   */
/* Change Activity:                                                  */
/*                                                                   */
/* CFD List:                                                         */
/*                                                                   */
/*   FLAG REASON       LEVEL DATE    PGMR     CHANGE DESCRIPTION     */
/*   ---- ------------ ----- ------- -------- ---------------------- */
/*   $A0= P9948595     4P50  010611  ROCH     New include            */
/*   $A1= P9B26115     6D10  061406  ROCH     Apache 2.2             */
/*   $B1= P9C39619     6P10  040109  ROCH     Apache 2.2.11          */
/*                                                                   */
/* End CFD List.                                                     */
/* End Change Activity.                                              */
/*-------------------------------------------------------------------*/


System software-wise, all I've ever done is download/install PTFs. Could a
PTF have mucked things up?  How do I go about getting *ADMIN instance to
startup?

Thanks!
TomH

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Links:
------
[1] http://www.kisco.com