Three strikes your out, DisableLoopBackCheck

Here’s an oldie but a goldy, cause it’s still their and as far as I know of it’s not a SharePoint issue but something of IIS.

Here’s the problem: If your trying to login to a site and you’re promped for a user name and password and full of enthausiasm you enter the credentials, one, two and THREE and boom theirs the with screen on the end of the tunnel. IE or any other browser is giving you the cleanest web site ever cause it’s completly blank.

To solve this you need to add a registry key to all the web front end servers in your farm.

1. Open the Registry editor, Start >> Searchbox >> Regedit (make a SnapShot or registry export first).
2. Go here,HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. Add a new DWORD vallue and name it DisableLoopBackcheck.
4. Enter the new DWORD key and give it a value of 1.
5. With every registry change you need to reboot your server and beware all clients will be thrown off.

When you test it you see it’s working but maybe your site continues loading and loading forever.
In that case it’s not yet added to the trusted site zone of your browser.

Check this Microsoft KB article for more info about the issue,  http://support.microsoft.com/kb/896861

Update

Recently I found the PowerShell equivalent to disable the LoopBackCheck for the double hop problem. So I just copy and paste the script reboot and ta daaaaa, it’s working.

Just open PowerShell and add the SharePoint snap-in Add-PSsnapin Microsoft.SharePoint.PowerShell

No run the script below and reboot your system.
New-ItemProperty HKLM:\System\CurrentControlSet\Control\Lsa -Name “DisableLoopbackCheck” -value “1” -PropertyType dword

The trail period for this product has expired

A moment a go I was toying around on my home portal and created some nice trouble for myself. I made some site collections with host headers and all seamed to work. Then I installed Office Web Apps and when I tried to activate the feature on the site collection I got an error saying file not found.

huh………….

Than I tried opening my portal and got the error as shown below, Double huh……………    😦

I removed my host headers and I could access the site again only stil “File not Found” when I tried to activate the feature. When I adjusted the AAM (Alternate Access Mapping) I could activate the office Web Apps feature smoothly.

Only now I want my host headers back. After filling them out again I got “The trail period for this product has expired” message again. But I never installed any trails or what so ever (triple hun…….).

After a walk with the dog and some fresh Google energy I found a temp solution.

1. Add the Pool accounts for the web applications using host headers to the BUILDIN\Administrators (group, local).
2. You will get a new error in the health analyzer, saying you use pool accounts in the local admin group but you just have to find a way to life with it or take a beer or 12 a day to coop it.
3. Then you need to iisreset /noforce, pray and start to smile again.

 

Problem solved, up to the next one.