Posted at: 09:44 on 21 May 2009 by Muhimbi
I keep running into this problem and wasting hours Googling for the solution, which is why I have decided to write a quick post to prevent the same from happening to others.
The symptoms are as follows: You are installing an instance of MOSS 2007, everything is going well, the account you are using is an administrator in all the places where the account should be an administrator, you get to the bit where you are going to configure the Shared Service Provider and BOOM! access denied.
You double check all privileges, farm administrators, application pool accounts etc, read well meaning advice from other users experiencing something similar, but basically you are not getting anywhere.
Then you hear the faint sound of a 10 pence coin drop (we don’t do quarters in the UK)… didn’t Microsoft introduce some security fix to prevent systems to be accessed using a name other than the machine’s hostname? This machine’s name is someserver1 while the SSP is hosted under portal.companyname.local/ssp/admin.
In order to solve the problem, apply this registry change as described in KB926642. Everything is humming along fine now.
Update: ‘SharePoint Master’ Spencer Harbar has written a good article about the reasoning behind this security feature'.
.
Labels: Articles
19 Comments:
Thank you!!!! This finally helped me get in.
By
TheMAN, At
01 June, 2009 22:40
THANK YOU! We have been struggling on this for weeks now! Never put 2 and 2 togerther that it could be the loopback check causing the issue.
By
Anonymous, At
03 June, 2009 20:19
BINGO! Thanks a lot!
By
Anonymous, At
10 June, 2009 19:05
Just another post that say: THANK YOU!!! I wish I would stumble on this article 3 hours sooner...
By
Anonymous, At
25 June, 2009 10:05
Whoop! You ROCK!
By
Anonymous, At
27 June, 2009 02:52
THANK YOU!! So the other similar issues were a massive red herring. Would have saved best part of a week messing about if i'd found your article sooner
By
pauly, At
04 August, 2009 14:56
I can acces with firefox, i don´t need change nothing
By
Enamorados, At
05 August, 2009 21:07
Man you just saved me! I have been pulling my hair out over this for days now. Thank you so much!!!
By
Anonymous, At
12 August, 2009 05:23
One more post of amazing thanks, great job!
By
Anonymous, At
15 October, 2009 02:35
that one really a sweety stuff... thanks so much dear !
By
Anonymous, At
03 November, 2009 20:19
One more voice in the crowd here, letting you know that this solved weeks' worth of pain and gnashing of teeth. Thanks for documenting that one, M$!
By
Anonymous, At
03 December, 2009 02:11
I have done EVERTHING, creating a new app pool with the right account and associate the SSP Web app to it, I have create the disableloop key and STILL have the problem.. Any more ideas?
By
Anonymous, At
21 January, 2010 05:48
Nop sorry, the solution discussed in this post usually solves the problem.
By
Muhimbi, At
21 January, 2010 08:35
Is this true of (will this work for) Windows Server 2008 as well?
By
Anonymous, At
14 July, 2010 23:31
Yes, this is true for any modern Windows Server OS.
By
Muhimbi, At
15 July, 2010 09:15
Does this reg fix work for Server 2008 as well?
By
Anonymous, At
19 November, 2010 04:28
Yep, server 2008 as well.
By
Muhimbi, At
19 November, 2010 08:09
plz help how to use this product in sharepoint server 2010
By
sri, At
14 July, 2011 08:12
Hi sri. This works the same on SP2010. If you have any specific questions you need help with then please click the 'Contact Us' link at the top of the screen.
By
Muhimbi, At
14 July, 2011 09:43
Post a comment
Subscribe to Post Comments [Atom]