Dave Burke - Freelance .NET Developer specializing in Online Communities

A freelance .NET Developer

To SPS2003 : Cannot complete this action, unsolved part II

This follows an earlier post on the “Cannot complete this action” errors I receive when using the Microsoft.Sharepoint libraries on my development server.  The error does not occur on my company's staging server.  Weird. 

I completely removed Sharepoint Services from my development server and changed the account to a bonafide domain admin group account.  I made sure Network Service and IIS_WPG had the appropriate permissions, duplicated my IE settings with those on the working server.

Still friggen' nothin' to report.  Sorry.  Chances are, however, that since this seems such a generic error that my fix wouldn't necessarily help you anyway.  Here's the first of 10+ pages of results from googling the sharepoint groups as evidence.

My first impressions of Sharepoint Services is 87% positive, but if I were writing a review I would definitely include the word “squirrelly.”

Posted: Jun 16 2004, 09:23 AM by daveburke | with 17 comment(s)
Filed under:

Comments

James Edelen said:

Couple suggestions. This error is usually generated when your custom web parts throw an unhandled exception.
1) You can attach a debugger to the server to see what the error is.
2) You could edit the web part to catch the generic System.Exception and display it as output in the part (not necessarily the best for usability, but it would at least tell you that something is going wrong with a specific part and it will also let the rest of the page render unaffected).
3) Make sure in web.config that the trust settings are the same on the staging server and the Production server. My guess is that on staging/dev it is set to WSS_Medium while it is set to WSS_Minimal on the production server. If that is the case, then it is quite likely that the parts are throwing some form of Code Access Secuirty (CAS) exception (from the System.Security namespace).
# June 17, 2004 5:41 PM

James Edelen said:

Oh, also, if you got a COMException rather than just the generic Cannot Complete this Action, make sure you are running the code on a Front-End sharepoint server (yes, it must be a FE).
# June 17, 2004 5:43 PM

Dave Burke said:

James, I will investigate each of your suggestions and hopefully have something to report back. Thanks very much for taking the time to share your thoughts on this.
# June 17, 2004 8:03 PM

Dave Burke said:

I'm promising myself not to post another weblog on WSS "Cannot complete this action" until this is resolved, so I'll be adding updates as comments here.

Tonight I added a top-level site on the Default Web Site, and using the root "/" for the workspace.

Interestingly I reran the Sharepoint Configuration Analyzer and when I previously got an error "virtual site tied to static IP address," I received none.

Rebooted, reran test page. Error persists. btw, here is the screenshot of the error:

http://dbvt.com/x/blog/2004/spcannot617.gif

Compared the web.config files for the trust setting, want to inspect further there. Also want to do more in the debug area.

I AM getting a COMException, which means I need to investigate James' FE statement.
# June 17, 2004 10:08 PM

James Edelen said:

That looks exactly like errors I have gotten when I ran code on a non-SharePoint Server. Do you have multiple SharePoint servers in a farm? If so, then all OM code needs to run on the Front-end servers (the one(s) with the "Web" Component role). If not I would be hard pressed to find the cause.
# June 18, 2004 12:52 AM

Dave Burke said:

James, Thanks for checking back! Thank you also for clarifying the "Front-end server." I never heard that term (having been working on a SPS2001-to-WSS migration as time permit for nearly a month now), and am definitely going to investigate it further, as I mentioned above. Best regards to you! Dave
# June 18, 2004 1:20 AM

Dave Burke said:

James, in answer to your question, SharePoint Services is installed in a farm configuration, but running on only a single machine. This is the same configuration of the HQ server (on my company's network which works) and my development server (which is on my home office network, which does not work.)

The home office W2K3 server is connected to my LAN but not the Internet. I'm wondering if it could have to do with the network configuration differences, or possibly not being connected to the Internet. Just fishing now...
# June 18, 2004 1:27 AM

TrackBack said:

# June 19, 2004 11:20 AM

TrackBack said:

# June 19, 2004 11:21 AM

Dave Burke said:

I had an idea at DevTeach that perhaps the security on the site pertaining to its Zone setting was an issue. So I put added my WSS sites to my trusted sites zone, but it didn't change anything.
# June 23, 2004 11:58 AM

Makarov said:

Has anybody tried to add in web.config this line :

<identity impersonate = "true"/>

As soon as I did that, my "cannot complete this action" error was gone .
# June 30, 2004 4:33 PM

Dave Burke said:

OH...MY....GOD!!!!!!

Makarov. I shouldn't say this on an open channel, but...I love you, man!

I feel like one of the guys in Das Boot and the U-boat is beginning to rise after being stranded on the bottom of the Straights of Gibraltar, and they're shouting, "It's rising! It's rising!!!!!"

Sincerely. Thank you, Makarov. I hope I can return the favor some day. And I'm sure you helped a lot more guys than just me today!

# June 30, 2004 5:12 PM

TrackBack said:

# June 30, 2004 5:47 PM

Alex Makarov said:

Dave, u r not kidding, right?
# July 1, 2004 9:17 AM

Dave Burke said:

Alex, No, I am MOST DEFINITELY NOT kidding. You fixed the problem I was dealing with for weeks, and I'm sure you helped a lot of other guys, too!
# July 1, 2004 9:23 AM

kikus said:

как всегда на высоте

# June 15, 2010 12:27 PM

KeegeCiz said:

buy   with confident <a href=www.modernportraitstudio.com/.../a>  for more

# January 24, 2012 1:05 PM
Leave a Comment

(required) 

(required) 

(optional)

(required)