powershell build-in function not recognized as the name of a cmdlet

Question

The term 'Write-Host' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

The term 'New-Object' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again

aka:Write-Host is build-in function in powershell. how to find root cause of that issue?

Update

The same script works while executed in other dev machine.

update

I have tried to set max memory of powershell for single instance to 1GB, and set max memory of powershell for single user to 100M. It still not work.

> Write-Host hello world it's working fine here. check your spelling and are you in powershell cmd — Nikson Kanti Paul
– Nikson Kanti Paul, Commented Jan 18, 2016 at 5:36
Seems like issues with powershell.exe without enough memory. it really work in my dev machine but not work in production env. — suiwenfeng
– suiwenfeng, Commented Jan 18, 2016 at 5:39
What's with all the powershell instances? Why do you need so many? — Lieven Keersmaekers
– Lieven Keersmaekers, Commented Jan 18, 2016 at 6:49
i use powershell in sqlserver agent job. so there are many sqlserver instance and many jobs run at the same time. — suiwenfeng
– suiwenfeng, Commented Jan 18, 2016 at 6:59
Just to make sure: if you open a powershell prompt on that machine and execute Write-Host, you get the error message? What do you get if you execute gcm *host*? — Lieven Keersmaekers
– Lieven Keersmaekers, Commented Jan 18, 2016 at 7:44

Vivek Athalye · Accepted Answer · 2016-01-18 08:12:02Z

3

Looks like there is a limit on number shell instances that can be run by a single user. Are you hitting that limit?

Ref: https://msdn.microsoft.com/en-us/library/ee309367(VS.85).aspx

MaxShellsPerUser: The maximum number of shells per user. The default is 30.

answered Jan 18, 2016 at 8:12

Vivek Athalye

2,9792 gold badges24 silver badges34 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

suiwenfeng Over a year ago

Thanks vivek. it works after I remove some silos in our dev environment.

Ken Chen Over a year ago

@suiwenfeng, could you please shed more light about how you resolve this problem as i run into the same issue. btw, I didn't see i hit the shell instance etc limits. Thanks !

suiwenfeng Over a year ago

@KenChen check all powershell processes and kill some of them, avoid over the limitation(MaxShellsPerUser);

Collectives™ on Stack Overflow

powershell build-in function not recognized as the name of a cmdlet

1 Answer 1

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related