Goldmine 6.0

  • Thread starter Thread starter Scott
  • Start date Start date
S

Scott

This isnt so much a compatability issue, more of an
inconvience.

I have workstations that use XP pro with Office XP on
them. We currently use Goldmine to track clients and then
create letters to send out to them. Normally Goldmine
opens up Word to create the letters. Once I installed the
Microsoft Anti-spyware it would take at least a minute or
more for Goldmine to open up Word to create the letter.
When I disable the active protection, it goes back to
normal, taking only 5-10 seconds. Any ideas as to why
this slowdown would be caused??
 
Maybe you could identify which of the agents are causing
this (there are 59 separate ones); you can disable them
individually, so if you identify the one, you could still
have the protection of the others. It would also narrow
down the problem, possibly useful to MS if you report back.
 
This may be a good idea, however, I've seen at least one instance of a
performance related issue where disabling all the agents and checkpoints
didn't change the behavior, but disabling real time protection by using the
registry key in this KB article:

http://support.microsoft.com/kb/892375 End users may be prompted to allow or
block administrative actions that originate from a central management tool
after they install Windows AntiSpyware (Beta) on a computer that is managed
by Systems Management Server 2003

did. My conclusion is that the issue is with the code involved in the
ShellExecuteHooks.

This is one issue that I'd like to see re-tested with the new .509 build,
since it mentions performance as one area of change.
 
So then the obvious question would be, how does one narrow
down which if the 59 agents is causing the problem?

Any ideas appreciated.
 
I'd recommend the following triage:

1) use the KB article I posted to turn off real-time protection completely.

Observe whether that does the job.

2) If it does, turn it back on.

Then disable all three agents, and all checkpoints. I can't recall, but I
believe this is pretty easy to do in the UI. You might expect that this
would have the same effect as (1), but check.

If the issue is still there, don't worry about digging further. If you want
to avoid this symptom, you'll need to run without the real-time protection
in place, using (1) as the method of shutting it off.

Do be sure that you are running build '509 and have updated definitions to
5691.

3) the issue is gone when you disable all agents and checkpoints, you could
enable individual agents and all checkpoints under them, one by one, until
the symptom reappears.

If the symptom seems associated with, say, application checkpoints, disable
half of them, test, disable the other half, test. Among the half associated
with the problem do this again--disable half of those, test, the other half,
test. This should get you to the culpret in the least number of steps.
However, I suspect you will find the issue solved with step 1 and 2.
 
Back
Top