Ghost Solution Suite

We are currently going through an exercise of installing Ghost Solution Suite .2266 on various Windows 2003 Servers across the estate along with a few other products. On some of these servers Perfmon is now showing 2 instances of Memory Performance Counters. Each of these instances point to the same set of counters and residing in the instance is Ghost Solution Suite. It is therefore GSS that's being blamed for the issue.

Does anyone know any history of GSS causing this type of issue as currently the rollout of GSS has been put on hold.

Hi,

I dont see 2 instances of Memory Performance Counters when installed GSS 2.5.1 build 2266. Can you please provide the detailed step to see / investigate this problem? Did you upgrade the GSS from previous version or it was fresh install?

Perhaps I badly worded it. When adding Performace Counters in PERFMON there are 2 Memory Performace Objects listed in the left hand window of the screen shot (There should only be one). On selecting either of the two memory objects in the left hand window, an single instance of Symantec Ghost is seen in the right hand window. Investigation shows that the instance in each memory counter is the same single instance running on the machine. The issue therefore is that there are 2 Performance Objects showing as this gives issues to monitoring software.

GSS has not ever been installed before on the affected servers and hence it was a fresh install. Of the 13 Servers that the product has been installed on, 8 are exhibiting this problem and 5 are not.

Internally to the GSS console it embeds a run-time edition of SQLAnywhere; the SQLAnywhere database exposes a number of internal performance counters to Perfmon, and these are registered as a consequence of installing the SQLAnywhere run-time.

Installation of SQLAnywhere may expose counters but I would not expect it to cause duplication of an existing memory object. If this has caused my issue is there a solution to stop it except by not installing GSS?

These are definitely not duplicates of an existing object; it's merely that the performance counter instances exposed by SQLAnywhere happen to appear to be filed under that performance object type by Perfmon.

If you're determined to suppress the SQLAnywhere performance counters even though there is really nothing to be gained from doing so, you can do this by removing the associated registry keys which register the SQLAnywhere performance DLL for client applications like Perfmon to load: see http://support.microsoft.com/kb/152513 to learn how Perfmon works.

Specifically, Performance Counter extension DLLs are registered under registry paths of this form:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\service name\Performance

If you remove the entry corresponding to the SQLAnywhere product, then you should be able to prevent Perfmon loading the client extension and seeing those counters.