IIS Server - Partial success in getting FP extensions to work

Author

Partial success in getting FP extensions to work

=?Utf-8?B?Y292ZTM=?=

2004-01-28, 3:39 am

I've had some partial success in getting a test post to a discussion board to take without the component error.
although with some very puzzling results:
1. Installing IIS without FP2000 extensions & then installing & enabling 2002 extensions has give me more analysis tools, including the server health check which I will report on below.
2. With my board still failing in IE 6 with http://localhost:79/, I switched to http://cove3a.no-ip.info/. I was asked for a password but my Windows administrator password would not take.
3. I opened Windows Explorer, right clicked on the default web in question, and clicked sharing/security. I got a message "the permissions in zztest2 are incorrectly ordered. Click ok to correct & sort entries correctly. This discussion web had been c
reated in FP 2002 with the discussion web wizard. The only entry was for EVERYONE, but after the fix, 7 or 8 groups appeared, starting with Administrator which had full access shaded out.
4. Now my test posts are accepted without the component page error.

Now for the puzzling part.
1. I created a new web zztest4 in FP2002 using discussion web wizzard to try & replicate the problem
2. Windows Explorer gave the same error message & fix as 3 above. So obviously I have to read up on FP 2002 web creation, although I would think the Wizard would guide me though any permissions necessary before it created the web.
3. I now switched the IIS default directory to zztest4 and right click/new/fp2002 extensions subweb. I named this subweb zzfpextension.
4. I then did a web health check which reported 3 or 4 files missing, unlike the check for the good web which was ok
5. I removed zzfpextension and recreated it naming it fpextension, the same name as in my good web
6. Now health check showed no problems. Apparently the fp extensions have to be in a web named only fpextension.
I surely did not come across this in any IIS/FP documentation
7. With the new default web, I now opened in IE 6.0 http://localserver:79/ I got message web not found. Same with http://cove3a.no-ip.info, even after rebooting, closing & opening IIS.
8. However, after deleting all temp internet & history files, I got to the discussion web. I don't know why I should have had to do this simply by changing the IIS default directoey.
9. Now for the puzzling part. With the new test web looking exactly like the working one, clean server health check, permissions identical, fpextension folder with the same name & subfolders as zztest2, I get the FP component error.

I cannot isolate the failure path which I was sure was due to the permissions problem & the correct naming of the fpextension subweb.

I will post this on the FP board, where I see 10 or 15 people tearing their hair out over this same issue, although I still think it's so tight in with IIS that it perhaps belongs on both boards.

Regards, Eon

David Wang [Msft]

2004-01-28, 9:36 pm

I really have no idea how FPSE works (in your terms, it's about as clear as
cement to me :-) ), but I will forward your comments to the FPSE guys and
see what they say about this "usability" problem.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"cove3" <cove3@aol.com> wrote in message
news:50DA0420-638B-4E6B-9C2D-2D6F66186188@microsoft.com...
I've had some partial success in getting a test post to a discussion board
to take without the component error.
although with some very puzzling results:
1. Installing IIS without FP2000 extensions & then installing & enabling
2002 extensions has give me more analysis tools, including the server health
check which I will report on below.
2. With my board still failing in IE 6 with http://localhost:79/, I switched
to http://cove3a.no-ip.info/. I was asked for a password but my Windows
administrator password would not take.
3. I opened Windows Explorer, right clicked on the default web in question,
and clicked sharing/security. I got a message "the permissions in zztest2
are incorrectly ordered. Click ok to correct & sort entries correctly.
This discussion web had been created in FP 2002 with the discussion web
wizard. The only entry was for EVERYONE, but after the fix, 7 or 8 groups
appeared, starting with Administrator which had full access shaded out.
4. Now my test posts are accepted without the component page error.

Now for the puzzling part.
1. I created a new web zztest4 in FP2002 using discussion web wizzard to
try & replicate the problem
2. Windows Explorer gave the same error message & fix as 3 above. So
obviously I have to read up on FP 2002 web creation, although I would think
the Wizard would guide me though any permissions necessary before it created
the web.
3. I now switched the IIS default directory to zztest4 and right
click/new/fp2002 extensions subweb. I named this subweb zzfpextension.
4. I then did a web health check which reported 3 or 4 files missing, unlike
the check for the good web which was ok
5. I removed zzfpextension and recreated it naming it fpextension, the same
name as in my good web
6. Now health check showed no problems. Apparently the fp extensions have
to be in a web named only fpextension.
I surely did not come across this in any IIS/FP documentation
7. With the new default web, I now opened in IE 6.0 http://localserver:79/
I got message web not found. Same with http://cove3a.no-ip.info, even after
rebooting, closing & opening IIS.
8. However, after deleting all temp internet & history files, I got to the
discussion web. I don't know why I should have had to do this simply by
changing the IIS default directoey.
9. Now for the puzzling part. With the new test web looking exactly like
the working one, clean server health check, permissions identical,
fpextension folder with the same name & subfolders as zztest2, I get the FP
component error.

I cannot isolate the failure path which I was sure was due to the
permissions problem & the correct naming of the fpextension subweb.

I will post this on the FP board, where I see 10 or 15 people tearing their
hair out over this same issue, although I still think it's so tight in with
IIS that it perhaps belongs on both boards.

Regards, Eon

=?Utf-8?B?Y292ZTM=?=

2004-01-29, 7:36 am

David, thanks. I took the advice & posted it on the FP board. Thanks to the following instructions and for those who may have been following this thread, my hats off to Tom Rowe, as I've finally got up & running but scores more like me haven't. Here's
what he wrote under my thread "Has Anyone Succeeded with IIS and Front Page Extensions:

Do the following:

1. Uninstall the FP2002 extensions from your system
2. Uninstall IIS and delete the C:\InetPub folder

Next (and do not change the default port from 80 to 79 or install the FP2002
extensions!)

1. Install IIS
2. Open IIS MMC, and right click on the default web site, All tasks, apply ( I think Tom meant New, not All Tasks)
the FP2000 extensions.
3. Open FP, then File Menu | Open Web and enter http://localhost
4. Create a folder, called Test, right click on Test, select convert to web, (must switch to folder view or else greyed out)
then double click to open in FP.
5. With Test open, File Menu | New | Page or Web | Web Site Template |
Discussion Web and enter the path/location as http://localhost/Test/DiscWeb
6. Open IE, and type in http://localhost/test/discweb/

Now if everything is working, you can install the FP2002 extensions, then
you must open IIS MMC and select each web, then All Tasks, then Upgrade the
extensions.

What is your reason for trying to change the port?

Also, from this point on when working on your web, also open in FP via
http://localhostt/webname/ and to via use the same URL or if in FP, use File
Menu | Preview in Browser.