Sharepoint v3 Installation Fails

I was trying to setup Sharepoint “v3” which is part of Office 2007; the Beta 1 Technical Refresh installs without a problem, but when I try and configure Sharepoint it fails in Step 2 and I get the error shown below. You can click on the image to see the full size.

However, when I trawl through the log file, I did find a few exceptions, a couple of which are listed below. The only reason the font is small on those is so it would fit and render fine in here. You can copy and paste that in notepad or something and see if in a bigger font; alternatively you can download the log file (see the end of this posting).

Exception 1:

Entering function CreateCentralAdministrationSiteForm.CreateCentralAdministrationSiteFormInitializeBeforeShow

A SocketException was thrown with SocketError ConnectionRefused
Connect has been refused for port 12838, so we will consider this a free port
Have not found a free port yet.  Number of tries is 1.  Min port we will try is 1024, Max port we will try is 49151
Leaving function CentralAdministrationSiteTask.GenerateRandomUnUsedPortForTheAdminVs
Leaving function CreateCentralAdministrationSiteForm.CreateCentralAdministrationSiteFormInitializeBeforeShow

Exception 2:

Entering function ResourceAccess.SetAccessRule
Entering function ResourceAccess.SetRegistryAccessRule
Entering function ResourceAccess.RetrieveRegistryRightsFromResourceAccessPermissions
Leaving function ResourceAccess.RetrieveRegistryRightsFromResourceAccessPermissions
Task secureresources has failed with an unknown exception
Exception: System.InvalidOperationException: This access control list is not in canonical form and therefore cannot be modified.
   at System.Security.AccessControl.CommonAcl.RemoveQualifiedAces(SecurityIdentifier sid, AceQualifier qualifier, Int32 accessMask, AceFlags flags, Boolean saclSemantics, ObjectAceFlags objectFlags, Guid objectType, Guid inheritedObjectType)
   at System.Security.AccessControl.DiscretionaryAcl.RemoveAccess(AccessControlType accessType, SecurityIdentifier sid, Int32 accessMask, InheritanceFlags inheritanceFlags, PropagationFlags propagationFlags)
   at System.Security.AccessControl.CommonObjectSecurity.ModifyAccess(AccessControlModification modification, AccessRule rule, Boolean& modified)
   at System.Security.AccessControl.CommonObjectSecurity.ResetAccessRule(AccessRule rule)
   at System.Security.AccessControl.RegistrySecurity.ResetAccessRule(RegistryAccessRule rule)
   at Microsoft.SharePoint.PostSetupConfiguration.ResourceAccess.SetRegistryAccessRule()
   at Microsoft.SharePoint.PostSetupConfiguration.ResourceAccess.Secure()
   at Microsoft.SharePoint.PostSetupConfiguration.SecurityTask.SecureResources()
   at Microsoft.SharePoint.PostSetupConfiguration.SecurityTask.Run()
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

I think I have everything outlined in the installation document for the Beta 1 Technical Refresh. BTW, I have this on Windows 2003 Enterprise Edition with SP1 and all latest patches. SQL Server 2005 Dev. Edition and VS.NET 2005 Professional Edition.

There are a couple of more exceptions along the same line – if it would help I have upload the full log file which you can download here (53 kb). But the real question is any idea what is broken and why?

Published by

Amit Bahree

This blog is my personal blog and while it does reflect my experiences in my professional life, this is just my thoughts. Most of the entries are technical though sometimes they can vary from the wacky to even political – however that is quite rare. Quite often, I have been asked what’s up with the “gibberish” and the funny title of the blog? Some people even going the extra step to say that, this is a virus that infected their system (ahem) well. [:D] It actually is quite simple, and if you have still not figured out then check out this link – whats in a name?

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.