Re: Can the site still function with corrupt extensions?
From: Richard (zxfiles_at_NOSPAMyahoo.com)
Date: 02/23/05
- Next message: Richard: "Re: Can the site still function with corrupt extensions?"
- Previous message: Tom Pepper Willett: "Re: Can the site still function with corrupt extensions?"
- In reply to: Tom Pepper Willett: "Re: Can the site still function with corrupt extensions?"
- Next in thread: Tom Pepper Willett: "Re: Can the site still function with corrupt extensions?"
- Reply: Tom Pepper Willett: "Re: Can the site still function with corrupt extensions?"
- Reply: Tom Pepper Willett: "Re: Can the site still function with corrupt extensions?"
- Reply: Kathleen Anderson [MVP - FrontPage]: "Re: Can the site still function with corrupt extensions?"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 23 Feb 2005 12:07:04 -0800
Sorry. Yes, I took a look at all of those links. Here is what I found.
1) If I browse to the website with IE and click on the Edit with Frontpage,
all it does is open a local copy of the page. If I try to save the page, it
only saves to my local computer.
2) Same thing happens if I try to use the run command for "frontpg.exe
http://oursite.com"
3) It is listed on recent webs part of FP and when I click that file, it
does nothing. No errors, but no logon prompts and not pages open. It remains
the default blank HTML page that you get when starting up FP. If I do this
for the other sites I mentioned I work on, it works fine. They pop up with
the logon screen.
4) We have asked IIS to check the extensions and we had it tighten the
security. Although, I was going to try this one more time as I saw it
mentioned elsewhere with this same problem.
5) The network is fine and up and running. No new passwords have been
created for anything related to the domain and servers.
6) I did have my shortcut arrows turned off. Turning them back on did not
help. Not that it matters, but I always opened FP through the Start menu.
7) The name capitalization doesn't seem to be a problem here. We use
lowercase.
This is bugging me to death. With the searching of this topic on the web, I
have never seen a resolution. They always say to consult the admin and have
them fix it. Well, I am the admin and I don't know how to fix it. :)
Thanks,
Richard
"Tom Pepper Willett" wrote:
> Did you also try the following that I posted to you before?
>
> The folder "http://Website" isn't accessible. The folder may be located on
> an unavailable volume or protected with a password.
>
> http://support.microsoft.com/support/kb/articles/Q260/7/55.ASP
> http://support.microsoft.com/support/kb/articles/Q264/7/49.ASP
> http://support.microsoft.com/support/kb/articles/Q266/6/65.ASP
> http://support.microsoft.com/support/kb/articles/Q272/5/42.ASP
> http://support.microsoft.com/support/kb/articles/Q287/3/99.ASP
> http://support.microsoft.com/support/kb/articles/Q310/8/46.ASP
>
> You may wish to download the FREE Jimco Open Web which bypasses the possibly
> corrupted web folders: www.jimcoaddins.com
> --
> ===
> Tom "Pepper" Willett
> Microsoft MVP - FrontPage
> ---
> About FrontPage 2003:
> http://office.microsoft.com/home/office.aspx?assetid=FX01085802
> FrontPage 2003 Product Information:
> http://www.microsoft.com/office/frontpage/prodinfo/default.mspx
> Understanding FrontPage:
> http://msdn.microsoft.com/office/understanding/frontpage/
> FrontPage 2002 Server Extensions Support Center:
> http://support.microsoft.com/default.aspx?scid=fh;en-us;fp10se
> ===
> "Richard" <zxfiles@NOSPAMyahoo.com> wrote in message
> news:BE60FCC3-45FC-457F-BA85-DC57BFDB77CF@microsoft.com...
> |I posted it in the general Frontpage groups a couple of days ago, but the
> | basic problem is that Frontpage will no longer edit the website anymore.
> It
> | used to at one time, I just can't figure out what may have broken it.
> |
> | We have a Server 2003 domain running active directory. This move took
> place
> | last year. However, we still have the website running on an NT4 server.
> When
> | I go into Frontpage 2003 and try to open the site I get multiple errors
> | depending on the logon.
> |
> | For example, I am part of the Administrators and Domain Administrators
> | group. I am also added as an author to the website in the IIS manager.
> | However, when I try to open the site for editing, it doesn't prompt me for
> | the logon, it immediately gives me an error that I don't have permission
> to
> | view the web folders in this location. If I logon to a different computer
> | with my domain logon, I get a different error this time saying the website
> is
> | not accessible and that it might be located in an unavailable location,
> | protected with a password, or the filename contains a / or \.
> |
> | I decided to try loggin on to the computer as the Domain Administrator
> logon
> | and I get the same message. But if I try to use File -> Open instead of
> Open
> | Site, it tells me that I can only view it as read-only. Same thing happens
> if
> | my boss tries to edit the site.
> |
> | We have IIS setup on one of the new 2003 servers in anticipation of the
> | website move. I am able to open that site up for editing. I get the logon
> | prompt. I also edit an off-site website elsewhere on campus this same way
> and
> | it works too. I get the logon prompt. But for some reason, on this NT4
> server
> | it will no longer prompt for the logon and immediately pops up these
> messages.
> |
> | Based on some suggestions, I emptied the FP temp folder, but that didn't
> | help. I have tried turning the XP firewall off and that doesn't help.
> These
> | machines all have Office 2003 SP1 and XP Pro SP2 installed.
> |
> | As a last resort, reinstalling the extensions seemed liked the only other
> | solution, but the site itself seems fine. There are some thoughts it might
> be
> | some security setting, but I don't know what could have changed, unless
> SP2
> | did something.
> |
> | BTW, allow annonymous access is checked in the IIS manager if that helps.
> |
> | Thanks,
> | Richard
> |
> |
> | "Kathleen Anderson [MVP - FrontPage]" wrote:
> |
> | > What problem are you having publishing?
> | >
> | > --
> | >
> | > ~ Kathleen Anderson
> | > Microsoft MVP - FrontPage
> | > Spider Web Woman Designs
> | > web: http://www.spiderwebwoman.com/resources/
> | > blog: http://msmvps.com/spiderwebwoman/category/321.aspx
> | >
> | >
> | > Richard <zxfiles@NOSPAMyahoo.com> wrote:
> | > > We are having a problem with FP2003 publishing that I think a
> | > > reinstall of the server exyensions might fix. But nothing else on the
> | > > site seems to be broken. Is it possible for the extensions to become
> | > > corrupt and yet the website still functions properly? Or would other
> | > > areas also show problems? Thanks.
> | >
>
>
>
- Next message: Richard: "Re: Can the site still function with corrupt extensions?"
- Previous message: Tom Pepper Willett: "Re: Can the site still function with corrupt extensions?"
- In reply to: Tom Pepper Willett: "Re: Can the site still function with corrupt extensions?"
- Next in thread: Tom Pepper Willett: "Re: Can the site still function with corrupt extensions?"
- Reply: Tom Pepper Willett: "Re: Can the site still function with corrupt extensions?"
- Reply: Tom Pepper Willett: "Re: Can the site still function with corrupt extensions?"
- Reply: Kathleen Anderson [MVP - FrontPage]: "Re: Can the site still function with corrupt extensions?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|