'cscript' is not recognized as an internal or external command, operable program or batch file.

[tajdarahmad]

Hi Team,

When I am trying to discover a windows machine, I am getting
'cscript' is not recognized as an internal or external command, operable program or batch file.

I have RDP'd the windows server and everything looks fine. I was able to execute 'cscript' command in cmd.exe without any problems.

Any suggestions from you guys will be helpful.

Thanks.

[tajdarahmad]

Doug, I have sent you a mail regarding this. Hope to hear from you.

[Gerald Harris]

We are experiencing what seems to be a similar issue. Has there been a resolution? Can anyone pass it on?

[mark_sonter]

Has this issue been resolved by anyone. Across the fleet of 500 servers I've got several that throw this error. NMAP confirms ports are open, WMI remote testing using discovery credentials work and WMI repository has been rebuilt. Still no change.

[doug_schulze]

Mr Harris was able to provide some additional insight to this problem..Good work here!

1) Logging in as the MID server user, we checked the environment variables for the user and saw that the path did not have the location "C:/Windows/system32".
So, we added this in the variables, however this did not immediately resolve the issue.

2) We then investigated and saw the MID server was installed in a local user directory "C:/Documents and Settings/[user]/...."
We have seen issues before where if the MID server is not installed under the main C:/ directory, this may cause issues.

2a) We also saw that the MID server was actually from the Berlin instance, so we also needed to download the latest MID server from the Calgary instance.

3) We uninstalled the current MID server, then installed a new MID server (xxx_midserver) and when we ran a scan on the same server as the MID server, we saw that the probes were running correctly and returning data.