NetSetMan Support

dudongwtf

Member

Registered: 2016-10-03

Posts: 3

PIPE does not exist. (Error 121) at startup Standard User Win7 Pro 64

Hi,

I created a batch file that will run on startup to change IP per user's account. I have a Standard User and an Administrator account. Ex, Standard User = 192.168.1.1 and Administrator = 192.168.2.1. I noticed that at the startup in Standard Account, I received this error "PIPE does not exist. (Error 121) and NSM Service is installed and running, but an error occured while trying to start NetSetMan. (Error:". But when I am in Administrator account, there is no error and NSM is running fine. Thanks!

Batch file:

Standard User: "C:\Program Files (x86)\NetSetMan\netsetman.exe" -as 1 (192.168.1.1)

Administrator: "C:\Program Files (x86)\NetSetMan\netsetman.exe" -as 2 (192.168.2.1)

Last edited by dudongwtf (2016-10-03 03:59)

NetSetMan Support

Administrator

Registered: 2005-08-06

Posts: 1,878

Re: PIPE does not exist. (Error 121) at startup Standard User Win7 Pro 64

Which NetSetMan version is this? Please alsways include this information as requested in the info box when creating a new topic.

If it's the latest version:

Did you verify your assumption by retrying multiple times or is your observation and description based on a one-time test?
Does running the application in the user account without the batch file work?
Try adding a delay before executing this command. It might be possible that the NSM Service isn't started up completely when the batch file is executed.

dudongwtf

Member

Registered: 2016-10-03

Posts: 3

Re: PIPE does not exist. (Error 121) at startup Standard User Win7 Pro 64

Hi,

Which NetSetMan version is this?
- 4.2.2

Did you verify your assumption by retrying multiple times or is your observation and description based on a one-time test?
- Multiple times.

Does running the application in the user account without the batch file work?
- Yes. NSM is running fine without the bath file. I can switch to any profile I want but not on startup where the batch file will set a profile for me.

Try adding a delay before executing this command.
- Yes. I already add a delay with the batch file but still getting the errors.

Thanks!

NetSetMan Support

Administrator

Registered: 2005-08-06

Posts: 1,878

Re: PIPE does not exist. (Error 121) at startup Standard User Win7 Pro 64

Does running the application in the user account without the batch file work?
- Yes. NSM is running fine without the bath file. I can switch to any profile I want but not on startup where the batch file will set a profile for me.

This leaves us with the question whether you can run the script in Windows manually (not on start-up) or if that creates the error as well. The circumstances need to be narrowed down as precise as possible to have a good starting point for our analysis.

In your case we need to know the results of the different starting methods (all in the restricted user account):
1. Run program manually using its shortcut/executable.
2. Run the command manually in a cmd.exe dialog (outside of your script):
"C:\Program Files (x86)\NetSetMan\netsetman.exe" -as 1
3. Run the script (that you're currently using for autorun) manually.
4. Add a really long delay (~2min) before executing the command on startup.

If running the program manually works fine but the startup script fails, then the only reason can be timing (where some Windows components or the NSM Server aren't fully loaded yet when you execute the script/program).

dudongwtf

Member

Registered: 2016-10-03

Posts: 3

Re: PIPE does not exist. (Error 121) at startup Standard User Win7 Pro 64

Hi,

Please close this thread as I solved the issue. I found out that the issue is not on the account type. I unchecked "Start with Windows" and let the script run and call NetSetMan on startup. Then the error is gone. Thanks!

NetSetMan Support

Administrator

Registered: 2005-08-06

Posts: 1,878

Re: PIPE does not exist. (Error 121) at startup Standard User Win7 Pro 64

Thank you very much for posting your results!
So the reason in your case is possibly that when the first instance is started it uses the communication channel with the service. If the service isn't fully loaded yet, the application waits for it. Now when the second instance is started it cannot use the same communication channel, so it fails. We'll try to reproduce this behavior (which is difficult, because it depends on the startup behavior of the system) and if we succeed, we'll implement either a solution or at least a better/explanatory error message.