FP 2003 compatibility

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Is it correct that FP 2003 is not compatible with FP server extensions 2002 or Sharepoint services.

My website built in FP 2003 is not discovered by either one of the apps, they keep referring to a version 5, while FP 2003 refers to a version 6

Any pointer much appreciated
 
1. There are no FP2003 extensions.
2. FP2003 will use either FP2000, FP2002 or SharePoint Services

--

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

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


Pim said:
Is it correct that FP 2003 is not compatible with FP server extensions 2002 or Sharepoint services.

My website built in FP 2003 is not discovered by either one of the apps,
they keep referring to a version 5, while FP 2003 refers to a version 6
 
No, that is not true, it is compatible.

The server extensions are version 5.x for 2002 and 4.x for 2000. Your
version of FrontPage is irrelevant to the version of the extensions.

What do you mean it is not discovered? What do you mean "they keep
referring to a version 5"?

-John




Pim said:
Is it correct that FP 2003 is not compatible with FP server extensions 2002 or Sharepoint services.

My website built in FP 2003 is not discovered by either one of the apps,
they keep referring to a version 5, while FP 2003 refers to a version 6
 
Not sure that is correct. I have a Beta FPage 2003 site
hosted by a company that first said they only did 2002.
But I did some checking with Microsoft.com/technet. they
had a "chat" that indicated that 2003 is backwards
compatible. My host must have found something similar.
Because he agreed to host, and we are not having any
problems -- he started hosting in September. All is
still well.
cneubie


-----Original Message-----
Is it correct that FP 2003 is not compatible with FP
server extensions 2002 or Sharepoint services.
My website built in FP 2003 is not discovered by either
one of the apps, they keep referring to a version 5,
while FP 2003 refers to a version 6
 
No, FP2003 will work fine with the FP2002 Extensions.
You do however need the updated WSS.

Regards Jens Peter Karlsen. Microsoft MVP - Frontpage.
 
Can you clarify what you mean here? While I do use WSS for some things, I
don't use it for internet development. Clearly it is not needed inorder to
use FrontPage.

Thanks!
-John
 
-----Original Message-----
Is it correct that FP 2003 is not compatible with FP
server extensions 2002 or Sharepoint services.

On the contrary, it's compatible with both.
My website built in FP 2003 is not discovered by either
one of the apps,

Please explain what you mean by this. For example, what's
not working? Do you get an error message? If so, what does
it say?
they keep referring to a version 5, while FP 2003 refers
to a version 6.

Where are you looking, and why?

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*------------------------------------------------------*
|\----------------------------------------------------/|
|| Microsoft Office FrontPage 2003 Inside Out ||
|| Microsoft FrontPage Version 2002 Inside Out ||
|| Web Database Development Step by Step .NET Edition ||
|| Troubleshooting Microsoft FrontPage 2002 ||
|| Faster Smarter Beginning Programming ||
|| (All from Microsoft Press) ||
|/----------------------------------------------------\|
*------------------------------------------------------*
 
I've got multiple sites, only one of them made in FP2003. This specific one can not be uploaded to the remote server using server extensions/shaprepoint cause it does not recognise the server as such, so I upload it through the "file" mechanism

On the server W2K3 with iis 6, all site can be right clicked and configure the server extensions, except the new FP2003 one

I've got sharepoint services running too, when firing up the manager it see the old sites with version 5 extensions, and the new one with version 6, which is the same as in the sites properties in FP.
The sharepoint manager does not give me the option for the new site to "extend" , it says it's "too old for this server"

Tried to de- and reinstall IIS, server extensions and sharepoint, same result

Driving me absolutely mad
 
Pim said:
I've got multiple sites, only one of them made in FP2003. This specific one
can not be uploaded to the remote server using server extensions/shaprepoint
cause it does not recognise the server as such, so I upload it through
the "file" mechanism

It sounds as if the server extensions aren't installed on that virtual
server.
On the server W2K3 with iis 6, all site can be right clicked and configure
the server extensions, except the new FP2003 one

Do you mean in Internet Services Manager? If so, do any virtual
servers on that computer hhave the option to install server
extensions?

If not, the extensions may not be installed on the computer.
I've got sharepoint services running too, when firing up the manager it see
the old sites with version 5 extensions, and the new one with version 6,
which is the same as in the sites properties in FP.
The sharepoint manager does not give me the option for the new site
to "extend" , it says it's "too old for this server"

Right, if you have Windows SharePoint Services running on a virutal
server,
you don't install the FrontPage Server extensions. WSS provides a
subset of the FPSE functions.
Tried to de- and reinstall IIS, server extensions and sharepoint, same result

WSS is a much different environment from FPSE 2002. WSS adds a lot of
new fucntionality, but you have to give up some things as well. For
example, ordinary ASP and ASP.NET pages won't run under WSS.

If you want the "classic" FPSE environment on a virtual server,
install FPSE.

If you want a SharePoint portal environment, install WSS.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*------------------------------------------------------*
|\----------------------------------------------------/|
|| Microsoft Office FrontPage 2003 Inside Out ||
|| Microsoft FrontPage Version 2002 Inside Out ||
|| Web Database Development Step by Step .NET Edition ||
|| Troubleshooting Microsoft FrontPage 2002 ||
|| Faster Smarter Beginning Programming ||
|| (All from Microsoft Press) ||
|/----------------------------------------------------\|
*------------------------------------------------------*
 
WSS is not required for FP2003
- except for the new features only supported by WSS
See http://www.microsoft.com/office/preview/frontpage/servers.asp

--




| Can you clarify what you mean here? While I do use WSS for some things, I
| don't use it for internet development. Clearly it is not needed inorder to
| use FrontPage.
|
| Thanks!
| -John
|
|
| | > No, FP2003 will work fine with the FP2002 Extensions.
| > You do however need the updated WSS.
| >
| > Regards Jens Peter Karlsen. Microsoft MVP - Frontpage.
| >
| > On Thu, 16 Oct 2003 12:06:04 -0700, Pim
| >
| > >Is it correct that FP 2003 is not compatible with FP server extensions
| 2002 or Sharepoint services.
| > >
| > >My website built in FP 2003 is not discovered by either one of the apps,
| they keep referring to a version 5, while FP 2003 refers to a version 6
| > >
| > >Any pointer much appreciated
| >
|
|
 
Jim,

a. Indeed the server extensions are not installed on that virtual server, and I see no way to do that, cause, again, right-clicking this server in IIS does NOT give me that option
b. other virtual servers have indeed that option, those are hte servers not made in FP2003

c and I tried all cobinations, only SE, only WSS and both, but server still not recognezed by SE, even further, FP2003 says in the remote server properties that this webserver does NOT support either SE or WSS

Again, it IS driving me mad
 
HURRAY, I solved the problem, and it works now after a week, and as usual a very stupid and simple solutio;

Thru FP 2003 I had published hte site directly in inetpub/wwwroot, after thsi I configured a virtual server in IIS which of course pointed to the wwwroot. I deleted the whole thing (including the site), and reinstalled IIS. Thereafter I told FP to upload the site to a remote wbeserver with the IP of the server. BINGO

Thanks for all the support and suggestions
 
Back
Top