I was having a problem creating a new SPWebApplication through Central Admin in SharePoint. It would run for a fair while – longer than I’m used to as this machine seems quite slow – and then I’d be shown the IE ‘timeout’ page within the ‘Create Web App’ iframe. The Web App seemed to have created, including creation of the IIS app pool and site, but they never worked correctly – for example, on different attempts I couldn’t:
- See the web application’s settings in central admin
- Create a Site collection
- Login to a site collection that had created successfully, despite being site collection admin.
Fortunately, I’m not the first person to have seen this. Some folks suggest using PowerShell to provision the web application – which I’m guessing doesn’t suffer IIS timeouts – and others suggest increasing the time outs on the application pool itself. I set:
- Ping Maximum Response Time
- Shutdown Time Limit
- Startup Time Limit
… to 900 (instead of 90), I was able to create and successfully access my new site collection!
New job, new problem. We’ve a SharePoint 2010 Publishing site using content deployment to push content from an authoring site collection to a live one – and the live site collection started to return an HTTP 401 – Unauthorized to any request for a page.
Continue reading “401 Unauthorized from a content publishing site”
I had this exception start occurring on a workflow I was testing earlier. It was very strange – I’d already run through the workflow step at which this was happening successfully 3 times. Then I started to receive this error, consistently, at the same point of my unchanged workflow each time I ran it.
Continue reading “Nintex – “This task is currently locked by a running workflow and cannot be edited.””
I’m working with a Nintex workflow at the moment, and trying to do a simple thing – format a date. Unfortunately, the function fn-FormatDate does not work correctly. Continue reading “Nintex fn-FormatDate inline function failure”
In SharePoint 2007 and 2010, if you wanted a neat hierarchy of publishing pages, you had two options. Either, you structured your SharePoint site so that you got the navigation you wanted, or you built custom navigation providers. Unfortunately, customers typically want everything to be ‘out of the box’, even if that means some absurd structures just to get the navigation right. Developing custom navigation providers is a really tough sell, but I’ve also seen site structures 7 levels deep to try to avoid this – and a 7 level deep site structure is a really bad idea.
SharePoint 2013 gives us a standard alternative to structural navigation. Instead, we can use ‘Managed Navigation’. This is a Managed Metadata termset that define’s our site’s hierarchy.
That’s great, but there are some problems with this still. Continue reading “Making Managed Metadata Navigation work well”
SharePoint 2013’s master pages do not, by default, show breadcrumbs. SharePoint 2010 had reduced them to a fly-out menu (which was nice, as it used up less page space):
SharePoint 2013 doesn’t have them at all:
However, they can be restored… Continue reading “Add Breadcrumbs back into SharePoint 2013”
I’ve been studying ASP.NET MVC 4 over the last while; this is the subject of second of the 4 exams required for the SharePoint Developer MCSD, and I really need to spend some time on that.
The idea of an MVC (Model-View-Controller) framework is to separate the different concerns of your code, and that usually this allows you to design a data model, and then let your tools create a scaffolding of your site. Such things aren’t new; I implemented a Chinese Chess web site in Ruby on Rails which uses this approach in 2005. I loved the MVC approach. Continue reading “SharePoint vs (?) ASP.NET MVC”