Are you a .NET Developer or Contractor interested in working with Sitecore or Dynamics CRM?

Apply for our Mentorship Program. If accepted, we will mentor you on Sitecore and provide you with project to help you build your skills and make some money at the same time. If you are interested send your resume with details on why you want to work with Sitecore or Dynamics CRM to: Chris Williams - or Dennis Augustine - We look forward to working with you to achieve your goals.

Friday, November 21, 2008

SharePoint Event Log Error: Windows NT user or group 'DOMAIN\Administrator' not found. Check the name again.

So your SharePoint install seemed to work but in the event log you are getting messages like this:

A runtime exception was detected. Details follow.
Message: Windows NT user
or group 'DOMAIN\Administrator' not found. Check the name again.
Techinal Details:
System.Data.SqlClient.SqlException: Windows NT user or group
'RODINIA\Administrator' not found. Check the name again.
System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception,
Boolean breakConnection)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
bulkCopyHandler, TdsParserStateObject stateObj)
System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds,
RunBehavior runBehavior, String resetOptionsString)
cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior,
RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult
System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result,
String methodName, Boolean sendToPipe)
at Microsoft.Office.Server.Data.SqlServerManager.GrantLogin(String
more information, see Help and Support Center at

I searched for hours for a solution and found lots of posts that were not clear on why. Here are the two reasons I found for it:

  1. The user mentioned in the error does not have access to SQL Server
    CONFIRMATION STEPS: To determine this outside SharePoint simply go to Control Panel and create an ODBC Connection to the database and click test connection. If it fails then you hypothesis is right. If not try the second reason.

  2. The user mentioned in the error does not have write access to SQL Server
    CONFIRMATION STEPS: You can either drop a simple app that connects to the database on the server or you could look at the security settings on the sql server in question and see if that user has write permission
  3. I found an article on another reason for the error. If you are running SQL Server 2005 on a Windows 2000 box. Here is the article:

The thing to note here is that there may be more than one SharePoint database. You may think its failing on the content database connection but it could be on one of the other databases or if its a farm you may not have configured it on one of the farm databases.

Another thing to try if the above do not work or you are not sure what its trying to connect to is to look at the ULS log. You can find this by looking in:

\program files\commonfiles\microsoft shared\web server extensions\12\logs\{Machinename -timestamp}

If you have any more info on this error or other tips, tricks, resources please email them to and we will post them.

1 comment:

Brett said...

We had this error continually on installing SharePoint 2010, the SQL server I created was before I setup the Domain, so the credentials in SQL did not match, this post helped me identify this, so infact it was database security even though Machine\Administrator was mapped to Domain\Administrator there were some issues in SQL resolving this. Deleting the Administrator user (note use another Administrator user to do this!) and re-adding it with Domain\Administrator and then reinstalling the Server Search Service (or use the wizard) worked for us, thanks heaps.