Question-and-Answer Resource for the Building Energy Modeling Community
Get started with the Help page
Ask Your Question
3

openstudio-workflow gem error

asked 2021-03-12 08:14:02 -0600

Craig Simmons's avatar

When running OS CLI v2.9.0 am getting the following error.

Exception: Embedded file not found ':c:/ruby/2.2.0/gems/openstudio-workflow-1.3.4/lib/openstudio/workflow/version.rb'

Tried uninstalling other versions and reinstalling v2.9.0 in case there was some mix up but that did not help. Simply running a more recent version is not a solution because we have some automated tools that are dependent on v2.9.0. The machine being used in this case is Windows and does not have Ruby installed outside of the OS installation. I'm basically trouble-shooting a supposedly generic machine that others would use.

edit retag flag offensive close merge delete

Comments

I'd seen this issue. But I was eventually no longer able to reproduce it and I don't think we ever figured out why it happened.

shorowit's avatar shorowit  ( 2021-03-12 08:52:01 -0600 )edit

thats strange. maybe an ENV setting? as a work around, If you are just using the CLI, install PAT and use the CLI in its server directory. it has all the gems preinstalled.

BrianLBall's avatar BrianLBall  ( 2021-03-12 09:00:10 -0600 )edit

It could be related to ENV settings. We had some issues earlier with admin rights on this machine that impeded some ENV settings. I thought we had resolved those but maybe there is something lingering.

Can you think of a specific PATH setting that might help? The OS path is defined to point to v2.9.0, maybe add a Ruby path?

Craig Simmons's avatar Craig Simmons  ( 2021-03-12 09:19:20 -0600 )edit

maybe RUBYLIB... i wonder if doing bundle install with verbose through the CLI will give any clues...

BrianLBall's avatar BrianLBall  ( 2021-03-12 09:25:49 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted
1

answered 2021-03-15 15:08:13 -0600

tijcolem's avatar

Sounds like due to this. https://github.com/NREL/OpenStudio/is.... We've correct this for 3.2 release. For previous release you'll need to make sure you in upper case C: vs lower c: prompt on windows.

edit flag offensive delete link more

Comments

Thanks Tim. That was the issue. In our case we are using Anaconda to manage the environment and there seems to be some odd inconsistencies within Anaconda between users and whether they get an uppercase or lowercase 'C'. but that does indeed seem to be the issue.

Craig Simmons's avatar Craig Simmons  ( 2021-03-16 18:42:48 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Training Workshops

Careers

Question Tools

1 follower

Stats

Asked: 2021-03-12 08:14:02 -0600

Seen: 223 times

Last updated: Mar 16 '21