    
|
 | | |
Microsoft.SharePoint.Upgrade.SPUpgradeException: Action 12.0.1.0 of Microsoft.Office.Server. Search.Upgrade.SearchServiceInstanceSequence failedFebruary 1, 2008 14:14Migrating your SharePoint environment inside a virtual machine might cause some unexpected behaviour. It can be possible that you bump into this error:
And for Google indexing the detailed error report:
Exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Action 12.0.1.0 of Microsoft.Office.Server.Search.Upgrade.SearchServiceInstanceSequence failed. —> 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.ObjectSecurity.ModifyAccessRule (AccessControlModification modification, AccessRule rule, Boolean& modified) at Microsoft.Search.Administration.Security.Registry.ConfigureCommonACL(RegistryKey key, String username) at Microsoft.Search.Administration.Security.Registry.ConfigureCommonACL(RegistryKey baseKey, String keyPath, String username) at Microsoft.Search.Administration.Security.ServiceRegistry.EnsureACL(String username) at Microsoft.Office.Server.Search.Administration. SearchServiceInstance.Provision() at Microsoft.Office.Server.Search.Upgrade. ProvisionSearchServiceInstance.Upgrade() at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade() — End of inner exception stack trace — at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade() at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Administration. SPPersistedUpgradableObject.Upgrade(Boolean recursively) at Microsoft.SharePoint.Upgrade.SPManager.Initialize() at Microsoft.SharePoint.PostSetupConfiguration.UpgradeBootstrapTask.Run() at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask() The solution is hard to find, but easy to fix. The reason that the SharePoint Products and Technologies Configuration Wizard upgrade sequence fails is that it is not possible for the process to access certain registry keys on the computer. Checking out the permissions on the registry keys with regedit.exe learns that the permissions are incorrectly ordered:
It’s a bit unclear what caused this behaviour, but it seems that changing/updating the SID of a virtual machine is the problem. Now the solution: Browse with regedit.exe to the following 3 registry nodes:
Right click the registry keys and choose the Permissions option from the menu.
Regedit will show you a warning message about the incorrectly ordered permissions. Press OK and also close the permission dialog that is presented afterwards. Once you fixed all 3 keys this way, you can start up the SharePoint Products and Technologies Configuration Wizard again and finish your migration. Tags: Configuration Wizard, exception, registry, SearchServiceInstanceSequence, SharePoint, unexpected behaviour.8 Comments »RSS feed for comments on this post. TrackBack URL Leave a comment |
 |
|
YOU ARE MY HERO !!!!!!
Comment by Marco — May 7, 2008 @ 1:55 pm
You are a God!
Comment by Greg Siegert — May 27, 2008 @ 7:12 pm
after lots of searches, i found the missing keys (what a joke…) to unlock the setup.
thank you
Comment by paolo — June 30, 2008 @ 11:41 am
i didn’t find the following:
-HKLM\Software\Microsoft\Shared Tools\Web Server Extensions\12.0
-HKEY_CLASSES_ROOT\AppID\{58F1D482-A132-4297-9B8A-F8E4E600CDF6}
i can only find: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Eventlog\Application\SharePoint Products and Technologies Configuration Wizard
Comment by jamil haddadin — July 2, 2008 @ 3:46 pm
Hi Jamil. Those keys will only exist after you experience the error. SharePoint will first have to install the keys that belonging to version 2007
Comment by Edwin Vriethoff — July 2, 2008 @ 3:52 pm
I got all registry keys and right click on the permission, but i got no warning message and i sinply clicked OK buttob. Then run the prodcut and technology wizard and i got same error again. Can you tell me what to do in this case?
Comment by Sarvesh — March 25, 2010 @ 6:33 am
#Sarvesh, I’m sorry but I will not be able to check out any more possible solutions. There might be another registry key problem in your environment.
Comment by Edwin Vriethoff — March 25, 2010 @ 3:07 pm
That worked like a dream!
It must of been the SID change as you mentioned.
The Vmware image I am using to test Sharepoint 2003 to 2007 upgrades (what joy) has indeed has its SID updated by sysinternals “new sid” utility. Thankyou very much!
This has saved me a lot of time and effort.
Comment by Simon — July 12, 2010 @ 6:12 pm