Hello.
Thank you. I used your values and ran the utility in Debug mode. I noticed that .NET DateTime structure couldn't parse the date and time in the format that QTP supplies to the utility in your system.
Earlier, I had believed that QTP also will use the same date time format as your system date and time but it appears that they are not the same. The funny thing is that here on my system QTP utilizes the same date/time format as my system and .NET, hence I never saw this issue.
I think the safest bet is to utilize DotnetFactory here. Can you replace Line 13 where we're assigning CStr(Now) to the variable: lastPrintedTime with two lines that I pasted below?
Set dotNetDateTime = DotnetFactory.CreateInstance("System.DateTime")
lastPrintedTime = dotNetDateTime.Now
Also capture the value as it goes this time.
If you see the value is still being passed the same way as before, then consider using the following lines instead:
completeDate = year(Date) & "-" & month(Date) & "-" & day(Date)
lastPrintedTime = completeDate & " " & Time
What still perplexes me though is the fact that on 15th July, the utility exported almost all the pages in your notebook beginning from 19th May! Now, I couldn't link 19th May 2011 and 15th July 2011 at all. Have you got any idea about this? According to the code, it shouldn't have exported a single page because .NET couldn't parse the date at all.
And another puzzle is the generation of log file. Can you check if the file OneNote2PDF.exe.config which exists in the same location as the utility itself has the following key/value pairs?
1. <add name="DataMessagesSwitch" value="1" />
2. <add name="TraceLevelSwitch" value="4" />
When you ran the script this time, did you allow the utility to run to finish? Or, you just put the breakpoint on Line 25, captured the values of variables and stopped the script? Remember the log will only be available if the utility was really invoked and allowed to run for some time.
Please also make sure that the folder where you've placed the utility and the config file isn't read-only and that you have write permission on the folder.
I'd wait for your observations.
Thanks,
Light.
Thank you. I used your values and ran the utility in Debug mode. I noticed that .NET DateTime structure couldn't parse the date and time in the format that QTP supplies to the utility in your system.
Earlier, I had believed that QTP also will use the same date time format as your system date and time but it appears that they are not the same. The funny thing is that here on my system QTP utilizes the same date/time format as my system and .NET, hence I never saw this issue.
I think the safest bet is to utilize DotnetFactory here. Can you replace Line 13 where we're assigning CStr(Now) to the variable: lastPrintedTime with two lines that I pasted below?
Set dotNetDateTime = DotnetFactory.CreateInstance("System.DateTime")
lastPrintedTime = dotNetDateTime.Now
Also capture the value as it goes this time.
If you see the value is still being passed the same way as before, then consider using the following lines instead:
completeDate = year(Date) & "-" & month(Date) & "-" & day(Date)
lastPrintedTime = completeDate & " " & Time
What still perplexes me though is the fact that on 15th July, the utility exported almost all the pages in your notebook beginning from 19th May! Now, I couldn't link 19th May 2011 and 15th July 2011 at all. Have you got any idea about this? According to the code, it shouldn't have exported a single page because .NET couldn't parse the date at all.
And another puzzle is the generation of log file. Can you check if the file OneNote2PDF.exe.config which exists in the same location as the utility itself has the following key/value pairs?
1. <add name="DataMessagesSwitch" value="1" />
2. <add name="TraceLevelSwitch" value="4" />
When you ran the script this time, did you allow the utility to run to finish? Or, you just put the breakpoint on Line 25, captured the values of variables and stopped the script? Remember the log will only be available if the utility was really invoked and allowed to run for some time.
Please also make sure that the folder where you've placed the utility and the config file isn't read-only and that you have write permission on the folder.
I'd wait for your observations.
Thanks,
Light.