Comments on: MOSS 2007: SharedServiceProvider & ‘Cannot Complete this Action’ Error

By: François Souyri

François Souyri — Thu, 05 Mar 2009 12:43:01 +0000

Just had exactly the same problem on a test MOSS RTM, and Microsoft has a KB fix :
- add a registry key as follow to your Web Front End and retry the Create New Site, et Voila !

NEW REG :
Create New KEY under :
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0
Called “ServerLanguage”
In that key , create a New Binary Value “1033″.
Close Registry.

By: cwxwwwxdfvwwxwx

cwxwwwxdfvwwxwx — Thu, 25 Dec 2008 16:59:23 +0000

well, hi admin adn people nice forum indeed. how’s life? hope it’s introduce branch

By: Rahul Singh

Rahul Singh — Fri, 26 Sep 2008 09:20:49 +0000

I am not able to open the site created by me and also not able to create site collections.Each time I get an error saying “Cannot Complete this action”.Could anyone Suggest the Solution to it.

By: Anita Claxton

Anita Claxton — Tue, 02 Sep 2008 12:35:47 +0000

Hi Chris,

Thanks for this post, after moving my sharepoint farms database 4 times now, each time there is something new to solve and I have learn’t it often involves the SSP and it’s admin site. So when I saw your post I had to give it a go – Many, many thanks Anita

By: SharePoint Error: Cannot complete this action. Please try again. « Dot Net Engineer

Mon, 30 Jun 2008 21:02:16 +0000

[...] http://cregan.wordpress.com/2006/10/20/moss-2007-sharedserviceprovider-cannot-complete-this-action-e... Posted in SharePoint Troubleshooting, Uncategorized. Tags: SharePoint, SSP. [...]

By: Melina

Melina — Thu, 20 Dec 2007 17:11:06 +0000

very interesting. i’m adding in RSS Reader

By: Joseph

Joseph — Mon, 30 Apr 2007 15:29:40 +0000

Chris,

Thank you very much for this solution. After much “head banging” this solved the problem I was running into

By: Victor

Victor — Wed, 25 Apr 2007 22:18:56 +0000

Hi Chris,
Do you know if there has been a fix released for the ‘Cannot complete this action’ bug?
VJ

By: Heather Solomon - MVP, WSS - Blog about Design, MCMS, SharePoint, and CSS

Heather Solomon - MVP, WSS - Blog about Design, MCMS, SharePoint, and CSS — Thu, 30 Nov 2006 03:00:57 +0000

SharePoint Blogs

By: MikeH - Another geek in need...

MikeH - Another geek in need... — Thu, 23 Nov 2006 16:51:15 +0000

Hey Chris,

I have been working on some B2TR upgrades and have run into an interesting issue – or set of issues I should add.

Though I am a long way from being an expert in anything, I have performed over 3 dozen TR upgrades on existing servers. I know the pains, obstacles, and plain frustration like few others – perhaps.

Now, these upgrades are somewhat different – 1 of the servers has custom workflow / features, a couple have custom web parts that use the MOSS API vs. just .Net 2.0 (which I have done on other TR servers).

The upgrades appear to finish with error. But when you try to browse a site – you’ll get the error.aspx with the message that you should setup a custom error page to get a better error message. If I try something like browsing directly to the _layouts/settings.aspx page – I get an error stating the resource with tag ‘open_menu’ cannot be found. Almost like a JS piece is expected and yet missing.

When I browse the upgrade.log on this upgrade I do see an error near the end – 2 of them actually – referencing a feature that could not be upgraded on this farm because it could not be found. The feature ID is the publishing layouts feature ID. Very interesting.

These sites were Internet Presence Web Sites when deployed in B2 – so the custom master page will have deprecated items in it – but it has generally come up with an error representative of that. In this case, I simply get the errors mentioned.

Yes, I can pull up CA – but not the site. Yes, I can create a new web app and site collection and browse it – just can’t browse the original site.

Any ideas would be very much appreciated.

Thanks…