August 11, 2015, cumulative update for SharePoint Server 2013 (KB3055009)
URL: https://support.microsoft.com/en-us/kb/3055009
SharePoint Spells
Wednesday, 12 August 2015
Tuesday, 4 August 2015
How to Download Deployed WSP files from Central Administration Using PowerShell
Problem Statement:
When you reach to a SharePoint server which already has a custom solution (.wsp) deployed but you don't have that .wsp solution available on file system and you need the .wsp solution.
Reason:
When you deploy any solution (.wsp) in SharePoint, it stores in database not file system.
Solution:
You can use below power shell script to download these .wsp files.
-For single solution file
#Get reference to SharePoint farm
$SPFarmVar = Get-SPFarm
#Get reference to deployed SharePoint Solution file SolutionPackage.wsp
$SPWSPVar = $SPFarmVar.Solutions.Item("SolutionPackage.wsp").SolutionFile
#Saving SolutionPackage.wsp to root on C: Drive
$SPWSPVar.SaveAs("C:\SolutionPackage.wsp")
-For all deployed solution files
#Get reference to SharePoint farm
$SPFarmVar = Get-SPFarm
When you reach to a SharePoint server which already has a custom solution (.wsp) deployed but you don't have that .wsp solution available on file system and you need the .wsp solution.
Reason:
When you deploy any solution (.wsp) in SharePoint, it stores in database not file system.
Solution:
You can use below power shell script to download these .wsp files.
#Get reference to SharePoint farm
$SPFarmVar = Get-SPFarm
#Get reference to deployed SharePoint Solution file SolutionPackage.wsp
$SPWSPVar = $SPFarmVar.Solutions.Item("SolutionPackage.wsp").SolutionFile
#Saving SolutionPackage.wsp to root on C: Drive
$SPWSPVar.SaveAs("C:\SolutionPackage.wsp")
-For all deployed solution files
#Get reference to SharePoint farm
$SPFarmVar = Get-SPFarm
#Download all the solutions. Please make sure WSPs folder exist on C:
foreach ($solution in $SPFarmVar.Solutions)
{
$solution = $SPFarmVar .Solutions[$solution.Name]
$solutionFile = $solution.SolutionFile
$solutionFile.SaveAs('C:\WSPs' + $solution.Name)
}
$solutionFile = $solution.SolutionFile
$solutionFile.SaveAs('C:\WSPs' + $solution.Name)
}
That's it folks :)
..::Keep on SharePointing::..
Saturday, 1 August 2015
Invalid Data 0x80070003 error on Restore-SPSite when restoring a SharePoint 2013 Site Collection
Problem Statement:
When you try to backup a site collection and restore it to the same SharePoint server on another web application, it gives below error:
This error usually occur when you take site collection backup from a server and restore it to another server and both source and target server have different builds of SharePoint 2013 but in the above case, server is same and there must not be build difference. So, what is the reason?
Reason:
The only reason for this problem is the site collection which is being backed up is not upgraded after installation of patches on SharePoint server. When you install any KB update or service pack in SharePoint environment, content databases must be upgraded.
Resolution:
Following is the power shell command to upgrade content database:
Command: Upgrade-SPContentDatabase <Content DB Name>
Example: Upgrade-SPContentDatabase WSS_Content
Now, you can take the site collection backup and restore without any hindrance
That's it folks :)
..::Keep on SharePointing::..
Friday, 31 July 2015
The tool was unable to install SharePoint 2013 on Windows 2012 R2
Problem Statement:
Reason:
Actually, Prerequisites installer on SharePoint 2013 tries to execute the executable C:\Windows\System32\ServerManagerCMD.exe but Windows 2012 R2 comes with C:\Windows\System32\ServerManager.exe.
Resolution:
When I run Prerequisite Installer for SharePoint 2013 on Server 2012 R2, it gives following error: "The tool was unable to install Application Server Role, Web Server (IIS) Role"
Reason:
Actually, Prerequisites installer on SharePoint 2013 tries to execute the executable C:\Windows\System32\ServerManagerCMD.exe but Windows 2012 R2 comes with C:\Windows\System32\ServerManager.exe.
Resolution:
You just need to make a copy of ServerManager.exe and rename the copy to ServerManagerCMD.exe and execute Prerequisites Installer.
That's it folks :)
..::Keep on SharePointing::..
..::Keep on SharePointing::..
Subscribe to:
Posts (Atom)