How to reinstate Contact Linking in Outlook 2013

For Outlook 2007 and 2010 there is an Option > Contacts > Linking > Show contacts linked to the current item

This has been removed in Outlook 2013, apparently because they have a new feature of Links when you are on People and the current view is People and then look at details. I don’t use that but and tend to use the List view which does not have the links. Also I have historic links, so wanted to reinstate links. Thanks to:

Which I found via

So steps copied from first of these are:

  1. Regedit
  2. HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\Preferences
  3. Add DWORD: ShowContactFieldObsolete
  4. Set to 1

That page also referred to a Group Policy registry setting. I did not have that on my machine, did not create it and found that the links were there anyway

To remove:

Set to 0, or remove the Key



Office upload center upload failed permission issue


Sometimes Office upload centre just stops working.

Sometimes with failed permission, sometimes with

“OneDrive for Business found a problem while accessing the Microsoft Office Document Cache and needs to repair it before it can continue.
As part of the repair a copy of the cache will be saved as a backup and a new cache will be created.”

See also: on time 5/14/2014 10:58 PM

If required then:

  1. Stop syncing
  2. Rename folder as backup in case you lose files
  3. Stop related services in Task Manager Resources, including Groove, MSOSync or similar
  4. Clear cache to “C:\Users\username\AppData\Local\Microsoft\Office\Spw” and delete all the content. You will see that this is all related to groove, and spw equals SharePoint Workspace.Go to “C:\Users\username\AppData\Local\Microsoft\Office\15.0\OfficeFileCache” and also delete all content from this folder. This is where all the caching from your files are stored.
    Note : Just try to delete all, if one or two items cannot be deleted, that’s OK.
  5. Sync again
    It may or may not allow you to choose a location



Programming against Sharepoint (Online) Client Side Object Model CSOM


Add References to:

  1. C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\ISAPI\Microsoft.SharePoint.Client.dll
  2. C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\ISAPI\Microsoft.SharePoint.Client.Runtime.dll

Problem 1

The referenced assembly “Microsoft.SharePoint.Client, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c, processorArchitecture=MSIL” could not be resolved because it has a dependency on “System.Web, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a” which is not in the currently targeted framework “.NETFramework,Version=v4.0,Profile=Client”. Please remove references to assemblies not in the targeted framework or consider retargeting your project. SharepointWinFormsCSharp

Solution 1

Ensure that the project targets .Net Framework 4 and not Client Profile

Project > Properties > Application > Target Framework

Problem 2

The type or namespace name ‘SharepointOnlineCredentials’ does not exist in the namespace ‘Microsoft.SharePoint.Client’ (are you missing an assembly reference?)

Solution 2A – use this

First check that the spelling is precise including casing

Second, odd, but I copied the references to the bin folder and re-directed the reference to there and it started working. Odd thing was when I then pointed the reference back it continued to work.

Solution 2B – just creates a new problem

  1. Select Reference Microsoft.Sharepoint.Client
  2. Right-Click > Properties
  3. Embed Interop Types change from False to True
  4. Build

This returns new problem

  1. Cannot embed interop types from assembly ‘c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\ISAPI\Microsoft.Sharepoint.Client.dll” because it is missing either the ‘ImportedFromTypeLibAttribute’ attribute or the ‘PrimaryInteropAssemblyAsstribute’ attribute
  2. Cannot embed interop types from assembly ‘c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\ISAPI\Microsoft.Sharepoint.Client.dll” because it is missing the ‘GuidAttribute’ attribute

How to use CSOM

After the above each of the use cases in the following demonstrations then worked.

How to: Complete basic operations using SharePoint 2013 client library code

            using (var context = new ClientContext(""))
                var web = context.Web;
                var login = "xx@xx";
                var password = "xxxx";
                var securePassword = new System.Security.SecureString();
                foreach (char c in password)
                context.Credentials = new SharePointOnlineCredentials(login, securePassword);

The end

SkyDrive Pro “Can’t connect to the specified SharePoint site…”


“Sorry we are having some temporary server issues.”
Office Outlook reporting that it is not activated

Solution 1

This may be a bit extreme and you may lose other settings, but this was the only thing I found that worked.
Internet Explorer > Tools > Internet Options > Advanced > Reset

Solution 2

My sub-site had unique permissions. When I removed the unique permissions, I was able to sync.

What did not help

Programs and Features > Office > Change > Repair

Windows Key – type credentials > Credential Manager > Remove a couple of the office credentials.

Add external access for Lync

When trying to make a Lync IM

When contacting your support team, reference error ID 1002 (source ID 243). Troubleshooting information is available online, including best practices for using Lync.

In Office 365 Plan E3

  1. Lync Admin Center
  2. Organisation
  3. External communications must turn this on

The other organisation must also have this setting on:

This message wasn’t sent because <recipient>doesn’t have permissions on your organization’s network, or because the address is incorrect. Please contact your support team.