cobian wrote: ↑29 Feb 2024, 13:25
if (!String.IsNullOrEmpty(theEvent.Parameter2))
process.StartInfo.Arguments = theEvent.Parameter2; <-- the whole quoted set of parameteres assigned here
What do those two lines look like in Cobian Backup?
The "if not the string is null or empty for the event 's second parameter" may be the problem. Perhaps for some odd reason, it thinks "theEvent.Parameter2" is null or empty or maybe even it is randomly picking the wrong parameter or the wrong pre-event, perhaps one that does not exist.
Can you add a proofing statement to see what '"theEvent.Parameter2" actually is? Maybe slip it into the log or spin test version for me to test?
MS documentation for Process.Run says: Quotes in ProcessStartInfo.Arguments must be escaped as three quotes ("""). This is because a single quote is used for passing a string containing spaces as a single argument.
Screenshot_2024-03-01_21-49-28.png (34.44 KiB) Viewed 420 times
And with all the quotes:
k:\Windows\NtUtil\RunLineTest.bat """C:\NtUtil\CobianWrapper.pl6"" ""--rotates 4"" ""--backup_path"" ""[BACKUP]\MyDocsBackup\backup1"""
Everything gets jammed into the first parameter, which goofs up my stuff pretty badly:
Todd wrote: ↑05 Feb 2024, 23:46
Fixed for the next version
Yippee!!!! Thank you!
Working great in 2.6. Thankyouthankyouthankyouthankyou!!!
Sorry but what about this, this didn't worked.
Hi Ushavilash,
This is what is known as an "intermittent". It is the worst, most irritating bug for a programmer to isolate and correct. That being said, Cobian is a genius programmer and he will eventually fix it. He might not have an hair left and might have picked up a few new "Colourful" words in the process, but he will eventually fix it.
