Web developers wiki ASP.NET Sitecore Sharepoint Kentico by Evident Interactive

Sharepoint installation: System.Security.Principal.IdentityNotMappedException

Modified: 2008/02/22 14:40 by janwillem - Categorized as: MOSS, SharePoint
A few days ago I ran into trouble while installing MOSS on a new box. I installed MOSS and after messing up the configuration I decided to completely reinstall it. During the second installation the installer aborted and logged a System.Security.Principal.IdentityNotMappedException exception in the Application Event log. The full message was:

-----------------------------
Failed to create the configuration database. An exception of type System.Security.Principal.IdentityNotMappedException was thrown. Additional exception information: Some or all identity references could not be translated. System.Security.Principal.IdentityNotMappedException: Some or all identity references could not be translated. at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess) at System.Security.Principal.NTAccount.Translate(Type targetType) at Microsoft.SharePoint.Administration.SPProcessIdentity.GetCurrentSecurityIdentifier() at Microsoft.SharePoint.Administration.SPProcessIdentity.GetCurrentSid() at Microsoft.SharePoint.Administration.SPProcessIdentity.Update() at Microsoft.SharePoint.Administration.SPApplicationPool.Update() at Microsoft.SharePoint.Administration.SPWebApplication.CreateDefaultInstance(SPWebService service, Guid id, String applicationPoolId, IdentityType identityType, String applicationPoolUsername, SecureString applicationPoolPassword, String iisServerComment, Boolean secureSocketsLayer, String iisHostHeader, Int32 iisPort, Boolean iisAllowAnonymous, DirectoryInfo iisRootDirectory, Uri defaultZoneUri, Boolean iisEnsureNTLM, Boolean createDatabase, String databaseServer, String databaseName, String databaseUsername, String databasePassword, SPSearchServiceInstance searchServiceInstance, Boolean isPaired, Boolean autoActivateFeatures) at Microsoft.SharePoint.Administration.SPAdministrationWebApplication.CreateDefaultInstance( SqlConnectionStringBuilder administrationContentDatabase, SPWebService adminService, IdentityType identityType, String farmUser, SecureString farmPassword) at Microsoft.SharePoint.Administration.SPFarm.CreateAdministrationWebService(SqlConnectionStringBuilder administrationContentDatabase, IdentityType identityType, String farmUser, SecureString farmPassword) at Microsoft.SharePoint.Administration.SPFarm.CreateBasicServices(SqlConnectionStringBuilder administrationContentDatabase, IdentityType identityType, String farmUser, SecureString farmPassword) at Microsoft.SharePoint.Administration.SPFarm.Create(SqlConnectionStringBuilder configurationDatabase, SqlConnectionStringBuilder administrationContentDatabase, IdentityType identityType, String farmUser, SecureString farmPassword) at Microsoft.SharePoint.Administration.SPFarm.Create(SqlConnectionStringBuilder configurationDatabase, SqlConnectionStringBuilder administrationContentDatabase, String farmUser, SecureString farmPassword) at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb() at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run() at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask() -----------------------------

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


After some Googling I eventually found a blog post by Ray Linder with the explanation and a three step guide how to fix it. Apparently the Application Pool for the Sharepoint Central Administration website was not deleted when I removed my initial MOSS installation, causing every subsequent reinstall to fail.
Ray's three step guide says:

1. Delete/Remove all SharePoint databases.
2. Go into IIS and delete the "SharePoint Central Administration V3" site (if it didn't get removed during an uninstall).
3. MOST IMPORTANT!!! - Go into IIS and under "Application Pools" and delete "SharePoint Central Administration V3"

You can find the original post here: http://geekswithblogs.net/raylinder/archive/2007/03/10/108472.aspx

 © Evident Interactive BV