Solved

Sharepoint Server Site Restore Issue

Posted on 2014-12-18
2
474 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
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

Creating Instructional Tutorials  

For Any Use & On Any Platform

Contextual Guidance at the moment of need helps your employees/users adopt software o& achieve even the most complex tasks instantly. Boost knowledge retention, software adoption & employee engagement with easy solution.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains how to reset the password of the sa account on a Microsoft SQL Server.  The steps in this article work in SQL 2005, 2008, 2008 R2, 2012, 2014 and 2016.
These days socially coordinated efforts have turned into a critical requirement for enterprises.
This tutorial will give a an overview on how to deploy remote agents in Backup Exec 2012 to new servers. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as connecting to a remote Back…
This tutorial will walk an individual through locating and launching the BEUtility application and how to execute it on the appropriate database. Log onto the server running the Backup Exec database. In a larger environment, this would generally be …

705 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