Hello there
My intranet site is Windows Sharepoint Services (WSS) which is running on MSDE (Sharepoint) not SQL Server.
I have downloaded your adm file and added to group policy.
In Group Policy under user config.
In the search tab of Windows Desktop Search I have set the Primary intranet search location.
I have set as follows: intranet,http://servername/_layouts/1033/searchresults.aspx k=$w
when i actually search it finds a load of docs on network email as normal.
but when i click on the new intranet tab it opens WSS in a search tab but never finds anything.
What am i doing wrong is it the fact i am rnning WSS on MSDE and not SQL Server.
microsoft dont mention that i need SQL so hopefully it something else simple
thanks
WDS and WSS
robinsenior
hey Jeff
just havent had a chance to look at it much last few days but appreciate your follow up.
Sure at least i have an answer to this.
thought it might have something to do with this alright, but i couldnt find anything to say this
Thanks again
Alejandro Rodriguez
Hi SoHandy,
When I mentioned SPS I was referring to SharePoint Server WSS is Winows SharePoint Services. WDS supports both of these.
'I didnt specify anything i just entered a space so i could enable it.'
By Default WDS loads the IFilters and Protocol Handlers listed below for WSS/SPS and other stores as well as Outlook, Outlook Express, Office files, HTML files etc.
I think we have a winner... When using the Group Policy to Prevent Unwanted IFilters and Protocol Handlers Please Note that because of a limitation in the Group Policy editor, you must add at least one entry in the allow list. If a blank entry <single space> is made in the allow list it will accept it however it will also stop WDS from indexing even the default file sets that were originally configured with WDS. When using this registry key WDS will only use the IFilters and Protocol Handlers listed in the allow list. If this list has only a white space in it, you are effectively telling it not to use any IFilters or Protocol Handlers and would severely limit the products functionality.
If this is what you have done, I'm honestly suprised you are able to index anything but text files properly.
To restore functionality, you can either enter the GUIDs of the IFilters and Protocol Handlers you want to use or enable this policy.
The IFilters and Protocol Handlers GUIDS that come with WDS by default are as follows:
Type GUID File Types Enabled
When using Policy Manager to edit this policy, be sure to enter the above GUIDS in to the Allow List. When entering the GUID(s) make sure you include the braces ‘{}’ as they are required.
If a file type has an associated IFilter the file type will be registered at the following locations:
HKEY_CURRENT_USER\Software\Classes\ext
HKEY_CURRENT_USER\Software\Microsoft\RSSearch\ContentIndexCommon\Filters\Extension\.EXT
In the example above .EXT is the extension you are looking for. The .EXT key will have the GUID for that file type listed in the CachedFilterIID or Default value respectively.
let me know if this helps. :)
Efraim Kyriakidis
Hi ya,
sorry I didn't get back to you sooner... Things have been a little nuts.
The URL looks exactly correct, no spaces between etc. So if that's correct then we may want to look at any other possible things that may be conflicting such as a group policy etc. For other group Policies I'd look at things like 'Prevent Unwanted IFilters or Protocol handlers'. When you enable that you need to specifically add the IFilters and Protocol Handlers you want enabled to the Allow list. Also Index Only Email and My Documents may cause what you are describing as well...
Troubleshooting 101.
If it works on one system but not another, what's different about the system that's broken (besides the fact that it's broken of course) Do you have any dev software or special filters or virus software that's unique to your system Did you test the Policies on your system first If so did you leave any behind that may be impacting now Do you have any machine preferences that may be impacting
Machine Preferences are under HKLM\Software\Policies\Microsoft\DesktopSearch\
User Policies are at the same location only under HKCU
The other thing is the Protocol Handler for SPS may be munged or a wrong version I'll have to look in to that one and see how to verify that for you.
Let me know if that helps and I'll try to get back to you sooner this time!
once again sorry 'bout that!
Best regards,
Jeff
aboreham
Hey Jeff
i literally only enabled this option yesterday for the first time.
since i have installed last week i only have had primary search location set, thats it.
i hasnt worked with just that. i only started enabling these others since you been emailing me.
i have set the filters with what you specified just there but still no results again just opens the search page
Flip
Try changing the URL to the following:
intranet,http://sitename/Search.aspx k=$w
let me know if that helps!
Steve Boyd
Hi Sohandy,
To help keep unresolved posts down to a minimum I'm now following up with a post's original author to see if the latest reply to their post has helped, answered their question or remind them to provide additional information. If the original author does not reply to the follow up, I will often delete the thread (again, to keep unresolved posts down).
That said, did Jeff's reply help
Thanks in advance,
Bill Connors
Program Manager, Windows Desktop Search - Communities
Posts 31
Was this post helpful
Edit Post | Delete Post(s) | Split Posts | Lock Post
Try changing the URL to the following:
intranet,http://sitename/Search.aspx k=$w
let me know if that helps!
kharulli
After doing some digging I found that the MSDE backend of SharePoint Server (SPS) does not include a query interface. News to me, I had thought that SPS regardless would allow querying.
This is apparently not the case. If it does not have a SQL backend the Search Interface is not available, thus WDS gets no response from the SPS.
This would explain the issue you are seeing. I wish I had a fix but I don't currently see a way around this issue. I'll keep digging but the way it is currently I think going to an SQL backend is the only resolution to this issue.
Best regards,
Jeff
Gurumeet_WebTech_India
Hey Jeff
no bother. i have only emails and my doc indexing, i have enabled ifilters and protocol.
i didnt specify anything i just entered a space so i could enable it.
all i have enabled is the primary search location thats it.
so with your intstructions i have 2 things enabled.
i never installed the policy on my own pc so nothing there.
just keeps coming back with no results.
i have it on XP with SP2 which is my own but just installed on a 2000 Pro SP4 system as well. Still getting no results just opens the search page.
the other thing you mentioned regarding protocol handler. you stated SPS.
are you talkin about Portal Server if so i dont know if this is the same as Windows Sharepoint Services. This is the one that comes with 2003 server out of box its not the full portal product we would have to upgrade to this.
sorry if you have coped this already
thanks