Wednesday 11 November 2015

SharePoint Online 2013 - ContentTypeHub Issues with Word Templates

ContentType Hub Issues with Word Templates

Recently we had an issue at a client, when using Document Content Types to Propagate a Word Template to Sub-Sites.

What would happen is after we create the content type and publish it, we would see the created content type in the folder structure of the sub-site. But clicking on it, to open the document, it failed.

Clicking "New" gave the option of creating a new document from the content type template. In this case, TestDocContentType

Instead of opening the Word Document in the editor, it gave the option to create a new document (This should NOT happen)  I typed a name and clicked on "OK"

After clicking "OK" this error popped up and the document was not opened.


We did allot of troubleshooting trying to figure the issue out, as it worked for Excel Templates, but not Word. Eventually we logged it with MS Online Support. First level support could not resolve the issue either, so it was escalated to second level support where help was found!

What seemed to be the problem (Specifically for Word Templates) is that for some or other reason you can no longer specify a relative URL to the location of the document template, for example https://clientname.sharepoint.com/sites/contenttypehub/documents/wordtemplate.docx. The system will change it into a relative URL (./sites/contenttypehub/wordtemplate.docx)

This ALWAYS worked!!

Specifying a relative URL when creating a content type

The method that should be used (Specifically for Word Templates) is by uploading the Word Template directly to the content type.

Upload Template directly to content type

After uploading and publishing the content type (The Publishing frequency is another sore point for me. There is just no info available on exactly when the publishing jobs run. According to this article, it may take up to 48 Hours to propagate, which i find rather ludicrous. I was lucky and it took about 2 hours before the published templates was available.

This case the Project Initiation Document was selected that was uploaded to the content type in previous steps

The document template then opens successfully!


 
 Below is the feedback i got from the support engineer. Note the "By Design" in inverted commas. To me, it would seem like this is "Broken by Design", but you will see MS is looking at "Enhancing" (Fixing) the issue

Engineer's feedback

I hope this may help some of you sorting out this issue. Just to re-iterate again, Excel Templates work when specifying the relative URL, not WORD templates

Andre






Thursday 3 September 2015

Project Online 2013: Duplication of Custom Views

Project Online 2013: Duplication of Custom Views

I have come across a bug with Project Online, when creating custom views, this impacts any custom views, like Project , Project Center, Resource Center views.
 
When saving these views, if you click on the "Save" button more than once when initially creating it will save a duplicate of the view, with the same name.
 
I logged this with Microsoft and they confirmed they could re-produce the issue.
 
Duplication in Views
Latest feedback from MS is that they are working on the issue and will revert with feedback.
 
 
Once I have any further feedback I will revert on this post.
 
Andre

Thursday 25 June 2015

SharePoint 2013 Install Error : Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)

I have recently come across a weird issue when installing at a new client. If a am correct, what caused this issue, was a mismatch between SharePoint 2013 and Project Server 2013 SP/CU on initial Install.

SharePoint 2013 with SP1 was used to install but Project Server 2013 was not the SP 1 install. I then tried to uninstall Project Server 2013, but it failed. I thing Uninstalled SharePoint and installed again. The install went without hiccups , but when running he config wizard using the GUI or via PowerShell I got this error :

Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).at System.Guid ..........

The reason for this seems to be an invalid value in a registry key of "0"

The solution is to open Regedit and navigate to: 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server extensions\14.0\WSS\InstalledProducts

The values in there must have a Proper Data Value set to work. Use list below to set correct value :


For Enterprise trial Version: 88BED06D-8C6B-4E62-AB01-546D6005FE97 
For Enterprise licensed Version : D5595F62-449B-4061-B0B2-0CBAD410BB51 
For Standard trial Version : B2C0B444-3914-4ACB-A0B8-7CF50A8F7AA0
For Standard licensed Version : 3FDFBCC8-B3E4-4482-91FA-122C6432805C

If you then run the config wizard, it should run through without any hickups.

I hope this helps someone else with issue as i was stuck for quite a while on this one.