What's new
- Facebook login issues fixed
Download and more information here.
Exact answers to exact problems.
Visio Graphs are not working on SharePoint 2013, you will see generic error message in Visio Web Part and the following error messages in Windows Application Log.
Log Name: Application
Source: Microsoft-SharePoint Products-Visio Graphics Service
Event ID: 9004
Task Category: Web Access
Level: Warning
Description:
Failed to access the cache.
---
Log Name: Application
Source: Microsoft-SharePoint Products-Visio Graphics Service
Event ID: 8079
Task Category: Graphics Service
Level: Error
User: AD\svc_sp_serviceapppoo
Description:
Failed to generate raster diagram for file http://intranet/Documents/MyVisio.vsdx page Image0 Error : System.IO.FileNotFoundException: E:\Program Files\Microsoft Office Servers\15.0\Data\VisioServer\VisioCache372264ef-b563-434d-bee0-11dede201c0b\VisioBundle637d234b68df44f8b5957a482056ef00.cache
at Microsoft.Office.Visio.Server.GraphicsServer.DiskCache.ReadBundlePart(Bundle bundle, Int32 index)
at Microsoft.Office.Visio.Server.GraphicsServer.ServiceCore.GetRasterPageItem(RasterPageItemRequest request)
at Microsoft.Office.Visio.Server.GraphicsServer.VisioGraphicsService.GetRasterPageItem(RasterPageItemRequest request)
---
Log Name: Application
Source: Microsoft-SharePoint Products-Visio Graphics Service
Event ID: 8078
Task Category: Web Access
Level: Error
User: NT AUTHORITY\IUSR
Description:
Failed to get raster diagram for visio file http://intranet/Documents/MyVisio.vsdx page Exception : System.ServiceModel.FaultException: The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.
Server stack trace:
at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)
at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.Office.Visio.Server.GraphicsServer.IVisioGraphicsService.GetRasterPageItem(RasterPageItemRequest rasterPageItemRequestContract)
at Microsoft.Office.Visio.Server.Administration.VisioGraphicsServiceApplicationProxy.GetRasterPageItem(RasterPageItemRequest request)
at Microsoft.Office.Visio.Server.ServiceWrapper.GetRasterPageItem(RasterPageItemRequest request)
Look at the path highlighted in yellow on one of the error messages. You need to grant Modify permission to the folder E:\Program Files\Microsoft Office Servers\15.0\Data\VisioServer\ for the account Visio Services is using. You can find the account by going to Manage Service Applications page in Central Admin, and highlighting the Visio Graphics Service row, then clicking on the Properties button and looking at the Application Pool used.
Then, in Service Accounts page in Central Admin, you can find the actual AD account you need to grant the Modify permissions.
When you add List View Web Part to a page in SharePoint and would like it to display e.g., all pages in the Pages library, and provide links to items, you will run into issue where you're not able to link to the item using the title of the item. You can only link to the item usin the file name, which will look bad, and include dashes, remove special characters, etc.
In SharePoint 2010, you would modify the XSLT of the XSLTListViewWebPart using SharePoint Designer (like here), but in SharePoint 2013 you can use new feature in SharePoint 2013, called JSLink to do the same.
Use JSLink to override how Title column is rendered. In the override, add link tags around the title. I do like this JSLink method better compared to the old XSLT SharePoint Designer way as you can reuse the JavaScript file and only reference that in the Web Parts when required.
(function () {
// Initialize the variables for overrides objects
var overrideCtx = {};
overrideCtx.Templates = {};
//List of default Object.keys(ctx.CurrentItem)
//ID,PermMask,FSObjType,HTML_x0020_File_x0020_Type,ContentType,File_x0020_Type,
//File_x0020_Type.mapapp,HTML_x0020_File_x0020_Type.File_x0020_Type.mapcon,
//HTML_x0020_File_x0020_Type.File_x0020_Type.mapico,serverurl.progid,
//ServerRedirectedEmbedUrl,File_x0020_Type.progid,File_x0020_Type.url,
//FileRef,FileLeafRef,CheckoutUser,CheckedOutUserId,IsCheckedoutToLocal,Title,
//Created,Created.FriendlyDisplay,firstRow
overrideCtx.Templates.Fields = {
'Title': { 'View' : '<a href="<#=ctx.CurrentItem.FileRef#>"><#=ctx.CurrentItem.Title#></a>' }
};
SPClientTemplates.TemplateManager.RegisterTemplateOverrides(overrideCtx);
})();
If you're using 3rd party password manager application, such as LastPass, you might run into issue where you need to press "Sign In" button twice in order to log in.
Steps:
This is due to new ADFS improvement made in the new Login UX. The improvement is great for ADFS users as it verifies the user name field automatically when focus moves away from the user name box, BUT for us password add-on users it will cause nasty side effect of having to hit Sign In twice. This is because user name validation javascript is not run when password manager injects username and password to the form.
Keep pressing that Sign In until you're in.
As soon as you add Script Editor Web Part to a page in SharePoint 2013 and publish the page, RSS Viewer Web Part will get stuck on the loading animation. If you remove the Script Editor Web Part, RSS Viewer Web Part start to work immediately.
NOTE! When in Edit mode, and even after checking-in the page, RSS Viewer works nicely, this only occurs after you publish the page.
None, will add it here as soon as I figure out a workaround. Occurs at least on March 2013 update, unsure if it occurs on RTM bits.
By default, SharePoint 2013 Content by Search Web Part (CSWP) displays dates in long date format, such as March 13, 2013 or 7. maaliskuuta 2013 (in Finnish). How to change that to short date format?
You need to create custom Display Template, and also custom Value Renderer.
You need to create the site without Navigation Inheritance, so select No to Use the top link bar from the parent site?.
After creating the site, go to Navigation Settings of the site, and select Display the same navigation items as the parent site.