An URBANopt installation was found at C:\URBANopt-cli-0.8.0 but the URBANopt executable is not accessible

Hello Everyone,

I installed the programs exactly in the compatibility matrix and I got this message
run error

Could someone help, Many thanks in advance!

Hey @Mohammad.ElGhandour ,

As the message indicates, this is an issue to work out between you and your IT department. It seems that your User account on Windows doesn’t have access to run the URBANopt CLI executable. Your IT department would need to whitelist the URBANopt installation for you to be able to use it from your account.

Many thanks for your help. I just added an exception for it in the Windows defender.
Is that what you meant?

image

I am still getting the same message. Any further advice I could do as its my personal laptop?

Many thanks again and eager to hear from you

:thinking: Hmm. In that case, maybe your URBANopt installation was corrupted or it did not install correctly. Does uninstalling and reinstalling URBANopt have any effect?

1 Like

Many thanks for your consideration. I uninstalled and reinstalled and nothing happened.

In fact to make sure from that, now I removed the whole Rhino software including all plugins and reinstalled them, I got the same result unfortunately.

Thanks @Mohammad.ElGhandour ,
I wonder if this has something to do with your username.

Can you open up a command prompt and they in the following:

C:\Users\[USERNAME]\.env_uo.bat

… but replace [USERNAME] with your actual username. Then hit Enter and post a screenshot of the result. This will help me understand if your environment isn’t being set up correctly.

1 Like

Kindly find it below

Thanks, @Mohammad.ElGhandour . This greatly narrows down the issue. Can you run the following batch file from command line and post a screenshot of the output:

C:\URBANopt-cli-0.8.0\setup-env.bat

There’s a chance that the command succeeds, in which case it will give you the .env_uo.bat file that you are currently missing and will get everything working for now. If not, then the message will tell us exactly where things have gone wrong.

I have to imagine that this issue is likely related to the spaces in your username and I’ll try to investigate myself to see if I can recreate it.

Many thanks for your consideration Chris, I do appreciate it a lot!

Kindly find it here

Hey @Mohammad.ElGhandour ,

This is very helpful and I can now say that it’s definitely the result of the spaces in your username. It’s also definitely an issue that I plan to report to NREL to see if they can permanently fix it.

I’ll see if I can find a workaround to get you a setup-env.bat file that will work for your username but I don’t know how long this might take.

What I can tell you for sure is that creating another user on your machine that does not have spaces and running Ladybug Tools/URBANopt from there will definitely fix it. I know that creating another user profile is potentially a big effort but this may prove to be the fastest way to fixing it for now until we can get a better solution. I’ll also clarify that this issue is specific to URBANopt simulation and all other Ladybug Tools simulation capabilities should be usable with the spaces in your username.

Ok, I’m hopeful that this was actually a lot easier to address than I was originally thinking. Can you give the following a try:

  1. Download this custom version of setup-env.bat that I put together to handle the spaces in your username:
    setup-env.bat (808 Bytes)
  2. Copy it over the file that is currently at C:\URBANopt-cli-0.8.0\setup-env.bat
  3. Run the setup-env.bat either by double-clicking it or running it from command line as you’ve been doing
  4. See if you can run a successful URBANopt simulation

If this works, then I’ll let NREL know that this is a way to permanently fix the issue and they should integrate it into the URBANopt release.

I exactly did the steps, Unfortunately it gave me the same result.

  1. Solution exception:An URBANopt installation was found at C:\URBANopt-cli-0.8.0
    but the URBANopt executable is not accessible.
    ‘C:\Users\Mohammad’ is not recognized as an internal or external command,
    operable program or batch file.
    ‘uo’ is not recognized as an internal or external command,
    operable program or batch file.

I hope it helps, This is the new command prompt for setup-env.bat

Ok, we’re making progress! Thanks for bearing with me, @Mohammad.ElGhandour .

From your second screenshot, I see that we’ve definitely fixed one of the issues by means of the updated setup-env.bat file. Can you now send a screenshot of what happens when you run the file that’s at:

C:\Users\[USERNAME]\.env_uo.bat

Also, if you can upload a copy of this .env_uo.bat file here, I think I can get you a version of it that fully addresses the issue.

In fact its thanks to you for your help and effort, I am really so much grateful!

Kindly find the file requested attached
.env_uo.bat (728 Bytes)

Please find the screenshot here

Thank @Mohammad.ElGhandour ,

It’s a little odd that it isn’t working as it seems the .env_uo.bat is working but maybe I am missing something. Let’s see if we can get it to work with the following file:

env_uo.bat (718 Bytes)

Just paste that into:

C:\Users\[USERNAME]\.env_uo.bat

and see if that gets the simulation to suceed.

Thanks a lot, but Unfortunately the same result.

This is the screenshot

  1. Solution exception:An URBANopt installation was found at C:\URBANopt-cli-0.8.0
    but the URBANopt executable is not accessible.
    ‘C:\Users\Mohammad’ is not recognized as an internal or external command,
    operable program or batch file.
    ‘uo’ is not recognized as an internal or external command,
    operable program or batch file.

Hey @Mohammad.ElGhandour ,

Sorry for the delayed response. After sleeping on it and taking a look at the error message with fresh eyes, I am pretty sure that I know where the problem is now. Give me little time to push a fix and I’ll post back here when it is ready to test.

1 Like

Hey @Mohammad.ElGhandour ,

Ok, I just merged a fix into the latest development version of Ladybug Tools, which should address your issue here:

You can get the fix on your end but, because the latest development version of Ladybug Tools uses URBANopt 0.8.2, you’ll have to install the latest URBANopt. So, to get everything working on your side, you’ll have to do the following:

  1. Run the LB Versioner component and then close Rhino/Grasshopper (this will give you the latest version of Ladybug Tools).
  2. Uninstall your current version of URBANopt and install URBANopt 0.8.2 from here.
  3. Copy the following file to C:\URBANopt-cli-0.8.2\setup-env.bat, overwriting the file that is there in the process:
    setup-env.bat (808 Bytes)

After doing all of this, I think you should be able to successfully run URBANopt simulations on your machine. Let me know if you encounter any issues.

FYI, I have already let NREL know about the first issue that we addressed via the setup-env.bat and they will hopefully be able to incorporate this fix into the next release of URBANopt.

1 Like

Many many thanks for your consideration and effort.

I just have one query, according to the compatibility matrix I should have 0.8.0 with Rhino 7.18 which is the version I have.

So I want to ask could I still install 0.8.2 or not?

I am eager to hearing from you