New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


Error sending "EXE": File "Powershell.exe" not found

Votes:

0

Your Vote:

Up

Down

I am attempted to run a powershell script to restart a service on the affected server when PRTG detects that it is down or not responding in a timely fashion. However, when PRTG attempts to run this script, I get this error:

Error sending "EXE": File "Powershell.exe" not found

Powershell 3.0 IS installed on the PRTG box. Do I also need to install Powershell 3.0 on the affected servers as well? (they should already have PS 2.0 as part of windows server)

exe powershell prtg

Created on Feb 13, 2014 6:05:27 PM by  Peter Bollwerk (0) 1



17 Replies

Votes:

0

Your Vote:

Up

Down

If you have installed PS3 recently and didn't restarted your PRTG box the path variable to the powershell folder may not be set correctly.

Please try to run Powershell.exe from the DOS command line. If it's not found restart your PRTG box, and try again.

You can check the Path variable by set | grep Path

Created on Feb 14, 2014 2:08:00 PM by  Stefan Messner [Paessler Support]

Last change on Feb 14, 2014 2:10:59 PM by  Stefan Messner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Powershell.exe runs fine from inside a DOS command line. Any other ideas?

C:\Users\peter.bollwerk-priv>powershell.exe
Windows PowerShell
Copyright (C) 2012 Microsoft Corporation. All rights reserved.

PS C:\Users\peter.bollwerk-priv> exit

Created on Feb 14, 2014 7:10:57 PM by  Peter Bollwerk (0) 1

Last change on Dec 20, 2016 6:46:13 AM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

The problem may occur by 32/64 bit mix ups Please check if you PowerSchell installation matches your PRTG installation.

Created on Feb 17, 2014 7:06:31 AM by  Stefan Messner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

I don't understand what you mean. The server is running Windows Server 2008 R2 (which only comes in 64-bit) When you install Powershell on a 64-bit OS, it installs BOTH 32-bit and 64-bit versions. When PRTG calls on Powershell, it's up to PRTG which version to use, isn't it? As far as Windows is concerned, if you don't specifically run the 32-bit version (ironically in C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe ), then it will run the 64-bit version, as it is located in C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

I'm not Powershell expert, but the books I've been reading say to use the 64-bit version when you're on a 64-bit OS. I'm not sure why it matters though.

Created on Feb 18, 2014 4:32:16 PM by  Peter Bollwerk (0) 1



Votes:

0

Your Vote:

Up

Down

BTW, here is proof that both versions exist on this server:

C:\>dir /s powershell.exe
 Volume in drive C has no label.
 Volume Serial Number is 80D6-EC1D

 Directory of C:\Windows\System32\WindowsPowerShell\v1.0

08/21/2012  04:17 AM           474,624 powershell.exe
               1 File(s)        474,624 bytes

 Directory of C:\Windows\SysWOW64\WindowsPowerShell\v1.0

08/21/2012  04:43 AM           454,656 powershell.exe
               1 File(s)        454,656 bytes

Created on Feb 18, 2014 4:34:57 PM by  Peter Bollwerk (0) 1

Last change on Aug 16, 2018 6:49:29 AM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi,

thank you for your detailed information.

PRTG calls Powershell.exe without any path, so the path must be in the Path variable of the execution environment.

Could you please post the result of the command set | grep Path

Created on Feb 19, 2014 7:50:46 AM by  Stefan Messner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

FYI - grep is a linux command. It doesn't work in Windows. Here is the path environment variable:

%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;%systemroot%\System32\WindowsPowerShell\v1.0\

It looks like the 64-bit powershell path is in there, but not the 32-bit powershell path. I will add the 32-bit powershell path and test again.

Created on Feb 19, 2014 3:48:59 PM by  Peter Bollwerk (0) 1

Last change on Aug 16, 2018 6:50:02 AM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Works fine after adding the 32-bit powershell path!

Thanks

Created on Feb 19, 2014 4:53:21 PM by  Peter Bollwerk (0) 1



Votes:

0

Your Vote:

Up

Down

Some customers have had to reboot after performing the above actions before this worked correctly.

Created on Jun 23, 2015 3:35:20 PM by  Greg Campion [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi, i have now the same issue. Installed Powershell ver. 3.0 an rebooted. Error "Powershell.exe" not found is stil there.

What can i do?

Thanks

Created on Oct 22, 2015 12:28:35 PM by  Rraiden (0) 1



Votes:

0

Your Vote:

Up

Down

Have you tried adding the path to the 32 bit version as indicated above?

Created on Oct 22, 2015 3:39:38 PM by  Greg Campion [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi, we have the same problem. Where do I have to set the path?

Thanks

Created on Dec 29, 2017 9:21:09 AM by  kelloxx (0)



Votes:

0

Your Vote:

Up

Down

Hi there,

Could you post the result of the following command:

Get-ChildItem Env:Path



Best regards.

Created on Dec 29, 2017 11:02:45 AM by  Dariusz Gorka [Paessler Support]

Last change on Dec 29, 2017 11:02:51 AM by  Dariusz Gorka [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi,

this is the result:

PATH => %SystemRoot%\system32\WindowsPowerShell\v1.0\;C:\Windows\system32;C:\Windows;C:\Windo...

Created on Jan 5, 2018 7:43:15 AM by  kelloxx (0)

Last change on Aug 16, 2018 6:50:25 AM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi kelloxx,

Are you able to run "powershell.exe" via a command line on the Core Server/Probe?

Best regards.

Created on Jan 5, 2018 11:53:18 AM by  Dariusz Gorka [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi,

yes this works without any problems.

Thanks.

Created on Jan 8, 2018 5:06:00 PM by  kelloxx (0)



Votes:

0

Your Vote:

Up

Down

Hi kelloxx,

Great, what sensor exactly is affected? More detailed, what sensor type?

Best regards.

Created on Jan 9, 2018 6:41:22 AM by  Dariusz Gorka [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.