Office 365 Outage 9/29

29 09 2014

Just wanted everyone to know that as of this morning O365/SharePoint online is suffering a slight outage.

You may experience some delay in getting to any site collection in SharePoint Online.

Documents and list items will not display in web parts presented on the SharePoint site “canvas.”  It you click on the web part titles you may or may not see content.

There have been thousands of support calls on this issue which may have arisen around 8:30 AM today.


Online: issue successfully fixed Monday, September 29, 2014, at 5:19 PM UTC. Post-incident report available within five days….


View HTML pages in SharePoint Online.

23 07 2014

Did someone in your organization save an entire website in a document library?
Did they complain they couldn’t open the start.html page?
Do you have users that want to view html pages inside SharePoint online?
If you answered yes to any of these questions (i am aware of the irony of this post), then I have a solution for you!
Simply open your html files in your library using explorer view and change the extension from HTML to ASPX. It even works with Flash content.
Yup, its that easy (and confusing at the same time, but for other reasons).


CSGPRO Guest Blogging

11 06 2014

As a new member of the CSGPRO team, I have committed to posting more Office 365 blogs.
Here is a dandy one for anyone about to migrate to the cloud.
Enjoy the goodness.

ps, yes thats me.

Taking Longer Than Expected

11 03 2014

So a couple of weeks ago, I said i was going to move the blog to office 365. Well it has taken longer than expected. So i have decided to keep posting here for the time being. Thanks for the patience.


Once more unto the breach, dear friends. SHAREPOINT STYLE

27 01 2014

The decision hath been made. SharePointDojo is in cocoon mode once more. From said cocoon The Helios Cooperative will rise like a phoenix built on the very platform which the caterpillar of SharePoint Dojo could not be. Hence forth, SharePoint Dojo shall be….wait for it…..

THE HELIOS COOPERATIVE. A SharePoint portal about SharePoint built on Office 365.

Patience is greatly appreciated

Once more unto the breach, dear friends, once more;
Or close the wall up with our MICROSOFT dead.
In peace there’s nothing so becomes a man
As modest stillness and humility:
But when the blast of SHAREPOINT blows in our ears,
Then imitate the WORKFLOW action of the tiger;
Stiffen the DOCUMENT LIBRARY sinews, summon up the blood,
Disguise fair nature with hard-favour’d METADATA rage;
Then lend the eye a terrible INFOPATH aspect;
Let pry through the portage of the CSS head
Like the brass MASTERPAGE cannon; let the brow o’erwhelm it
As fearfully as doth a galled GHOSTED PAGED rock
O’erhang and jutty his confounded COLUMN base,
Swill’d with the wild and wasteful oceans OF SITE COLLECTIONS.
Now set the teeth and stretch the nostril wide AS A WEB APPLICATION,
Hold hard the breath and bend up every spirit OF SHAREPOINT DESIGNER
To his full height. On, on, you noblest English TRANSLATION ENGINE.
Whose blood is fet from fathers of war-proof SPELLCHECK!
Fathers that, like so many Alexanders OF WILD CARD ENTRIES,
Have in these parts from morn till even fought
And sheathed their swords for lack of  argument:
Dishonour not your mothers; now attest
That those whom you call’d fathers did beget you.
Be VSS SHADOW copy now to men of grosser blood,
And teach them how to war. And you, good yeoman,
Whose SEARCH limbs were made in England, show us here, LINKS
The mettle of your pasture; let us swear ON CENTRAL ADMIN
That you are worth your breeding; which I doubt not;
For there is none of you so mean and base,
That hath not noble lustre in your CONTENT DEPLOYMENT  eyes.
I see you stand like greyhounds in the slips,
Straining upon the start MENU. The game’s afoot:
Follow your spirit, and upon this charge
Cry ‘God for MICROSOFT, SHAREPOINT, and Saint OFFICE 365!’


LORD Nando and some famous english guy.

Dynamic Link to a specific Infopath Form View using a SP Workflow

11 12 2013

I had a requirement to create an infopath form for a client for assigning security badges. Not a difficult thing to do, I said. But as I gathered the requirements, and confidently shook my head back and forth saying, YES WE CAN!, I realized something nagging in the back of my mind.
I of course paid no attention to it and got to work on the infopath form.

It was nothing complex, just a user input form and an approval section at the bottom for official use only. But then that a fore mentioned nagging feeling, finally surfaced. I was going to have to use infopath views to hide the official use only section from the user. Simple enough for infopath, but now i had to surface a link to that view in a custom workflow email. That one took a bit of investigation, but i found 2 solutions for this. I will give credit to both parties, but i had to combine them to create one DOJO worthy Solution.

The first part of the solution can be found here. Kudos to  S.Y.M. Wong-A-Ton  for blogging about this.

The second part of the solutions comes courtesy of the wonderful Laura Rogers. Nicely Done!

Here is how I did it.

  1. First in SharePoint Designer 2010 i created a simple condition :
  2. “if current item equals value then Email a user”
  3. step1
  4. In the email editor I created a custom link and in the string builder i copied the following url and filled in the blanks.
  5. http://ServerName/SiteName/_layouts/FormServer.aspx?XmlLocation=[INSERTLOOKUP] &Source=http%3A%2F%2FServerName%2FSiteName%2FLibraryName%2FForms%2FAllItems%2Easpx&DefaultItemOpen=1
  6. From the string builder I clicked on add or change lookup and inserted the following in the [INSERTLOOKUP] referenced above.
  7. Data Source = Current Item
  8. Field From Source = Server Relative url. step3
  9. The new Url should look like this:
  10. step2
  11. I adde a reference to the hidden view using : &DefaultView=hiddenview
  12. Save and publish the Rule and test it out.
  13. The url link should open the infopath form with the new default view.

VOILINS……i mean voila.



SharePoint 2010 Documents Failing to upload in the morning.

25 10 2013

This was by far the most complex and vexing issue I have encountered in SharePoint. A little background on this first.

Everyday users would get the following errors BUT ONLY IN THE MORNING!!!:






This by itself seems quite strange to begin with, so i started down the familiar troubleshooting SharePoint path, starting with event viewer, then uls, then fiddler, then pulling out my hair, then calling Microsoft and then pulling out my hair some more.

I tried modifying the web config files for max upload time and ASP timeouts with no luck.

I looked at Load balancing settings and that yielded a dead end.

One promising direction i started going down was investigating the famed warm up script. This particular direction seemed fruitful. I wasn’t exactly sure that the warm up script was warming anything up. I asked one of my colleagues (sp dev, and a talented one) to help me create an automatic document upload script. Why an automatic upload script you ask? because after the first couple of users uploaded a document to SharePoint in the morning, the rest of the day it worked fine. So we created this band aid work around till we could figure out why it was happening.

So band aid in place we continued testing with fiddler and we found this little nugget of stress:

Tuesday, October 22, 2013 12:28:00 AM Start Upload http://prodservers/DatabaseWarm-upFile.docx

Tuesday, October 22, 2013 12:29:41 AM Upload Complete.  Duration = 100.7616918

Interesting. All uploads at 12 am where taking over at 100 seconds. I looked for timer jobs that kicked off at midnight and i found quite a few, but they were default SharePoint timer jobs. I didn’t think messing with those was a road we should go down. However, looking at performance data we could NOT ignore this particular spike in IO. My dev colleague identified [dbo].[proc_UpdateStatistics as the culprit. This is the stored procedure that was causing the issue.  There is an actual health analyzer rule that kicks off this timer job.


I had never heard about this before so i took to the net to see if anyone had this problem.

Thanks to Chun Liu’s blog we found this:

What? I say, what? How have i been working with SharePoint this long and never heard of this at all?

Needless to say, the fix that worked for us to was to set auto create statistics to false on all content databases.

Be warned that this should only be done in content databases and not search ones.


At midnight upload files went fro 100 seconds to 2 seconds.

This took me 3 months to diagnose and fix.

Enjoy this golden nugget! Learn from my fail.




Get every new post delivered to your Inbox.

Join 106 other followers