/build/static/layout/Breadcrumb_cap_w.png

K1000 prepending "C:\Windows\system32\config\systemprofile" when using enviornment variables

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
  • I should mention that running the scrip as "logged-in user" doesn't make a difference. - jcalvo@huntonbrady.com 7 years ago

Answers (1)

Posted by: anonymous_9363 7 years ago
Red Belt
-1
Set the script to run in the context of the logged-in user.

Comments:
  • 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. - jcalvo@huntonbrady.com 7 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

View more:

Share

 
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