Outlook without religion is lame : Outlook

I am a PC

Scott Fellman — Sat, 20 Sep 2008 19:15:00 GMT

Our recent marketing campaign with Bill Gates and Jerry Seinfeld was a hoot! It was meant for a short run, and unfortunately, it is now over.

But we have a new campaign and I appreciate that Microsoft have taken the high road with it. After watching all of the silly Mac vs PC commercials from Apple for the past three years, what better way to respond than with real users, with real stories of how they are PCs, and how their PCs help them in various aspects of their lives.

Being a proud member of Microsoft Support Services, I am even happier about the new campaign because I support our friends and users for a living. No on calls me and says "Scott, SharePoint and Outlook are working great together; our SQL has months of uptime and our Active Directory and Exchange environments are functioning superbly". I get the calls when folks have problems, sometimes huge problems, and I am glad to work for a company like Microsoft that truly values our customers. And my first order of business every day is to be helpful to others, so my job fits me perfectly. My dad always said "if you do what you love, you will never work a day in your life".

So as always, I want to thank all of you who use our products and support. You are my fellow PCs, and here is my evolution as a PC:

In high school, I was a BASIC on cassette tape PC.
In college, I was a FORTRAN on punch card PC, until a quarters game went horribly wrong.
I was an 8086 with an 8087 co-processor PC.
I was an 80286 PC when I got my first hard drive.
I was and 80386 and 486/100 PC so I could play Doom.
I built/was a dual proc 400 mhz PC running Windows NT 4 from the ground up - I did this so that I could have an affordable, maintainable server supporting a graphics group of Mac artists that could RIP huge image files in a hurry.
I was a Toshiba Tablet PC.
Currently, I am a Dell Inspiron laptop PC running Vista, great up-time and perf thanks so much!
I am also a Dell PowerEdge server running Windows 2003.
I am also an HP Server running Windows 2008 and lots of virtual, Hyper-V based baby PCs running everything from my own AD forest with multiple Exchange, SQL and SharePoint versions and clients for those servers in perfect harmony.
And to stay connected, I am a Windows Mobile 5 Motorola Q as well, upgrading this weekend to WM 6.1 on a new device (still undecided, but I have choices)!
And I am also upgrading from my PowerEdge to a 64 bit Vista Dell 740 with 512 MB dual DVI video card supporting two 22 inch Acer Monitors. One card, two monitors, 16.7 million colors and no waiting. Drool.
I am an Xbox
I am an Xbox 360 Elite.
I am a Zune.

I am not hidden in a pizza box to trick college kids
I am not a king with loyal subjects
I do not need calming teas, though some may argue less caffeine may be a fair option
I don't need a genius to transfer my files; I can do that myself. Perhaps I should take the MENSA test?
I don't have Vista blues, nor a tick hound that howls when I play my bass.
I am not secure because of obscurity, by rather because the ubiquitous enterprise usages of my kindred spirit PCs demand it.

I am not a PC because I have to be. I am not a PC to be different. If a better solution comes along, I will be that platform.

But for now, like the billion around me, I am and will remain a PC.

Quote for the Blog: Until we're educating every kid in a fantastic way, until every inner city is cleaned up, there is no shortage of things to do.

Bill Gates

Large Pictures clipped in Outlook 2007 - Maximum size for images?

Scott Fellman — Thu, 18 Sep 2008 04:46:00 GMT

Hi everyone, quick vacation blog concerning images (JPG, BMP, etc...) rendering improperly, and specifically clipping of said images, in Outlook 2007. When viewed with the legacy clients, the images render properly. When viewing the images with Outlook Web Access, the images also render perfectly.

As you probably know, the reason for the difference in behavior with Outlook 2007 is that the legacy clients used a limited subset of IE's functionality as the rendering engine for emails and images within those mails. As you also likely know, we have changed the rendering engine to Word 2007 with Office 2007 (“by design” as you may have heard a time or two on other questions). This decision was made for a number of reasons from what I can gather:

Plethora of browser versions and developers
Different HTML standard adherence among those browsers
Different HTML Composition Tools (Notepad rules!)
Probably others I have neither heard of nor imagined...

By choosing Word as the rendering engine, the Outlook team has made the decision to bypass all the browser and HTML tools issues that they cannot possibly track or control. In so doing, now HTML developers will need to be able to convert from their tool of choice to Word to insure optimal rendering. This is not a problem, and in fact is documented well here: http://msdn.microsoft.com/en-us/library/aa338201.aspx.

The HTML validation tool for Word 2007 is downloadable here: http://www.microsoft.com/downloads/details.aspx?FamilyId=0B764C08-0F86-431E-8BD5-EF0E9CE26A3A&displaylang=en.

But the point of this blog isn't to rehash the developer work that has already been done on conversion to Word so that it renders well in Outlook 2007; rather, the point is simply to document a technical point that I can't seem to find publicly documented anywhere.

What is the maximum size for images that will render without clipping in Outlook 2007? The answer to the question is 18 inches in height. And that size is the size as shown in Word 2007, not as shown in any other program. I haven’t tested width maximums yet, but feel free to share if you have J.

Quote for this blog:

Every man is said to have his peculiar ambition. Whether it be true or not, I can say for one that I have no other so great as that of being truly esteemed of my fellow men, by rendering myself worthy of their esteem.

Abraham Lincoln

Outlook Calendar issue troubleshooting steps published to TechNet

Scott Fellman — Sun, 31 Aug 2008 08:31:00 GMT

A great read on common Outlook calendaring issue troubleshooting and data gathering has been recently published:

http://technet.microsoft.com/en-us/library/cc891495.aspx

This is a huge article, suggesting many standard requirements from a data and informational perspective. As I reviewed the article, I saw a couple of points I would suggest changing or ammending:

"A missing or corrupted meeting often cannot be recovered. You might try to delete and re-create the meeting"

Deleting a meeting is a tough step for many users to take. Before deletion, you may want to try to:

- Back the meeting up, via either exporting the meeting using drag and drop to your desktop, or by using a low level editor like MFCMAPI (www.codeplex.com/MFCMAPI) or Outlook Spy (www.dimastr.com). Note that neither of these are Microsoft supported products (you can't get hot fixes from Microsoft for them), but the authors of each do take feature/fix requests.
- Put an end date on a corrupt meeting item instead of deletion. This way you can get to any attachments you have made to the meeting using the aforemention MAPI editors. Create a new meeting with the starting point where you ended the old meeting.

"Without all the data requested, the support engineer will not be able to definitively determine why there is a problem with the meeting item.

Even with all the data requested, we may not be able to find a root cause of what in the meeting is corrupt. Outlook doesn't have any kind of back-end database that keeps a record of changes or other referential mechanisim Once a property is stamped with a value, it is stamped. Period. While Outlook logging, Exchange logging, or third-party logging MAY catch the bad property being stamped, none of these solutions monitor EVERY property of every calendar item that gets stamped. Even on a simple meeting with a subject, body and no recurrences, attachments or other attendees, there are about 80 to 90 properties:

There are other requirements in the article for things like Exchange Store tracing, third-party tracing and Outlook tracing (Tools > Options > Other > Advanced > Check the box for Outlook logging and restart), and process monitor as well! Each of these data collection pieces use lots of resources, so you will need to do a couple of things as an administrator:

- Use the logging steps in a test enviornment before putting them on a prodcution machine. Perf by some of these tools can push a given box over the edge, so don't be that guy that doesn't test!!!
- Make sure that you have a feeling for how much disk space the logs are consuming per unit of time. If for example, you are engaging Outlook logging on a client machine with an 80 GB drive, and 20 gigs of that is free when you start testing, run the test for 10 minutes. Figure out how much disk you are filling per hour! Say you collected 1 gig of data in 10 minutes. You do the math and figure out that this is 6 GB per hour consumed by the logging. This means you can log safely for three hours before needing to pull the logs off the machine. You can perform the move manually, or script it, but you don't want to fill up that drive in hour four by not moving the data out!!!! If you let this happen, you have a bigger issue than you started with!!!

Finally, realize that the resolution of any given problem may not be the one that you initially sought. Resolution may take various forms: working around the issue by taking steps to avoid it, or reseolution may be to restore a backup, or it may be a code change request, or it may be a logging of the issue internally with Microsoft for future review. Calendaring issues are complex, and they often require many hours to research, dig, prod, poke and postulate just to get to the point of "I don't know what is causing this". Be patient on calendar issues, and be observant. Finally, remember you are working the problem with a serious group of Microsoft Engineers who will do everything possible to get you to an acceptable resolution!

Quote for this blog: Outlook Good! - Magic Eight Ball

Issue - Programmatically posting WSS 2007 Discussion List Items shows sender as "System Account" in Outlook 2007

Scott Fellman — Tue, 18 Dec 2007 06:35:00 GMT

I have been working through some hardware issues so Part two of my SPSreport blog continues to hold , but I wanted to take a few minutes to share some findings from a recent case with you.

In this case, our customer is a programmer who sent in some code wherein he was programmatically setting the Email Sender and From field in WSS Discussion list items using OM code like this:

SPListItem discussion = SPUtility.CreateNewDiscussion(list.Items, "subject");

discussion[SPBuiltInFieldId.Body] = "body";

discussion[SPBuiltInFieldId.Categories] = "category";

discussion[SPBuiltInFieldId.EmailSender] = "SenderEmail@email.com";

discussion[SPBuiltInFieldId.MessageId] = "Server Internet Message ID";

As most of you know, I describe myself as a "code toddler"; I can read some code, I can write "Hello World" in a couple of languages. So I didn't know if I would be able to help our customer… but I knew I needed to try to do so. And I can understand that the code above should be setting values on specific columns and fields for a Discussion Board item. So off we went!

The above code shows the proper person, as pushed from the OM into each of the appropriate custom columns in WSS's UI. But from the other side of this issue, after a sync to Outlook the From column is the Creator of the post as shown in the Outlook UI, i.e., the person that ran the code in SharePoint. In our case, this was the system account.

In my initial research, I found a couple of OOB reasons why we might see the System Account as the sender. First, of course, is if the Creator of the post is the system account (never discount the obvious!). Second, if you see content in the document library that is assigned to the system account, it sometimes means that the document library has treated the incoming mail as an anonymous user due to the inability to resolve the name in the list of users with rights to submit mail to the list. To check to see if this was the cause of our issue, we checked to see if the library was set to accept mail from all senders. You check this from WSS by browsing to the Discussion list, then choosing Settings > Discussion Board settings > Incoming Email Settings (and then navigate to the bottom of the page). Neither of these was the case when we checked them…

To reset: the code makes the "poster" looks good on the Discussion Board list item, but on the sync to Outlook, the From field is changed to the WSS System Account. Nothing left to do but break out the troubleshooting tools! For this issue, my weapons of choice were netmon, Outlook Spy and source code for SharePoint and Outlook (sorry, no links for these :)).

I set up an OOB Discussion list (modified the theme, thus the difference in color), added a column (blue), started netmon and performed an Action > Sync to Outlook from the list.

In reviewing the netmon of the trace, I see two properties in the

In reviewing the netmon of the trace, I see two properties in the XML going across the wire; these are ows_author and ows_editor:

0000 00 08 74 15 39 b5 00 07 b3 0f 59 ca 08 00 45 00 ..t.9.....Y...E.

0010 03 80 77 26 40 00 37 32 84 9e 9d 36 1a 25 41 35 ..w&@.72...6.%A5

0020 4b f7 f7 9c 09 4a 00 00 00 8a 00 50 11 b0 4d d7 K....J.....P..M.

0030 80 23 a2 25 e3 b8 50 18 ff e9 d2 4f 00 00 33 34 .#.%..P....O..34

0040 45 43 44 38 38 38 33 33 32 36 33 42 38 38 43 39 ECD88833263B88C9

0050 43 34 42 26 67 74 3b 26 6c 74 3b 64 69 76 26 67 C4B><div&g

0060 74 3b 26 6c 74 3b 2f 64 69 76 26 67 74 3b 26 6c t;</div>&l

0070 74 3b 2f 64 69 76 26 67 74 3b 27 20 6f 77 73 5f t;/div>' ows_

0080 54 68 72 65 61 64 49 6e 64 65 78 3d 27 30 78 30 ThreadIndex='0x0

0090 31 43 39 45 46 30 35 34 31 43 41 46 34 45 37 35 1C9EF0541CAF4E75

00a0 30 38 33 32 32 45 31 34 37 45 43 42 30 44 38 44 08322E147ECB0D8D

00b0 41 36 34 45 34 43 35 36 39 34 43 27 20 6f 77 73 A64E4C5694C' ows

00c0 5f 41 75 74 68 6f 72 3d 27 31 3b 23 53 63 6f 74 _Author='1;#Scot

00d0 74 20 46 65 6c 6c 6d 61 6e 20 28 53 45 4b 49 57 t Fellman (SEKIW

00e0 41 4b 45 29 2c 23 4e 4f 52 54 48 41 4d 45 52 49 AKE),#NORTHAMERI

00f0 43 41 5c 73 66 65 6c 6c 6d 61 6e 2c 23 73 66 65 CA\sfellman,#sfe

0100 6c 6c 6d 61 6e 40 6d 69 63 72 6f 73 6f 66 74 2e llman@microsoft.

0110 63 6f 6d 2c 23 73 66 65 6c 6c 6d 61 6e 40 6d 69 com,#sfellman@mi

0120 63 72 6f 73 6f 66 74 2e 63 6f 6d 2c 23 53 63 6f crosoft.com,#Sco

0130 74 74 20 46 65 6c 6c 6d 61 6e 20 28 53 45 4b 49 tt Fellman (SEKI

0140 57 41 4b 45 29 27 20 6f 77 73 5f 45 64 69 74 6f WAKE)' ows_Edito

0150 72 3d 27 31 3b 23 53 63 6f 74 74 20 46 65 6c 6c r='1;#Scott Fell

0160 6d 61 6e 20 28 53 45 4b 49 57 41 4b 45 29 2c 23 man (SEKIWAKE),#

0170 4e 4f 52 54 48 41 4d 45 52 49 43 41 5c 73 66 65 NORTHAMERICA\sfe

0180 6c 6c 6d 61 6e 2c 23 73 66 65 6c 6c 6d 61 6e 40 llman,#sfellman@

0190 6d 69 63 72 6f 73 6f 66 74 2e 63 6f 6d 2c 23 73 microsoft.com,#s

01a0 66 65 6c 6c 6d 61 6e 40 6d 69 63 72 6f 73 6f 66 fellman@microsof

01b0 74 2e 63 6f 6d 2c 23 53 63 6f 74 74 20 46 65 6c t.com,#Scott Fel

01c0 6c 6d 61 6e 20 28 53 45 4b 49 57 41 4b 45 29 27 lman (SEKIWAKE)'

01d0 20 6f 77 73 5f 50 65 72 6d 4d 61 73 6b 3d 27 30 ows_PermMask='0

01e0 78 37 66 66 66 66 66 66 66 66 66 66 66 66 66 66 x7ffffffffffffff

01f0 66 27 20 6f 77 73 5f 5f 4d 6f 64 65 72 61 74 69 f' ows__Moderati

0200 6f 6e 53 74 61 74 75 73 3d 27 30 27 20 6f 77 73 onStatus='0' ows

0210 5f 5f 4c 65 76 65 6c 3d 27 31 27 20 6f 77 73 5f __Level='1' ows_

0220 55 6e 69 71 75 65 49 64 3d 27 33 3b 23 7b 37 45 UniqueId='3;#{7E

0230 41 34 43 38 41 44 2d 42 33 33 31 2d 34 36 44 46 A4C8AD-B331-46DF

0240 2d 41 33 37 38 2d 42 37 35 36 46 31 34 41 38 35 -A378-B756F14A85

0250 38 38 7d 27 20 6f 77 73 5f 46 53 4f 62 6a 54 79 88}' ows_FSObjTy

0260 70 65 3d 27 33 3b 23 31 27 20 6f 77 73 5f 46 69 pe='3;#1' ows_Fi

0270 6c 65 52 65 66 3d 27 33 3b 23 73 69 74 65 73 2f leRef='3;#sites/

0280 73 66 65 6c 6c 6d 61 6e 2f 4c 69 73 74 73 2f 44 sfellman/Lists/D

0290 61 6c 6c 61 73 20 43 6f 77 62 6f 79 73 20 44 69 allas Cowboys Di

02a0 73 63 75 73 73 69 6f 6e 2f 52 6f 6d 6f 20 72 6f scussion/Romo ro

02b0 63 6b 73 21 27 20 6f 77 73 5f 4d 65 74 61 49 6e cks!' ows_MetaIn

02c0 66 6f 5f 76 74 69 5f 76 65 72 73 69 6f 6e 68 69 fo_vti_versionhi

02d0 73 74 6f 72 79 3d 27 62 66 65 32 66 37 36 34 66 story='bfe2f764f

02e0 63 37 65 34 36 31 36 61 61 34 66 31 35 38 36 33 c7e4616aa4f15863

02f0 37 31 35 38 61 34 63 3a 31 27 20 2f 3e 0d 0a 3c 7158a4c:1' />..<

0300 2f 72 73 3a 64 61 74 61 3e 0d 0a 3c 2f 6c 69 73 /rs:data>..</lis

0310 74 69 74 65 6d 73 3e 3c 2f 47 65 74 4c 69 73 74 titems></GetList

0320 49 74 65 6d 43 68 61 6e 67 65 73 53 69 6e 63 65 ItemChangesSince

0330 54 6f 6b 65 6e 52 65 73 75 6c 74 3e 3c 2f 47 65 TokenResult></Ge

0340 74 4c 69 73 74 49 74 65 6d 43 68 61 6e 67 65 73 tListItemChanges

0350 53 69 6e 63 65 54 6f 6b 65 6e 52 65 73 70 6f 6e SinceTokenRespon

0360 73 65 3e 3c 2f 73 6f 61 70 3a 42 6f 64 79 3e 3c se></soap:Body><

0370 2f 73 6f 61 70 3a 45 6e 76 65 6c 6f 70 65 3e 01 /soap:Envelope>.

0380 01 06 78 2a 58 47 c6 34 92 6d f3 44 90 69 ..x*XG.4.m.D.i

When I look at the same message as rendered in Outlook, and specifically the MAPI properties, with Outlooks Spy, I see this:

In all, I see 4 MAPI properties with my name on them. I then went to a source search on each term. Ows_editor yielded one hit in Outlook source; he is responsible for conversion of the incoming ows_editor parameter. The conversion goes to the MAPI properties of PR_LAST_MODIFIER_NAME and PR_SENT_REPRESENTING_NAME; this is hard-coded. Searching source for ows_author yields that "Created By" in WSS maps to PR_ORIGINAL_AUTHOR_NAME_W. This is exactly confirmed by the Outlook Spy results above. So these are hard coded and cannot be modified simply by stamping a WSS property on them programmatically.

I then went through that same set of steps after adding a column called blue. When I viewed the trace, there was no ows_ property associated with the column that would be translatable by Outlook. So again, another thought, and another dead end.

Then my customer asked a question - "How do I add users to SharePoint that aren't in my domain". Having worked with contact lists in SharePoint, I knew that this is very simple; you just need to add a contact name and email address; there is no requirement from SharePoint that your contact be from your domain! And yes, from other work with our STSADM command line Administrative tool, I also knew that SharePoint will also recognize a local account of the SharePoint box as a valid user as well. This last piece of information is just what my customer needed.

With this piece of information, he wrote the code in WindowsAccount.cs, tied that in with WSSAccount.cs, and boom! A solution is now in place that is allowing him to use SharePoint and Outlook interoperability to programmatically list SharePoint posts and have them sync to Outlook as he wishes. This is a fantastic example of a code toddler like myself using wide product knowledge in the Microsoft Office Family and troubleshooting tools to help an experienced programmer build a custom business solution. Everyone wins when this kind of synergy happens!

Sample code attached with customer's permission! He reviewed ths blog before publishing as well; his desire here is that someone else might benefit from our work. All typical disclaimers apply, the code is not supported by Microsoft, nor myself - use at your own risk/benefit, etc...

Have a safe and happy holiday!

Scott

ISSUE - Deleted SharePoint document library re-appears in Outlook 2007

Scott Fellman — Mon, 25 Jun 2007 19:37:00 GMT

Issue: After syncing a document library to Outlook, our user tried to deleted it. A short time later, it reappeared! In the example below,the folder of note is the “My Site – Private Documents” folder at the bottom of the Outlook folder list:

Technical Details: Upon reviewing the addition of the document library as an Outlook folder with various troubleshooting tools including filemon, regmon and netmon, we were able to discern very little in the way of odd looking data. After talking with the user, we found that he was a user of Outlook on several machines, and that he he used OWA and a Windows Mobile device to sync up as well.

Upon further investigation, we did find that there is a setting in Outlook’s UI which allows a list to be displayed on other machines. This setting is found in Outlook under Tools > Account Settings > SharePoint Lists:

When you access the tab (above) and double click the list, you will see the check box that says “Don’t display this list on other computers I use”. By default, this setting is disabled (unchecked) in Outlook. Therefore, if you access Outlook with multiple machines and choose to sync your SharePoints lists with Outlook 2007, you are almost guaranteed to hit this issue!!!

Resolution: We have provided workaround steps that our customer has accepted:

Launch Outlook

Tools > Account Settings > SharePoint Lists tab

Double click the SharePoint list that you want to delete from Outlook

Check the box that says "Don't display this list on other computers I use" and select OK

This takes you back to the SharePoint Lists tab - click the list you wish to remove to highlight the list

Click the Remove Button above the list

Click Close

Close Outlook

Repeat the above steps on each machine where you use Outlook.

We requested a change to the Outlook Product team from the SharePoint support team within Microsoft so that the default behavior for "Don't display this list on other computers I use" is checked instead of unchecked. Unfortunately, we were told that making this change would break other Outlook mobility functionality so that our request had to be denied. Perhaps we have a customer out there who would be able to make a better business case for such a change...

Hope this helps!

ISSUE - Outlook/SharePoint Interop - Documents won't sync to Outlook

Scott Fellman — Sat, 23 Jun 2007 23:48:00 GMT

Issue: One of our customers was seeing an issue wherein site users migrated from v2 to v3 were unable to sync the contents of document folders hosted on the my site to their Outlook 2007 folder list. Interestingly, the folders containing the documents would sync as expected.

References:

- MOSS2007 My Site (personalization) - http://blogs.msdn.com/sharepoint/archive/2006/12/01/getting-started-with-personalization-in-moss-2007.aspx

- Content Types in SharePoint - http://msdn2.microsoft.com/en-us/library/ms452896.aspx and http://msdn2.microsoft.com/en-us/library/ms472236.aspx

- Outlook 2007 integration with V3 - http://download.microsoft.com/download/7/5/1/75168f8a-e2dc-479a-861c-afb3730c9ee6/OutlookSharePointIntegration_OV_E.ppt

- Netmon - http://blogs.technet.com/netmon/

Technical Details: We used netmon to determine that metadata about the documents was being transferred across the wire from MOSS to the Outlook client. In the packet below, note that the name of the document is test.docx (highlighted in green). Also note the Site Content type highlighted in yellow. I have snipped out the involved IP addresses.

No. Time Source Destination Protocol Info

5259 2007-05-15 12:50:13.329717 <snip> <snip> ESP ESP (SPI=0x83312de5)

Frame 5259 (1510 bytes on wire, 1510 bytes captured)

Arrival Time: May 15, 2007 12:50:13.329717000

[Time delta from previous packet: 8.550813000 seconds]

[Time since reference or first frame: 8.550813000 seconds]

Frame Number: 5259

Packet Length: 1510 bytes

Capture Length: 1510 bytes

[Frame is marked: False]

[Protocols in frame: eth:ip:esp]

Ethernet II, Src: Cisco_0f:59:ca (00:07:b3:0f:59:ca), Dst: DellComp_15:39:b5 (00:08:74:15:39:b5)

Destination: DellComp_15:39:b5 (00:08:74:15:39:b5)

Address: DellComp_15:39:b5 (00:08:74:15:39:b5)

.... ...0 .... .... .... .... = IG bit: Individual address (unicast)

.... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)

Source: Cisco_0f:59:ca (00:07:b3:0f:59:ca)

Address: Cisco_0f:59:ca (00:07:b3:0f:59:ca)

.... ...0 .... .... .... .... = IG bit: Individual address (unicast)

.... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)

Type: IP (0x0800)

<snip>

Version: 4

Header length: 20 bytes

Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)

0000 00.. = Differentiated Services Codepoint: Default (0x00)

.... ..0. = ECN-Capable Transport (ECT): 0

.... ...0 = ECN-CE: 0

Total Length: 1496

Identification: 0xc8aa (51370)

Flags: 0x04 (Don't Fragment)

0... = Reserved bit: Not set

.1.. = Don't fragment: Set

..0. = More fragments: Not set

Fragment offset: 0

Time to live: 55

Protocol: ESP (0x32)

Header checksum: 0x03cd [correct]

[Good: True]

[Bad : False]

Source: <snip>

Destination: <snip>

Encapsulating Security Payload

SPI: 0x83312de5

Sequence: 353

0000 00 08 74 15 39 b5 00 07 b3 0f 59 ca 08 00 45 00 ..t.9.....Y...E.

0010 05 d8 c8 aa 40 00 37 32 03 cd 9d 36 47 1a 41 35 ....@.72...6G.A5

0020 4b f7 83 31 2d e5 00 00 01 61 00 50 11 7e 9e 10 K..1-....a.P.~..

0030 78 29 a2 f8 69 f2 50 10 ff ff ef a4 00 00 54 79 x)..i.P.......Ty

0040 70 65 3e 31 3c 2f 43 61 6c 65 6e 64 61 72 54 79 pe>1</CalendarTy

0050 70 65 3e 3c 54 69 6d 65 32 34 3e 46 61 6c 73 65 pe><Time24>False

0060 3c 2f 54 69 6d 65 32 34 3e 3c 54 69 6d 65 5a 6f </Time24><TimeZo

0070 6e 65 3e 34 38 30 3c 2f 54 69 6d 65 5a 6f 6e 65 ne>480</TimeZone

0080 3e 3c 53 6f 72 74 4f 72 64 65 72 3e 32 30 37 30 ><SortOrder>2070

0090 3c 2f 53 6f 72 74 4f 72 64 65 72 3e 3c 50 72 65 </SortOrder><Pre

00a0 73 65 6e 63 65 3e 54 72 75 65 3c 2f 50 72 65 73 sence>True</Pres

00b0 65 6e 63 65 3e 3c 2f 52 65 67 69 6f 6e 61 6c 53 ence></RegionalS

00c0 65 74 74 69 6e 67 73 3e 3c 53 65 72 76 65 72 53 ettings><ServerS

00d0 65 74 74 69 6e 67 73 3e 3c 53 65 72 76 65 72 56 ettings><ServerV

00e0 65 72 73 69 6f 6e 3e 31 32 2e 30 2e 30 2e 34 35 ersion>12.0.0.45

00f0 31 38 3c 2f 53 65 72 76 65 72 56 65 72 73 69 6f 18</ServerVersio

0100 6e 3e 3c 52 65 63 79 63 6c 65 42 69 6e 45 6e 61 n><RecycleBinEna

0110 62 6c 65 64 3e 54 72 75 65 3c 2f 52 65 63 79 63 bled>True</Recyc

0120 6c 65 42 69 6e 45 6e 61 62 6c 65 64 3e 3c 53 65 leBinEnabled><Se

0130 72 76 65 72 52 65 6c 61 74 69 76 65 55 72 6c 3e rverRelativeUrl>

0140 2f 73 69 74 65 73 2f 76 2d 64 61 73 68 65 65 3c /sites/v-dashee<

0150 2f 53 65 72 76 65 72 52 65 6c 61 74 69 76 65 55 /ServerRelativeU

0160 72 6c 3e 3c 2f 53 65 72 76 65 72 53 65 74 74 69 rl></ServerSetti

0170 6e 67 73 3e 3c 2f 4c 69 73 74 3e 3c 2f 43 68 61 ngs></List></Cha

0180 6e 67 65 73 3e 0d 0a 3c 72 73 3a 64 61 74 61 20 nges>..<rs:data

0190 49 74 65 6d 43 6f 75 6e 74 3d 22 34 22 3e 0d 0a ItemCount="4">..

01a0 20 20 20 3c 7a 3a 72 6f 77 20 6f 77 73 5f 49 44 <z:row ows_ID

01b0 3d 27 31 27 20 6f 77 73 5f 6f 77 73 68 69 64 64 ='1' ows_owshidd

01c0 65 6e 76 65 72 73 69 6f 6e 3d 27 32 27 20 6f 77 enversion='2' ow

01d0 73 5f 43 72 65 61 74 65 64 3d 27 32 30 30 37 2d s_Created='2007-

01e0 30 31 2d 30 38 54 32 31 3a 32 39 3a 32 39 5a 27 01-08T21:29:29Z'

01f0 20 6f 77 73 5f 4d 6f 64 69 66 69 65 64 3d 27 32 ows_Modified='2

0200 30 30 37 2d 30 31 2d 30 38 54 32 31 3a 32 39 3a 007-01-08T21:29:

0210 34 33 5a 27 20 6f 77 73 5f 43 6f 6e 74 65 6e 74 43Z' ows_Content

0220 54 79 70 65 49 64 3d 27 30 78 30 30 44 36 36 35 TypeId='0x00D665

0230 36 32 44 42 44 31 42 35 33 30 34 44 39 35 33 42 62DBD1B5304D953B

0240 46 41 42 37 36 36 44 34 32 41 32 37 27 20 6f 77 FAB766D42A27' ow

0250 73 5f 46 69 6c 65 44 69 72 52 65 66 3d 27 31 3b s_FileDirRef='1;

0260 23 73 69 74 65 73 2f 76 2d 64 61 73 68 65 65 2f #sites/v-dashee/

0270 50 72 69 76 61 74 65 20 44 6f 63 75 6d 65 6e 74 Private Document

0280 73 27 20 6f 77 73 5f 45 6e 63 6f 64 65 64 41 62 s' ows_EncodedAb

0290 73 55 72 6c 3d 27 68 74 74 70 3a 2f 2f 6d 79 2f sUrl='http://my/

02a0 73 69 74 65 73 2f 76 2d 64 61 73 68 65 65 2f 50 sites/v-dashee/P

02b0 72 69 76 61 74 65 25 32 30 44 6f 63 75 6d 65 6e rivate%20Documen

02c0 74 73 2f 74 65 73 74 2e 64 6f 63 78 27 20 6f 77 ts/test.docx' ow

Root Cause: On a clean SharePoint install, the site content ID for a document starts with 0x0101. If it doesn’t, then Outlook will not respect the item to be synced as a document. As can be seen above, this content ID (0x00D65...) doesn’t indicate to Outlook that a document is being transferred (according to MSDN, this is not even a valid content id) in spite of the fact that the rest of the document’s metadata looks great!

Resolution: Upon further investigation, this assignment of a bad contnet ID was found to be an issue that only happened in Beta1 for V3. There are two workarounds:

Delete and recreate the user’s my site
The second set of workaround steps are to add a new, valid content type to the list, change everything to be that content type, delete ‘Document’, Re-add ‘Document, change everything back to document, then delete the temporary content type you added. Then, disconnect the list from Outlook and reconnect. HINT - Bulk edit of site content types is achievable in the UI:

Starting at my site, I created a custom site content type called sfellmandoc. I then created a custom datasheet view for my Shared Documents list that includes the site content type as a column as seen here:

Note that I changed the first item to the custom site content type sfellmandoc; this is mandatory to make the bulk edit. Then comes the UI magic:

Right click on the column header “Content Type” then choose Fill and Fill Down from the drop-down menu that appears.

The item that you changed in the first field will now be filled for all docs in the list:

Cool issue! Let me know what you think...