Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

snc ui-component "The system cannot find the file specified."

josteinenge
Kilo Guru

Servicenow Custom Components

 

Yesterday it was working fine, today i get this message.

The system cannot find the file specified.

 

I have reinstalled  CLI, NVM and Node.

 

josteinenge_0-1762161931523.png

Im running version

NPM 8.5.5

Node 22.21.1

 

as shown in docs, however im running Windows 11, but this has not been a problem in the past..

josteinenge_2-1762162458660.png

 

 

I can connect profile 

Connection to https://*****dev.service-now.com successful.
Metadata retrieved successfuly from https://*****dev.service-now.com
Profile default has been saved

 

When i run

 snc extension add --name ui-component

i get

Extension ui-component installed successfully

 I have removed and updated

PS C:\WINDOWS\system32> snc extension update --name ui-component
Extension ui-component already upto date

 

But i still get this.

 

PS C:\WINDOWS\system32> snc ui-component --help
The system cannot find the file specified.
PS C:\Users\*****\Desktop\Folder> snc ui-component project --name @myorg/movie-quotes --description 'A web component that prints movie quotes.'
The system cannot find the file specified.
PS C:\Users\****\Desktop\Folder\Project> snc ui-component develop
The system cannot find the file specified.

 

Do anybody have a fix to this issue?

 

1 ACCEPTED SOLUTION

josteinenge
Kilo Guru

After hours of reinstalling and debugging, I discovered the issue: my newly generated ServiceNow password contained special characters "!{_<;". I suspect the semicolon (;) was causing the command to break. I regenerated a new password without "{, <", or ";" and now everything is working.

 

Fantastic...

View solution in original post

1 REPLY 1

josteinenge
Kilo Guru

After hours of reinstalling and debugging, I discovered the issue: my newly generated ServiceNow password contained special characters "!{_<;". I suspect the semicolon (;) was causing the command to break. I regenerated a new password without "{, <", or ";" and now everything is working.

 

Fantastic...