Tag Info

The problem i've encountered was linked to the reference i was using.. I used Microsoft.SharePoint.Search.Query instead of Microsoft.Office.Server.Search.Query In the version i was using it was impossibile to query sharepoint giving him parameters and so on... But the firm of every class and method was the same.. Now it works! Thanks to all!

SharePoint Search does by default not index unapproved items as well as draft versions (minor versions). This is so because the search crawling account only has read access to the content and only users with contribute access or better can see unapproved documents and draft versions. Consequently, you could get around the issue by granting contribute access ...

I'm guessing that Tag is a Managed metadata column? If so, doing an equals compare using Column = 'Value' won't work, as the actual text in the property could potentially hold more values, lookup value based managed metadata properties store the values differently in the index. So you would have to use a CONTAINS or a LIKE. Any search using a lookup column ...

Installing Search Server Express effectively replaces Foundation Search and in fact, enhances it. Check that you have a Service Application created for search and that the service is running. Microsoft TechNet has good information on the subject of configuring Search Server Express: http://technet.microsoft.com/en-us/library/ee808897.aspx

This is a problem we have encountered time and time again. Downgrading SharePoint is a pain in the proverbials... Basically the only known way of doing this is backing up your data, removing and reinstalling SharePoint on the machine in question. So as you said the solution is: "In a previous attempt (different environment) to remove Search Server ...

Whilst the Search Topology configuration is fully operational in Search Server Express, I can't think that there is too much you could usefully do with it. This is all about putting multiple crawl and query components on different servers, which isn't possible with the Express edition. I think this error message is the (none too helpful) result. If you have ...

The problem turned out to be a policy applied in Active Directory that messed with default permissions. A post from the TechNet forums pointed me in the right direction.

Why aren't you using: <QueryPacket xmlns='urn:Microsoft.Search.Query' Revision='1000'> You query doesn't look like a fulltext query, but like a keyword query, it that correct? A reference can be found here to build the different queries: http://www.itidea.nl/index.php/example-of-using-the-spservices-search-web-service/ Probably the date format ...

Sharepoint by default only crawls major version of content, because the content acces account only has read permissions one the sharepoint site. For more details on search and security trimming... http://support.microsoft.com/kb/2304855 http://www.sharepointblues.com/2010/03/17/draft-item-security-search-results-security-trimming/ Hope it helps.