SQLH2 Perf Loader error

Last Post 08 Dec 2009 01:49 PM by jelong. 2 Replies.
AddThis - Bookmarking and Sharing Button
Author Messages
MPatel1
New Member
New Member

--
20 Dec 2004 08:51 AM
Currently I am running Pref collector on three servers. Looks like it is collecting the perf data in text files on all servers. When I am tring to run SQLH2 so that it will put perf data into repository, but I am getting following error on Perf counter loader (H2Log.txt)

12/20/2004 11:19:50 AM Status: Starting Perf Loader
12/20/2004 11:19:50 AM INFO: Perf host_id = 2
12/20/2004 11:19:50 AM INFO: Lock aquired: pid = 1
12/20/2004 11:19:50 AM INFO: Lock released: pid = 1
12/20/2004 11:19:50 AM INFO: Perf host_id = 3
12/20/2004 11:19:50 AM INFO: Lock aquired: pid = 1
12/20/2004 11:19:51 AM ERROR: The network path was not found.

12/20/2004 11:19:51 AM INFO: Perf host_id = 4
12/20/2004 11:19:51 AM INFO: Lock aquired: pid = 1
12/20/2004 11:19:51 AM ERROR: The network path was not found.

12/20/2004 11:19:51 AM WARNING: Errors were encountered processing PerfProviders
12/20/2004 11:19:51 AM Status: Perf Loader finished

How I can fix the above error.

Thanks for your help in advance.
cityofcorvallis
New Member
New Member

--
11 Feb 2005 08:07 AM
I believe that MS intended the PerfCollector service to run on a single machine and simply harvest the perf counter data from the subscription or client machines. We have the Perfcollector service running on our mangement server and recording the data from the client servers to a local pf text file. Then it has no trouble getting the data into the database.

When I first installed SQLH2 I had thought that I needed to run the perfCollector service on each server I wanted to track. But then I realized it's designed so you don't install anything on the target server. The PerfCollector service account must have authority to Profile system performance and Profile single process.

So if a similar setup would work in your environment you might give it a try. Just remember to modify the PerfCollector config xml file to add in the other target servers and then stop and start the service. Also keep in mind that the PerfCollector service can log extensively to the Application event log. I have found that to be a handy place to troubleshoot it as well. I've also had great response from the e-mail address listed in the deployment guides.

Good luck!
jelong
New Member
New Member

--
08 Dec 2009 01:49 PM
I fixed the "Network path was not found" error by starting "remote registry service" in the target server.
I found that this error used to occur when SQLH2 tried to access registry and failed.

Go and check the target server's remote registry service.


Acceptable Use Policy
---