16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

1130 Part XI: Upgrading <strong>and</strong> Migrating to SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong><br />

The import process will then fail. When the documents are imported, an area<br />

is created for each folder; a document library in that area is created with the same<br />

name as the area. The relevant documents are stored in this new document library,<br />

<strong>and</strong> links are placed in the Portal Listings list for the area, for each document in the<br />

document library. The SPIn output you will see on the comm<strong>and</strong> line will look similar<br />

to the following text:<br />

W:\SPOutSPIn>spin http://intranet woodgrovedocsit.xml /area it<br />

Validating .xml file. This might take several minutes.<br />

The .xml file is valid.<br />

Setting this registry key value will grant full permissions to the current user on<br />

the portal site.<br />

Do you want to continue? [y/n] y<br />

The registry value was set.<br />

Disabling search schedule.<br />

Verifying database access ...<br />

Importing content.<br />

Percentage completed: 100.00 %<br />

Content was successfully imported.<br />

Deleting registry key value.<br />

Enabling search schedule.<br />

Import Statistics:<br />

Number of site groups created: 0<br />

Number of areas created or modified: 4<br />

Number of document libraries created or modified: 4<br />

Number of folders created or modified: 0<br />

Number of documents (not counting versions) imported: 16<br />

Total time: 00:01:01<br />

If the server running SharePoint Portal Server where you are running the SPIn<br />

tool is also an index server, the search component will be stopped. This is primarily<br />

for performance reasons. SPIn process creates a special registry value under<br />

HKEY_LOCAL_MACHINE\SOFTWARE\<strong>Microsoft</strong>\<strong>Sharepoint</strong> Portal Server\FullControlSID<br />

to ensure that the person who is running the import-job always has the right to<br />

access the imported files. This registry value is removed after the import job is<br />

finished.<br />

In the folder where you execute SPIn, two SPIn-related text files will be created:<br />

an error file <strong>and</strong> a log file. You should review both these files. If SPIn could not resolve<br />

the accounts specified in the export XML files, it will default to the account that is performing<br />

the migration. This behavior is similar to the SharePoint Team Services migration<br />

tool. Therefore, when restoring a site, it is often helpful to create an account<br />

specifically for this purpose.<br />

If you migrated SharePoint Portal Server 2001 categories into SharePoint Portal<br />

Server 2003 as portal areas, SPIn will detect this <strong>and</strong> use any categories in the document<br />

profiles information to link the imported documents into the appropriate areas.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!