Hello.
I've learnt something here. No matter how simple or complex some code is, whenever one distributes code, one should include all relevant information in an external log file. I kind-of knew that and yet didn't stick to it causing some time loss (and some hair loss too). I'm sorry about that.
Let's not bang our heads against the error-pole anymore. You can effectively ignore my earlier post where I'm asking questions as if sitting in a dark room with no clue about what light is.
This time, I've used logging statements with abandon in this latest executable. When you run the utility now, it will produce a very detailed log file at the same location where the utility resides i.e. in the folder at your desktop. It will be named: OneNote2PDFDetailed.log
All we have to do is examine this log file to pin-point where the exception is occurring. Since there is going to be a lot of contextual data in the log, I'll be able to fix the problem in a jiffy.
Now, you have to do the following things:
1. Download the attachment.
2. Extract the utility and replace the old one with this new one.
2. Extract the configuration file and place it in the same folder as the utility.
3. Run the script.
4. Send the log file to my email address. Please don't upload it here on the forum. You can send an email to me by clicking on my name in the post and then clicking "Send Light an email" link.
5. Relax!
OneNote2PDF-WithLoggingAndConfig.zip (Size: 22.16 KB / Downloads: 132)
*Note: If there're any issues with sending the log file to me through the forum, please let me know. I'll communicate my email address to you or you can leave yours there.
When we're done with debugging, we'll turn off this detailed logging by flipping the switches in that file to value 0. But that will come later. Let's first fix it!
And once again, thanks for your patience and trust.
If you have any trouble following the instructions or have doubts / questions, please write right back.
Cheers,
Light.
I've learnt something here. No matter how simple or complex some code is, whenever one distributes code, one should include all relevant information in an external log file. I kind-of knew that and yet didn't stick to it causing some time loss (and some hair loss too). I'm sorry about that.
Let's not bang our heads against the error-pole anymore. You can effectively ignore my earlier post where I'm asking questions as if sitting in a dark room with no clue about what light is.
This time, I've used logging statements with abandon in this latest executable. When you run the utility now, it will produce a very detailed log file at the same location where the utility resides i.e. in the folder at your desktop. It will be named: OneNote2PDFDetailed.log
All we have to do is examine this log file to pin-point where the exception is occurring. Since there is going to be a lot of contextual data in the log, I'll be able to fix the problem in a jiffy.
Now, you have to do the following things:
1. Download the attachment.
2. Extract the utility and replace the old one with this new one.
2. Extract the configuration file and place it in the same folder as the utility.
3. Run the script.
4. Send the log file to my email address. Please don't upload it here on the forum. You can send an email to me by clicking on my name in the post and then clicking "Send Light an email" link.
5. Relax!
OneNote2PDF-WithLoggingAndConfig.zip (Size: 22.16 KB / Downloads: 132)
*Note: If there're any issues with sending the log file to me through the forum, please let me know. I'll communicate my email address to you or you can leave yours there.
When we're done with debugging, we'll turn off this detailed logging by flipping the switches in that file to value 0. But that will come later. Let's first fix it!
And once again, thanks for your patience and trust.
If you have any trouble following the instructions or have doubts / questions, please write right back.
Cheers,
Light.