Comments on: Display SharePoint in Outlook

By: Matt Bramer

Matt Bramer — Fri, 20 Aug 2010 22:05:13 +0000

Thanks for your feedback JoyceMR!

There must be some settings that are causing the error. Just out of curiosity, I tried this on a another computer here (Office 2010 and WSS 3.0, XP SP3), and I didn’t get any errors. I’d be a bit lost as to how to track down these settings, but if I remember correctly, Outlook uses Word as it’s HTML rendering engine. Settings between these two must be causing this issue altogether.

By: JoyceMR

JoyceMR — Thu, 19 Aug 2010 22:12:48 +0000

Just tried this with Outlook 2010 and SharePoint Foundation 2010 (both RTM). Pointing to the home page of my SP2010 project site I received a script error on the intial load (Object doesn’t suppor this propoerty or method with url pointing to _layouts/1033/init.js?rev=…..). Replied to continue running scripts on the page and it rendered. Received same error on each page to which I navigated. Also found it had trouble loading the ribbon when I tried to edit a list item. Looks like it would take some changes to get even a single page to load without error. Search Center gave multiple errors per page but then did render the search results and it did allow right clicking to open the desired result in a new window. There are deffinately some possibilities here. We’ll just need more time to work with it.

By: Jay

Jay — Thu, 19 Aug 2010 07:02:56 +0000

My guess is that scripting is disabled altogether in outlook (mine).
The site settings and change user drop downs do nothing when clicked. Normal links work fine. Can’t test the quick launch links as the mouseover error kicks in as soon as I get near them.

By: Jay

Jay — Thu, 19 Aug 2010 06:51:17 +0000

Already in the Intranet Zone, set security to low and restarted outlook.
Same deal. Mouseover errors.
Not a major problem (for me), probably not something I’d use… I was just trying out the blog post.

By: Matt Bramer

Matt Bramer — Thu, 19 Aug 2010 01:43:39 +0000

This may be a long shot, but can you put the URL of your site in the Intranet Zone under Internet Options, Security. Set the security level to low, if you are allowed to. If that doesn’t work, I’m at a loss for other options to try.

Anyone with Office 2010 (non-beta) want to chime in?

By: Satish Srivastva

Satish Srivastva — Wed, 18 Aug 2010 06:02:48 +0000

Thanks Dave. I have used this before but forgot about it. I have used now in SharePoint 2010. It works fine!

By: Jay

Jay — Wed, 18 Aug 2010 05:47:06 +0000

Nope not a beta version…
version 14.0.4760.1000 (32 bit)

Definately mouseover events that are causing the problem.
I’m also using Windows 7 but not sure what this means “linking to WSS3.0″ I just adding a feed to the feeds folder in Outlook 2010
Stand alone copy (Internet email not exchange connected) if that matters

By: Matt B.

Matt B. — Tue, 17 Aug 2010 14:03:43 +0000

Thanks for posting Dave. I’m not able to test 2010 on a non-beta copy and we’ll probably not upgrade for a while. If anyone else wants to chime in, feel free. For @IceM and @Jay, I’d make sure you aren’t using the beta version of Outlook. I know I am and I’m getting the same error messages. It seems to fire the error during mouseover events.

By: Dave Pyett

Dave Pyett — Tue, 17 Aug 2010 09:35:19 +0000

I am running Outlook 2010 on Windows 7 and linking to WSS3.0. No issues here (I’ve been using this method for some time – didn’t realise that it wasnt common knowledge).

By: Matt Bramer

Matt Bramer — Tue, 17 Aug 2010 04:30:04 +0000

I didn’t really test this with 2010 since I’m still running the beta edition, however I am affected by the same symptoms. I did some digging and it appears that Outlook 2010 pulls the web capabilities out and that would be to blame for the script errors.

Here’s a good reference to the changes between the versions: http://technet.microsoft.com/en-us/library/cc179110.aspx. With that, I really wouldn’t recommend using Outlook 2010 and this solution. It’s hard to create a one size fits all, but I’m sure there are a lot of people that can still use this functionality and not run into problems. I’ll definitely have to keep this on the radar when we move to the newer version though.

Thanks for the feedback!