Exporting a SharePoint list in SharePoint 2010

To export a list from a SharePoint site you can follow the steps below:

  • Ensure that the user account performing the process is a member of the farm administrator group.
  • In Central Administration, on the Home page, click Backup and Restore on the left hand menu.
  • On the Backup and Restore page, in the Granular Backup section, click on the Export a site or list option.
  • On the Site Or List Export page, select the appropriate web application, site collection and list that you want to export.
  • In the File location section enter the UNC path of the export folder. This should be a share on either the server or another network location.
  • If the file already exists and you want to overwrite this, then select the Overwrite existing file check box.
  • Select the Export full security check box if you want to export all the security and permissions settings with the select list or library.
  • Click on the Start Export button when you are happy with the selected options.

Done!

Advertisements

How to select a federation service name?

The Federation Service Name must never equal any machine name in the Active Directory forest when you are deploying a AD FS 2.0 farm. This requirement is in place to allow Kerberos authentication to succeed for your Federation Service.

Scenario 1: Non-working scenario
The Federation Service Name is ADFS.POCOFFICE365.COM and the host names of the two Federation Servers in your farm are: ADFS.POCOFFICE365.COM and ADFS2.POCOFFICE365.COM. Kerberos authentication will fail because your AD FS 2.0 service account needs to have the following servicePrincipalName (SPN) registered: HOST/ADFS.POCOFFICE365.COM. Since you already have a computer in Active Directory named ADFS.POCOFFICE365.COM, the HOST/ADFS.POCOFFICE365.COM SPN is already registered to this computer account, which means that registering this SPN to your AD FS 2.0 service account is not an option.

Scenario 2: Working scenario
The Federation Service Name is SSO.POCOFFICE365.COM and the host names of the two Federation Servers in your farm are: ADFS.POCOFFICE365.COM and ADFS2.POCOFFICE365.COM. Kerberos authentication can succeed since your AD FS 2.0 service account can have the SPN HOST/SSO.POCOFFICE365.COM registered to it since neither the AD FS 2.0 servers nor any other account in the Active Directory forest have this SPN registered.

SharePoint 2010 – “Installation of this product is not permitted on this computer. Please contact your network administrator for more details.”

If you have the following entry in the register of the target server:

HKLM\Software\Policies\Microsoft\Shared Tools\Web Server Extensions\14.0\ SharePoint\DWORD DisableInstall

DWORD DisableInstall=00000001

Users who try to install SharePoint 2010 on that server will receive the following error message:

“SharePoint installation is blocked in your organization. Please contact your network administrator for more details.”

You will need to set

DWORD DisableInstall=00000000

to allow installation of SharePoint 2010.

Part 2 of 2: Upgrading a Report Server database used by older versions of Team Foundation Server

If you can take the report server offline, you can detach the databases to move them to the SQL Server instance you want to use. This approach preserves permissions in the databases. If you are using a SQL Server 2012 database, you must move it to another SQL Server 2012 instance. After you move the databases, you must reconfigure the report server connection to the report server database. If you are running a scale-out deployment, you must reconfigure the report server database connection for each report server in the deployment.

Use the following steps to move the databases:

1. Backup the encryption keys for the report server database you want to move. You can use the Reporting Services Configuration tool backup the keys.

2. Stop the Report Server service. You can use the Reporting Services Configuration tool to stop the service.

3. Start SQL Server Management Studio and open a connection to the SQL Server instance that hosts the report server databases.

4. Right-click the report server database, point to Tasks, and click Detach. Repeat this step for the report server temporary database.

5. Copy or move the .mdf and .ldf files to the Data folder of the SQL Server instance you want to use. Because you are moving two databases, make sure that you move or copy all four files.

6. In Management Studio, open a connection to the new SQL Server instance that will host the report server databases.

7. Right-click the Databases node, and then click Attach.

8. Click Add to select the report server database .mdf and .ldf files that you want to attach. Repeat this step for the report server temporary database.

9. After the databases are attached, verify that the RSExecRole is a database role in the report server database and temporary database. RSExecRole must have select, insert, update, delete, and reference permissions on the report server database tables, and execute permissions on the stored procedures. For more information, see Create the RSExecRole.

10. Start the Reporting Services Configuration tool and open a connection to the report server.

11. On the Database page, select the new SQL Server instance, and then click Connect.

12. Select the report server database that you just moved, and then click Apply.

13. On the Encryption Keys page, click Restore. Specify the file that contains the backup copy of the keys and the password to unlock the file.

14. Restart the Report Server service.

Part 1 of 2: Upgrading a Report Server database used by older versions of Team Foundation Server

The report server database provides storage for one or more report server instances. Because the report server database schema can change with each new release of Reporting Services, it is required that the database version match the version of the report server instance you are using. In most cases, a report server database can be upgraded automatically with no specific action on your part.

The following summarizes the ways to upgrade a ReportServer database:

1. Setup upgrades a single instance of a report server. Then the database schema is automatically upgraded after service startup and the report server determines that the database schema version does not match the server version.

2. At service startup, the report server checks the database schema version to verify that it matches the server version. If the database schema version is an older version, it is automatically upgraded to the schema version that is required by the report server. Automatic upgrade is especially useful if you restored or attached an older report server database. A message is entered in the report server trace log file indicating that the database schema version was upgraded.

3. The Reporting Services Configuration Manager upgrades a local or remote report server database when you select an older version to use with a newer report server instance. In this case, you must confirm the upgrade action before it happens.

4. The Reporting Services Configuration Manager no longer provides a separate Upgrade button or upgrade script. Those features are obsolete starting with SQL Server 2008 due to the automatic upgrade feature of the Report Server service.

Fixing Visual Studio’s error “This server version is not supported…” for SQL Server 2012

When attempting to work on a SQL Server 2012 database from within Visual Studio 2010, Visual Studio throws the following error:

“This server version is not supported. Only servers up to Microsoft SQL Server 2008 are supported.”

You need to install “SQL Server Data Tools” to work with SQL Server 2012. The latest version of “SQL Server Data Tools” is “SQL Server Data Tools (December 2012)”. The “SQL Server Data Tools (December 2012)” update contains several improvements since the last web release of SSDT:

  • Database Unit Testing
  • Integration of SQL Server Data Tools Power Tools
  • Updated Data-Tier Application Framework
  • Bug fixes to customer-reported issues

This release is available for both Visual Studio 2012 and Visual Studio 2010.

For Visual Studio 2010:
Download URL: http://msdn.microsoft.com/en-us/jj650014

For Visual Studio 2012:
Download URL: http://msdn.microsoft.com/en-us/jj650015