frontpage 2002 server extensions

Discussion in 'Install/Configuration' started by The new guy, May 28, 2005.

  1. The new guy

    The new guy New Member

    installed fp2002 - no problem.
    have one VH getting all the traffic.
    under vh add-ons enabled the fp extensions looked ok but, could not proceed according to instructions.
    _vti_bin was not created under VH_ROOT/html - did it manually by copying from fp install, _vti_inf.html did not exist under vh_root/html, again did it maually, but still can't get fpadmcgi.exe to execute (getting forbidden access).
    log says fp extensions started successfully...
    so much tweaking to get it going?? what am I doing wrong??
    :?
  2. mistwang

    mistwang LiteSpeed Staff

    You should not create those files manually, please remove them all.
    Turn on debug log and check error.log and stderr.log and restart the server.
  3. The new guy

    The new guy New Member

    Removed 'em all, Uninstalled the server. Reinstalled the server, reinstalled the fp extensions and tried to add the fp extensions for all vh hosts by running owsadm.exe.Below is what I got:

    LNX269:/usr/local/frontpage/version5.0/bin# ./owsadm.exe -o setadminport -p 7090 -s /opt/lsws/add-ons/frontpage/conf/httpd.conf -username admin -pw temppass1

    Starting setadminport, port: 7090.

    Error: Server configuration file "/opt/lsws/add-ons/frontpage/conf/httpd.conf" has no Port orServerRoot directive. Please check that you have the correct configuration file for your server type.

    All the files under above folder ../conf/httpd.conf, access.conf, srm.conf have 0 bytes in them - empty. :cry:
  4. mistwang

    mistwang LiteSpeed Staff

    You should not run the owsadm.exe command by yourself. :) It will be invoked by the LSWS when server restarts, a dedicated apache configuration file for that virtual host will be created under lsws/add-ons/frontpage/ directory, just make sure "domain names" is set properly from the web admin interface, you should check the error.log and stderr.log after restart.

Share This Page