A BIG COMPLAINT!

[Guest]

I have a big complaint re: Win XP Pro, FP 2003, and the answers provided by "experts" on this site.

I've wasted DAYS worth of time trying to figure out how to publish my FP2003 webste to IIS that came on the Win XP Pro CD.

No where in the Win XP Pro, IIS, or FP 2003 screens does it say that the FPSE 2000 that comes with IIS on the Win XP Pro CD needs to be replaced with FSE 2002. None of the responses to my posts (from StarView) over the past few days asked if I had FPSE 2002 loaded or how to check or how to load them. I just happen to come across a post today, 7/7, in the FPSE board, with directions to install FPSE 2002. Once I followed the instructions, I was able to successfully publish a web site to my IIS server.

My recommendations: 1) When FP2003 is installed on a machine, it ought automatically check for, and if need be, install & upgrade FPSE 2002. 2) When the experts on this site respond to all of the posts on difficulting publsihing to their local IIS server that they ask if the person is using FP2003, if the FPSE2002, verses 2000 are installed. Instructions ought to be given on how to check and how to download.

Regards, StarView - (e-mail address removed); or (e-mail address removed)

 

[Thomas A. Rowe]

The reason you do not see this info, is that the FP2000 extensions DO NOT need to be
replaced/updated to use FP2003 under Windows XP Pro.

FP2003 is designed to work with any previous version of the FP extensions, however the version of
the extensions will determine which run-time components (feature/functions) of FP2003 that can be
used.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

I have a big complaint re: Win XP Pro, FP 2003, and the answers provided by "experts" on this site.

I've wasted DAYS worth of time trying to figure out how to publish my FP2003 webste to IIS that came on the Win XP Pro CD.

No where in the Win XP Pro, IIS, or FP 2003 screens does it say that the FPSE 2000 that comes with

IIS on the Win XP Pro CD needs to be replaced with FSE 2002. None of the responses to my posts
(from StarView) over the past few days asked if I had FPSE 2002 loaded or how to check or how to
load them. I just happen to come across a post today, 7/7, in the FPSE board, with directions to
install FPSE 2002. Once I followed the instructions, I was able to successfully publish a web site
to my IIS server.

My recommendations: 1) When FP2003 is installed on a machine, it ought automatically check for,

and if need be, install & upgrade FPSE 2002. 2) When the experts on this site respond to all of the
posts on difficulting publsihing to their local IIS server that they ask if the person is using
FP2003, if the FPSE2002, verses 2000 are installed. Instructions ought to be given on how to check
and how to download.

 

[Guest]

Well Thomas, thank you for the reply, but the fix was nothing else other than the installation of FPSE2002. When troubleshooting situations like mine - WinXP Pro + IIS + FP2003, to me it's clear that the question needs to be asked if FPSE2002 is installed. Based on my war wounds (reference the post threads), FP2003 is not cleanly backward compatible with previous versions of FPSEs.

 

[Thomas A. Rowe]

My experience is that FP2003 work just fine with the FP2000 extensions under Windows XP Pro, IIS
5.1, just limit my ability to use any of the FP2002 features which are unchanged in FP2003.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

Well Thomas, thank you for the reply, but the fix was nothing else other than the installation of

FPSE2002. When troubleshooting situations like mine - WinXP Pro + IIS + FP2003, to me it's clear
that the question needs to be asked if FPSE2002 is installed. Based on my war wounds (reference the
post threads), FP2003 is not cleanly backward compatible with previous versions of FPSEs.

 

[Jim Cheshire]

Well Thomas, thank you for the reply, but the fix was nothing else
other than the installation of FPSE2002. When troubleshooting
situations like mine - WinXP Pro + IIS + FP2003, to me it's clear
that the question needs to be asked if FPSE2002 is installed. Based
on my war wounds (reference the post threads), FP2003 is not cleanly
backward compatible with previous versions of FPSEs.

StarView,

Understand first that the people answering questions here are volunteers and
answered your questions out of the kindness of their heart. Given that
fact, even though you may be very frustrated by your issue, it's certainly
not warranted to complain loudly and chastise them by putting the word
"experts" in quotes as you have.

With that said, Thomas is correct in that FrontPage 2003 does not require
the FrontPage 2002 Server Extensions to publish. It will publish against
the FrontPage 2000 Server Extensions, the FrontPage 2003 Server Extensions,
Windows SharePoint Services, FTP, or WebDAV enabled servers. I'm not sure
what your problem was, but a reinstall of the 2000 Server Extensions would
have likely resolved it as well since it seems obvious that the Server
Extensions were not working correctly.

--
Jim Cheshire
Jimco
http://www.jimcoaddins.com
================================
Author of Special Edition
Using Microsoft Office FrontPage 2003
5 Stars on Amazon and B&N
================================
The opinions expressed by me in the
newsgroups are my own opinions and
are in no way associated with my
employer or any other party. Jimco is
not associated in any way with any other
entity.

 

[=?iso-8859-1?Q?Crash_Gordon=AE?=]

Glad to see you got it fixed.

Looking forward to seeing the website, currently it's; server not found.


| I have a big complaint re: Win XP Pro, FP 2003, and the answers provided by "experts" on this site.
|
| I've wasted DAYS worth of time trying to figure out how to publish my FP2003 webste to IIS that came on the Win XP Pro CD.
|
| No where in the Win XP Pro, IIS, or FP 2003 screens does it say that the FPSE 2000 that comes with IIS on the Win XP Pro CD needs to be replaced with FSE 2002. None of the responses to my posts (from StarView) over the past few days asked if I had FPSE 2002 loaded or how to check or how to load them. I just happen to come across a post today, 7/7, in the FPSE board, with directions to install FPSE 2002. Once I followed the instructions, I was able to successfully publish a web site to my IIS server.
|
| My recommendations: 1) When FP2003 is installed on a machine, it ought automatically check for, and if need be, install & upgrade FPSE 2002. 2) When the experts on this site respond to all of the posts on difficulting publsihing to their local IIS server that they ask if the person is using FP2003, if the FPSE2002, verses 2000 are installed. Instructions ought to be given on how to check and how to download.
|
| Regards, StarView - (e-mail address removed); or (e-mail address removed)

 

[Tom Pepper Willett]

Yes, many of us have put in some time and effort to help you with your
problem. Your comments were offensive.
--
===
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
===

Jim -

My apologies if I've offended any one here. My wasting of many days has

been very frustrating. I may have wrongly assumed that the experts on this
site worked for Microsoft, as their answers typically come across as quite
knowledgable. I admit that this forum is very helpful and beneficial, and I
do appreciate it.

Regarding the FPSE - I have reformatted my system 3X, cleanly loaded IIS,

then FP2003, and set the admin, author, & browser groups & users, and
repeatedly had problems publishing to the local web server. Only when FPSE
2002 was installed did FP2003 smoothly and immediately access & publish to
the server. Though it is said that FP2003 should have no problems with
using FPSE 2000, it is very clear, at least in my situation, that there is
something in FPSE2002 (perhaps the administration utility) that enables
quick and successful configuration and functioning of the server.

I still recommend that FP2003 be installed with FPSE2002 and that all of

the folks who graciously field postings here give thought to asking if
FPSE2002 may be an option to fixing reported difficulties.

 

[Jim Cheshire]

Jim -

My apologies if I've offended any one here. My wasting of many days
has been very frustrating. I may have wrongly assumed that the
experts on this site worked for Microsoft, as their answers typically
come across as quite knowledgable. I admit that this forum is very
helpful and beneficial, and I do appreciate it.

Regarding the FPSE - I have reformatted my system 3X, cleanly loaded
IIS, then FP2003, and set the admin, author, & browser groups &
users, and repeatedly had problems publishing to the local web
server. Only when FPSE 2002 was installed did FP2003 smoothly and
immediately access & publish to the server. Though it is said that
FP2003 should have no problems with using FPSE 2000, it is very
clear, at least in my situation, that there is something in FPSE2002
(perhaps the administration utility) that enables quick and
successful configuration and functioning of the server.

I still recommend that FP2003 be installed with FPSE2002 and that
all of the folks who graciously field postings here give thought to
asking if FPSE2002 may be an option to fixing reported difficulties.

Thanks, John.

John,

There are cases where the FrontPage 2002 Server Extensions are less
desirable than the 2000 Server Extensions. For example, I work primarily
with ASP.NET applications. The FPSE 2002 maintain permissions via the
roles.ini file. Therefore, if you check server health and tighten security,
it will remove the ASP.NET process account's permissions to Web content and
break your ASP.NET applications. For that reason, I prefer the FrontPage
2000 Server Extensions and never use anything else.

--
Jim Cheshire
Jimco
http://www.jimcoaddins.com
================================
Author of Special Edition
Using Microsoft Office FrontPage 2003
5 Stars on Amazon and B&N
================================
The opinions expressed by me in the
newsgroups are my own opinions and
are in no way associated with my
employer or any other party. Jimco is
not associated in any way with any other
entity.

 

[Guest]

Ah - interesting detail. Though I don't think it will apply in my situation, I understand your recommendation and am sure other users would find it quite helpful. Thanks.

 

[chris leeds]

also i believe the "web publishing wizard" which is included in or works
with some apps (ulead's photoimpact 'save to web' for instance) will only
work with fp 2000 extns.

--
The email address on this posting is a "black hole". I got tired of all the
spam.
Please feel free to contact me here:
http://nedp.net/contact/
--

Ah - interesting detail. Though I don't think it will apply in my

situation, I understand your recommendation and am sure other users would
find it quite helpful. Thanks.