So I just got back from the MVP summit! What an awesome time with a bunch of great people! I will be posting a summary of the people I have met and of course paintball stories sometime tomorrow but first let’s get to business. I have been running into an error lately that was somewhat new to me when creating the configuration database when running the PSCONFIG wizard otherwise known as the SharePoint configuration wizard. You run this wizard after you have installed MOSS 2007 and are ready to provision your configuration database. I ran the wizard and it got about to step two and quickly failed with this error:
"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.
I check the long log that came along with the error and searched for the letters "Err".... I did a bit more digging and found that it may be an issue with the application pool identity that was communicating with the SQL server for provisioning of the configuration database. Because I was setting up a medium farm the SQL server was on a separate box. I checked the application pool identity "SharePoint central administration V3" and it was set to "network service" yikes!! So after about 1 hour searching through log files, checking SQL permissions it came down to the application pool which had the wrong identity. Once I changed the application pool to the correct service account that I was using all was installed without any more problems! One thing to note is that the
Turns out this specific server was previously being used as the sandbox environment and previously had MOSS installed on it. When MOSS was uninstalled for some reason the application pool was left and when I reinstalled MOSS it was using the same app pool and its identity. So my hope is that users who receive this error message will be able to find this post and solve their problem in minutes...hence the obvious title :)
Cheers!