Link to home
Start Free TrialLog in
Avatar of slemmesmi
slemmesmi

asked on

Problem: Word 2016 cannot import a .vsdx created with Visio 2013

I have many times embedded .vsdx Visio drawing into a (existing or new) Word document through "Insert" > "Object" > "Create from File" and have never encountered any problem.
Then recently on two PC's I encounter:
 User generated imageThe program used to create this object is Visio.
That program is either not installed on your computer or it is not responding.
To edit this object, install Visio or ensure that any dialog boxes in Visio are closed.


Same drawing saved as .vsd (instead of .vsdx) in Visio 2013 can be embedded without any problem, so that is what I do as "work-around".

Scenario is two different Windows 7, both with Word 2016 (click-to-run installed) from Office 365 and Visio 2013 (.msi installed).
Same Visio 2013 (15.0.4569.1506) on both PCs.
Word 2016 included in Office update channel "Insider Fast", Version 1703 (Build 7920.1000), (new Microsoft Office 365 ProPlus - en-us Version 16.0.7920.1000 on one PC, and Word 2016 included in Office update channel "Current", Version 1701 (Build 7766.2060), Microsoft Office 365 ProPlus - en-us Version 16.0.7766.2060 on other PC.

I've tried repairing both Visio and Office, "quick" as well as "Online", and in both sequences, but problem persists.
I've tried removing and reinstalling both Visio and Office, but problem persists.
Unfortunately I cannot tell what has "changed since last time it worked", so a "fallback" is not possible.

Of course searching the Internet finds many possible solutions (also I tried such referring to Office/Visio 2007/2010), but none have worked for me, so please do not post any reference to such pages nor "try this".

I am looking for a resolution to this problem, secondarily to learn about the root cause.
ASKER CERTIFIED SOLUTION
Avatar of slemmesmi
slemmesmi

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of slemmesmi
slemmesmi

ASKER

Cancelling my question
Avatar of Scott Helmers
I'm curious why you've cancelled your question. Did you find a resolution or is your workaround of saving to vsd satisfactory?

I ask because I've corresponded with the Visio development team about this and it is not a known issue. They even tested with a similar environment (Windows 7, Word C2R 7920.1000, Visio 2013 MSI 4569.1506) but didn’t encounter the error. If you need further help I'd be happy to work with you to try to isolate what is causing the problem.
Dear Scott,

thank you for your comment.
I got feedback from https://answers.microsoft.com/en-us/msoffice/forum/msoffice_word-mso_other/problem-word-2016-cannot-import-a-vsdx-created/962a0267-8a42-4946-bf4a-9751d6ecf468?msgId=16be7dfe-abf2-40e4-aa3b-45effa20e62d which led me to further testing, and therein finding that the problem was with only one specific .vsdx file (I must assume was somehow "corrupted").
Hence the "resolution" was opening the "corrupt" .vsdx file into Visio (which didn't fail) and copying the content thereof into a new "blank" .vsdx file.

Kind regards,
Soren
Soren -- I'm glad you found the source of the problem. If the apparently corrupted file doesn't contain proprietary information, would you be willing to share it with the Visio dev team? They might like to take a look at it to see what they can learn. If yes, don't post it here but send the file, or a link to a file, to the email address in my profile. If no, not a problem but I thought I'd ask.

Scott
Dear Scott,

sorry the "corrupt" .vsdx does indeed contain confidential information I cannot disclose.

Kind regards,
Soren