First Attempt: Logged in as Domain "Administrator", Installation of MOSS
completed successfully as Single Server. Configuration failed on Task
configdb. Here's the applicable log entries:
05/25/2006 14:54:29 8 INF Now joining to farm at server
MOSS\OfficeServers database
SharePoint_Config_786aa3af-9cf2-4668-a0a9-807e8537af4a
05/25/2006 14:54:46 8 ERR Task configdb has failed with an
unknown exception
05/25/2006 14:54:46 8 ERR Exception:
System.InvalidOperationException: This access control list is not in
canonical form and therefore cannot be modified.
at
System.Security.AccessControl.CommonAcl.SetQualifiedAce(SecurityIdentifier
sid, AceQualifier qualifier, Int32 accessMask, AceFlags flags, ObjectAceFlags
objectFlags, Guid objectType, Guid inheritedObjectType)
at
System.Security.AccessControl.DiscretionaryAcl.SetAccess(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.SetAccessRule(AccessRule
rule)
at
System.Security.AccessControl.RegistrySecurity.SetAccessRule(RegistryAccessRule rule)
at Microsoft.SharePoint.Administration.SPDiagnosticsService.Provision()
at Microsoft.SharePoint.Administration.SPFarm.Join()
at
Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb()
at
Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
I spent a while trying to figure out why it would have failed and finally
decided to rerun the config program to reread the message. This time it
completed the configdb task and then failed on Task secureresources.
Here's that section of log:
05/25/2006 16:55:13 8 ERR Task secureresources has failed
with an unknown exception
05/25/2006 16:55:13 8 ERR 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()
After doing more research, I decided to uninstall MOSS (which completed
clean), install SQL 2005 Developer ed., and then rerun the install logged in
as a Domain User account configured as SQL sysadmin, dbcreator, and
securityadmin, choosing the option to become the first server in a server
farm. The exact same sequence of failures occurred. First the configdb,
rerun, and then the secureresources.
I'll probably start on a fresh copy but if anyone has seen this error and
knows a work around, please let me know.
--
Harold
did you choose an existing SQL Server or used the MSDE option? If you used
an existing SQL Server, did you add the domain administrator as sysadmin,
security admin and db creator within the SQL Server? Which account did you
use as service account for the SPS ?
br
René
"LaRoux" schrieb:
Udo
But as a general check out tool, you should always take the text of the
error message and stuff it into Google and search on it. Microsoft
would like you to do that on the MSN site, also, but I rarely get
results there. The Technet search site is much better, and sometimes
the MSDN works. But Google is clearly the best.
--
Hollis Paul
Mukilteo, WA USA
05/31/2006 16:49:04 10 ERR Task secureresources has
failed with an unknown exception
05/31/2006 16:49:04 10 ERR Exception:
Filemon log :
3739 16:49:04 psconfigui.exe:3440 OPEN C:\WINDOWS\symbols\dll\mscorlib.pdb PATH
NOT FOUND Options: Open Access: All
3740 16:49:04 psconfigui.exe:3440 OPEN C:\WINDOWS\dll\mscorlib.pdb PATH
NOT FOUND Options: Open Access: All
3741 16:49:04 psconfigui.exe:3440 OPEN C:\WINDOWS\mscorlib.pdb NOT
FOUND Options: Open Access: All
3742 16:49:04 psconfigui.exe:3440 CLOSE C:\WINDOWS\assembly\GAC_32\mscorlib\2.0.0.0__b77a5c561934e089\mscorlib.dll SUCCESS
Help me
thx
Yes, I've heard of Google. Thank you for asking.
>it will show you two documents on F5 that will show you how to secure the SharePoint resources.
These documents are on how to configure F5 firewall products to enable
secure access to SharePoint from outside the firewall. Hardly a MOSS Beta
configuration primer.
> But as a general check out tool, you should always take the text of the
> error message and stuff it into Google and search on it.
I always do a search on error text, with quotes around it so I don't get
millions of useless answers like how to configure a firewall. Of course if I
search on the quoted error message now, I get four different sites with
copies of this same message thread.
>But Google is clearly the best.
I prefer Yahoo.
--
Harold
In the first install, I used the MSDE. In the second install, I pointed it
at a fresh 2005 Dev. SQL, installed on the same system.
>did you add the domain administrator as sysadmin, security admin and db creator within the SQL
> Server? Which account did you use as service account for the SPS ?
In the first install, I did exactly as you describe, I added the domain
admin to each of those three groups and used the domain admin account as the
service account. In the second install, I created a Service account
specifically for SharePoint, added it to domain admins and the three SQL
security groups. Same result.
--
Harold
Possibly unrelated, I had a lot of trouble (performance) running the Vista
Beta on a Virtual Server instance. Are you running the MOSS installation on
Virtual Server? Is anyone who has been successful running on Virtual Server?
--
Harold
thanks
joe
This access control list is not in canonical form and therefore cannot be
modified.
This issue will occur if you are using Sysinternal's Newsid utility to
reset the SID of the machine or image.
To work around this issue do the following:
Remove the Office Server Beta install.
Join a workgroup.
Remove machine account from domain.
Run sysprep from Windows Support Tool's deploy.cab.
Reboot and rejoin the domain.
Install the Office Server Beta.
You can also build the server from scratch and not use NewSID.
This worked for me. The other multi-step method still failed.
--
Harold
"LaRoux" wrote:
> > You can also build the server from scratch and not use NewSID.
>
> This worked for me. The other multi-step method still failed.
>
> --
> Harold
>
sysprep did nothing to solve the problem. Re-installing the virtual server
and NOT using the NewSID did thre trick.
I have the same issue as well it seems that this error then triggers a
number of other errors in the log (naturally). I am running 2 boxes (Both VM)
on is SQL 2005 and the other to be a web server. AD is on another box on the
domain.
All a fresh installs .. well not exactly they are pre build OS environments
that then get propmoted as memeber servers before I insall anything.
would this be the correct way to install this BETA?
Regards,
Ivan brebner
Better later then never. It looks like here is the fix:
http://www.combined-knowledge.com/Downloads/StandaloneDomainController.zip
Unpack and read "readme.txt".
http://blogs.interknowlogy.com/billsheldon/archive/2006/05/22/2705.aspx