Page 1 of 1

export invalid string position

Posted: Thu Dec 11, 2014 8:25 pm
by alf329
Just tried to export all my notes in cn 2.8.3 and got this error message:

The program has encountered an error during export
invalid string position

any ideas

Re: export invalid string position

Posted: Fri Dec 12, 2014 7:35 am
by CintaNotes Developer
What type of export is this?
Could you pinpoint the exact note that fails to be exported?

Re: export invalid string position

Posted: Fri Dec 12, 2014 9:12 am
by alf329
export the entire database, all fields, to xml

Re: export invalid string position

Posted: Fri Dec 12, 2014 9:51 am
by CintaNotes Developer
Could you please record the log of the export?

1) Run CintaNotes and activate "Help/Debug/Debug Logging"
2) Try to repeat the problem (run export)
3) This will produce the file named "log.N.txt" (either in CN folder,
or in %APPDATA%\CintaNotes) - please send it to

Please note that this file may contain some of your private data, such as tag
names (but no passwords). You may want to edit the file and remove this data

Hope this is not too much to ask, thank you!

Re: export invalid string position

Posted: Sat Dec 13, 2014 2:06 pm
by alf329

I'll make a note of turning on debug etc as soon as it happens if any more errors occur, as I've moved on.

cn did produce a little mini diag though and this is the contents:

Timestamp Thread Forced Function Details
20:26:28.255553 5700 logging::Log::init Started logging
20:26:28.255553 5700 X ui::`anonymous-namespace'::runProgressFunction ERROR:invalid string position

There doesn't look to be too much to go on here, hence your point about turning on debug.

Are there any other debug options that could give a bit more info that I could leave on. The only debug option in help that I can see is obviously only to be used for short time periods as it can create 50MB of data in a few minutes.

Re: export invalid string position

Posted: Mon Dec 15, 2014 7:54 am
by CintaNotes Developer
Unfortunately you're right, these lines don't give us anything.
And alas CN has just one debug log which yes generates a lot of data and is not really intended to be left on for
significant periods of time.

Do I understand correctly that the problem is not repeatable any more - you can export to XML without any errors now?