This time SharePoint 2010 Products Service Pack includes new functionalities in addition to the regular security updates and hotfixes.
Service Pack 1 includes the following features:
- Supporting the installation over SQL Server “Denali”.
- Shallow Copy: Moving the Site Collection between content databases..
- Site Recycle Bin:I saw this feature in Google Sites before a while and I wished to have the same one in SharePoint, Simply you can restore a deleted site collection/sub sites from a recycle bin.
- Storage Space Allocation.
- Cascading Filters in Performance Point Services.
- IE9 and Google Chrome Support.
SharePoint 2010 Service Packs 1 includes the following Updates:
Of course with the releasing these new features, some PowerShell commands will be released too such as Move-SPSite, Get-SPDeletedSite, etc..
At the same time June 2011 Cumulative Update for SharePoint Server is released and you can obtain it from here.
- Microsoft SharePoint Team Blog Post.
- Service Pack 1 for SPF 2010 and SPS 2010 White Paper.
- June 2011 Cumulative Update for SharePoint Server 2010.
- SQL Server Code Name “Denali”.
While Performing setup for SharePoint training lab PCs for some customers of my company (Devosis), I usually fix an issue that appears on SharePoint Server 2010 when the user tries to add a new document from a Word Client.
The problem appears when user tries to add a new document using SharePoint ribbon as the following:
The Microsoft Word will not be able to store the document in the SharePoint site due to some security settings, and it will show an error “Word has encountered a problem” and “There is a problem saving the file..” as the following:
To fix this: Goto File-> Options –> Trust Center, and then click the Trust Center Settings:
Then select from the right tabs (Protected View) and uncheck the “Enable Protected View for files located in potentially unsafe locations” option.
Now the word client will work fine, and it will be able to save the files into the document library.
For the third time in as many weeks, I have had this weird problem in updating the Workflow Settings for one of the SharePoint Lists workflows, whenever I change the Start Options to “Start workflow automatically when an item is created/changed” and publish it to SharePoint, the start behavior of the WF execution doesn’t change and once I refresh the SharePoint Designer (SPD) and check the start options again, it returns as it was “Allow this workflow to be manually started”.
After many hours of fighting with SPD, I went to a conclusion that SPD will cause this issue sometimes because of certain Workflow Activities .NET assemblies caching problem within the SPD.
The solution? It’s simple, you have to clear the SPD Workflow Activities Assembly Cache Folders:
Close the SharePoint Designer.
Open the Windows Application Data Store Folder by going to Start->Run and then type %APPDATA%\Roaming\Microsoft\SharePoint Designer\ProxyAssemblyCache (%APPDATA% is a Windows Environment Variable that points to the Windows Applications Store Folders) and press Enter.
Delete all these directories inside the ProxyAssemblyCache Folder.
Browse again to %LOCALAPPDATA%\Microsoft\Windows\Temporary Internet Files\WebTempDir
Delete all the files inside this Folder.
Run SPD again, and everything will work out fine