Menu

#31 'the notebook either does not exist of isn't accessible!'

New
nobody
None
Medium
Defect
2014-07-08
2014-07-02
Anonymous
No

Originally created by: m.wat...@sheffield.ac.uk
Originally owned by: tortoisesvn

This issue is with onenote2evenote not evimsync, but can't find issue tracker for o2e.

What steps will reproduce the problem?
1.In onenote2evernote, click 'Start Import'
2. After a moment get message 'the notebook either does not exist of isn't accessible!'  

What is the expected output? What do you see instead?
Hoped to find notes quickly transferred to onenote, but see the error message instead

What version of the product are you using? On what operating system?
1.0.9 on Windows 8.1

Please provide any additional information below.
I've managed to transfer a brand new note in its own brand new notebook, but existing notes seem to refuse to transfer. I've tried moving just one note into a new notebook and checking carefully to remove all special characters in title, checking tags, in the body text, etc, but still no luck

Discussion

  • Anonymous

    Anonymous - 2014-07-02

    Originally posted by: tortoisesvn

    Can you please export one such note that does not work and attach it here?

     
  • Anonymous

    Anonymous - 2014-07-02

    Originally posted by: m.wat...@sheffield.ac.uk

    Thanks
    I've attached one to an email to you
    Cheers

     
  • Anonymous

    Anonymous - 2014-07-06

    Originally posted by: tortoisesvn

    (No comment was entered for this change.)

    Owner: tortoisesvn
    Status: Started

     
  • Anonymous

    Anonymous - 2014-07-06

    Originally posted by: tortoisesvn

    This issue was closed by revision [r159].

    Status: Fixed

     
  • Anonymous

    Anonymous - 2014-07-08

    Originally posted by: m.wat...@sheffield.ac.uk

    Hi
    I downloaded the latest release of en2on: on trying the import I didn't get the same error messages, but got the error window captured in this attachment
    Cheers

     
  • Anonymous

    Anonymous - 2014-07-08

    Originally posted by: tortoisesvn

    There's still a message in there that isn't proper xml and e2o fails to encode this special case.
    The note seems to be pretty 'late' in the whole notebook, as you can see it's on line 50652 in the notebooks enex file (if you export the whole notebook to an enex file, open that file in a text editor, go to line 50652 and from there find the closest <note> tag to find out which note it is).
    Maybe if you can export that note and attach it here.

    Status: New

     

Log in to post a comment.

MongoDB Logo MongoDB