|
|
|
|
|
|
|
|
|
|
| |
| |
Tuesday, April 07 2009 @ 08:23 PM MDT
Contributed by: admin
Views:: 2,914 |
|
Common error situation when using backup/restore to transfer a database to a new farm on MOSS 2007
When you use STSADM -o backup or backup the SQL database manual, and after restoring to the same or different server you experience the system.arguementException error.
After the restore operation is done several operations fail to work with the following exception:
System.ArgumentException. Value does not fall within the expected range.
at Microsoft.SharePoint.Library.SPRequestInternalClass.GetMetadataForUrl(String bstrUrl, Int32 METADATAFLAGS, Guid& pgListId, Int32& plItemId, Int32& plType, Object& pvarFileOrFolder)
at Microsoft.SharePoint.Library.SPRequest.GetMetadataForUrl(String bstrUrl, Int32 METADATAFLAGS, Guid& pgListId, Int32& plItemId, Int32& plType, Object& pvarFileOrFolder)
at Microsoft.SharePoint.SPWeb.GetMetadataForUrl(String relUrl, Int32 mondoProcHint, Guid& listId, Int32& itemId, Int32& typeOfObject, Object& fileOrFolder)
at Microsoft.SharePoint.SPWeb.GetFileOrFolderObject(String strUrl)
at Microsoft.SharePoint.Publishing.CommonUtilities.GetFileFromUrl(String url, SPWeb web)
The reason this happen is because the references from the old database does not adjust to the new restore to reflect the changes. The references needs to adjust from the publishing page objects in the Pages library to their Page Layouts. Sometimes these URLSs are stored in the database as an absolute URL and it needs to be adjusted to reflect the changes with the new server name URL.
Be aware that backup/restore of MOSS content databases between server farms are not fully supported! Official documentation of this support limitation is currently in the works. The supported way to transfer content between server farms is to use STSADM -o export/import or content deployment. Backup/restore is only supported for the same server farm.
In case that you have run into the above problem you have two options:
* Throw away the database and transfer it correctly using STSADM -o export/import or content deployment
* Fix the incorrect links manually using the following steps
- Open the web in SharePoint Designer
- On the “task panes” window, pick hyperlinks.
- For the “hyperlink” heading, click the arrow and pick (custom…)
- In the dialog, ask to show rows where the hyperlink begins with a URLs which are not valid on the current server farm
- For each of the files, right click and say “Edit hyperlink…” and Replace hyperlink with the hyper link that is valid on the current server farm.
|
|
|
| |
|
|
|
|
|
|
