This is going to be short and sweet. But to get this solution, I have burned many Virtual Machines and our developer rebuilt real servers atleast 7 times. It is a different story that the Windows Server 2003 build was automated. However after every build was given to me, I used to run the setup and the configuration wizard would fail on Step 5 of Step 10.

No help from newsgroups, Microsoft or anyone. Atleast this will help someone.

This solution worked for me in our environment, it should work for you. Please consult your system administrators to make sure, this solution fits your environment. I was given a go ahead. I am not responsible for what you do to make Windows SharePoint Services v3 work in your environment on your domain controllers.

This is the error, after the Configuration Wizard failed on Step 5.

An exception of type System.Runtime.InteropServices.COMException was thrown. Additional exception information: Class not registered

I have tried so many combinations of security permissions that I have no words to express my frustration! Well in the end, it works and has been approved by the system administrators. I don’t know if it is compromising security, but Windows SharePoint Services V3 installs on the DC.

Lets not delve into the security groups, just grab this information (which you have been wanting to know):

C: Local Service (Read& Execute List Folder Contents Read)
Network Service (Modify Read& Execute List Folder Contents Read Write)
WSS_Admin_WPG(FC)

C:Windows Temp Network Service Full Control
WSS_Admin_WPG(FC)
WSS_WPG (Read& Execute List Folder Contents Read)

Apply these permissions to C: drive and you are done. No more errors for Step 5!

Whew!

Next UP: Moving Windows Internal Database using a script (batch file)

%d bloggers like this: