mike hodnick -> mhodnick <-> kindohm

Mike Hodnick is a geeky consultant guy living in Chaska, MN. He enjoys writing code, writing music, and doing fun stuff with his wife and daughter. This is his personal website, where you can get to his blog, music library, and other nonsense.

Latest From Twitter...

The Blog

Best SharePoint error ever:

error

Actually, I don't know that this is a SharePoint error at all.  The core exception thrown is a COMException.  Internet research has only yielded a small amount of forum posts relating to using System.IO.Directory and System.IO.DirectoryInfo, which as far as I can tell are not being used on this page. 

I cracked open Reflector hoping to learn more.  An internal SharePoint class just catches the COMException and throws a new SPException.  As you can guess, the SharePoint method that does the work is just wrapping a COM call.  

Unfortunately, I think we may resort to more drastic measures to save time (backup/restore from another environment) to eliminate this error rather than try to understand what the cause of the error is. 

But you have to admit, the exception message is totally awesome. 

Technorati Tags:  
posted on Thursday, May 22, 2008 9:37 AM |

Comments

Gravatar
# re: "There are no more files" error in SharePoint
Posted by Jussi Palo
on 6/5/2008 7:18 AM
I'm seeing this exact error in testing environment after trying to create duplicate of our production environment (using stsadm backup/restore).

Have you managed to solve this somehow?
 
Gravatar
# re: "There are no more files" error in SharePoint
Posted by Jussi Palo
on 6/6/2008 4:41 AM
Workaround in my case was not to use stsadm backup/restore but to use SQL Server database backup/restore to move the content.
 
Gravatar
# re: "There are no more files" error in SharePoint
Posted by mike h
on 6/6/2008 9:13 AM
Jussi - that's pretty much what our solution ended up being too. We never resolved the error as-is.
 
Gravatar
# re: "There are no more files" error in SharePoint
Posted by Michael
on 7/18/2008 1:34 AM
We encounter this sometimes as well; as far as I can tell, the stsadm -o backup operation sometimes completes but fails to back up the entire site.

I've got it happening now, and the backup file is just over 2 GB -- if I recall correctly it's usually just over 2.1 GB. We have two sub-sites which are raising this error, so I think stsadm just failed to back up those sites and that's what causing the problem.

The other day it failed to complete the back up several times in a row, but they were falling short by several hundred megabytes so I noticed before trying to restore. I find just trying again (and again and again...) until the backup is the "right size" solves the issue.

Not sure what affects this; we have an automated backup that runs early in the morning and I've never noticed that being smaller than it should be, so maybe it's got something to do with server load.

(Before anyone asks, we're backing up and restoring a 2 GB content database because content deployment has never worked for us with our sites)
 
Gravatar
# re: "There are no more files" error in SharePoint
Posted by Mike R
on 7/18/2008 4:43 PM
Just to chime in - we have a huge backup (27 GB) that we are trying to migrate to a new server environment using stsadm -o backup and restore. We thought it was successful, but upon further use, we started noticing that some stored docs would not open and we would get the "There are no more files" error.

Unfortunately, I don't think we can use the SQL Server backup as the site is on a shared content DB. I hope Microsoft fixes this apparent error/bug/issue!
 
Post Comment
Title *
Name *
Email
Url
Comment *  
Please add 8 and 1 and type the answer here: