Re: FP 2003 message: An error occurred accessing Windows Sharepoint Services site files.

It won't install, even with NAV disabled: Error 1911. Could not register
type library for file C:\Program Files\Open Web\OpenWeb.dll. Contact your
support personnel.

I think my install of IIS is hosed.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/


"Tom Willett" <tompepper@xxxxxxxxxxxx> wrote in message
news:uYuzVzkwGHA.1288@xxxxxxxxxxxxxxxxxxxxxxx
Kat: Did you ever download and install Jimco's "Open Web" which bypasses
the web folders? I use it religiously.

--
Tom Willett
Microsoft MVP - FrontPage
FrontPage Support: http://www.frontpagemvps.com/
----------
"Kathleen Anderson [MVP - FrontPage]" <spiderwebwoman@xxxxxxxx> wrote in
message news:eZRf0GkwGHA.1272@xxxxxxxxxxxxxxxxxxxxxxx
Thanks, Larry. I followed this step-by-step; when I got to opening my
local site from My Network Places, I got the attached error message.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/


"Larry Kahm" <lkahm@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:eGCT%23ujwGHA.1296@xxxxxxxxxxxxxxxxxxxxxxx
OK, so I had the time this afternoon to contact Microsoft PSS about this
issue.

In a Live Meeting conference, I demonstrated the error and how it
occurred.
File, Recent Sites, site name. Then, after going through that several
times
to finally open the site, getting the error on opening a page.

Long story short, here's what we did to resolve this:

Open IIS, expand the local computer, expand Web sites, right-click
Default
Web Site, select Properties

Click the Server Extensions 2002 tab, click the Settings button

If prompted, enter the user name and password for your computer

Click on the Administration link in the upper, left-hand corner of the
web
page

Click on the link for the Default Web Site (mid-page)

Scroll down to the Server Health section and click the link for Check
server
health. Now, make sure that all of the options are checked for "Detect"
and
click OK. Check any items that have "Fix this problem" and then click
Submit - be prepared to wait a while. IIRC there is a Done button when
it
is finished.

Get back to the Site Administration page and in the Server Health
section
click the link for Recalculate the web. Be prepared to wait for a
while,
depending on the size of your locally hosted web sites.

Close the Administration tool when finished; click OK on the Default Web
Site properties page.

Now, right-click on your local computer, select All tasks, select
Restart
IIS. When this event is finished, close IIS.

Open FrontPage. Note: I have been instructed to NEVER use the File,
Recent
Site links - no reason other than they WILL cause the idiotic SharePoint
error message.

Instead, for local sites use: Select File, Open Site, and select
Network
Places. Open your local site from there.
If you are using the file system, Select File, Open, and My Computer,
and
open C:\Inetpub\wwwroot\folder name

So far - and it's only been a half an hour, this >seems< to have worked.

Hope that helps!

Larry Kahm
Heliotropic Systems, Inc.



"Larry Kahm" <lkahm@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OMyYAOXvGHA.1888@xxxxxxxxxxxxxxxxxxxxxxx
I'm running Windows XP Pro with SP2 and FP 2003 with the most recent
set
of Microsoft updates.

Recently I've started receiving the following message:

"An error occurred accessing your Windows Sharepoint Services site
files.
Authors - if authoring against a Web server, please contact the
Webmaster
for this server's Web site. WebMasters - please seee the servers's
application event log for more details."

Well, the web sites that I'm getting this error message are running
locally (http://machine_name/site_name) and this message pops up when I
try to open a site, or when I attempt to edit pages, or when I attempt
to
publish changes to the remote site, or even if I try to look at the
Tools.. Site Settings.

Needless to say, most of the articles I've seen on Google refer to a
Windows Server issue - and that's not the case with this local
workstation.

To further confuse the issue, I don't know what "server's application
event log" this message is referring to.

Does anyone have any idea of a) what caused this to start happening and
b)
some mechanism to correct it?

Thanks!

Larry Kahm
Heliotropic Systems, Inc.













.