You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The script seems to be reading the notebooks OK. It creates the correct directory structure in the target markdown directory.
However, it seems to fail in various ways relating to a missing RPC server.
Exception calling "GetPageContent" with "3" argument(s): "The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)"
and (much later):
Error while publishing file 'Ikigai: The Japanese Secret to a Long and Happy Life Might Just Help You Live a More Fulfilling…' to docx: Exception calling "Publish" with "4" argument(s): "The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)"
There are other errors, but this might be the root cause that cascades down to them.
The text was updated successfully, but these errors were encountered:
I just discovered this tool and I had the same issue. If I launch this PowerShell script while OneNote is stopped, the filetree is created, but I see the same messages and no MarkDown file is generated. However, if Onenote is started before I launch the script, all is working like a charm. I'm using OneNote from Office 365 under Windows 11 24H2.
I don't know if this behavior is expected. In this case, the README must be updated.
The script seems to be reading the notebooks OK. It creates the correct directory structure in the target markdown directory.
However, it seems to fail in various ways relating to a missing RPC server.
Exception calling "GetPageContent" with "3" argument(s): "The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)"
and (much later):
Error while publishing file 'Ikigai: The Japanese Secret to a Long and Happy Life Might Just Help You Live a More Fulfilling…' to docx: Exception calling "Publish" with "4" argument(s): "The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)"
There are other errors, but this might be the root cause that cascades down to them.
The text was updated successfully, but these errors were encountered: