Jump to content
gazumped

Office 2013 Outlook Clipper Issue - Failed to import note

Recommended Posts

Not sure if this is related to the latest update or not.  Anyone else using Outlook 2013 (as a part of the installed Office apps) and Windows 10 and finding the outlook clipper is broken?

I tend to forward emails these days,  so haven't tried the Clipper for a while,  but recently it failed on one email,  and then the next... and I haven't been able to successfully clip an email since.  The full error in the clipper window is

ScreenClip.png.77ce6c59909c603cf630df35bac7598f.png

I raised a ticket #2753464 and will report outcomes.

Interestingly I had extra problems reporting this - in Firefox 64.0.2 (64bit) I filled in the ticket form at https://help.evernote.com/hc/en-us/requests/new and the 'send' button would not work.  Reloaded the page,  checked I was logged in and filled in the form. Again.  Still no send button action.  So I used Vivaldi - no problems.

And.  Being conscientious I created a note to record all this and keep my clips.  Drag and drop into the note didn't work for this image.  I had to 'attach' this pic (a 4kb PNG) to the note.

My other stats are Windows 10 (1709) and Evernote Desktop 6.17.4.8270

I'll flag this in the release thread for 6.17.4 too,  in case anything is related...

  • Like 1

Share this post


Link to post

Ah *****. We fixed the issue from the last Beta with this in the main EN application. But missed it in the other supporting executables. I'm on it...

  • Haha 1

Share this post


Link to post

Hi,

I have been having this issue all weekend long with my personal computer. Now that I am at work I just updated to the newest version of Evernote and it just crashed my Outlook 2013 clipper. Please get this fixed as soon as possible. I use this option all day long and it is fundamental to my productivity.

Thanks for the help. 

Share this post


Link to post

It was released last night. ("Help -> Check for Updates" to get it now, I don't believe we've released it to 100% yet - but a manual check will always find it)

  • Like 1

Share this post


Link to post

Just to confirm - now using 6.17.5 for windows,  and things are back to normal.  Thanks again for the fix!

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...