"No Server Found" when Uninstalling a Frontpage Extension

[Pinoywh]

Hi,

When I uninstall a FrontPage Extension to a domain, I get this error message, "No Server Found.". How can I fix this?, and I tried adding again and here are the messages:

Using Frontpage 5.x!

Starting install, port: 80.

Created: 04 Aug 2005 23:17:09 -0000
Version: 5.0.2.2634
Server extensions already installed on port 80.
Reverting to upgrade.

Starting upgrade, port: 80.

Created: 04 Aug 2005 23:17:09 -0000
Version: 5.0.2.2634
Chowning Content in service /.
Port 80: Upgrade completed.
Upgraded Version: 5.0.2.2634.

Starting chown, port: 80, web: "/".

DocumentRoot: "/home/fantasti/public_html"
Setting Password
Frontpage passthough auth enabled!
"

How can I fix this?

 

[Blapto]

Using Frontpage 5.x!
No Server found

I get this error when I try to give a new account Frontpage extensions.

WHM 10.1.0 cPanel 10.2.0-R82
RedHat 9 i686 - WHM X v3.1.0

I'm looking into it now.

 

[Pinoywh]

Are there any solutions out there? I tried all fix and updated cpanel but to no avail....

Thanks in advance.

 

[Blapto]

Run
/scripts/upcp --force

Frontpage extensions seem to be behaving now. Sorry I didn't post earlier, I've been all over the place.

 

[jcsolutions]

This problem still exists. I tried /scripts/upcp --force but it didn't help.

Attempting to install FrontPage extensions...
No Server found
FrontPage extensions are currently: not installed

I'm running WHM 10.6.0 cPanel 10.8.0-R54

 

[anton_latvia]

Pretty old thread, I must say, but I am experiencing this problem right now.

WHM 10.8.0 cPanel 10.9.0-C9565
CentOS 4.4 x86_64 - WHM X v3.1.0

Just tried to upcp --force with no luck. Except that in my case this is about enabling FP on subdomain. Client got 5 subdomains, 3 of them have FP installed, but 2 are getting "No domain found" error when trying to enabled.

Any guru here?

 

[rhenderson]

Most of our old FrontPage problems were releated to mod_security. I would back up the mod_security file and take everything out and see if the porblem goes away. If so add the rules one or two at a time testing FP in between.

 

[anton_latvia]

Thanks for the guess, we had though mod_security with no rules set. Unfortunately even after disabling it I still was unable to enable FP extensions on a subdomain.

 

[kielsky]

I had similar problems, and none of the "upcp" and so forth fixes worked, so I painstakingly investigated -- and discovered that the FrontPage setup script "/scripts/setupfp5" was failing to properly locate the appropriate VirtualHost entry in my httpd.conf because the pattern it was looking for was not a match for our installation.

I modified the pattern inline:

replace '(m/^\\s*<virtualhost\\s+([\\d.]+)(?::80|\\s*>)/i)' '(m/^\s*<virtualhost\s+([\d.]+|\*)(?::80|\s*>)/i)' -- /scripts/setupfp5

This worked for us and our somewhat non-standard httpd.conf. Your mileage may vary, use at your own risk, etc., etc.

-- Michael Kielsky
BetterThanYours.com
http://BetterThanYours.com
+1.888.398.4405

 

[anton_latvia]

Well, I found on some other thread, that sometimes buggy FP adds _vti_* folders and .htaccess file to the user's root folder (/home/username/_vti*). I deleted them and problem was fixed.