Solved

Sharepoint Server Site Restore Issue

Posted on 2014-12-18
2
420 Views
Last Modified: 2014-12-22
Having an issue with a couple Sharepoint sites...

Had a server crash and the only recent Sharepoint backup was the Site Collection backups. I've been able to recover most sites using the stsadm command, but having an issue with 2 of the Sites restoring.

The error received is:
"One or more files in the restored site collection will exceed the maximum supported path length. Please select a shorter destination site address and try again."

These 2 sites are the largest and most used on the site and are 20+ GB and 40+ GB respectively.

Some of the things I've seen online relate to some contents in the site exceeding the 250 character limit and causing the restore to flake out.

I've been on with Microsoft for the last 4 days and would appreciate any assistance.
Maybe someone has run into an issue like this before.
Maybe someone knows of a tool that can truncate file lengths the file paths in the created .dat file.

I'm pretty desperate. Would give 1000 points if I could...  

OS Version: Server 2008 R2
Software: Sharepoint Server 2007
0
Comment
Question by:IAmDH
2 Comments
 
LVL 15

Accepted Solution

by:
colly92002 earned 500 total points
ID: 40509141
Sharepoint has a 260 character limit on paths (URLs).   You probably have either deep folder structure or very long file names that are going above this limit somewhere.
I suspect you are restoring the site collection to a root path that is not the same as it was backed up from?  

Try restoring to the shortest possible location (path wise) that you can.

As a suggestion to get the smallest possible root path, I would suggest you create a test web app, and restore one of the site collections to the ROOT of that web app.  This will give you the smallest "root" URL possible,i.e. the root will become something like:
http://server:port/  

rather than say:
http://server:port/site/siteCollectionName

This will save you characters.  If that restores you can either keep the site collection here, or search the content db for long paths and fix them, back it up again, and restore it where you want it.

Note you can use AAM and DNS to give the webapp a nicer name than http://server:port
0
 

Author Closing Comment

by:IAmDH
ID: 40512802
That's exactly what I ended up doing, but just wanted to be sure that was the only option... no one has given any alternate solutions.
0

Featured Post

Want to promote your upcoming event?

Attending an event? Speaking at a conference? Or exhibiting at a tradeshow? Easily inform your contacts by using a promotional banner in your email signature. This will ensure your organization’s most important contacts are in the know.

Join & Write a Comment

Suggested Solutions

Title # Comments Views Activity
Sharepoint Max date with criteria 2 22
Log Backup 2 12
Sql query 34 17
Renaming multiple file extensions using Powershell 4 13
In this article we will get to know that how can we recover deleted data if it happens accidently. We really can recover deleted rows if we know the time when data is deleted by using the transaction log.
A safe way to clean winsxs folder from your windows server 2008 R2 editions
This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…

708 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now