Send Spreadsheet/Document from Word/Excel 2013, no message body

Two workstations both have Office 2013 and both have this 100% repeatable problem. When in Word or Excel and selecting File > Share > Email > Send as Attachment; after composing the message and sending, the recipient does get the attachment, but none of the composed body text.

How do I fix this?
LVL 1
MarkAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David SankovskySenior SysAdminCommented:
Is it any recipient or only inside the organization?
Some email clients are known to transmit / read HTML mails incorrectly - check if the email client (presumably MS Outlook 2013) Is set to compose messages as HTML ones or simple text and see if that solves it.
MarkAuthor Commented:
it is any recipient. I tried sending mail to my external email address with a plain test mail reader. Definitely no body. The local (sending) email program is Outlook 2013. I'll test the HTML thing and post back, though from the message headers (below) it looks like text/plain.

From ryoung@ohprs.org  Thu Sep 17 00:38:54 2015
From: "user" <user@ohprs.org>
To: "'Mark Foley'" <mfoley@novatec-inc.com>
Subject: Quick Reference.docx
Date: Thu, 17 Sep 2015 00:38:20 -0400
Content-Type: multipart/mixed;
        boundary="----=_NextPart_000_0015_01D0F0E1.27D39570"
X-Mailer: Microsoft Outlook 15.0
Content-Language: en-us
Thread-Index: AdDxAXsbyDBm7YcXSCqQp6eMaquxvQ==
x-vipre-scanned: 22827E2900AB2C22827F76
X-Spam-Status: No, score=-101.9 required=5.0 tests=BAYES_00,TVD_SPACE_RATIO,
        T_RP_MATCHES_RCVD,USER_IN_WHITELIST autolearn=ham
        version=3.3.2-_revision__1.4__
X-Spam-Report:
        * -100 USER_IN_WHITELIST From: address is in the user's white-list
        * -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
        *      domain
        * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
        *      [score: 0.0000]
        *  0.0 TVD_SPACE_RATIO TVD_SPACE_RATIO
X-Spam-Checker-Version: SpamAssassin 3.3.2-_revision__1.4__ (2011-06-06) on
        server.novatec-inc.com

Part 1:
Content-Type: text/plain;
        charset="us-ascii"



Part 2:
Content-Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document;
        name="Quick Reference.docx"
Content-Disposition: attachment;
        filename="Quick Reference.docx"

Open in new window

David SankovskySenior SysAdminCommented:
Was this sent in exactly the same way as the others, as in, the file was selected and then used "Share as attachment" Or did you open a new mail and attach the file from there?

You said it only happened on two workstations - Does it happen for all users?
if an affected user used a different workstation, did it work properly for him?
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

MarkAuthor Commented:
Yes, this is the actual message I tested with via "Share as attachment"

It happens on only 2 workstations because the others are still on Office 2010. It is not a problem with 2010.
regmigrantCommented:
There was a similar problem for some of my clients last year but only from Excel and when HTML was the default format, choosing RTF as the default would work.

MS response was to ask us to check that the outlook profile was not pointing to .pst but the email account as the default recipient which seemed to resolve it but I was never convinced they actually knew the root cause.

There is anecdotal evidence that Windows 8.1 caused the issue but MS are not admitting to that.

A bit of googling did highlight that a patch was release in May 15 so its worth checking all updates are applied from this version:
Current 2013 version is 15.0.4711.1002
MarkAuthor Commented:
I will experiment with the HTML/RTF things after business hours.
MS response was to ask us to check that the outlook profile was not pointing to .pst but the email account as the default recipient which seemed to resolve it but I was never convinced they actually knew the root cause.
Not sure what you mean by "check that the outlook profile [is] not pointing to .pst but the email account as the default recipient". I believe the Outlook profile *is* stored in a .pst, no? Please rephrase your comment. This might be very important.
There is anecdotal evidence that Windows 8.1 caused the issue but MS are not admitting to that.
Well, we're still on WIN7, so that's probably not it for us.

I'll also check the updates, but these are automatic so I would be surprised if that patch had not been applied.

BTW - You mention MS response. How did you get that in the first place? Did you pay an incident fee? Service contract? MS web forum? Would love to have actual MS feedback on this and other Office issues.
MarkAuthor Commented:
Tried setting the 'Compose' option to RTF instead of HTML. No difference.

All MS Updates are "Up to Date".

Office version is 15.0.4711.1002.
regmigrantCommented:
MS response was via the SharePoint consultancy we had working with us at the time they are a gold partner.

Go to backstage, account settings,
email tab should point to: user@domain.com\inbox as the place for 'deliver new messages'
Data files tab - there should be an equivalent .ost file
MarkAuthor Commented:
Got this fixed. Nothing I tried worked, including doing a "Repair". But, doing a "web-repair" did fix it.
regmigrantCommented:
bizarre but good news :)
MarkAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for jmarkfoley's comment #a40987175
Assisted answer: 250 points for Davsank's comment #a40981709
Assisted answer: 250 points for regmigrant's comment #a40983093

for the following reason:

I solved the problem, but thanks to Dave Sankovsky and remigrant for paricipating in the question.
MarkAuthor Commented:
I'm requesting this question NOT be closed. The problem is not solved.
MarkAuthor Commented:
First, some backstory ... When we purchased Office 2013, download version, I was required to "register" with a "Windows Live" email account. As we did not have an office Live email account, I used my personal one, not having any idea of the downstream implications. That was about 9-10 months ago.

Sometime since then, the users must have switched accounts in order to get my bright-shiny face off their Excel/Word pages. They accomplished this by clicking on the account drop-down (see red arrow in attached image) and selecting their own local domain account instead of my external Windows Live account. Probably, this is what caused them to lose the "message body" when emailing from Word/Excel in the first place.

When I recently did the web-repair, I had to re-register Office 2013 with (my) Windows Live account, which fixed the problem, but put my visage and hotmail account back on their Excel/Word.

Naturally, they changed this back to their own account -- which un-fixed the "empty message body" problem. I tried simply changing back to my account, but the problem still persists: no message body on attachments mailed from within Word/Excel. Likely, I'd have to re-do the web-repair to fix that.

So, this is all bizarre! I don't even know where to begin to fix all this. I suppose I could uninstall Office completely, then reinstall using a different Windows Live account (why do we need this anyway?), but would I have to have a Windows Live account for each person installing Office? They could never, it seems, change to their own local account. And what if some other domain user logs onto that workstation? They certainly won't have their own account and would likely mess up the main workstations user if they changed it.

Need some help!!
OfficeAccount.jpg
MarkAuthor Commented:
I've also posted the following to a related question: http://www.experts-exchange.com/questions/28715146/More-Office-2013-woes-message-sent-within-Word-going-to-wrong-Sent-folder.html

In the end, our solution was to "downgrade" to Office 2010. That has support for another 5 years during which time we can look for alternative solutions. Plus, we've had zero problems with 2010.

The problem discussed throughout this question started with the requirement to register the Office software using a Windows Live ID account. In my case I used a personal hotmail.com account, not knowing what I was in for. However, even if I registered each staff member with their own individual account (can you say "time consuming"?) that still creates problems. For example, the CFO's workstation is on its 3rd CFO. The director's workstation on its 2nd director. No big deal, it's a AD Domain, right? The new user just sits down and logs into the workstation. Done. Not so if Office 2013 is in the mix. We would not be able remove the previous user's Windows Live account so the new user (and the company) would have to keep access to the ex-employee's Live account as you cannot transfer Office 2013 registration between Live accounts.

Even if we did that there are still problems. In the AD domain, if a user logs onto a different workstation and opens Office/Outlook there, the "account" defaults, not to the registered "Live" account, but to that user's domain account, e.g. username@hprs.local. If/when the user manually changes this back to the registered "Live" account, all the problem discussed in this message recur: bodyless emails from Word/Excel, read-only documents in My Documents, ... The only way to fix this is to re-web-install Office from the Internet, and NEVER switch accounts, EVER!

Apparently Office 2013 works fine on standalone workstations with one possible Live ID user and/or in the Cloud. As a public pension fund, we're never going to the Cloud (I wonder what banks and investment companies are doing?)  Office 2013 does not function well in a non-Outlook.com Active Directory environment.

With the dropping of the Small Business Server product, removal of Exchange from Server Essentials and the apparent direction Office is heading, is seems clear that Microsoft no longer considers small businesses and offices as part of its target market, unless those entities are willing to go to the Cloud. Given the built-in data mining features of Windows 10, I'm skeptical about how "secure" my information is in Microsoft's cloud -- not to mention the nearly weekly break-in of high-profile private and government data stores. The Cloud and Office 2013 are not for us, and perhaps neither is Microsoft.

We will be looking at alternatives to Office, and possibly alternatives to Windows in the next several years.

I'll leave this open a bit longer for any commentary participants might have.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MarkAuthor Commented:
My solution was to remove Office 2013. Thanks to david and regmigrant for participating
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Office

From novice to tech pro — start learning today.