- An error has occurred, which probably means the feed is down. Try again later.
Posts Tagged ‘en-US’
Microsoft AppFabric 1.1 support will end soon but what about its integration in SharePoint 2013
I recently found article which says “Microsoft AppFabric 1.1 for Windows Server Ends Support 4/2/2016“. This was a shocking news for me because SharePoint 2013 uses Microsoft AppFabric 1.1, and this means support for SharePoint will also be effected.
In case if you don’t know what is AppFabric 1.1, AppFabric provides hosting, management and caching capabilities for Web applications and middle-tier services. This application helps us to build, scale and manage applications, in particular those built using ASP.NET, Windows Communication Foundation (WCF) and Windows Workflow Foundation (WF).
Microsoft has recommended all applications using AppFabric 1.1 for Windows Server to migrate off this technology by April 2, 2016. Recommended alternative is Azure Redis cache.
Azure Redis Cache is was build on the popular open source Redis Cache. It provies you access to a secure, dedicated Redis cache, managed and fully supported by Microsoft, so you can focus on your application rather than the infrastructure. We recommend all Microsoft AppFabric customers using Cache to move to Microsoft Azure Redis Cache.
As per my knowledge SharePoint 2013 leverages Workflow Manager and an internal workflow hosting for legacy workflows.
Finally I found a comment by Erica Mohler(Microsoft) which says “SharePoint functionality (including the Distributed Cache feature) will be supported under the Microsoft Support lifecycle for SharePoint 2013” which was a relief moment for me.
Another important point to consider that the next version of SharePoint which is suppose to be SharePoint 2016 will integrate with Azure Redis.
Hope this will help you.
PowerPivot Thumbnail Rendering Error
Snapshots will not work if you have chosen to open the workbooks in the Client application. To remedy this, follow the below instructions:
To set the default open behavior for site collections
- In the SharePoint site collection, click Site Actions, and then click Site Settings.
- On the Site Settings page, under Site Collection Administration, click Site Collection Features.
- On the Features page, for the Open Documents in Client Applications by Default feature, click Activate (OpenInClient Feature is enabled) to open documents in the client application. Click Deactivate (OpenInClient Feature is disabled) to open documents in the browser.
To set the default open behavior for a document library by using the document library settings page
- On the <document library>: All Documents page, under Library Tools, click Library.
- In the library toolbar, click Library Settings.
- On the Document Library Settings page, click Advanced Settings.
- On the Advanced Settings page, in Opening Document in the Browser, select one of the following options:
Open in the client application When a user clicks on a document in this library, the document will open in the corresponding client application (if available). - Open in the browser When a user clicks on a document in this library, the document will open in the Web browser Web app for that document type. When the document is opened in the Web app, the user can then decide to open the document in the client application
- Use the server default When a user clicks on a document in this library, the document will open by using the default open behavior specified for the server on which SharePoint 2010 Products is installed.
You need to invoke the Getshapshot.exe (which is located here: C:\inetpub\wwwroot\wss\VirtualDirectories\80\bin>GetSnapshot.exe)*Note: Browse to C:\inetpub\wwwroot\wss\VirtualDirectories\80\bin>GetSnapshot.exe and make sure it is 50/56kb. I have seen instances where is is corrupt 0kb and it needs to be replaced.
To invoke the Getsnapshot.exe (re-title a workbook) via:
PowerPivot Gallery > Select a Report > Documents > Edit Properties > Title (give the workbook a title):
If None of the above solve your problem, Please try this also it solved my issue.
Under browser settings on the server (all SharePoint servers in the server farm), uncheck “Check for server certificate revocation”
Powellshell Script to backup WSP files
.But, what is we are creating a replica of an environment manually and we do not have WSP backup file or source code for the solution deployed in the farm. There is no option left for us to deploy the same solution into another environment without this two approaches.
For these kind of situations, please use below mentioned Powershell command
$farm = Get-SPFarm
$file = $farm.Solutions.Item(“solution.wsp”).SolutionFile
$file.SaveAs(“c:\Solution.wsp”)
This way, we can take backup of the solution which is already deployed into the server farm and can re-use it into another environment.