You have to 'use' Win32::PerfLib..
put use Win32::PerfLib; at the top of your script : ) | [reply] |
Hello,
We got the same error once we validated against the server
it's gone.We tested this with just creating a drive
mapping to the sever we wanted to monitor windwos then
uses the credentials it has.
I also used
AuthenticateUser($Domain, $DomainUser, $DomainPassWD);
but with no result
Grtz
| [reply] |
Hi,
I get the same error and I am 'using' Win32::PerfLib. Any ideas?
Thanks,
Mawster
| [reply] |
use warnings
instead of
-w
and it works :)
| [reply] |
I had this error when trying to connect using a Windows account that didn't have rights on the remote server.
However, running the script with a userid that can access the remote server gives you the full list. | [reply] |
Does a remote machine need to have IIS installed on it for PerfLib to work? Its just that when I try it on a network, I only manage to get process lists from machines with IIS installed....
| [reply] |
No, it does not need to have IIS, FORTUNATELY.
| [reply] |
