Re: [cobalt-users] Frustration with FrontPage Extensions

[Will DeHaan <will@xxxxxxxxxx>]

Joseph wrote: "One particular site, I have removed totally from the
server several times...Front Page always returns the error..."

The RaQ 3 Update 2.0, http://www.cobalt.com/support/download, fixed a
bug that prevented Frontpage from being re-enabled after a site was
deleted then re-created.

Have you both installed this update?

The bug was the result of a frontpage configuration file, 

  /usr/local/frontpage/any.virtualsite.com:80.cnf

...not being deleted when the site is deleted.  When FP is enabled on
the re-created site, FP will notice that the stale configuration file
exists and will fail with a shortsighted error message.


	-- Will

Nawaf Al-Bash wrote:
> 
> Hi,
> 
> I have the same problem with the same error message. I also have around 29
> websites on Raq3i. I discovered this problem today and re-installed the site
> several times and still the same.
> 
> Nawaf Al-Bash
> Clix Clix
> 
> -----Original Message-----
> From: cobalt-users-admin@xxxxxxxxxxxxxxx
> [mailto:cobalt-users-admin@xxxxxxxxxxxxxxx]On Behalf Of Joseph Brennskag
> Sent: Monday, March 20, 2000 7:43 PM
> To: cobalt-users@xxxxxxxxxxxxxxx
> Subject: [cobalt-users] Frustration with FrontPage Extensions
> 
> Greetings!
> 
> I am having a problem which has been frustrating me for several days.  I am
> hosting a number of sites on a Raq3i (approx 30).  Nearly all of them have
> FP extensions installed. No problems.
> 
> One particular site, I have removed totally from the server several times,
> uninstalled, reinstalled many times and cannot get the front page extensions
> installed.  I repeat I have installed FP extensions successfully many, many
> times.  Front Page always returns the error that the server appears to not
> have the FP Extensions installed.  Or I get an error that "the folder isn't
> accessible.  The folder may be located on an unavailable volume or protected
> with a password.  For details see c:\windows\temp\wecerr.txt".
> 
> A review of that file indicates a standard 404 error from the web server.
> 
> I am at my wits end.
> 
> Joe Brennskag
> HardyNet