Archive for the ‘SharePoint’ Category


A New Year’s Resolution for Evernote – More Tags and Less Notebooks


This post has now been migrated to

Follow this link to go directly to the article.


Firefox IE Tab Script Debug Errors


Recently I’ve been working a little bit with Microsoft Office SharePoint Server 2007.  It is recommended that Internet Explorer is used to interact with this web based system as it provides the widest and tightest integration and range of features.  Unfortunately I have a strong preference for Mozilla Firefox over Internet Explorer.

However there’s a nice add-on for Firefox that helps me get round the annoyance of having to have two browsers open – IE Tab.  Whilst it is still fundamentally using Internet Explorer, it allows me to set sites to automatically load into a Firefox tab and render a page using the Internet Explorer ‘engine’.  One browser window and no need to remember when to open another browser.

Unfortunately SharePoint seems to play poorly sometimes.  Whilst still fundamentally working I was getting a lot of problems accessing my ‘My Site’  and occasional problems in other areas.  I was plagued by dialog boxes asking me if I would like to debug when trying to move the mouse pointer to click on a link.  So much so that it just seemed to be unusable.

This seems to be a known issue (and looks like it falls back to some poor SharePoint coding), and Microsoft recommend simply turning off the warnings by setting an option in Internet Explorer.  Far from ideal, but it’s not like I can fix the problems for them.

Disable Script Debugging

Disable Script Debugging

To set this, open Internet Explorer, select the tools menu and Internet options… .  Select the Advanced tab and in the browsing section select the “Disable Screen Debugging (Internet Explorer)” option.

Unfortunately the debug messages continue to appear, but they don’t appear in Internet Explorer when it is run outside of Firefox.  I double checked and without this option set Internet Explorer did experience the same issues.

The resolution to the IE Tab in Firefox is however close to hand.  It seems odd at first that the disable option explicitly mentions Internet Explorer.  After all what else would you set an option for…?  Well it looks like there’s a separate option for anything using the Internet Explorer rendering engine outside of the main browser … such as IE Tab.  The option is “Disable Screen Debugging (Other)” and it works like a charm.

So until Microsoft sort out their SharePoint warnings and for all those IE Tab users out there who need to use SharePoint I’d recommend popping into Internet Explorer and setting the script debugging options.


SharePoint Filenames Issue


Today I came across an issue in Microsoft SharePoint Server 2007 (a.k.a. MOSS).  I was trying to upload some Microsoft PowerPoint slides into a slide library in a My Site and everything had gone fine with the first presentation, but the second one I tried came up with an error:

1 of 1 slides being published to ... failed

1 of 1 slides being published to ... failed

As you can see this is not a useful message as there’s simply no indication of why the failure occurred.

After a couple of minutes trawling the web I came across a TechNet article that suggested using explorer and uploading using WebDav might overcome this.  I published the slides to a local folder and set them copying to the library through explorer.  Unfortunately this didn’t work either.

An error occurre copying some or all of the selected files.

An error occurred copying some or all of the selected files.

Another meaningless message and still no further towards resolving the issue.

After another five minutes of further hands on and Internet free investigation I found the cause of the issue.  Apparently SharePoint is a bit particular about file names.  If a file name has two successive dots / periods in it, then it won’t allow you to upload it.  I checked this for document and image libraries too.  All libraries are lists in SharePoint, so I’m reasonably confident that it’s an issue across the board.

So if you have a file named “” for example would give you the issue but “” would work just fine.  So if you see an error like those shown above, check your filename and rename it if it has the two successive dots.


Merging URLs into SharePoint Document Libraries


After spending a bit of time looking at service desk records today I had the opportunity to look at a particular request where a SharePoint user wanted to include links to files on other web sites in a document library without uploading the file onto the SharePoint site.  This is actually a really nice idea as then if the other site is updated (assuming the URL remains the same), the latest version is always accessible via the SharePoint site.

Now normally links would be handled by using a link based web part, but the integration with a document library was what made this notably interesting.

Whilst a custom list web part could provide an interesting option, the document library the user wished to add to was already in use so I took the simpler and more pragmatic approach.

Most web browsers (notably Microsoft Internet Explorer which is the browser of choice for using Microsoft SharePoint) allow bookmarks to be saved out (e.g. by drag and drop from the address bar/field) into a simple URL file a.k.a. an Internet short cut file (at least you can in Windows XP which the user is running).  So if this can be done it would make sense to upload this into the document library.

Unfortunately by default URL files are on the ban list for SharePoint so a system administrator must first amend the list in the operations settings to allow URL files to be uploaded.

This should have been the solution, but when trying to upload the file I at first got a sample file being upladed onto SharePoint from another web site.  Exactly what I was trying to avoid.  However the option to upload multiple files uses a different upload process.

Choosing just one file on the upload multiple files (to a document library) option will successfully upload the URL file.  once uploaded to the document library, any user clicking on the file then gets the appropriate browser action that relates to the link.  This is actually quite a versatile thing to include into a document library as this could in theory (though I didn’t actually get around to trying it) provide access to FILE, FTP and mail-to protocol actions as well as HTTP for the typical URLs.

The developer in me still wonders what could be done with a customised list with this sort of functionality requirement in mind….