Share via

Visio internal error 3405

Anonymous
2017-04-14T20:39:04+00:00

Our application uses a docked window to allow the user to drop objects onto a Visio drawing page using OLEDragDrop. The application was functioning correctly in Visio 2003/2007/2010/2013, but not in 2016. Here is the error dialog:

Visio internal error: #3405

Action 1246: Drop On Page

First try closing and reopening the file. Next try restarting Visio.

I have not found any helpful information in regards to this error in the forums. Does anyone have any insight as to what may have changed in Office 2016 in regards to OLE drag and drop? Anyone else experiencing issues with OLE drag and drop implemented in Office COM Add-ins that worked before Office 2016?

My platform is Windows 10 Professional v1703, as a clean install, with all the latest windows updates.

Regards,

Todd Mueller

More information:

We have found that this issue is only present on Windows 10 with Visio 2016. The issue does not occur with Windows 8.1 or 7 with Visio 2016, or with Visio 2007, 2010, or 2013 on Windows 7 or 8.1.  Even works on Windows 10 and Visio 2010 when both Visio 2010 and Visio 2016 are on the same system.

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2017-04-25T14:10:51+00:00

    Hi Yuki,

    I was waiting on a customer that had this issue on Windows 7 and Visio 2016. He was able to update his system with the latest Windows Updates (1.5 GB), and still had the issue.  He then did an Office update, and the problem was resolved.

    The only platform that always has the issue is Windows 10 with Visio 2016.  Issue exists even after fully upgrading both the OS and Office.  Also, Windows 10 systems that have Visio 2007, Visio 2010, and Visio 2016 on the same system have the issue only with Visio 2016.

    Thank you for your quick reply.

    Regards,

    Todd Mueller

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-04-17T09:29:38+00:00

    Hi Todd,

    Based on my research, the message corresponding to "Visio internal error: #3405" was "DVOBJ Error" in previous versions of Visio (e.g. Visio 2000). But I am not quite sure if it is still applicable to Visio 2016 and after much research, I didn't find any documentation stating this :(

    In your situation, does this issue affect all machines with Visio 2016?

    Best regards,

    Yuki Sun

    Was this answer helpful?

    0 comments