Also, you don't mention the version - you're using the 2002 extensions?
Main Topics
Browse All TopicsI'm having a problem getting the FrontPage search component to work on a newly configured Windows 2003 Server that is running IIS 6.0. The install was configured as an application server with only the FrontPage server extensions option selected (no .net)
When you view the page you get the following message: [FrontPage Search Component] and the component does not display (no box to type in search criteria).
No matter what I try, I can not get the FP search component to work. I tried other FP components such as a counter and it works. I do have indexing running on the server. I am able to query the windows catalog and I do get results back.
I have done the following:
1) Recalculated hyperlinks
2) Checked server health and repaired any problems
3) Recalculated the web
I have gone as far as uninstalling the app server and reconfiguring it. No matter what I do, I can not get the search feature to work. I have the same functionality working on a Win2k server running IIS 5.0 and I haven't had any problems with it.
Any solutions would be greatly appreciated!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
And you have done the following to enable the Indexing Service Web Extension:
1. Click Start, point to Administrative Tools, and then click Internet Information Services Manager.
2. Expand ServerName, where ServerName is the name of the server, and then click Web Service Extensions .
3. In the right pane, right-click Indexing Service, and then click Allow.
4. Quit Internet Information Services Manager.
seanpowell:
1) No this is a standard HTML page - no asp is involved.
2) These are 2002 server extensions - installed right from the Windows 2003 server disk when the application server was configured through the wizard.
3) When I followed your instructions to verify that the index service is enabled in IIS, I did not have an option to enable indexing in the right pane. All I'm able to do here is allow/disable components such as FP server extension, server-side includes, asp, etc. If I right click on the default website - under the home directory tab, the option to "index this resource" has been checked. If I go to "manage my computer" and look under the indexing service, I do see that inetpub/wwwroot is being indexed.
The actual version of the FP 2002 server extensions is v5.0.2.5012 if that makes a difference.
Yesterday I also tried downloading the 2002 server extensions from Microsoft's site (which happened to be an older version) and I experienced the same problem with them.
This morning I uninstalled the application server and reinstalled it using the server extensions that were supplied on the Win2003 Server cd.
Here's a copy of the code:
<html>
<head>
<meta http-equiv="Content-Langua
<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
<meta name="ProgId" content="FrontPage.Editor.
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<title>test</title>
</head>
<body>
<p>test</p>
<!--webbot bot="Search" S-Index="All" S-Fields S-Text="Search for:" I-Size="20" S-Submit="Start Search" S-Clear="Reset" S-TimestampFormat="%m/%d/%
</body>
</html>
I actually tried something similiar today. I have an existing search running on our current production (Win2k with FP2002 extensions). I copied and pasted the code from this server into the html page that resides on the Windows 2003 Server. The search still failed.
Here's an extract of the code that I got from our Win2k Server (production server) that functions properly. This same code fails on the Win2k3 server:
<!--webbot bot="Search" S-Index="All" S-Fields="TimeStamp,Docume
Notice that the code from the existing and functional server has the b-useridnexserver set to 0 rather than 1. I tried it both ways on the new 2003 Server and it still failed.
I checked the Server extensions and the only problem it found was the recommendation to "tighten security" - which I did let it fix. I also recalculated the server extensions. No matter what I do it doesn't fix the problem. I bet I have checked server extensions and recalculated at least 20 different times now.
I'm starting to wonder if anyone has succesfully implemented a search component on a Win2k3 Server? Might this be a bug with Win2k3?
Are you using UNC Content?
From Microsoft:
Index Server Does Not Support UNC Content
As of this writing, Index Server on Windows Server 2003 only supports indexing of local content; therefore, UNC content searching is not supported. In addition, FrontPage Server Extensions 2002 on Windows Server 2003 no longer includes the Wide Area Information Server (WAIS) search engine, which is used by FrontPage webs that use a search component. As the currently recommended replacement is to use Index Server in place of WAIS, FrontPage webs using the search component will not work on UNC-based storage.
I am not using UNC content. I am only indexing the local content that resides within the c:\Inetpub\wwwroot\ folder and the search fails. If I query the local index server catalog, the infomation is there. The problems appears to be with the link between the indexing service and FP2002 server extensions.
Ok...I couldn't wait any longer so I dumped $ 245.00 into Microsoft's pocket to get a solution on this issue. Can I award the points to myself? *grin*
Here's what I found out:
By default, Windows 2003 Server does not install the indexing server. You should actually see an option in the IIS console to "allow" or "prohibit" the indexing service under the Web Service Extension section.
The solution:
1) Go to "add/remove components" - "Windows Components" and uncheck the indexing service so it can be uninstalled.
2) Reboot the system
3) Go back to "add/remove components" and reinstall the indexing service.
4) In the IIS console, under "Web Service Extension", "allow" the indexing service.
5) Recalculate the website
The search should function properly!
I expressed concern to Microsoft that many others are experiencing this problem and more than likely they will create a knowledge base article for this problem.
So my comment from above:
1. Click Start, point to Administrative Tools, and then click Internet Information Services Manager.
2. Expand ServerName, where ServerName is the name of the server, and then click Web Service Extensions .
3. In the right pane, right-click Indexing Service, and then click Allow.
4. Quit Internet Information Services Manager.
Only applies after the indexing service is uninstalled and then re-installed? Just trying to make sure I understand...
Yes, it only applies after the indexing service is uninstalled and re-installed. Do you see the indexing option before doing the uninstall of the indexing service? My scenario is based on a clean install of Windows 2003 Server. Based on the conversation with the tech, the scenario might look different for a server that was upgraded.
Here's the solution that Microsoft provided to correct the problem for me:
By default, Windows 2003 Server does not install the indexing server. You should actually see an option in the IIS console to "allow" or "prohibit" the indexing service under the Web Service Extension section.
The solution:
1) Go to "add/remove components" - "Windows Components" and uncheck the indexing service so it can be uninstalled.
2) Reboot the system
3) Go back to "add/remove components" and reinstall the indexing service.
4) In the IIS console, under "Web Service Extension", "allow" the indexing service.
5) Recalculate the website
The search should function properly!
I expressed concern to Microsoft that many others are experiencing this problem and more than likely they will create a knowledge base article for this problem.
Hi all,
Same problem, but I'm not able to reinstall the Indexing Service because it doesn't matter if I check it or uncheck it, it seems to be installed: service is running, checkmark won't show up.
So I would ask slimjim28 to tell me:
What are the required files by that Indexing Service under Web Service Extensions?
I don't think it'll help but this seems to be the last chance...
Thanx,
copas2
Business Accounts
Answer for Membership
by: seanpowellPosted on 2003-10-23 at 09:43:43ID: 9608118
Just want to make sure first that your search page is not an asp page, correct?