I have a set of machines that all run the same application, Microsoft Commerce Server 2002, when the CPU is checked using check_nt it returns the following:
CPU Load 4294967295% (60 min average) 4294967295% (120 min average)
Now, even the most inexperienced admin would know that my CPU was not running at 4294967295%. I think this has to do with a library that is being used to check the CPU utilization being replaced by a different, maybe older version when MSCS2002 was installed. The reason i say this is because up until the point MSCS2002 was installed the CPU reported correctly.
Anyone have any similar experiences?
Thanks,
D.S.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Double check the Windows client version that you are running via check_nt CLIENTVERSION.
provided it is nc_net, it uses the performance counter for the Category CPU, Instance _TOTAL to calculate CPU load. When a funny number like you specified occures, it usually indicates that there is only a single CPU instance without the named instances. thus changing the Startup variable for cpu_single resolves this particular issue. you can check the performance counter instances either using check_nc_net or via Administrative tools, performance.
please follow up and let us know if this resolves the issue.
Tony
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a set of machines that all run the same application, Microsoft Commerce Server 2002, when the CPU is checked using check_nt it returns the following:
CPU Load 4294967295% (60 min average) 4294967295% (120 min average)
Now, even the most inexperienced admin would know that my CPU was not running at 4294967295%. I think this has to do with a library that is being used to check the CPU utilization being replaced by a different, maybe older version when MSCS2002 was installed. The reason i say this is because up until the point MSCS2002 was installed the CPU reported correctly.
Anyone have any similar experiences?
Thanks,
D.S.
Hi,
Double check the Windows client version that you are running via check_nt CLIENTVERSION.
provided it is nc_net, it uses the performance counter for the Category CPU, Instance _TOTAL to calculate CPU load. When a funny number like you specified occures, it usually indicates that there is only a single CPU instance without the named instances. thus changing the Startup variable for cpu_single resolves this particular issue. you can check the performance counter instances either using check_nc_net or via Administrative tools, performance.
please follow up and let us know if this resolves the issue.
Tony