Verify that the file "" was modified since ""

There is a verify option in Kscripting that allows you to check the date on a file before continuing.

I've specified the path and name which seems fine but I can't seem to get the script to accept any date I set for the "Modified Since:" field. I get parse errors that look like the following:

2010-07-08 08:36:16 Cached Parse Error changed from 'KBotXMLParser: invalid document (XSD check failed) for 632: BookMaster update Z742AOCP.jwr July 01 2010 , Element 'file_modified_since', attribute 'expectedValue' ['date']: The value '07/01/10' is not valid., ' to '
Removed dependencies: kace2656.bat (e8d6586e42be0392a5689c20ce3ce79e), kace5394.bat (da505c6edd1b264a6924301fd3b12c93)
Added dependencies: kace5758.bat (e8d6586e42be0392a5689c20ce3ce79e), kace7916.bat (da505c6edd1b264a6924301fd3b12c93)
Policy or Job Rules changed.

Has anyone else succesfully used this paticular Verify type? Please let me know what I may be doing wrong or missing?

Thanks so much,

0 Comments   [ + ] Show comments

Answers (3)

Posted by: anonymous_9363 11 years ago
Red Belt
Try the KBox-specific forums.
Posted by: bryceb 11 years ago
Senior Yellow Belt
Thanks for stopping by and looking. As they say if you want something fixed you have to do it yourself. I kept trying and sure enough this Verify works with hyphens not backslashes in this format. YYYY-MM-DD

Hopefully this helps someone else trying to do the same thing!!!!

Posted by: anonymous_9363 11 years ago
Red Belt
I wonder if the date format which is set in the workstation's Regional and Language Options is relevant to the format which KBox "understands"?
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ