Recover a Deleted Site Collection in SharePoint 2010 SP1 and above

Unfortunately, there is no user interface for restoring deleted site collections. Managing deleted site collections requires using PowerShell. SharePoint 2010 introduces 3 new PowerShell CmdLets for managing the Recycle Bin for site collections.

When users delete a site, they are presented with the following page:

As you can see from the message, the entire site including its contents, permissions are sent to recycle bin.

When you click Delete, you are prompted with another message box, which may be confusing:

Even though it says the site will be deleted permanently, it is not.

Hit OK.

If you are a PowerShell user, you can use the Remove-SPWeb cmdlet to delete the web instead of the UI. Just use the –Recycle parameter:

Remove-SPWeb http://site -Recycle

After the site is deleted, it will be available in the top-level site’s recycle bin to restore:

 

The easiest way to get a list of all the deleted site collections is to just call Get-SPDeleteSite without any parameters. In the following example, for brevity, I have formatted the output as a table and filtered the columns displayed. In the second sample, I have added a wildcard filter to the command that can be used to easily filter sites based on relative paths.

 

Once you have identified the site you want to restore, you call the Restore-SPDeletedSite. To restore one or more sites, it is easiest to just pipe the results from Get-SPDeletedSite. By default, the command will ask you to confirm the restore. To eliminate the confirmation, just add "Confirm:$true" to the end of the command.

 

 

 

Error: The report server installation is not initialized in SharePoint 2010 farm

Interesting problem whilst configuring SQL Server Reporting Services (SSRS) integration on the web front end in a new SharePoint 2010 farm

I’m using SharePoint Server 2010 fundation with Service Pack 2 and the Augest 13 CU applied. SQL Server 2008 R2 is the DB latest version. Using the Reporting Services Configuration Manager I’d configured Reporting Services on the server to point to the Reporting Services DB on the back-end database server and created the relevant virtual directories on the server. For the time being the service account is being used for the Reporting Services integration.

Next I’ve gone to Central Admin –> General Application Settings and selected Reporting Services Integration and successfully completed the configuration as you can see from the picture below.

The next step is usually to return to the General Application Settings page and select Set server defaults under Reporting Services but as soon as I did this I received the following error…

 

Resolution :

The tip was to return to Reporting Services Configuration Manager and click on Encryption Keys in the left menu and then delete the encrypted content.

 

and when I returned to the General Application Settings page and ran Set server defaults it now worked as expected and allowed me to maintain the default settings for Reporting Services

SharePoint 2010 Foundation + SQL Server Reporting Services Integrated mode installation issues

When trying to configure the SQL Reporting Services Add-in for SharePoint 2010 from Central Admin you might see the following error:

huge collection of free MS ebooks

http://blogs.msdn.com/b/mssmallbiz/archive/2013/06/18/huge-collection-of-free-microsoft-ebooks-for-you-including-office-office-365-sharepoint-sql-server-system-center-visual-studio-web-development-windows-windows-azure-and-windows-server.aspx

The report server installation is not initialized. Check the documentation for more information. (rsReportServerNotActivated)

Problem Description:

The report server installation is not initialized. Check the documentation for more information. (rsReportServerNotActivated) Get Online Help -2147159549

0x80090005

Cause:

Keys Corrupted

Solution : 

1) If it is new server then remove the existing Report Server Database and re-create new one using reporting serivces confiruation window

2. Connect to SSMS - Report Server Database -- Delete the row which machine is our server name

3. Restart Reporting Services service

An error occurred within the report server database.  This may be due to a connection failure, timeout or low disk condition within the database.  (rsReportServerDatabaseError) Get Online Help Keys lock row not found

If you delete any records in ReportServer database or due to misconfiguration you may receive that error, ReCreating Reporting Services help to solve the issue,

Scale-out deployment is not supported in this edition of Reporting Services. (rsOperationNotSupported)

Issue with Installed and configured with the Office products in SharePoint 2010 – SharePoint PSConfig Error

I had issue with Installed and configured with the Office products in SharePoint 2010 .

Scenario. We have Three Windows 2008 R2 Std machines (WEF1, WEF2 and App) installed and configured with the Office Web Apps with SP2

After completing the installation Office Web Apps  while trying to running the PSConfig we got the below error one of the server.

Troubleshooting steps.

Verified ULS logs and find interesting 
The license state for the current server doesn't match the farm's license state
After log research found good blog from msdn . 

Resolution:

Run the following Power Shell commandlet on all the servers in the farm. 

Set-SPFarmConfig –InstalledProductsRefresh

This will pick the entries from the server and reset the entries in the Config DB

Original Post : http://blogs.msdn.com/b/sowmyancs/archive/2012/08/08/the-license-state-for-the-current-server-doesn-t-match-the-farm-s-license-state-sharepoint-psconfig-error.aspx

SharePoint 2010 CU and securtiy patch upgrade Issue

Issue : 

I faced as mentioned after installing the SP2 patch and trying to run PSConfig command. I have done a fair bit of patching but never encountered this issue. The PSConfig failed and referred to the upgrade logs as usual to find the error. The upgrade log error listed below was cryptic and did not provide any direct information on what was causing it.

Resolution : 

Error in configuration wizard while trying to add new SharePoint Server to an existing Farm [Scale out] after reset the Farm passphrase

Fixed with below refernce 

http://blogs.msdn.com/b/fabdulwahab/archive/2011/10/25/error-in-configuration-wizard-while-trying-to-add-new-sharepoint-server-to-an-existing-farm-scale-out-after-reset-the-farm-passphrase.asp

2. Null exceptions

3 : Timer job filed

4. Decided to installation SP2 in all servers with sp2 language packs

·         Installed SP2  Updates on WFE2  and APP Server

·         Ran Product Configuration Wizard and it failed

·         Tried PSConfig.exe -cmd upgrade -inplace b2b –wait  - This too failed at the last step

·         Tried psconfig -cmd upgrade -inplace b2b –force – this too failed at the last step

·         IISRESET to both SharePoint Servers

·         Restarted SharePoint Timer Service

·         Restarted SharePoint Search Service

·         Clear Config Cache on all the  servers  set 1 as a cache

·         Ran PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures – this one failed at the last step

That issue was with respect to Web Application, At the end we Deleted the Web App and Recreated it, Issue got resolved, and then PSCONFIG Works like.