Troubleshooting ServiceNow CLI errors

[Marc Mouries]

Here are common problems you might come across with the ServiceNow CLI, along with the reasons behind them and suggestions on how to address them:

INSTANCE VERSION COULD NOT BE VALIDATED 

• Reason: This issue arises when ServiceNow attempts to confirm the version of your instance. It does this by accessing the stats.do page. However, starting from the 'San Diego' version, access to stats.do is restricted to only the administrator account. 
• Action: You can safely ignore it.
• Solution: On your development instance, you can set the system property glide.security.diag_txns_acl to false to allow access to non-Administrators.

NPM INSTALL ERRORS

Error npm ERR! Failed at the node-sass@4.12.0 postinstall script.

And you see a message Can't find Python executable "python",

• Reason: This issue arises on Mac computers with the M1 (Apple silicon) chips. 
• Action: Follow the steps below.
• Solution: Use either option 1 or 2 below
  1. Configure the out-of-the-box Terminal app
     1. Open Finder and navigate to the Application -> Utilities folder
     2. Select the Terminal app and select Duplicate.
     3. First, duplicate the Terminal and rename it to Terminal Rosetta.
     4.  Type "⌘ + i" and check the box "Open with Rosetta".
     5. Use this terminal going forward
  2. Use an alternate Terminal app like iTerm (https://iterm2.com/)

Error npm ERR! gyp ERR! cwd /your_path/node_modules/node-sass

• Reason: Likely due to not using the right node version. 
• Action: Follow the steps below.
• Solution: 
  1. Check you are using the correct Version of Node/NPM to use to create a custom component

Unsupported Instance Version

• Reason: You're likely upgrade your ServiceNow instance and it no longer matches the version of the CLI 
• Solution: Update the CLI: 

  • snc extension update --name ui-component

Scope is Taken

• TBC

[Aylee Andersen]

Here is a blog post on other common Now CLI errors. There is some crossover but also some additional information and workarounds. Hope it helps as an additional resource to whatever poor soul is troubleshooting Now CLI errors!

https://blog.yansalabs.com/2023/07/20/resolving-common-now-cli-errors/

[Marc Mouries]

@Aylee Andersen Thanks for sharing your knowledge with the community. Note however that in your blog, for  the issue of Unsupported Instance Version, you mention changing code inside node_modules. That is not a good practice. Usually the issue is a mismatch between the instance version and the ui-component package inside the ServiceNow CLI. If people encounter this issue they should update the CLI with the command above first.

[Shiva Prasad]

Hi @Marc Mouries 

Do CLIs support proxy settings? Trying to authenticate to SN instance by setting the proxy settings in visual studio code and it does not seem to work .

Error: Encounted an error while accessing resource: xyz.service-now.com, Could be a network issue or an invalid URL

Regards

Shiva

[Marc Mouries]

@Shiva Prasad  Check this page to Use a proxy server with ui-component extension