SharePoint – Heiserfamily Happenings

The cost of supposed fun!

breaker119 — Sun, 25 Sep 2011 00:15:51 +0000

So I’m trying to swing attending a SharePoint conference in Aneheim next week, and Aimee and I thought it may be possible to take the whole family, piggy back on the paid for hotel room, and then extend our stay a little bit. Being from southern California Aimee would have liked to use the opportunity to visit some friends, check up on her mother’s rental property, and we would have vistited my sister and her family while we were at it.

Of course, since we would be in Aneheim we’d have to go to Disney Land! I haven’t been there since my family moved to Texas from Huntington Beach in 1985, and I know that it has been quite some time for Aimee as well. Really, though, I thought Sara would enjoy it (although I know she is still a tad young to really get it). Here’s where the problem lies – Admission for our family would be $235! Yes, that’s correct $235! That is ridamndiculous! That’s before feeding ourselves! Forget it…out of the question…not for that price. I can maybe see it if this had been a long planned for trip, but apparently Disney takes themselves pretty seriously. Can you imagine what would have happened if Wally World had been open when Clark Griswald made it to the gate?

Teller: Hi welcome to Wally World
Clark : I’d like to buy tickets for my family. It is me, my wife and my two kids Russ and Audrey.
Teller: Wonderful – that will be $240
Clark: #E@E#@(!@&#^@&#@(! Two hundred and forty dollars?
Clark: Is that Canadian? What if my children were under 3?
Teller: Oh, in that case it will be $230

I just assume that you’ll let your imagination finish out that scene.

Needless to say, the family will not be going to the left coast with me this time. I’ll still try to see my sister and her family while I am there. I think that I’ll be skipping Disney Land, though!

Bing Search

breaker119 — Tue, 23 Aug 2011 19:45:57 +0000

Friends, I am by no stretch what one would call a developer, but lack of resources often requires me to dive into code on my own. I only needed to add a simple web search box to my SharePoint landing page, but I couldn’t find a simple way. Google has a simple method, but I wanted to use Bing as I find their search results often more accurate. Plus, if I’m already in the MS stack I may as well go ahead and use their brand.

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:



   

	  

   </A>

   

   

</FORM>

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

SharePoint 2010 – Search Error access denied

breaker119 — Fri, 19 Aug 2011 16:14:26 +0000

If you’ve been getting the below error in SharePoint 2010 you have probably come across the REGEDIT DisableLoopbackCheck fix.

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.