• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Frontpage Extensions

BoiseComputer

Regular Pleskian
http://www.domain.com/_vti_bin/_vti_adm/fpadmcgi.exe?page=webadmin.htm
Not Found
The requested document was not found on this server.

One of my domains is not letting me access the Frontpage Webadmin. It gives the above error. I have tried moving all the files to another directory, deleting all of the frontpage related files, enabling frontpage to create a fresh set of frontpage files and folder in the directory and then copying the origional files back without overwriting any of the frontpage files. I don't know what else to try without deleting the whole account and placing the files back in.. Any help would be greatly appreciated.
 
:-( I am getting the same problem ... Just had a client ring me up and complain that frontpage is not working...

Errors in log files:
(access_log)
81.3.118.81 - xxxUSERxxx [29/Aug/2006:09:14:23 +0100] "GET /_vti_bin/_vti_adm/fpadmcgi.exe?page=webadmin.htm HTTP/1.1" 404 317 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)"

(error_log)
[Tue Aug 29 09:14:23 2006] [error] Incorrect permissions on webroot "/home/httpd/vhosts/xxxDOMAINxxx/httpdocs/_vti_pvt" and webroot's _vti_pvt directory in FrontPageAlias().
[Tue Aug 29 09:14:23 2006] [error] Incorrect permissions on webroot "/home/httpd/vhosts/xxxDOMAINxxx/httpdocs/_vti_pvt" and webroot's _vti_pvt directory in FrontPageAlias().
[Tue Aug 29 09:14:23 2006] [error] [client 81.3.118.81] File does not exist: /home/httpd/vhosts/xxxDOMAINxxx/httpdocs

The ftp user name and the frontpage user name can be different or the same and the same errors get logged...

The user permissions on the _vti_pvt folder are 755 ftpuser : psaserv
I tried changing to 755 ftpuser : psacln (no change in errors)
and even had 777 for a few seconds - still no joy

Can anyone point us in the right direction to get this fixed? I have never tried frontpage extensions - just my client requested they change over from ftp :-(

-DJ
 
... Ok, so I carried on plugging away at permissions ... and have it working!

I used the sledge-hammer aproach and tried:

cd /home/httpd/vhosts/xxxDOMAINxxx
chown xxxUSERxxx : psaserv _vti_* -R (without the spaces between user and group)

That seemed to do the trick.

Mind you I did go and set up a new domain from scratch to test & that worked out of the box - so it must be some permissions not being set when the fronpage extensions are enabled after a change of ftp user or something like that...
 
Try disabling the front page settings on the domain and then re-enabling them.

Alot of times this fixes things.
 
I have tried all of these things.. Nothing seems to fix the problem.. I would delete the whole account... Actually.. I will try that and let you know if I still have the problem...



*** UPDATE ***
I deleted the whole domain... (Backing up the actual files under httpdocs of course) and then recreated the domain... The Frontpage extensions then worked... I copied all files back only overwriting the index.html file... What a pain.. Something in the structure must have really gotten messed up.. Thank you for your input all...
 
Back
Top