We’ve been hearing Q1 2014 as a release date for SharePoint 2013 SP1 for some time now, and most of us have been thinking we’d get that date at SharePoint Conference 2014. The conference Yammer feed was just updated with the news that SharePoint 2013 SP1 has been released.
SP2013 SP1 Download Info
Ensure you follow all the guidance listed here when installing:
Windows Server 2012 R2 Support
One major change we’ve been waiting for is support for Server 2012 R2. You *must* use the slipstreamed version available for download via MSDN, VSLC, or MPN.
The issues fixed are listed in the download at the following URL:
Stephan Gossner has provided an FAQ at the following url:
During a recent deployment of SharePoint 2013 for a client, we came across an issue with Central Administration getting the error:.
You may be trying to access this site from a secured browser on the server. Please enable scripts and reload this page.
Generally this is resolved by adding the CA site as a Trusted Site. The client required that trusted sites be added via GPO.
The client added the site to the GPO and we forced a refresh. We still had the same issue. After checking internet settings, we found the trusted site was not set. We attempted reboots and GPO refresh forces to no avail.
IE ESC had been turned on for both Administrators and Users on the server. After disabling IE ESC, the trusted sites were properly applied and the error disappeared.
Learn more about Tallan or see us in person at one of our…
Tallan’s SharePoint Practice Lead, Reddy Kadasani, shows you how to add custom validation logic (UI portion, and code) to validate a phone number field.
A common problem after setting up SharePoint 2010 is to get the System.Security.Cryptography.CryptographicException – Keyset Not set error.
A few notes regarding this:
This is a known issue with .NET and SP2010.
It is not a critical issue however.
The Timer service is recycled every so often to reclaim system resources. The exception is thrown during the shutdown process. When you check the timer service everything seems to running fine, except that you see the exception logged in the event log of course.
If you have Visual Studio installed, you may also see the “do you want to debug” dialog.
A detailed explanation of why this happens is provided here and here
Although the author above mentions why this problem occurs, there is no real “solution” to the issue which is a bit troublesome.
This blog post will explain how to accomplish the seemingly easy task of adding over ten slices to a Visio pie chart. This is done using Visio 2013, but the steps using 2010 and 2007 should be very similar. Once all the slices are added to the pie chart, each individual slice will be bound to external data, giving them a dynamic thickness.
I was trying to get the new workflow engine installed and configured with SharePoint 2013 but was encountering an error in the Service Bus configuration step.
Installation Instruction for Workflow Manager and SharePoint 2013 Workflow Configuration:
The full installation steps are provided here (in a video series): http://technet.microsoft.com/en-us/library/dn201724.aspx and here: http://technet.microsoft.com/en-us/library/jj193478
The instructions provided above are pretty detailed and helpful except that I kept getting this error while configuring workflow manager and there was not much to go with online.
Program C:\Program Files\Windows Fabric\bin\Fabric\Fabric.Code.1.0\FabricDeployer.exe exited with error: Windows Fabric deployment failed.DeploymentValidator:
warning: The Fabric Data Collection Agent is disabled for this deployment.
None of the declared nodes is for the current machine.
Finally i looked at the hosts file on the Developer VM and noticed that I had an entry for 127.0.0.1. Since I was using FQDNs for my workflow configuration, I commented this line and…
Navigating through a list or library with dozens or hundreds of items or folders can be a tedious task. There are a few ways to make it easier to find the information you are looking for. One unique way is to build a rolodex to filter the list items conveniently.
The rolodex is configured by using a Query String Web Part and Content Editor Web Part to filter a list or library. The high-level steps to accomplish this are:
Create an “Index” field in the list or library.
Add a Query String Filter Web Part, a Content Editor Web Part, and the web part for the list to a site page.
Add code to the Content Editor Web Part with links that reload the page with the query string value.
Configure the Query String Filter Web Part to send data to the list web part.
The requirement for a domain trust relationship depends on how a SharePoint Farm is configured, the SharePoint Farm could either reside in a perimeter network (or hosted environment), or the SharePoint Farm could be split between a perimeter network and the internal network.
In this post we will assume a simple SharePoint Extranet where a SharePoint Farm and an Active Directory are in a hosted environment, and resource from the local Corporate domain (domain.local) are needed in the hosted environment (domain.ext).
Delegate Controls are generic controls found in all of the out-of-the-box master pages in SharePoint, a Delegate Control provides the ability to dynamically render ASP.net controls (candidates) in master pages extending the functionality of SharePoint without the need to directly modify any of those master pages.
So Basically, a Delegate Control provides a “plug-in” framework making its child candidates (ASP.NET user Controls) pluggable and replaceable.
Some of the available delegate controls in the master pages are:
In this post we will take a look at using the AdditionalPageHead Delegate control to quickly add a jQuery reference in SharePoint master pages.
I recently installed and configured a small SharePoint farm containing two virtual servers using Oracle Virtual Box and decided to share my experience of the process. For the most part the configuration is simple, but there are a number of common small discrepancies that can be the difference between your servers communicating correctly, or you throwing your laptop out of the window after a week of errors. I will not be going through a click by click summary of setting up the SharePoint farm, and will instead be giving a high level overview of the process and spend more time on these issues I ran into.