I am fairly new to working with Sharepoint. I did a complete install of Sharepoint on one server and set up our database on another server. I am in the process of making all of the necessary configurations to our install. However, I am having some trouble creating a SSP. I created two separate web applications to use for the SSP. I created a domain account to use for the SSP web services. After trying to create the SSP, I keep receiving an error saying "Provisioning failed: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)". I checked the event log and there are details about a number of exceptions, and it seems that the exception first occurs when the SPWeb.ApplyTheme method is called. Any help in diagnosing this error would be appreciated. Brian

Brian Did you get any feedback or make any discoveries on your issue creating SSP's? I'm having the same problem. I suspect its a permission issue related to the service account I'm using, but haven't proved that yet. Tim

Did you start and configure Office SharePoint Server Search service? I got the same problembefore, after starting and configuringOffice SharePoint Server Search service, it worked fine.And pleaseenter the username in "server\user" format instead of "user" or ".\user" in Office SharePoint Server Search page.I don't know if this is in your case, just hope it will work for you.

Hi, I got the same error and same case after stop / start the Windows SharePoint Search Service and Office SharePoint Search Service. The username using "domain\user" , the user added in domain group, SQL all roles and MOSS farm admin group. Even I create second / third SSP got the same error. Hope someone can advice.

I am likewise fairly new to sharepoint but have had earlier versions running just fine. I am having exactly the same issue as Brian (and have re-installed from clean 4 times so far). My service account(s) have been allocated full permissions in SQL server (2005), and I have even gone to the extent of adding them to the component service registry against the IIS WAMREG admin servicewith remoteand local permissions (found in another post). Any help would be greatly appreciated as this is beginning to get massively frustrating (and consuming far more time than it should). Regards. Mark.

I think the problem is that creating the SSP admin site is failing. Which Web Application are you trying to put the site into? Are the rights for that Web Application set up correctly?

how to check for those rights ? my first SSP is running fine but its give the error when i tried to provision new site An unhandled exception occurred in the user interface.Exception Information: Value cannot be null. Parameter name: uriString I dont know whats going wrong but i can see two entries in event logs with error Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: <local machine>] Also what i noticed is the no of tables in my first SSP (which is running fine) is 164 but for this new SSP its only 6 in the Shared Service database and the Search database is not even created. I have a single server deployment where both SQL server 2005 and sharepoint are on the same WS 2003 machine. Thanks

I am also have the exact same issues as all of you. Has anyone found a resolution?

What was the resolution for this?

I am having the same issues as above, can anyone recomend a resolution?

I have been watching this thread as I am getting similar errors but a different issue with SSP's.When is Microsoft going to address this question with a solution?

I do not have any problems creating SSP's in my MOSS 2007 farm.I am assuming that you have created a web application and are able to create site-collections in MOSS? If so,try using the same account to create you ssp,you can change it later to rule out any permission issues.In my case,MOSS is running as a domain account and I made that account a local adminin my MOSS\DB Servers.

Check to make sure that if you have antivirus software installed on your MOSS Server(s) that it isdisabled during the MOSS installation. I had this problem once when I was installing MOSS on a server that had McAfee Enterprise installed on it. I had to disable McAfee and reinstall MOSS. Once the install is done reinstall the antivirus software. If you have MOSS already installed on the server try disabling the antivirus software and preform a "Repair". Keep me posted though. Tony

Hi Even i was getting the same error while creating SSP. Then i gave the user account Log on for Windows Sharepoint Services Timer in services and it started the provisiong process.I have the same log on for Windows sharepoint sevices search and timer.Hope this helps.Shobha

U mentioned you created a domain account to use the SSP web service. have you tried using the SA account (the one u install MOSS with). does that give an error as well?thanks505

Hi,I have been facing the similar issue.My ssp creationused to stuck at in progress page. I clicked back button of the browser to end up this un ending wait. The result was intermediate creation of SSP. I changed the Timer service account to my domain account which was which was the administrator of the server machine and sharepoint installation was done with the same account.Yes it worked :)Thanks a lot Regards,Beenish Tanweer

I had the same problem. What fixed my problem is making sure the account running the sharepoint services also has administative rights on the farm. Do this by adding that account to: Central Administration > Operations > Security Configuration > Update farm administrator's group.

SSP failed to be created, generating errors like: "Timed out waiting for SSP.................." "check event logs............" "SSP provisioning will be retired...................." OR "An unhandled exception occured in the user interface.Exception: Value cannot be null. Parameter Name:UriString" OR In event viewer: "Login failed for user 'DEV\svc_mossfarm_tel'. [CLIENT: <local machine>]" Resolution (for me): It was the "Windows SharePoint Services Timer" services that was down. Most probably due to a change of service account password. So, I went to Services, put in the current password and started. SSP was smoothly created after that. Hope this helps-- Rehman. Rehman Gul