Hello, I'm setting up a MOSS2007 server.I followed the setup instructions from the sharepoint admin console, there are no servers to add except the one it's installed on, and so I moved onto service setup and configured all the services to run under a service account created for the task.The next item is SSP creation.I have setup two web applications running under non-local service accounts and then use these in the SSP creation process.The problem is that when I enter the SSP server credentials,I enter DOMAINNAME\USERNAME as I have with the services setup.I get the error 'Provisioning failed: Windows NT user or group 'DOMAIN.com\USERNAME' not found. Check the name again.However, I didn't type domain.com, sharepoint seems to have just appended this of it's own accord.Next I tried using a completely different account to setup an SSP. The setup fails and gives me the same error with the same username as before - completely ignoring my typed in username which was nothing like the original. Therefore sharepoint seems to be either storing the original attempted username (with the added '.com') or getting it from somewhere and ignoring the credentialsI type in.Can anyone tell me what might be wrong? Thanks, Stu.

bump! can't anyone help? How about a small prize? a token cake or something?...Thanks, Stu.

Do you mind posting info from the logs when this was going on? That may offer a clue.Thanks! - M- Michael Mukalian - MCTS: MOSS 2007 Configuration - http://moss2007stuff.blogspot.com

Sure, these are the three most relevant posts. I might go checkout the component services admin tool & see what can be set there... Event Type:ErrorEvent Source:DCOMEvent Category:NoneEvent ID:10016Date:14/08/2008Time:11:58:39User:DOMAINNAME\USERNAMEComputer:ServerNameDescription:The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {61738644-F196-11D0-9953-00C04FD919C1}to the userDOMAINNAME\USERNAME SID (S-1-5-21-3799145211-2582239028-911126011-1148). This security permission can be modified using the Component Services administrative tool. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type:ErrorEvent Source:DCOMEvent Category:NoneEvent ID:10016Date:14/08/2008Time:14:49:08User:NT AUTHORITY\NETWORK SERVICEComputer:ServerNameDescription:The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {61738644-F196-11D0-9953-00C04FD919C1}to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security permission can be modified using the Component Services administrative tool. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type:ErrorEvent Source:Office SharePoint ServerEvent Category:Office Server General Event ID:7888Date:17/08/2008Time:02:35:42User:N/AComputer:ServerNameDescription:A runtime exception was detected. Details follow. Message: Windows NT user or group 'DomainName.com\USERNAME' not found. Check the name again. Techinal Details:System.Data.SqlClient.SqlException: Windows NT user or group 'DomainName.com\USERNAME 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.SharedResourceProvider.SynchronizeConfigurationDatabaseAccess(SharedComponentSecurity security) at Microsoft.Office.Server.Administration.SharedResourceProvider.SynchronizeAccessControl(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. Thanks, Stu.

How about the SharePoint log from the "12 hive"?Thanks! - M- Michael Mukalian - MCTS: MOSS 2007 Configuration - http://moss2007stuff.blogspot.com

located in 'C:\Program Files\Microsoft Office Servers\12.0\Logs' by default ?it's empty barring the following:1DECF4C0 00400000 6.0.3790.3959 SERVERNAME <br>Log Created on 08/14/08 14:26:15<br><br>Thanks, Stu.

The "12 Hive" is normally in C:\Program Files\Common Files\Microsoft Shared\web server extensions\12. The logs are located in the LOGS folder under 12.- M- Michael Mukalian - MCTS: MOSS 2007 Configuration - http://moss2007stuff.blogspot.com

In Win2003 SP2 there was additional security features in the DCOm settings.Follow these steps,1. Double-click Administrative Tools, and then double-click Component Services. 2. In the Component Services snap-in, expand Computers, expand My Computer, and double-click DCOM Config. 3. In the right pane, locate the program by using its friendly name ( In this case it should COM Server application with CLSID {61738644-F196-11D0-9953-00C04FD919C1})4. Right-click the program name, and then select Properties. 5. On the Security tab, in the Launch and Activation Permissions group box, select Customize, and then click Edit. Add the user to the permissions list, and give the user the appropriate permissions. Reference:http://technet.microsoft.com/en-us/library/cc738214.aspxHarish

I applied the DCOM modifications, but still cannot get the server to complete the SSP creation process. There is only one error message: --------- Event Type: ErrorEvent Source: Windows SharePoint Services 3Event Category: Database Event ID: 5586Date: 15/09/2008Time: 11:32:17User: N/AComputer: SNOOPYDescription:Unknown SQL Exception 547 occured. Additional error information from SQL Server is included below.The DELETE statement conflicted with the REFERENCE constraint "FK_Dependencies1_Objects". The conflict occurred in database "SharePoint_Config", table "dbo.Dependencies", column 'ObjectId'.The statement has been terminated.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.----------I tried to look for further information on this, and it appears to be a SQL connectivity issue, but this is a stand alone server - it has MOSS and SQL2005 installed on the same tin.There were a few posts from people experiencing the same issue, but I couldn't find any fix.. Thanks, Stu.

Hi StuUK, Did you find a fix for it ?

Hi Guys, I was able to solve this problem only by doing everything from the scratch. I reinstalled MOSS and when i tried creating a new SSP i had no problems. Thanks.