Sharepoint Server Site Restore Issue

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
D HService Desk ManagerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

colly92002Commented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
D HService Desk ManagerAuthor Commented:
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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SharePoint

From novice to tech pro — start learning today.