Calculating server uptime gives "The network path was not found"

Question

For the following code, I am getting

System.ComponentModel.Win32Exception: The network path was not found

Can anyone help?

PerformanceCounter pc = new PerformanceCounter("System",
        "System Up Time");
                pc.MachineName = "1.2.3.4";

                //Normally starts with zero. do Next Value always.
                pc.NextValue();
                TimeSpan ts = TimeSpan.FromSeconds(pc.NextValue());

                Response.Write("This system 1.2.3.4 has been up for " + ts.Days + " days " + ts.Hours + " hours, " + ts.Minutes + " and " + ts.Seconds +" seconds.");

Edit: I tried with machine name, and I still get the same error! Note: 1.2.3.4 is a sample value.

Perhaps you just don't have any machine with 1.2.3.4 as its name? It looks like an example value, which you might have to change appropriately. — pimvdb, Jan 24 '11 at 18:39
yeah thats the sample ip address, I did not put the actual value. — genericuser, Jan 24 '11 at 19:04

score 11 · Answer 1 · answered Nov 12 '12 at 09:44

11

This error can be caused if the Remote Registry service is not started on the remote machine 1.

answered Nov 12 '12 at 09:44

nftw

589
4
10

This was the problem I had. – Novaterata Mar 21 '16 at 14:14
Same for me. it was the issue that I was facing. Thanks for help! – Oleh Udovytskyi Jan 19 '18 at 10:53

score 2 · Accepted Answer · edited Jul 25 '12 at 12:37

2

Uncomment pc.NextValue() and the code works. The problem is reproduceable by giving a bad machine name or IP address. So your IP is bad.

var machineNameOrIP = "10.16.7.1";
var pc = new PerformanceCounter("System", "System Up Time");
pc.MachineName = machineNameOrIP;
//Normally starts with zero. do Next Value always.
pc.NextValue();//uncomment this
var ts = TimeSpan.FromSeconds(pc.NextValue());
Response.Write("This system " + pc.MachineName + " has been up for " + ts.Days + " days " + ts.Hours + " hours, " + ts.Minutes + " and " + ts.Seconds +" seconds.");

edited Jul 25 '12 at 12:37

bluish

26,356
27
122
180

answered Jan 24 '11 at 18:50

P.Brian.Mackey

43,228
68
238
348

no, the IP is not bad, I tried to ping it, and it works. pc.NextValue() is the place where it fails and gives "The network path was not found". "1.2.3.4 is sample ip that I put in the above code sample" – genericuser Jan 24 '11 at 19:03
4

At least 3 of us have run the code and the code works. I'm running Windows XP SP3. Its something with your environment. Permissions, OS configuration, network..etc. This forum is for code issues. Walk over to the machine make sure its running a windows OS, you have the right IP, run systeminfo make sure it returns the uptime, check with netOps...these are your next steps and these arent code steps. – P.Brian.Mackey Jan 24 '11 at 19:16

score 0 · Answer 3 · answered Jan 24 '11 at 18:48

0

Either the MachineName "1.2.3.4" does not exist, or it cannot be reached on the network.

I tested your code with a machine name that exists on my network, and it works fine.

answered Jan 24 '11 at 18:48

driis

161,458
45
265
341

score 0 · Answer 4 · answered Jan 24 '11 at 18:48

0

More than likely the MachineName value that you are using is not a machine that can be found on the network. i would start with that and validate that you are able to connect to it.

answered Jan 24 '11 at 18:48

Mitchel Sellers

62,228
14
110
173

Calculating server uptime gives "The network path was not found"

4 Answers4

Linked