Re: [cobalt-users] Re: Raq2- frontpage 2000.. and weak connection

["Cobalt-Canada" <info@xxxxxxxxxxxxxxxxx>]

----- Original Message -----
From: "Ziad Sidawi" <ziad@xxxxxxxx>
Sent: Saturday, March 24, 2001 8:08 PM
Subject: [cobalt-users] Re: Raq2- frontpage 2000.. and weak connection


> We have a dedicated Raq2 with FP extensions used by one customer
> that uploads every night a 20 MB newspaper (etc.)
> ...every 3 or 4 months while the connection is not that good.. or if
> disconnected during trasnmission- at a certain point... then the
extensions
> on the Raq2 becomes corrupt.
> We usually wait like 30 minutes then things get ok..
> However, at one time.. the 30 minute magic did not work out..
> My question is 2 folds
>
> 1- if the site has frontpage extensions.. and 40 user accounts... if you
> delete the frontpage extensions, and then re-install them (using the web
> interface to do so) does it effect the user accounts and their emails?
>
> 2- if you telnet to the machine.. are there any commands to fix/check or
> rebuild the frontpage extensions.
>
> Ziad
>

Hi Ziad

If you disable the FrontPage extensions for a virtual site on a RaQ 4i (I
assume it is the same on a RaQ 2) and then re-enable them, the site default
userID will be "webmaster" with whatever password you specified. Any other
userIDs that had been created (by FrontPage... not on the RaQ) for the main
web would have disappeared. You would have to create them again if they were
needed.

However, if you are referring to virtual site users, they should still
exist. As long as you don't delete a virtual site, the users and their email
should be intact. I am not sure what would happen if those site users also
had FrontPage enabled for their "sub-webs" (/users/name-of-user/web) - I
don't know if you would have to go back in and re-enable FrontPage for those
users.

If a user is publishing their site and the process is interrupted, they may
not be able to publish again until someone (you or the client) FTPd in to
the server and deletes the file _vti_pvt/service.lck   If they try and
publish and get "web busy or cannot open" then the service.lck file should
be deleted.

If there is only one FrontPage userID (webmaster is the default on the 4i)
then it should be a painless operation to just disable FrontPage for the
site (on a 4i) and then re-enable it and enter the webmaster's password. If
there are a number of FrontPage userID's (created by FrontPage... not in the
RaQ GUI) it would be a nuisance to have to go and create them all again on
the server. Even if you made note of the userID's before you disabled the
FrontPage extensions, you would still need all their passwords to enter them
again unless you just created new FrontPage passwords, and then you would be
stuck distributing all those passwords to the individuals. However, I
suspect the 40 user accounts you are referring to are virtual site user
accounts and not FrontPage userIDs.

Arthur