Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

2000+ cmd/conhost processes after vbscript?

Recently wrote a vbscript user experience monitor, which executes a couple of perl scripts in cmd, and echos/exits based on result.

Now a few days later our solarwinds server is at 98% memory, and has 1075 cmd.exe processes running, and 1077 conhost.exe processes running.

The scipt has the following lines after the objShell.Run "%comspec% /k perl C:\Users\solarwinds\ntpmonitor.pl >ntpmonitor.txt" line:

WScript.Sleep 6000
objShell.SendKeys "Exit"
objShell.SendKeys "{ENTER}"

Which should exit the cmd prompts, but clearly something is going wrong.

Any ideas?

windows.txt

Find more posts tagged with

Accepted answers

josh.clark

Any reason you can't just use /C to terminate the command prompt after the command finishes?

From cmd /?

/C Carries out the command specified by string and then terminates

All comments

josh.clark

Any reason you can't just use /C to terminate the command prompt after the command finishes?

From cmd /?

/C Carries out the command specified by string and then terminates

berger

Thanks for the quick reply. I didn't think /C would wait for my perl scipts to finish, much like an appended "& exit" wouldn't, but now looking at it again looks like I was wrong.

I will try out /C and post if it makes a difference.

Edit: Not sure why the other method was failing, but it looks like that did the trick, thanks again.

berger

Josh,

The /C appears to have only semi-fixed the problem. cmd.exe is indeed waiting for the perl script to finish before closing the cmd window; however, the vbscript keeps going without waiting, and in doing so causing only part of the file that's supposed to be written from execution of the perl script to get written.

Any ideas?

josh.clark

Don't you need to tell the WSH Shell to wait for the perl script to finish? The 3rd parameter to Run can tell it to wait.

http://msdn.microsoft.com/en-us/library/d5fk67ky(VS.85).aspx

bWaitOnReturn: Optional. Boolean value indicating whether the script should wait for the program to finish executing before continuing to the next statement in your script. If set to true, script execution halts until the program finishes, and Run returns any error code returned by the program. If set to false (the default), the Run method returns immediately after starting the program, automatically returning 0 (not to be interpreted as an error code).

berger

Thanks again for the quick response.

I somewhat re-wrote the earlier script, and actually had ",1, True" but apperently an argument wasn't getting passed correctly into the perl script, causing nothing to be placed in the created .txt file, and causing me to thing that the vbscript wasn't waiting.

Although the ",1 True" or just ", True" doesn't seem to be enough, since it appears that windows takes a tiny bit of time between when the >egtxt.txt command is executed and when the file is actually created. So a short WBScript.Sleep needs to be used as well.

Sorry for the confusion