When creating a KSCRIPT and using the verify that a file exists task/step, K1000 is prepending "C:\Windows\system32\config\systemprofile" into the directory/path when using an environment variable such as %USERNAMES% or %APPDATA%.

For example, if I enter C:\%AppData%\Roaming\Autodesk\Revit\Addins\2016\ as the directory to check if file exist, then K1000 will prepend C:\Windows\system32\config\systemprofile, thus looking for the fileĀ in the wrong directory/path and triggering this error in the logs: File does not exist: C:\C:\Windows\system32\config\systemprofile\AppData\Roaming\Roaming\Autodesk\Revit\Addins\2016\FileName.Extension

We're on version 7.1.149 of K1000 appliance.

I found another KB article describing a similar issue with an older version of K1000 here: https://support.quest.com/kace-systems-management-appliance/kb/113838

1 Comment   [ + ] Show Comment

Comments

  • I should mention that running the scrip as "logged-in user" doesn't make a difference.
Please log in to comment

Answers

-1
Set the script to run in the context of the logged-in user.
Answered 10/02/2017 by: VBScab
Red Belt

  • I thought this was the issue as well, but I've tried running the script as "logged-in user" and it doesn't make a difference.
Please log in to comment
Answer this question or Comment on this question for clarity
Admin Script Editor
Admin Script Editor is an integrated scripting environment available free here at ITNinja

Share