• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5360
  • Last Modified:

Can’t install FrontPage 2002 Server Extensions

I have two web sites: Default Web Site, and mySite. (mySite is WebDAV shared and points to a directory on another local drive.)

I performed the following steps:

   1. Add or Remove Programs -> Install FrontPage 2002 Server Extensions.

   2. In IIS Manager, under Web Service Extensions, I set FrontPage 2002 Server Extensions to “Allow”.

   3. In IIS Manager, under Web Sites, under mySite, I selected All Tasks>>Configure Server Extensions 2002.

Here’s my problem......a “Please wait” page came up and ran forever. The configuration did not complete, so I eventually had to close the window. Now, I’m in a weird state and cannot install/configure this. After this completed, I noticed that I now have a Microsoft SharePoint Administration web site. That site seems to Configure Server Extensions 2002 just fine. Same for my Default Web Site. So, if I now go to All Tasks on my Default Web site (or the SharePoint Administration web site), I see three menu options for Server Extensions 2002 (Check, Recalculate, and Remove), which tells me that it installed correctly for these two sites. However, if I go to All Tasks for mySite, I only see “Save Configuration to a File” – there are no Server Extensions 2002 choices.

My question has two parts:

(A.) How do I get back to the state where I can again select “Configure Server Extensions 2002” on mySite? (I already tried uninstalling FrontPage 2002 Server Extensions and reinstalling it, but the option to configure didn’t come back.)

(B.) Assuming I can get back to reinstalling and reconfiguring Server Extensions 2002 on mySite and it fails again, how can I get it to install correctly?

Details:
* Windows Server 2003 SP1
* Logged in as Administrator on Server
* Yes, I can write files to the mySite directory as Admin.

Thanks,
Greg
0
Chief_Architect
Asked:
Chief_Architect
  • 14
  • 10
1 Solution
 
alimuCommented:
you can't operate that stuff from the menu in the mmc snapin anymore.  You have to use the Sharepoint Administration site (this is true for both Sharepoint and Frontpage 2002+)
Why do you think it's failed installation?  If that sharepoint admin page comes up ok, and all the sites are configurable there, seems to me like you've got a fully functional set of extensions..
0
 
Chief_ArchitectAuthor Commented:
Alimu,

Thanks for your reply, but let me first clarify a few things. First of all, I am not using MMC (see above). I have not mentioned MMC.

Second, NOT ALL OF MY SITES ARE CONFIGURABLE. That's the point! (see above). My web site (mySite) is not configuralble - and I can't configure it via SharePoint, either.

Thanks for your input and thanks in advance for any further suggestions you might have.

Greg
0
 
alimuCommented:
Hi Chief Architect,
You stated
">  3. In IIS Manager, under Web Sites..."
IIS Manager is a snap-in that runs within Microsoft Management Console (mmc).  I'm sorry if I caused any confusion but I tend to distinguish types of front-page management as "through the mmc" or "through the web interface".

Typing in upper case is the text-based form of yelling and may be considered rude, so please be wary of doing so when people are only trying to help you.

If you are able to uninstall server extensions, reboot the server and then re-install them, you then need to go into the Sharepoint Administration Web and extend each of your websites through that.  At that point you will get an administration link next to each of your sites from which you can hit the web-based administration pages for that particular site.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
alimuCommented:
I would also suggest running filemon from www.sysinternals.com to see if your problem stems from a security issue.  If the extension process has access issues that are causing it to hang, these will show up as "access denied" in filemon and you can work out how much you need to relax NTFS permissions from there.
0
 
Chief_ArchitectAuthor Commented:
Thanks. These are good ideas.......

I uninstalled FrontPage 2002 Server Extensions, rebooted and then reinstalled. I am seeing the same thing. (By the way, I have a pretty well organized and clean server that has only been running for about a month.) Here are some more details:

After reinstalling, I went to Sharepoint Administration Web as you suggested and I noticed that I saw two sites - My Default Web Site and my mySite - Good!.  The Default Web site had a link labeled "Extend", just as you suggested. But mySite (the one I'm trying to install) did not have any such link. I clicked on the "Extend" link for the Default Web site and it installed correclty, however, I could not do so for mySite.

Also, the mySite entry had a version number listed (6.0.2.6551). (Does this imply that it thinks that it is already installed? I doubt this because of what I write below.)

Under Sharepoint Administration Web, I also noticed that the mySite text was a link - I could click on it. I clicked on it and it errored on the following URL:
http://<my_IP_Address>/_vti_bin/_vti_adm/fpadmdll.dll?page=webadmin.htm

This error led me to investigate further.....here's what I found:

After I clicked on Extend for the Default Web site, I noticed that the Default Web Site now contained a "_vti_bin" folder - makes sense! However, mySite does not have (nor has it ever had) that folder......which maybe explains the link error I am seeing - the "_vti_bin" folder was not installed.

I am logged in as Administrator on the machine and Administrator had full rights to that folder.

Thanks for your assistance.

Greg



0
 
alimuCommented:
yes, that means it's already beein installed on that web at some stage but not being able to get to the page may mean either you don't have access or there's something missing, depending on the error.
When you click on "Administration" next to that site - what exactly are you seeing (http status code would be good - 404 / 401...)
0
 
alimuCommented:
check also that you have integrated and/or Basic authentication turned on in the web you need extended.  When you try to hit the admin page it'll pull your credentials to match against the NTFS permissions.  If it's using anonymous, this might be causing it to bomb out.
0
 
Chief_ArchitectAuthor Commented:
Alimu,

Good questions......

1. You say, "When you click on "Administration" next to mySite, what exactly are you seeing?" - Good question, because I can't click on "Administration" for that site. There is no such link. (I do see "Administration for my Default Web site, but not for mySite - I can't configure mySite. So, basically, I'm not getting any errors numbers, I just can see mySite working.)

2. I have Ingegrated Windows Authentication enabled for mySite.

It's like it won't install the special folders and then it won't let me configure Administration settings.

I hope my explanations are clear. What else can I do?

Greg
0
 
alimuCommented:
sorry for the multiple postings.
another thing you could try after the above is uninstalling extensions from that web via the command-line and then re-extending from the Admin page.
In IIS Manager, click on Web Sites and note down the "identifier" number that comes up for that website.
Go to the command prompt and run:
> owsadm -o uninstall -p 80 -m /LM/W3SVC/###  
(where 80 is the port you are running the website on and ### is replaced with the identifier number you grabbed before)
You might need to trackdown where owsadm.exe lives and run it from there if it's not in your path statement.
0
 
Chief_ArchitectAuthor Commented:
Alimu,

(Regarding my previous post, sorry, I obviously meant that "I CAN'T see mySite working.)

1. Here's another clue I just discovered: In Sharepoint Administration, my Default Web site version number is 5.0.2.6790. This is the site that works correctly. However, the mySite version number (the one that does not let me configure, does not have the "_vti_bin" folders installed, and does not have the "Administration" link) is 6.0.2.6551. Does this offer any clues?

2. I'm not sure how to get the "identifier" number to which you are referring. I went to Sharepoint and noticed that it is going to a web page that is mySite:2363. Is this what you are talking about?


Other questions:
1. Should I go to Web Service Extensions and Prohibit/Allow anything further?
2. Could ASP.net be an issue? I have two selections for these sites. 1.something and 2.something. 1.something is selected. (If you want the exact version number, I can get it.)


Thanks for any more help you can give me. I know that this is a tough one. :)

Greg
0
 
alimuCommented:
1(a).  according to http://mindsharpblogs.com/penny/articles/481.aspx, 6.0.2.6551 is the version you get with Windows Sharepoint Services SP2 Beta.  Sounds like a newer version of either Sharepoint or Frontpage Extensions was installed from a beta release at some stage. The uninstall routine should remove all references with any luck.  
Where did you get your fpse 2002 software from (i.e. which media)?
What OS are you running? 2000 Server / 2003 Server / 2003R2 Server?

2(a). 2363 would be the port on your server that the Sharepoint Administration web runs out of.  You need the identifier and port of your problem website.  Port is most likely 80 unless you've changed it.
If you are running Windows 2003+ and are logged onto the server, run through the following
Open Computer management --> Services and Applications --> Internet Information Services --> Click on "Websites" in the left-hand pane.
In the right-hand pane you will have displayed a list of all IIS Web Sites on your server.  One of the columns displayed should be "Identifier".  Find the website that's the problem and note down the identifier from there.  Note that you *won't* see this field if you're looking at it from an XP desktop.  You need to be on a 2003+ system.

1(b) not unless you're running something else.  Allowing server extensions should be enough to start with.  
2(b) I haven't come across .NET causing problems for the administration pages.  I think the problem is the corrupted install of sharepoint/fpse in that particular web.  I'm not sure what you mean by "selections" but I don't think this is your issue anyway.
0
 
Chief_ArchitectAuthor Commented:
Okay, thanks for the ideas. I tried your "owsadm" suggestion and it failed. Here's the command line error I received:

Error:  "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.
The version <6.0.2.6551> of the server extension you are trying to uninstall cannot be uninstalled with this tool. You must upgrade this virtual server to the current version, and then use owsadm.exe to uninstall."


What alarms me here is that I am always very careful about ONLY installing release software and Service Packs. I have no idea how a Beta version installed itself here. What I'm concerned about is what other damage might have occurred?

So, now what's the cleanest way to get out of this situation without installing more "Beta" sofware?

Thanks,
Greg
0
 
alimuCommented:
are you running 2003 or 2003 R2 version of Windows?
0
 
Chief_ArchitectAuthor Commented:
Alimu,

If you don't mind, here are some interesting questions we should consider....

1. How could this 6.0.2.6551 have ever been installed in the first place? (Especially, given my strict installation procedures?)

2. More interestingly:  How could this have only been installed for the mySite? (And not my Default Web site?)

Thanks,
Greg
0
 
alimuCommented:
gotta take off for the day and don't know if I'll be online for the next 12 hours (maybe, not promising anything)  but the answer to the above and where you got the server extensions software from (download, fp2002 cd, windows server install, etc) would help diagnose where this came from.

If you've never used frontpage or sharepoint in this web before, you can probably delete the _vti* directories safely and see if it's cleared its' status as having extensions installed.  If you have used them in this web, you might break stuff which it would be nice to avoid.
0
 
alimuCommented:
I *think* you might have installed the 2 from different media and ended up with 2 incompatible versions.  Hence my questions above - OS and media.  It only takes one button click to install the stuff so it's not that hard to miss having done it at some stage during install
0
 
Chief_ArchitectAuthor Commented:
Alimu,

***  I'm running Server 2003 Enterprise Edition SP1.

*** I do have FrontPage 2003 installed on this machine - if that helps at all.

*** You suggest deleting the "_vti" directories. I have NOT done this yet. Do you still recommend this?

*** I did install FrontPage 2003 on this machine from a single CD - nothing else. All installations have been from original released CDs. (Unless, of course, FrontPage was also installed as part of the Enterprise Editon install, or something like that.)

*** You suggest that I may have inadvertently installed from 2 different media. If I did, unkowingly, that would be easy to check in the registry settings, right? How can I check that, to rule this out?

I think we're converging on a solution. Please help.

Thanks,

Greg


0
 
alimuCommented:
Frontpage 2003 is probably ok, I've seen issues here and there with incompatibilities between versions but usually they crop up when different developers are running different versions rather than FP2003 having an issue with the server extensions.
This version of the development software still runs against FP2002 extensions.
The only thing I can suggest is that you continue to install the extensions from the same location.  If you use Add/Remove Windows Components --> Application Server --> IIS --> Frontpage 2002 Extensions or the "install extensions" from the IIS Management console, you'll be using the extensions that came with Windows 2003 OS instead.
 FP extensions come with the windows install, with the frontpage cd and also as a download from the MS site. All may be slightly different versions.

I would recommend uninstalling FP 2003 from the server - usually content editing isn't done there anyway and you'll avoid any issues with version mismatches between dlls.  It sounds like your currently installed version of extensions and administrative tools are 2002 so uninstalling them again shouldn't be necessary.

>*** You suggest deleting the "_vti" directories. I have NOT done this yet. Do you still recommend this?

*if* you haven't already frontpage-d this website (i.e. there's nothing frontpage extensions related like users and groups, etc that you need to keep) then this is probably worth a try and will involve less going around in circles :)
--Make a duplicate of your web content first (better safe than sorry), then stop the website (this releases any content files locked up by IIS).
--start out doing a search for all directories in that content called _vti_bin, delete them.  (other _vti directories may include frontpage specific
stuff required for form entries, etc in your web pages)
--start your website, go into the Sharepoint Admin Site and see if it gives you the option to extend the site.

*** You suggest that I may have inadvertently installed from 2 different media. If I did, unkowingly, that would be easy to check in the registry settings, right? How can I check that, to rule this out?
I'm sorry, can't tell you what to look for on this one - I would guess that this is what happened somewhere along the lines to cause the problem though.  As I said above, your admin stuff is now running at 2002 level which is what you want so if we can trash the frontpage stuff that's hooked into your problem web right now, we should be good to go.
0
 
alimuCommented:
how are you going with this?
0
 
Chief_ArchitectAuthor Commented:
Alimu,

Things are going well, thanks! I can see that we're on the right track now. Thanks for your suggestions.

I'm still investigating a  bit further. This has been a tough one. I'll post another update when I know more. (Hopefully in the next day or so.)

Greg
0
 
Chief_ArchitectAuthor Commented:
Alimu,

You did it!

The problem had to do with the fact that I had FrontPage 2003 installed on my server machine along with the FrontPage 2002 Server Extensions. The two do not coexist well.

This whole problem was a bit deceiving because it had nothing to do with Beta software, at all. When I installed FrontPage 2003, Office Update notified me that I should intsall Office SP2. This was the downfall. It looks like some .dlls were installed that were not compatible with the 2002 Server Extensions.

Interesting that I can't run FrontPage on my server. I thought that would be nice to have in the event of "quick changes". Oh well, I guess I'll have to use a remote machine.

Thanks for your help!

Greg
0
 
Chief_ArchitectAuthor Commented:
By the way, this is my first question posted. How do I give you credit?

I see several "Accept" buttons up in this dialog chain. Do I click on one of these? If so, which one?

Thanks,
Greg
0
 
alimuCommented:
ah... thanks for adding so much detail about the resolution.  it makes it a good PAQ.  Make sure your developers all use the same version of FP too, I've hit problems caused by version mismatches before (different functionality in each means they trample all over eachother).

To accept an answer you click Accept next to the comment that answered your question the best.

If you're in a question where a few different people have give together given you your answer, you use the "split points" button above the comment box (the one you type in) and split out the points between them.

When you accept your answer you also allocate a grade - if the answers as they stand are not worthy of an A, it's usual to try and get the additional information / explanation you're after from the Experts before grading the question or at the very least explain why you graded as you did.

Last of all, there's plenty of advice here: http://www.experts-exchange.com/help.jsp#hs5 - the help page section on closing questions.  The help file has pretty much everything you need to know about using EE.  (can you tell I'm a page editor *grin*)

glad it's all fixed up!
0
 
alimuCommented:
thanks!
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

  • 14
  • 10
Tackle projects and never again get stuck behind a technical roadblock.
Join Now