Archive Page 3

Coming Soon! The Business Application Strategy Survey 2011 Results

With the research completed and the results currently being processed in preparation for the inaugural PointBeyond Business Applications Survey, we have our first quick poll question to allow you to contribute directly to the research.

PointBeyond has already secured valuable input from over 200 senior IT decision makers responding to our September 2011 survey focused on business application strategy.

We are now busy interpreting the results and are confident that the research is going to provide a unique snapshot into how a significant number of businesses are approaching the selection and delivery of their application portfolios.  Headline making  trends are already emerging in the data relating to areas such as:

  • Application strategy drivers – what is new and what has changed?
  • What is the impact of getting it wrong?
  • The current and projected effect of the cloud on business applications
  • Today to mid 2012 – how will drivers change over the coming months?

Company Director and business application specialist, Dr Ian Woodgate, will highlight the important findings from the survey and share his expert opinion on the subject in a live webinar on November 16th. Please click here to find out more and to register. Everyone registering will also receive a preview copy of our research whitepaper.

Back to the PointBeyond website

Error communicating with Excel Services Application – Events 5231 5239 5240 (SharePoint Server 2010)

I’ve seen this issue twice on production systems now, and have a solution that has worked in both cases. From http://technet.microsoft.com/en-us/library/ee513104.aspx

Symptoms: One or more of the following symptoms might appear:

  • Delayed load times for workbooks.
  • Workbooks fail to load.
  • This event appears in the event log: Event ID: 5231 Description: Unable to reach Excel Calculation Server <URL of machine> [Session: <session ID> User: <username>].
  • This event appears in the event log: Event ID: 5239 Description: There was an error in communicating with Excel Calculation Server <URL of machine> exception: <exception message> [Session: <session ID> User: <username>].
  • This event appears in the event log: Event ID: 5240 Description: There was an error in communicating with Excel Calculation Server <URL of machine> exception: <exception message> [Session: <session ID> User: <username>].

The Technet article somewhat unhelpfully suggests a reboot. I’ve tried that and it works for a while then fails again. However I have found the following to be effective:

  • Log on to the SharePoint server(s) using the service account that is running the Excel Services Service Application
  • Log off

It seems that this creates a user profile for the service application account, which fixed the problem for me straight away, without a reboot.

Microsoft Project 2010 – Scheduling on-going tasks

I was looking for the best way to schedule on-going tasks, for example ‘project management’, in a simple project plan. I came up with a number of different ways of accomplishing this but have chosen to implement the method below.

Let’s suppose there are 2 people involved on a project, both of which are involved on the standard tasks, but 1 of which is also responsible for project management for 20% of the project lifecycle, therefore only allowing 80% of their time to be spent on other tasks.

I created 2 standard resources Bob (who will also be the project manager) and John and changed the Units of Bob to be 80%.

I then created a third resource Bob PM and changed the Units value of that resource to be 20%. My Resource Sheet now looks as follows

Back to the plan. I entered the appropriate tasks with relevant Start Dates, Predecessors, and Work values. The project lasts 2 weeks as per the below schedule

I know the project starts on Mon 3rd and finishes on Friday 14th so now I just need to add in the project management activity. Bob has time available to fit in 20% project management time due to the setup of the resources earlier. I add in a project management task as a ‘hammock task’ as follows to cover the project life cycle. Copy the date from the Start cell of Task A, this is the start date of the project. Highlight the Start date for the project management task and select Paste ->Paste Special -> Paste Link from the Task tab in the ribbon and click OK. Now copy the date from the Finish cell of Task F which is the end date of the project. Highlight the Finish date for the project management task and select Paste -> Paste Special -> Paste Link from the Task tab again. I then allocate this task to the Bob PM resource and now there is 16hrs of Bob’s time allocated to project management activities covering the project time period.

As mentioned earlier there are numerous ways to accomplish this and the above method is simple and may not suit you and that are many factors to consider when managing larger scale projects with shared resources etc. Other options include creating different calendars with only a 20% working week and assigning the task to a specific calendar.
Back to the PointBeyond website

SharePoint UK User Group Meeting Southampton 22 September 2011: SharePoint in the Real World

A great turn out for last night’s meeting, and I was very impressed by the quality of our speakers – all of whom were from local organisations that make use of SharePoint, and not regular speakers. They gave a refreshing and sometimes surprising take on the use of SharePoint.

First up was Gareth from a large local law firm. Gareth covered the challenges of the decisions that they had to make when implementing a SharePoint proof of concept from a standing start. Interestingly, Gareth did not present the SharePoint “Industry” in a very positive light. His frustrations included:

  • Being harassed endlessly by marketing teams and recruitment agents
  • Consultants with no knowledge of SharePoint but using it to get a “foot in the door”
  • Vendors who “Put SharePoint at the start of the name, and a zero at the end of the price”
  • Consultants with no interest in providing knowledge transfer, only in getting as much work for themselves as possible

Next up was Jim from Regs4Ships. Jim provided a fascinating insight into the world of shipping and explained their solution of running SharePoint on ships. Data is replicated between ships and office over a satellite link, with only 1Mb available per ship per day, so efficient compression and replication is essential. Their solution makes use of Infonic Geo-Replicator to send deltas via email.

After a break for refreshments at the bar conveniently located right next to the lecture theatre, we were back in to hear Chris from Southampton University. Chris explained their large scale SharePoint implementation which is designed to support a user base of 35,000 and comprises three farms. Chris also explained and demo’d a self service portal, that allows users to provision their own site collections. Chris explained the challenges they had faced with claims based authentication and how they had overcome them.

The evening ended with the giveaway of some goodies kindly provided by Regs4Ships, Axceler, and Microsoft.

See you at the next one!

Ian

Delivering Business Applications with SharePoint Composites: Don’t get Stuck!

Suppose that you are in New York and you want to come to my house. You could look at a map of the world that has New York and my house marked on it. Looking at the map you can see that London Heathrow airport is pretty close to my house. So you think, hey that’s cool I’ll fly over. You pay for your flight, tell me what time you are arriving, and tell your wife/husband/partner how much it costs. Sorted. Easy.

So you jump on the plane and all goes well for a few hours. You arrive at Heathrow and walk out of the airport. Now, Ian’s house is somewhere nearby isn’t it? Actually you’ve got still got 94 miles to go and although you have completed 97% of your journey you aren’t at my house. You’ve no UK currency and your mobile phone is flat (and you can’t plug your charger in because of our rather cool power socket design J). So you are stuck.

Let’s compare this to the case of building a SharePoint business application using tools such as InfoPath, SharePoint Designer, Excel Services and Access Services. It’s all too easy to get started with these tools without an absolutely clear idea of how your end solution will work. The tools allow you to do a lot very quickly. So you pull your application together and it almost meets your requirements. But then you hit a problem: the last little bit requires something that the tools don’t let you do. You are faced with having to resort to another tool, possibly some custom code, or even having to rework what you have already done. Also chances are you need to go back to the business and tell them that you need more time and/or money.

The conclusions to this are really as follows:

  • Before you embark on delivering a business application using SharePoint composites, be absolutely clear about what the end solution will be (where are you going)
  • Be clear about how the tools available will deliver all of the required functionality (what is the means of transport for each stage of the journey). If you do a proof of concept then make sure you tackle the difficult bits of functionality up front. Don’t just do the easy bits so that you can show the business users something nice! It may make them happy in the short term but they won’t like it when you have to go back telling them you need more time and money.

Enjoy your journey!

Back to the PointBeyond web site

Easy Tips to Improve Document Search Results in SharePoint

You have done all you can from a SharePoint perspective – Search is set up and it is crawling the documents, but the results returned are not what you’d expect. This is frequently the result of documents created without optimising them for SharePoint Search indexing.

The Search service in SharePoint crawls documents to index them for search.  This entails quickly scanning each document for words and phrases and ranking the document’s relevance accordingly. The Search crawl looks at filenames and titles first, then headers and finally the content itself.  Therefore, a keyword included in the title of a document helps it to rank higher than a keyword found in the content alone.

It is a common perception that Search will simply just work.  However, the reality is that it will only be as good as the content it is searching. The following tips are things users can do to help their documents appear correctly in search:

Check your Document Properties – I recently witnessed a search for the word ‘Policy’ that returned multiple documents displayed as ‘New Template’ , although when we opened them they were indeed policy documents.  On closer inspection we found they had all been created from one original document, overtyped and resaved multiple times, without anyone changing the document properties in Microsoft Word.  This led to the document having  a misleading appearance in SharePoint:

 SharePoint Document Title Properties

Search was in fact working correctly, but to the users it appeared that the results were meaningless.

This highlighted the difference between simply renaming a file when you save it and amending the document properties in Microsoft Word.

Micrsosft Word Document properties

 To read more about document properties see Microsoft Office help.

You can change the Title properties in SharePoint, but you must remember to do so after uploading the document, especially if using the multiple upload tool.

SharePoint Edit Properties

Check your Title – Make sure your Title and File Name is meaningful. I have seen many documents in organisations titled ‘General Admin’, ‘Update’ or ‘Checklist’. Initially, these may seem like sensible titles.  However, these titles don’t help Search identify the real subject of their content and they really don’t help your users identify whether they have found the correct document.

By contrast, a good title is a clear, precise and short description of the document’s contents. ‘Stationery Ordering Procedure’, ‘Update to Appraisal System 2011’ or ‘Setting up a New Customer Checklist’ are good examples of meaningful document titles.

Check your Headers – Microsoft Word has some handy styles to help you format and structure your documents. By using heading styles correctly, you are also helping SharePoint Search to crawl your document as efficiently as possible. It is therefore important to make sure that you have meaningful headings and preferably ones that include the key phrases people may search for if they wanted to find your document.

Microsoft Office Styles

Using header styles will also help your readers and can help you to auto generate Table of Contents for your document, something especially useful if your document is a long one.

To find out more about using styles visit Microsoft Office help

Check your Content – if the content of your document doesn’t contain keywords relating to the subject it covers, then this too may lead to it not appearing in the correct search results. To avoid this happening, you should always consider including an overview or summary that clearly outlines the topics covered in the document. This will help SharePoint Search index the document correctly and hopefully enable your users to identify the document they are looking for!

Back to the PointBeyond Website

Sites and lists not updating from the Content Type Hub

The Content Type Hub (CTH) brings fantastic new functionality to SharePoint 2010, functionality that anyone who has delivered or administered SharePoint 2007 will have been crying out for and no doubt welcomed with open arms.

The CTH can be a complex beast with settings located in lots of different places; Central Administration, Site Collections, sub-sites and the CTH itself.

Chances are, by the time you get to using content types from the CTH in document libraries way down in the basement of your SharePoint site structures it’s been a long time since you set up the Managed Metadata Service and the Hub – or perhaps you are an Information Manager and didn’t set it up in the first place.

So my question is: Where would you start to look if your content types in sub-sites and lists refuse to update properly?

Now I’m presuming here that you have correctly published the offending content type in the Hub, have run the 2 timer jobs in Central Administration and that the Site Collection you are trying to push the content type to is consuming the CTH.

In fact, I’m assuming you have one or more content type from the hub on your consuming Site Collection and have added them to document libraries – but now you’ve decided you need a new column on one of the content types.

You go through the same process described above (publishing the content type in the Hub, running the CA timer jobs etc.) but when you come to check the document library there is no new column.

To reassure yourself that you’ve done everything correctly, you look at the content type gallery in the consuming Site Collection and can see the new column. Very strange!

You’d be forgiven for thinking “this must be a setting in the document library”, or perhaps you forgot to tick the ‘Update all content types inheriting from this type?’ check box in the ‘Update Sites and Lists’ section of the content type in the Hub.

So you check and you check to no avail. You may even have tried running some PowerShell scripts to force the update. Nothing!

So what to do?

Turns out it’s simply the way the Managed Metadata Service Connection has been set up.

There are four useful little tick boxes, which you’re only likely to see at the point you create the service, two of which have a huge effect on how the Content Type Hub functions.

To get to them go to Central Administration > Application Management > Manage Service Applications > Highlight the ‘Metadata Service Application Proxy’ (click anywhere but the title) > Select ‘Properties’ on the ribbon (see screen shot below).

This should bring up the ‘Edit Managed Metadata Service Connection’ window.

Here you can see the four options I was talking about.

The first two are firmly aimed at the Term Store, but the last two have a huge impact on the CTH functionality as I mentioned. The last one is clearly what we’re after so let’s tick that box!

You should now see your document libraries and lists updating from the CTH without a problem.

As you can see, this can be a difficult problem to track down because the Site Collections are getting the content type updates as they should be, just not in the lists – but as ever, there’s just one more check box!

Back to PointBeyond web site

SharePoint 2010 Managed Metadata or Choice Column?

Interestingly enough this is a conversation I have independently had recently with two customers. How do you decide whether to use a choice column or a managed metadata column in SharePoint 2010?

Hopefully you have a properly defined Information Architecture (if not give me a shout J) and you are using content types effectively, preferably defining them in a content type hub and pushing them out through the managed metadata service. Note that this works fine with choice fields as well as managed metadata fields.

You may want to use a choice field when

  • You only have a smallish (say less than 100) items to choose from and they are not arranged hierarchically
  • You do not want to use the filtered views of libraries that are available with managed metadata
  • You want to create a “one off” column for a particular library, and have no requirement now or in the future to share that classification across other libraries
  • You want users to have a dropdown rather than the picker in the UI
  • You want to be able to set values in the datasheet view (you can’t do this with managed metadata)

When either are acceptable I tend to favour managed metadata as it is more powerful and flexible – unless one of the bottom two above is an absolute requirement.

Ian

Back to PointBeyond web site

Finding Duplicate Documents in SharePoint using PowerShell

This script looks through all documents stored in a SharePoint site collection and finds duplicate files based on document contents rather than document names. This script has been written for SharePoint 2010 but should find duplicate documents in SharePoint 2007 as well with very little modification.

Over time, it is quite possible the same document will be uploaded to numerous SharePoint libraries. Keeping track of duplicate content spread across multi libraries can be practically impossible.

Building on the article here http://blog.codeassassin.com/2007/10/13/find-duplicate-files-with-powershell/ that details duplicate checking on fileshares, the following PowerShell script scans all your document libraries with a site collection for duplicate content by calculating an MD5 hash of the file contents. The script groups identical hashes and produces a list of all duplicated files, detailing the full url to item and the file name.

To run the script, copy the contents to notepad and save as a .ps1 file on one of your SharePoint servers. Then launch a PowerShell console and run the ps1 file.

Output to console showing duplicate files

PowerShell Console Output

The function returns the full path of all duplicated content.

This information could be piped back into SharePoint, or exported to Excel for analysis. You could even set this as a recurring job. In a future article, I will package this functionality into a timer job feature.

At present, the script stores all results in memory while it is running. If you are running this over a large site collection this may not scale very well. It may be worth streaming the results into a SQL table or similar. Also, at present this script will only evaluate content on a site collection basis but could be scoped to a web application or a whole farm if required.

Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue

function Get-DuplicateFiles ($RootSiteUrl)

{

$spSite = Get-SPSite -Identity $RootSiteUrl

$Items = @()

foreach ($SPweb in $spSite.allwebs)

{

Write-Host “Checking ” $spWeb.Title ” for duplicate documents”

foreach ($list in $spWeb.Lists)

{

if($list.BaseType -eq “DocumentLibrary” -and $list.RootFolder.Url -notlike “_*” -and $list.RootFolder.Url -notlike “SitePages*”)

{

foreach($item in $list.Items)

{

$record = New-Object -TypeName System.Object

if($item.File.length -gt 0)

{

$fileArray = $item.File.OpenBinary()

$hash = Get-MD5($fileArray)

$record | Add-Member NoteProperty ContentHash ($hash)

$record | Add-Member NoteProperty FileName ($file.Name)

$record | Add-Member NoteProperty FullPath ($spWeb.Url + “/” + $item.Url)

$Items += $record

}

}

}

}

$spWeb.Dispose()

$duplicateHashes = $Items | Group-Object ContentHash | Where-Object {$_.Count -gt 1}

foreach($duplicatehash in $duplicateHashes)

{

$duplicateFiles += $Items | Where-Object{$_.contentHash -eq $duplicatehash.Name}

$duplicateFiles += “————————————————————”

}

}

return $duplicateFiles |Format-Table FullPath

}

function Get-MD5($file = $(throw ‘Usage:Get-MD5[System.IO.FileInfo]‘))

{

$stream = $null;

$cryptoServiceProvider = [System.Security.Cryptography.MD5CryptoServiceProvider];

$hasAlgorithm = New-Object $cryptoServiceProvider

$stream = $file;

$hashByteArray = $hasAlgorithm.ComputeHash($stream);

return [string]$hashByteArray;

}

Get-DuplicateFiles(<your sharepoint site>)

Back to PointBeyond Website

What are my choices for building a Business Application in SharePoint?

There are different approaches to building Business applications in SharePoint. Here we take a look at the pros and cons of each to help decide which is right for you.

Browser Based Customisations

There are out of the box lists, web parts and templates in SharePoint 2010 that can be used to create simple applications such as task trackers, calendars, charts and more. The user can choose their tool from the menu on their site and then configure it directly in the browser. They can also combine lists with workflows to automate processes such as approval and feedback.

Pros

Cons

  • Available Out of the box
  • Easy to use
  • Quick to set up
  • Good for simple processes
  • Low Risk
  • Limited to what is available
  • Simple customisation only
  • Not possible to deliver complex processes

Composite Tools

Composites are one of the six key capabilities of SharePoint 2010. These are tools provided to help you connect to data and reuse it through your applications, creating a solution through a ‘composition’ of the strengths of the individual tools available. This enables you to develop business applications in a stable environment and deploy these solutions to selected audiences.

The following are the tools currently available for creating composite applications:

  • Excel Services
  • Access Services
  • Visio Services
  • InfoPath Forms
  • SharePoint Designer
  • Business Connectivity Services

Pros

Cons

  • Can be fast and effective

  • Good for simple to medium complexity
  • Good for low to medium volume
  • Good for prototyping
  • Low risk

  •  You don’t have complete control of how it will look or work
  • There are limitations to what is possible
  • If you change your mind you may have to start again
  • Change management can be difficult

Third Party Products

There are a variety of products on the market that can be used to extend SharePoint. They can generally be split into three groups:

Components are products you can plug into your existing SharePoint system to help you achieve a solution. These are the building blocks which enable you to extend SharePoint’s out of the box capabilities.  Examples are: image viewers, bulk editing tools, reporting tools, group chat consoles and social media applications.

Workflow Applications give you the tools and capabilities to go beyond the out of the box SharePoint workflows and automate processes to meet your organisation’s needs. K2 and Nintex are great example of these, giving you drag and drop user interfaces to help build your workflow logic and rules.

Complete applications are products that you can buy, install and with some configuration, start to use straight away. They normally focus on one business solution delivering enhanced tools and ready to go processes that provide a complete solution in one area e.g. CRM, HR Management, Document management etc.

Pros

Cons

  • Someone else has developed the tools for you

  • Saves time
  • Benefit from Third Party expertise in a business area
  • Can often try before you buy

  • May not always be compatible with your environment or other systems
  • Can require additional support from Third party
  • Cost of product, additional licencing and support
  • May still require bespoke customisation

Custom Code

Both SharePoint Designer and Visual Studio can be used to customise SharePoint to create powerful business applications. However, developing an application on the SharePoint platform with custom code requires sound development and coding skills as well as an understanding of the SharePoint Framework. Custom coding is useful if the application you need is particularly complex or needs to do something that can’t be achieved by other means.  A common pitfall to be aware of are the problems custom code can cause later down the line when you come to upgrade. Working with experienced SharePoint developers will help to ensure that any that future changes won’t be problematic and that migration and scalability factors are taken into consideration.

Pros

Cons

  •  Creates a bespoke solution
  • More control over the look and feel of SharePoint
  • Can solve problems that out of the box solutions can’t
  • Can be a lengthy process
  • Can cause other bugs and defects
  • Requires test and development environments
  • Can be unnecessarily complex
  • Can make future upgrade difficult

Back to PointBeyond Website

« Previous PageNext Page »



Follow

Get every new post delivered to your Inbox.

Join 279 other followers