What was the file and permissions that needed to be changed???? I am still having the problem ----- Original Message ----- From: "Tom Shepard" <[EMAIL PROTECTED]> To: "'Apache Frontpage support list'" <[EMAIL PROTECTED]> Sent: Thursday, August 26, 2004 9:23 AM Subject: RE: [Fwd: [Apache-FP] Root web '80' does not accept password]
> Thanks for your help. I finally got it working....it was a file permission > problem. > > Tom > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Jacob Anawalt > Sent: Monday, August 23, 2004 12:30 AM > To: [EMAIL PROTECTED] > Subject: RE: [Fwd: [Apache-FP] Root web '80' does not accept password] > > [EMAIL PROTECTED] wrote: > > >-----Original Message----- > >From: [EMAIL PROTECTED] > >[mailto:[EMAIL PROTECTED] On Behalf Of V.M. Branyik > >Sent: Saturday, August 21, 2004 9:37 PM > >To: 'Apache Frontpage support list' > >Subject: RE: [Fwd: [Apache-FP] Root web '80' does not accept password] > > > > > >>I am having the same problem...is there anyone who can offer any > >>suggestions? > >> > >>Tom > >> > >> > >> > > > > I would suggest changing the password. Here is how I was instructed to > > do so > > (by Joshua and it worked): > > > > There is a Frontpage master admin (g-d) account. This user can access the > > main admin page on port 8090 and extend webs and do admin type things. The > > master admin account is stored in > > > > /usr/local/frontpage/version5.0/admin-exes/_vti_pvt/ > > > > service.grp > > service.pwd > > > > The way to change the master admin is to edit service.grp file to change > > "root" (or whatever usename you had in there) to be whatever you want. > > Then > > open service.pwd and delete the line with "root" . Now to change the > > encrypted password stored in service.grp > > you type this... (replacing root with whatever you put in service.grp) > > > > htpasswd -n root > > > > and enter the new password when prompted. The line that is returned > > will be > > the replacement line to paste in to service.pwd. > > > > You have now updated the master admin password. I think there isn't an > > easier way to do this simply because it is a very powerful account. > > You can also re-run owsadm.exe with the options to create the admin port > on an unused port with a new username and password. If you want to > re-use the existing admin port, delete it's VirtualHost section, restart > your web server and then re-run owsadm.exe with the options to create > the admin port on the old (and now unused) port. > > I don't think that was the issue though since they were talking about a > port 80 web. > > >Message: 3 > >Date: Sat, 21 Aug 2004 21:46:09 -0500 > >From: "Tom Shepard" <[EMAIL PROTECTED]> > > > > > >Thanks! I tried this but it did not solve my problem. I can access the > >main admin page on port 8080 but when I try to go to the site > administration > >site for the main web it asks for a password again and the admin password > >does not work. > > > >Any other suggestions? > > > >Tom > > > > > > > I think your term 'root web' while correct threw off the other poster. > You can either apply their suggestions of editing the service.pwd and > service.grp files of your frontpage enabled 'main web' by hand > (/path/to/web/_vti_pvt/ instead of /usr/local/frontpage/etc) or you can > use the GlobalAdmin web page to remove the extensions and then re-apply > the extensions or you can use owsadm.exe. > > It seems like I had a problem at one point where extending a web with > owsadm.exe (or was it the GlobalAdmin web?) somehow created a htpassword > that was incompatible with my web server, but I think that was when I > had apache and apache2 installed. Editing the password file by hand > worked for me. So did removing apache2 and only trying to do FPSE on apache. > > If a partial remove/restore doesn't work then try a full remove/restore > or try the manual editing of the _vti_pvt/service.* files. > > If all that fails to work then you probably have other apache > configuration issues at hand like AllowOverride None or some other > problem that is keeping your .htaccess files from being read and > followed (maybe file permissions?). > > Frontpage isn't (that much) black box magic. On *nix It's just 100's of > configuration files scattered in your web and > /usr/local/frontpage/versionX/ with some permission checks in the code. > Sometimes things don't get installed right or a permission or setting > gets changed and we don't realize the impact until a while later when we > try to admin the once working site. > > Generally, using the GlobalAdmin web to partially or fully uninstall and > then re-install the extensions does the trick since it re-permissions > your web as well as editing or creating the .htaccess files. Sometimes > you need to delete or edit the existing .htaccess files to get the > owsadmin.exe or GlobalAdmin web to start working because the programs > fail to parse the existing .htaccess files. > > If you know you didn't put any .htaccess files in the web's directory > and want to quickly remove them all: > find /path/to/web -name ".htaccess" | xargs rm > > -- > Jacob > _______________________________________________ > Apache-FP mailing list > [EMAIL PROTECTED] > http://lists.joshie.com/mailman/listinfo/apache-fp > > Donations: > http://www.amazon.com/paypage/PT5LZITM9L227 > > _______________________________________________ > Apache-FP mailing list > [EMAIL PROTECTED] > http://lists.joshie.com/mailman/listinfo/apache-fp > > Donations: > http://www.amazon.com/paypage/PT5LZITM9L227 > > _______________________________________________ Apache-FP mailing list [EMAIL PROTECTED] http://lists.joshie.com/mailman/listinfo/apache-fp Donations: http://www.amazon.com/paypage/PT5LZITM9L227
