Re: Server Ext 2002 admin program too old

From: Kevin Hughes (KevinHughes_at_discussions.microsoft.com)
Date: 09/13/04 

Date: Mon, 13 Sep 2004 13:43:36 -0700

Thank you for the response.

There is no option to choose to extend only with the FP server extensions or
with sharepoint extensions. The administration webpage will allow me to
extend the default website (created when IIS is installed) with version
5.0.2.5012 as long as there is no content other than the default content.

However, I can not then publish to that web from FrontPage 2003. When I try
using the frontpage option under "remote web site properties" called
"Frontpage or sharepoint services", I input the http:// url for the default
website on the server.

I get a prompt for a username/password and input the domain admin
credentials (yes, the webserver is a member of the AD domain). After a long
minute wait, I am greeted with a pop-up message telling me that "there is no
director named: \" and the only option is to click "OK".

If I change the location of the home directory for the default website, I
get an entirely different set of problems.

I am allowed to extend the site (again using the administration webpage) and
get the same version 5.0.2.5012. However, when I try to publish via FP 2003
using the same process as above, I am told that "it does not appear that the
server at that address has front page extensions installed". I check using
the administration webpage and it reports they are indeed installed.

I have checked to make sure that they extensions are listed and allowed, I
have uninstalled and reinstalled the extensions, uninstalled and reinstalled
IIS, and even done a complete OS reinstall. I have checked the permissions
on the directories and on the websites. They all seem to be in order for
share permissions and for NTFS permissions.

If I try to publish a web via FP 2003 before I extend the site, it will
publish only via FTP. I can't extend the website via the standard
administration webpage.

The knowledge base articles on this error suggest using the sharepoint
administration webpage to work around this.

I can then extend the website , but get a FP Server Extensions version of
6.0.2.5516 and am told that I can not administer the site as the
administration programs are too old.

I still, then, can not publish with the Frontpage or sharepoint services
option in FP 2003.

Hm....I think that is about it.

I have read many threads on this problem in this list over the past few
months. So far, I have seen no resolutions posted. It would be nice to see if
there could be some resolution posted for the others seeming to have this
same problem. If I am not the only one, then it doesn't seem so much like an
error on our part as admins, so much as a glitch in the software.

I did read on the MS website that the FP Server Extensions 2002 support
FrontPage 2002 and earlier versions. Does this imply that they do not support
FP 2003? If so, are there plans to support this product that is now almost 2
years old?

Thank you for your response.

Kevin Hughes
Avalon Technologies

"Hollis D. Paul" wrote:

> In article <064d01c49807$5f330a30$a301280a@phx.gbl>, Kevin Hughes
> wrote:
> > Creating a web in FP2003, I get a report in the admin
> > program of version 6.0.2.5516 after I extend the site.
> > However, I can't administer the site - error msg: "The
> > server administration programs and the server extensions
> > on the web server are not compatible. The administration
> > program is too old to use with this server." I do not get
> > a FrontPage Extensions tab in the properties of the
> > virtual server once I extend it.
> >
> I infer from this that you have extended the site with the SharePoint
> Extensions, and trying to use the FP2002 SE Admin pages should produce
> an error. Had you intended to extend it with the SharePoint
> Extensions? If not, remove them, using the SharePoint Central
> Administration, and then apply the FP2002 Server Extensions from the
> Appsrv.
>
> Hollis D. Paul [MVP - Outlook]
> Hollis@outhousebythesound.com
> Mukilteo, WA USA
>
> Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2600
> http://search.support.microsoft.com/kb/c.asp?FR=0&SD=TECH&LN=EN-US
>
> Mukilteo, WA USA
>
>
>

Relevant Pages

  • Re: Im doing something really dumb (I think) - Publishing to local PC with IIS and FP extensions
    ... then get FP2002 extensions installed. ... > right-click on 'default web site', ... > Tasks to 'Remove server extensions". ... > n) install IIS from add/remove programs/windows. ...
    (microsoft.public.frontpage.client)
  • Re: Server Ext 2002 admin program too old
    ... "I did read on the MS website that the FP Server Extensions 2002 support ... FrontPage 2002 and earlier versions. ...
    (microsoft.public.frontpage.extensions.windowsnt)
  • Re: ASP pages not running in Window Server 2003
    ... How to Determine Whether the FrontPage Server Extensions ... > I can't get ASP pages to run. ...
    (microsoft.public.inetserver.asp.general)
  • Re: [fitsbits] Abuse of EXTEND keyword
    ... This mention of the NEXTEND keyword caused me to rethink what is really meant by EXTEND = F: EXTEND = T is defined to mean that the FITS file *is permitted* to have extensions following the primary array; it does not mean that the file actually has any extensions. ... which means that the file currently has no extensions following the primary array, but it is permitted to add extensions if desired. ... I'm not really recommending this, however, because as previously mentioned by Preben Grosbol, it could become a burden to keep the NEXTEND keyword up to date as extensions get added or removed from the file. ...
    (sci.astro.fits)
  • Re: [fitsbits] Abuse of EXTEND keyword
    ... The inescapable conclusion appears to be that EXTEND and NEXTEND are ... actually wording in the Standard is "may contain extensions"); ... desired meaning can be expressed by this pair of keywords: ...
    (sci.astro.fits)