Corey Roth [MVP]

Pingback from  Twitted by coreyroth

Hi Corey!

Great Webpart, many thanks for this. Unfortunaltely I have one problem. I installed it in our development environment and it worked fine. Unfortunately I an'T get it running on production! Adding the webpart to the search page results in this error:

"Unable to add selected Webpart(s). Wildcards Search Core Results Webpart: Could not load file or assembly or one of its dependencies. Access is denied.

Do you have any idea what could cause this error?

Many thanks for your help!

Regards

Alex

Make sure you have .NET Framework 3.5 installed on your production server.  If you do confirm that the DLL actually got deployed to your bin folder on your particular web application.

fantastic idea, install was clean (v1.0R5), but when I add the webpart, there is no actual search field to enter criteria into.  Suggestions?  Thank you in advance for even making this available to start with.

Which page did you add this web part to?  Typically, you will edit your existing results.aspx page (which should already have a searchbox).

Corey, I want to use this as a People Search and I have it working from my homepage with the default site search as it passes the S= query string for scope.

However, when you use this with a people search box there are a few options to pass scope as an appended query string, etc. but it doesn't seem to work. any ideas?

Hi Corey,

Will the webpart work on 64bit architecture? I have run through the install and cant find the feature under Site Collection Features or Site Features?

It should.  Check your Solutions page in Central Admin and confirm that the solution package installed successfully.

Hi Corey,

I checked the solution page and found and error with the solution.

Access to the path 'C:\WINDOWS\TEMP\tmp42F.tmp' is denied.

<servername> : Access to the path 'C:\WINDOWS\TEMP\tmp42F.tmp' is denied.

I have tried to deploy the solution several times with different Administrator accounts and no joy.

Do you have any idea what i may be doing wrong?

Hi Corey,

Great web part - thank you for all your effort! We have been using this in our Production environment. Works great except we could not get the relevance to work properly. Is there something we are missing?

To give you an example with SharePoint default functionality if I'm searching for a keyword and there is a site by that name what would come ahead of a document in a library, right? But after installing this solution this is not the case any more. Is anyone else having similar issue?

Thank you for any suggestion.

Bright Sky

@BrightSky I'm sure this is because wildcard search uses a full text sql query.  With SharePoint 2010, I don't think this will be an issue for you.

Hello Roth.

I installed your web part on MOSS 2007, add to the page results. It works only with advanced search and without wildcards. In simple search no results are displayed. Any Idea?

Thanks

Hi Corey, I downloaded this web part and it's working fine if we search for documents starting with name "ML0611*". But if we search for "*0611*", it's not returning any results. Any idea?

@Yasu I'm afraid SharePoint search doesn't support prefix wildcards like the one you described.

Our intranet site consists of mostly PDF documents & these PDF documents are generated from office documents.

We have Taxonomy in place and have added metadata Site Columns to set right properties to the documents.

But when we search the PDF file properties are being read along with the metadata site column contents

How to exclude document file properties from being indexed for a search.

otherwise we have to go and manually edit file properties for several PDF documents.

hi Corey

Our intranet site consists of mostly PDF documents & these PDF documents are generated from office documents.

We have Taxonomy in place and have added metadata Site Columns to set right properties to the documents.

But when we search the PDF file properties are being read along with the metadata site column contents

How to exclude document file properties from being indexed for a search.

otherwise we have to go and manually edit file properties for several PDF documents.

@Sony I am afraid there isn't a simple way to do that.