Box Status

コメント

4件のコメント

日付 投票
  • Kamil Berdychowski

    Hello,

    what do you mean by not recognised? I was able to install cli using files provided in Github repository follow the guide and run commands.

    Can you provide more details?

    0
    コメントアクション パーマリンク
  • Ed Huels

    After running the installation, running box from a command windows results in message that it is "not recognized as an internal or external command..."  

    I did some more digging and realized this is probably a Windows or permissions problem.   I can navigate to the @boxcli\bin folder and successfully execute box from there.  I verified the PATH in the User variables contains the path to @boxcli\bin.  But it appears the path is not being recognized.

    I appreciated any assistance, but I realize this isn't really a Box issue

    0
    コメントアクション パーマリンク
  • Kamil Berdychowski

    Hi,

    you are right looks like a windows issue. I've created a non admin user and I can see that the path contains `@boxcli\bin` but I cannot invoke the cli unless I'm running as an admin.

    I was able to use a workaround Opening up Windows Terminal with elevated privileges, from within Windows Terminal - Stack Overflow and create a terminal window with admin rights and then it works. But I'm not windows administration expert... 

    0
    コメントアクション パーマリンク
  • Ed Huels

    Running the install under non-admin user, a prompt comes up for admin access.  In doing so the User PATH is updated but for the Admin account used.  I was able to manually enter the PATH in the System Variable, albeit using Admin credentials, and this resolved the issue.     Might be a consideration for CLI dev to have the install routine update the System PATH instead of the User PATH.

    0
    コメントアクション パーマリンク

サインインしてコメントを残してください。