08-30-05 07:53 AM
Warren,
You are not the only one seeing this error. Unfortunately I had this happen
to me last week. I was using Windows 2003 Web Edition, SP1, FPSE2002 versio
n
5.0.2.6738 on a P4 non 64 bit processor. It affected all of the FrontPage
extended websites. When I would open any of them and run check server healt
h
all of the sites would start working again. Then about 10 minutes later the
y
would stop. At any given point in time the web base Sharepoint administrato
r
would work. However when I would try to check the extensions through MMC it
would say page cannot be found. This went on for about a week till we
repaired/reinstalled windows and did not install SP1, which contains the
5.0.2.6738 version of the extensions. The current version, the default
version that comes with windows 2003, is 5.0.2.5012. These extensions are
working fine except the documented bug of searching the websites parent
folder and all of the subfolders for something (dont know what) and can take
forever on a server with a large ammount of sites in the folder.
At least I am not the only one with this problem, and my suggestion is to
uninstall the extensions and download the extensions on the MSDN website (
MSDN Home > MSDN Library > Office Solutions Development > Office XP >
FrontPage Server Extensions).
"Warren Sirota" wrote:
> Hello,
>
> Please excuse my ignorance. I'm just a programmer trying to set up a
> test Web on a development machine - there's a lot I don't understand
> about configuring servers, especially permissions.
>
> Context
>
> I was running FP2000, and just upgraded to 2003, running under WinXP
> SP2. Now, my IIS 5.1 installation was not functioning perfectly in all
> ways before (as I recall, it was having permissions issues creating
> objects from ASP pages), but now I need it to get better.
>
> Since I was now running FP2003, after installing that I downloaded and
> installed the 2002 extensions from the Microsoft site. Then, I ran
> officeupdate to make sure fp2003 was up to date (since I have elements
> of office 2000, 2002, and now 2003, this was about a 5-restart process,
> but that's besides the point).
>
> The Problem(s)
>
> Opening webs that I have on external servers seems to work fine.
> However, whenever I try to open an existing Web on localhost, I get that
> darned "Server error: Error 5 opening registry key
> "SOFTWARE\Classes\.8ba" message.
>
> If I go to the server extension administrator and simply click the entry
> for Default Web site (without actually doing anything), then I can close
> and reopen FP and then open a localhost subweb without error. That would
> be an OK enough workaround for me; however, I still cannot create a new
> Web from FP (I can from the Administrator, but that doesn't give me
> access to any templates). I keep getting a "Server Error: Cannot create
> folder" message.
>
> Related Information:
>
> I've gone into the FP Extensions administrator and gave every permission
> I could think of to everyone. I've done a "Check Server Health". It
> keeps coming back with this message for the root Web: "Your Web site
> security could be tightened. To tighten security as much as possible for
> your Web sites, select Repair", regardless of whether I check the Fix
> box or not, but that doesn't seem like it would affect my situation.
>
> One other thing: I seem to have two ways to administer this site, and
> they seem to be in conflict: one through the IIS MMC panel, and one
> through IE by going to _sharepoint/fpadmdll.dll?page=fpadmin.htm.
>
> I only intend to create non-Sharepoint Webs on this computer. Is
> Sharepoint confusing the process here?
>
> I'd uninstall and reinstall everything, except that I have little
> confidence that some incorrect registry entry would persist through the
> whole process, making this into a time-wasting exercise.
>
> Any suggestions? Thanks.
>
[ Post a follow-up to this message ]
| 
