Hi all, I have a strange issue with SSP when setting up a clean SharePoint Server 2007 SP2 on a Windows 2008 R2 x64 : I create a web application dedicated to host the SSP. I set up the SSP with no error. Result : I get this Event Log error : Failed to load the SafeControl assembly paths for web.config and I cannot open SSP admin page. After multiple re-installation, I found a "solution" : I create a web application dedicated to host the SSP (again) I create a site collection into this Web App I set up the SSP Result : SSP is working well, no problem. The question is : why should I create first a site collection in my web application before setting-up the SSP ? I feel that SSP setup is making mistake on the web.config that site collection setup doesn't. Have someone reproduce this issue ? Is it a bug ?

Hi Adrien, Sounds like you may have been using a new app pool for the ssp web app and had not recycled the app pool after the web app creation... Please let me know if this is the case... Cheers, -Ivan Ivan Sanders My LinkedIn Profile, My Blog, @iasanders.

Hi Ivan, Thank you for your answer ! In the two cases I have created my dedicated Web App with their own application pool. But I always ran IIS Reset (after creating Web App, even after creating SSP). During my tests, I even reboot server between the creation of the Web Application and the setup of the SSP. Between all my test, I have formated the server. I also tried an installation using a unique administrator account (to avoid any right issue).

Hi, It is not a bug. The SharePoint will create ssp site collection automatically (I have tested it in my vpc). For your situation, I think you should disable the lookback check and try again. For how to disable it, please refer to: http://support.microsoft.com/kb/896861 Hope it is helpful! Seven