Unfortunately, Microsoft stopped supporting their method of simply adding a search box in favor of the more robust Bing API. More power to them, but as I stated before – I am not a developer. APIs and API documentation are useless to me unless they come with exact code samples. I could not find a one…lot’s of code, but none of it complete. After doing some research and scrounging I ended up with this:


<FORM method=GET action="http://www.bing.com/search" target="_blank">
<A HREF="http://www.bing.com/" target="_blank">
<IMG SRC="/PublishingImages/img_windowsBingLogo.png" border="0">
</A>
<INPUT TYPE=text name=search_phrase size=42 maxlength=255 value="">
<INPUT type="image" SRC="http://www.bing.com/siteowner/s/siteowner/Spyglass_20x20.gif" alt="Search Bing!">
</FORM>


Make an html out of it and render it in a Page Viewer web part. It works like a champ for me.

Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has “Full Read” permissions on the SharePoint Web Application being crawled.

This seems like an easy fix – you know – just add the new DWORD entry. Well, I did that a week ago, and it didn’t solve my problem. 5 days of trying everything under the sun I went back to check the registry entry. HERE IS MY ADVICE TO YOU – take note that when creating your new entry “DWORD (32-bit) Value” and “QWORD (64-bit) Value” are right next to each other!

As it turns out, when I created my new DWORD entry for DisableLoopbackCheck at 1:30 am I accidentally created it as a QWORD. This, if you hadn’t guessed already, doesn’t work. So – lesson learned. I’m now down from over 29,000 errors to less than 3,000, and those are largely due to poorly named files in an email enabled list.