Not a cool story: Basic SharePoint installation

Spending 2 days sitting at my computer just to figure out why SharePoint couldn’t be successfully deployed shouldn’t be a cool story, should it? This made me remember when I was a fumbler setting foots on SharePoint land in the past from zero. This post isn’t going to cover whether my SharePoint life or SharePoint installation steps. It’s just a quick note that might be helpful to you one day.

To have a better development environment for my team, I decided to re-architect all computers in my office. Each 8-GB computer had VMware installed to host a dedicated SharePoint virtual machine. Memory were allocated for Windows 7 operating system and VMware first before given to a little space for SharePoint. Please don’t ask me why such an installation existed as this was a long story. My developers used to report that they couldn’t deliver their builds on time due to slow performance that I did acknowledge. I decided to take Windows 7 out of every machine to install Windows Server 2008 R2 Service Pack 1 (make sure you remember this version or later one for SharePoint 2013 installation). One of the developers gave me an ISO image of Windows Server 2008 R2 his friend shared. Everything went smoothly from installation, activation to Windows Update on every computer. SharePoint 2013 was installed successfully as well. With exciting mood I believed the new architecture would boost our productivity very much until the error thrown in the SharePoint configuration wizard at the step of creating configuration database.

System.Securuity.Principal.IdentityNotMappedException: Some or all identity references could not be translated”.

As normal I put my fingers on keyboard to look up the error in the world of Google Search. There are just some people encountering the same error. Almost aren’t provided right answer. No confirmation gets yet back to any suggestions too. There was a thread sharing a tip on running Sysprep that caught my eyes on. I then followed many tips including Sysprep approach on one of computers but no luck then. I thought the error was related to Active Directory that I wasn’t the one who installed and configured it. I left all client computers alone then began clearing the server (AD domain controller) before installing Windows Server 2012 R2 that I wanted to get around sometime. After promoting a new domain controller, I tried to run SharePoint configuration wizard again with my big hope. The “ugly” error punched me in the face. I would look incompetent to do basic SharePoint installation. Because the server and AD were installed and configured again, I thought there was no reason it was a culprit. So what was the root cause? My question came up as to why all server that were installed the same ISO image gave me a nightmare. Would the ISO image be my enemy in this case? I then came to MSDN Subscription to download another Windows Server 2008 R2 Service pack 1 image. After installing the new image, I managed to create many different SharePoint farms that used the same SQL Server database. Now we are having a seamless development environment that my developers really love.

Back to the story, today I asked my brother if there was any case he has got in his career regarding bad Windows Server ISO image. He immediately responded to me that he recently encountered the case in which he wasn’t able to configure Sharing feature on folders after he installed Windows Server 2008 ISO image given by his colleague. Sometimes you need to be fully aware of Windows Server image from untrusted source. Image can include some policies and adjusted settings that may conflict your system. It can also include registry entries edited to pass over Windows activation.



You may need to read the “Setting up SharePoint 2013 environment At Work” series:


Leave a Reply

© 2018 The Soldier of Fortune.