SharePoint - Content and Structure page is not working

Asked By Connie Branwell

19-Jan-09 02:16 PM

We are having the same issue with our site map.  SMObjectList.Handle_RowDataBound: ObjectList 'ObjectList1' could not add ECB menu to row '12' because of 'Cannot complete this action.  Please try again.'

Did you find a resolution for this issue?

EggHeadCafe - .NET Developer Portal of Choice
http://www.eggheadcafe.com/default.aspx?ref=ng

02-Dec-09 12:18 PM

1. Click on view all site content.



2. Click on all lists (try announcements first) When you reach the one that gives you the cannot complete this action open up SharePoint designer and delete it.



3. Then test manage content and structure to see if it is working.



4. Then restore the list from the recycle bin if it worked and test again.







I hope this helps.







Cheers,



Dave Rosen

02-Dec-09 12:20 PM

1. Click on view all site content.



2. Click on all lists (try announcements first) When you reach the one that gives you the cannot complete this action open up SharePoint designer and delete it.



3. Then test manage content and structure to see if it is working.



4. Then restore the list from the recycle bin if it worked and test again.







I hope this helps.







Cheers,



Dave Rosen

02-Dec-09 12:21 PM

1. Click on view all site content.



2. Click on all lists (try announcements first) When you reach the one that gives you the cannot complete this action open up SharePoint designer and delete it.



3. Then test manage content and structure to see if it is working.



4. Then restore the list from the recycle bin if it worked and test again.







I hope this helps.







Cheers,



Dave Rosen

11-Jan-10 03:39 AM

------=_NextPart_0001_0DC0A0A8
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Dave is right..

Manage Content and Sources enumerates all objects from the site. Generally
it fails on any corrupted list or library. This exception can be identified
by implemeting following changed in web.config file which will will show
you the actual exception message and stack trace which will help you in
further troubleshooting:

Locate the web.config file for the web application in question

Search for a tag customErrors and set its value to "Off".

Search for a tag CallStack and set its value to "true".

The other option you have is to visit all list and libraries manually once
and open at least one item to make sure its healthy.

If you want to see the error message immediately in ULS logs then do
following:

Run following command on the Web Front Sever being serving the site:

net stop sptrace
net start sptrace

Try to repro the issue then i.e Browse to Manage Content and Structure once.

Restart tracing service once again by running, this way you would capture
only the required information related to your error:

net stop sptrace
net start sptrace

This will actually force SharePoint logging service to start writiing to a
new log file located in C:\Program Files\Common Files\Microsoft Shared\web
server extensions\12\LOGS

Sort on "modified date" a take a look at the Second Last log file (since we
have restarted tracing service again and SharePoint has left the file whcih
contains errors) Check the time stamp of the file to make sure you are
looking at the right log file.
------=_NextPart_0001_0DC0A0A8
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 Dave is right..
\par
\par Manage Content and Sources enumerates all objects from the site. Generally it fails on any corrupted list or library. This exception can be identified by implemeting following changed in web.config file which will will show you the actual exception message and stack trace which will help you in further troubleshooting:
\par
\par Locate the web.config file for the web application in question
\par
\par \tab Search for a tag customErrors and set its value to "Off".
\par \tab\tab\tab <customErrors mode="Off" />
\par \tab
\par \tab Search for a tag CallStack and set its value to "true".
\par \tab\tab <SafeMode MaxControls="50" CallStack="false" />
\par
\par The other option you have is to visit all list and libraries manually once and open at least one item to make sure its healthy.
\par
\par If you want to see the error message immediately in ULS logs then do following:
\par
\par Run following command on the Web Front Sever being serving the site:
\par
\par net stop sptrace
\par net start sptrace
\par
\par Try to repro the issue then i.e Browse to Manage Content and Structure once.
\par
\par Restart tracing service once again by running, this way you would capture only the required information related to your error:
\par
\par net stop sptrace
\par net start sptrace
\par
\par This will actually force SharePoint logging service to start writiing to a new log file located in C:\\Program Files\\Common Files\\Microsoft Shared\\web server extensions\\12\\LOGS
\par
\par Sort on "modified date" a take a look at the Second Last log file (since we have restarted tracing service again and SharePoint has left the file whcih contains errors) Check the time stamp of the file to make sure you are looking at the right log file.
\par
\par }
------=_NextPart_0001_0DC0A0A8--