I'm building a completely new farm with all the latest patches and when I create the SSP it lets me create individual Application Pools for MySites and the SSP itself and I can confirm creation which gives me the lovely spinning icon:
And it just sits there for 10 minutes...I didn't want to close it so I opened another window with Central Administration.
Finding the error
The SSP link in Quick Launch is disabled, but clicking on the Shared Services Administration page gives me this:
Finally after 15 minutes the progress page comes back with a Failure message. It clearly failed way before that but still kept spinning! LOL
The ULS Logs gives the same error: "A runtime exception was detected. Details follow. Message: Windows NT user or group 'domain.wa.gov.au\SP_SSPAppPool' not found. Check the name again. ". But nothing more than that.
vNext Error reporting
The Note is not very clear:
"If you correct the error that caused this failure, provisioning will subsequently succeed. To stop provisioning from being retired, delete the SSP."
It doesn't tell you how to correct the error, I mean I can go into IIS and modify the Identity of the application pool, but if I try and go through SSP configuration it fails with an error when editing the Application Pool.
Deleting SSP
And deleting the SSP is an option in the User Interface! The link is disabled!
So the easiest way to recover from this...is delete the SSP using (had to delete Web Applications first for SSP and MySites):
1: stsadm –o deletessp –title SharedServices1
and then run through the steps again. This MSDN forum post help a lot.
Windows 2000 compatible domain
So this didn't work as some of my other accounts had the FQDN domain like 'domain.wa.gov.au' instead of 'DOMAIN' and so I had to go through where ever I've set service accounts and change them! The weird thing is that the FQDN ('domain.wa.gov.au\sp_admin') worked fine in the People Picker when setting the accounts and resolved, but obviously causes issues whenever it hits SQL! So best bet is just to use the DOMAIN within SharePoint. Lesson Learnt.
Not sure why it has only come up when creating SSP as install went fine! Once I'd done that the SSP page changed to "Provisioning in Progress":
I also noticed in the event log getting same errors for Search and this has now gone too! It always pays to check the logs for each step as you install SharePoint.
Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server General
Event ID: 7888
Date: 12/11/2008
Time: 4:55:56 PM
User: N/A
Computer: SOMSP01
Description:
A runtime exception was detected. Details follow.
Message: Windows NT user or group 'domain.wa.gov.au\SP_MOSSSearch' not found. Check the name again.
Techinal Details:
System.Data.SqlClient.SqlException: Windows NT user or group 'domain.wa.gov.au\SP_MOSSSearch' not found. Check the name again.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.Office.Server.Data.SqlSession.ExecuteNonQuery(SqlCommand command)
at Microsoft.Office.Server.Data.SqlServerManager.GrantLogin(String user)
at Microsoft.Office.Server.Administration.SharedDatabase.Microsoft.Office.Server.Administration.ISharedAccessControl.SetAccessControl(SharedComponentSecurity security)
at Microsoft.Office.Server.Search.Administration.SearchAdminUtils.GrantAccessToAccount(String username, ISharedAccessControl sharedAccessControl)
at Microsoft.Office.Server.Search.Administration.SearchSharedApplication.Install()
at Microsoft.Office.Server.Administration.SharedResourceProvider.ProvisionApplications(SharedComponentSecurity sharedApplicationSecurity)
at Microsoft.Office.Server.Administration.SharedResourceProvider.Microsoft.Office.Server.Administration.ISharedComponent.Install()
at Microsoft.Office.Server.Administration.SharedResourceProvider.Provision()
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.