Hi All,
We’ve been having an issue in our team - not sure if IT related but our process went as follows:
-
Normal install of LBT through food for rhino.
-
Running things normally, until i recieved this error.
Solution exception:No file was found at C:\Users\[USERNAME]\simulation\[MODEL_NAME]\openstudio\out.osw
-
Followed Radiance blocked post which suggested the Pollination move to program files is the fix (radiance produced similar error)
-
Run smoothly for a couple of days but same error returned (potentially IT induced)
-
Read the HB to OSM component Line 228 - suggesting the idf file isn’t being created properly.
-
Read HB to OSM component Line 38 which has alternative running methods.
-
Changed boolean toggle to integer “3” in a panel and managed to run the simulation okay.
Short workaround - not sure if there are some anomolous results writing and running the simulation this way but a short term fix at least.
@chris - would love a chance for you (or someone else) to give this another look over!
thanks!
We managed to fix & our IT explained a little bit about what’s happening. Basically a batch file is created in the user’s profile and run in the folder which in turn trips up IT security when a group policy is in place.
The error can be be viewed on MS Windows by going into Event Viewer - Applications and Services Logs - Microsoft - Windows - AppLocker - MSI and Script.
Error
%OSDRIVE%\USERS{Username}\SIMULATION\HB_MODEL_TEST\OPENSTUDIO\RUN_WORKFLOW.BAT was prevented from running.
The script was identified as not being signed as secure - and so IT have exempted by folder location through editing the group policy via AppLocker.
This was done by:
Location in group policy – Computer configuration – Windows Settings – Security Settings – Application Control Policies – Script Rules
Exemption type – Path
Folder exemption listed - %OSDRIVE%\USERS*\SIMULATION*\OPENSTUDIO*
Understanding the path rule condition in AppLocker (Windows) | Microsoft Learn
The first wildcard is for the name of the user who is running the script (their profile location). The second is the name of the project that the user created. The last is to allow any scripts in that folder to be run.
Hope this helps people needing a fix in the interim!
Hello all. I realize this thread’s a little dusty, but, I ran into the same error. It happened when I tried shifting my working directory onto an external drive (an SSD on a USB C port; not sure if it’s Thunderbolt). I moved everything back to good ol’ C, and it works (again). I assume the root issue is as identifed by @LeightonSS55 here, and, wow, that’s some troubleshooting you did! Glad I haven’t had to edit group policies…yet.