Microsoft shared service provider 2007

Sunday, February 25, PM. Thanks a lot Kiral. That fixed the problem for me. It really makes sense since a new top level site wouldn't know what accounts need to be in the admin group other than the account creating it.

Saturday, March 3, AM. Has anyone run across this situation: I cannot logon to Shared Services with the account used to install it, or any other account? Thanks, Matt. Monday, August 13, PM.

Wednesday, September 12, PM. Try logging in with that account. Saturday, September 29, PM. But nothing happened and still can'taccess the ssp admin site If I change the Authentication provider to Enable anonymous access, I can see admin site for one or two clicks. But no result. Saturday, October 6, AM. Saturday, October 6, PM. Monday, October 15, PM. Edit: I finally found the answer, it was just much further down the google tree than I normally go.

It worked like a charm! Saturday, October 20, PM. What I concluded and is not obvious from the documentation is that there are two 2 application pools associated with the SSP: One, is created automatically by the SSP creation process and it is named exactly like the SSP. If this was made clear from the beginning, we might not be tempted to name the SSP and the Admin site's AppPool the same. Monday, October 6, PM. But it's easy to get confused. When you go to assign a site collection administrator, note that you can choose another web application.

You need to choose the one associated with your Shared Services Provider site. Each web application can support multiple site collections. Each site collection may have both a primary and secondary site collection administrator. So, if you go to Central Admin, Application Management, Site Collection Administrators, and see your account as the secondary site collection administrator, you might be confused and think your account is assigned access to the shared svcs provider.

But look carefully at the drop-down "Site Collections" and explore a bit further. Click the radio button beside Web application pool. Select the application pool where you want to change the identity, for example: Sharepoint - Select the Configurable radio button. Provide the user name and password. Also be sure to use a strong password. Click OK. To restart the application pool, either open IIS and recycle the application pool, or open a command prompt and type iisreset -noforce.

Open your SharePoint site in a browser to confirm that the change was successful. Open SharePoint Central Administration in a browser to confirm that the change was successful. Under Search, click Search settings. Click Default content access account. Enter the credentials, confirm the password and click OK.

I have a few questions from the given information though Question set 1: If I need to update the password for the service account, then how can I currently access Central Administration and other areas having this service account assigned?

Shouldn't I also get an error for those areas? Question set 2: If updating the password is needed, what are the steps involved in doing so? And, how will it affect the use of SP? Is it best to do this on off hours? Warning 1: The identity of application pool [App Pool Name] is invalid. The user name or password that is specified for the identity may be incorrect, or the user may not have batch logon rights.

If the identity is not corrected, the application pool will be disabled when the application pool receives its first request. If batch logon rights are causing the problem, the identity in the IIS configuration store must be changed after rights have been granted before Windows Process Activation Service WAS can retry the logon. If the identity remains invalid after the first request for the application pool is processed, the application pool will be disabled.

The data field contains the error number. Event ID: Warning 2: Application pool [App Pool Name] has been disabled. Windows Process Activation Service WAS did not create a worker process to serve the application pool because the application pool identity is invalid. Please note i am still working through some of the errors and will update this post as i find the answers. I could no longer login to the server because the snapshot was older than 30 days - the computer account for the server had expired and so needed to be reset and reconnected to the domain.

See this blog for steps to fix this. The Central Administration site was the only site appearing in IIS even though all the web applications were still there.

To fix this: Delete the old web application using Central Administration. Recreate the web applications with Temp DB names.