Tag Archives: SharePoint

Degraded Search SharePoint 2013

So recently I came across this error within #SharePoint2013.

Search service overall state: Degraded

1

This was actually really easy to fix for me in this instance.  Both of my WFE’s had run out of space on the Index #LUNs. As soon as I expanded the disk, the #Degraded warning triangle disappeared!

Nice and simple but make sure you check this before resetting the Index.

Creating default SharePoint permissions groups (Hostname site collection)

When you create a #Hostname #SiteCollection within SharePoint 2013 you will notice that the default user groups aren’t there. This is because they aren’t created when you use #PowerShell to create a hostname site collection.

To get these groups back, this can be done via PowerShell or simply doing the following:

Navigate to http://yoursitename/_layouts/15/permsetup.aspx

From this page you will see the following:

groups

Simply click on OK and the groups will be available.

The important part of the URL is

_layouts/15/permsetup.aspx

Have fun with your permissions!

Active X errors SharePoint 2013/ SharePoint 2010 & IE11

This may not be the same for everyone but I recently had this error at work and it was doing my head in.

When a user got upgraded to IE11 from IE8 and went to a #SharePoint site, they were presented with a nice #ActiveX error that just wouldn’t go away! After lots of Investigations and Googling I still couldn’t find a solution.

FIX: 

Eventually I decided to get our #webapp URL’s and Host-name site collections added into the trusted site list and deployed via #GroupPolicy

Now we don’t get any #ActiveX issues within the sites we added to the trusted site lists.

As I said above, it might not apply to everyone but it certainly worked for the company that I work at.

Code blocks are not allowed in this file

Problem

Users report the following error when attempting to access a document library in #SharePoint.

An error occurred during the processing of /site/SharedDocuments/Forms/AllItems.aspx. Code blocks are not allowed in this file.

Explanation

Ever so often I have clients contact me with a SharePoint library fully corrupted reporting an error such as “Code blocks are not allowed in this file”.  The error is, in fact, limited to a specific view but it’s usually the default view, therefore the error makes the library appear like it is completely inaccessible.  The root cause of the error is simple – a user replaced a view file from the /forms/ folder of the document library, typically “AllItems.aspx” such as the screenshot below suggests.  Typically this occurs when the user is using explorer view but I’ve heard of manifest presentations of this error as well.

Solution

1) Open site that contains the library

2) Click on “Site Actions” >> “Site Settings” to view the site settings page “_layouts/settings.aspx”

3) Click on the library that displays the error to view the library’s settings page

4) Add a new view to the library and check the box “default view”

Such a long week

Well the week is finally over! It’s the first week in 3 weeks I have actually done a full one. I’m getting too old for all this working malarky! As much as I love it, creating/designing and getting my #SharePoint head on, some times it’s just a little too much. I’ve been working on my own all week with people off on holiday. Supporting #SharePoint for over 3000 users, over 50 different sites and looking after over 40 servers has definitely taken it’s toll on me this week. Not only that out of hours work also and on call! I had a major failure with just a simple server reboot, windows updates decided to try and install when it was coming back up and got the server stuck in a boot loop. 5 hours later at 2:30am it finally started reverting the changes!

Nothing much has happened this week except work, playing some #Fallout4, eating like a student and finally getting a well overdue tesco delivery done!

I’ve not really got much planned for the weekend except maybe just some sleep and some geekiness. I really fancy trying to get a decent wiki built into #Wordpress if it’s possible, I’ve not actually read up on it and I’ve been looking into getting #Confluence installed on my web server but it turns out it just won’t have enough resources.

SharePoint post!

All this talk about Confluence recently has really made me want to blog about SharePoint so I thought I would write about something that I have recently had to do. This was built within SharePoint 2013 and although it’s not really something great to some people, it has saved a lot of money within the company I work in and has made peoples lives easier for the tasks they are set to do.

I was tasked with replacing the manual post for a complete site (400 items per day) not very much but for a small site this is still quite a lot when you take into account the opening, checking, reading and actioning it.

I created a basic SharePoint team site within SharePoint 2013 and created a library for each area (7 in total) which all had unique permissions, locked down via Active Directory group embedded within a SharePoint group with custom permissions. The users can only open, edit meta data and view the libraries that they have permissions to view. No delete options! We don’t want someone getting the hump with a piece of post and deleting it because they don’t want to action it!

INFO: All of the post is delivered to our main sorting office and is opened, sorted and then put into a machine which scans the documents, converts them to PDF and sends them to SharePoint.

I created a library called “Drop Off” which is where all the items are sent to, during the send to SharePoint options the people in the sorting office can assign meta data to the documents which when doing in bulk really doesn’t take that much time.

Once the files hit the “Drop Off” area a custom workflow with “App Steps” run on each item and move to the relevant areas using the “Business Type” column I created.

If an items has been scanned incorrectly the users can just change the “Business Area” drop down menu and another custom workflow using “App Steps” will move to the correct area even if the user doesn’t have permissions to that folder.

By doing this I have ensured that all post is captured, none can go missing and no one can delete something. It also has full auditing on so managers can see who is doing what and how many items are currently completed, outstanding etc.

The completed items are then paused for 60 days before being deleted. During this time if someone needs to edit the meta data for this post the timer is restarted for another 60 days.

This isn’t on a big scale compared to one I built previously within SharePoint 2010, it’s built in the same way using “Impersonation Steps” and gets roughly about 1200 items of post each day. Yep that is a lot of storage in use to say an item of post can have 20 pages with a total PDF size of 40MB depending on the contents of the pages and the 60 day deletion limit.

So that is just a little something I have been working on recently, I will update more when I get some of my other projects completed and the outcome of them!