gcasDtServHolder window won't go away

  • Thread starter Thread starter jeff spencer
  • Start date Start date
J

jeff spencer

Sorry if this is a repost of someone elses, the search
function on this board gives me a System Error message.
Every time I switch my PC on, this little system tray
controller type window pops up in the centre of my screen
and will not go away. I assume it is part of the startup
procedure and instead of flashing by in a microsecond it
is just not closing at all.
Is there a tweak I can use to stop it appearing?
Is it safe to just close it? (seems to be - the system
tray icon disappears for a few seconds then returns)

Apart from that I'm having a very positive experience
with the app, automatic updates seem to be working and it
found some stuff I did not spot with Ad-aware, Bazooka
and SpyBlaster in combination.
In case it helps with the above problem, my startup
procedure also includes the Kerio Personal Firewall and
Norton AntiVirus.
 
Jeff - you are definitely seeing a bug. I don't have a clear fix that I
know will work in your situation, but I would recommend reinstalling
Microsoft Antispyware to see whether that might tweak something that is
causing the symptoms you see.

You could either uninstall and reinstall, via Control Panel, add or remove
programs, or you could also try, before that, control panel, add or remove
programs, Microsoft Antispyware, change, update.
 
Thanks for getting back to me Bill.

Using the Change option to update didn't get rid of it -
it was back there in the centre of the screen as soon as
the update finished. I have removed the program and will
reinstall the latest version available in the morning.
(I'll have to rerun a full scan and stuff, and its 2am
here now (Netherlands). I'll post my experiences and
anything else I can think of tomorrow. Anything I can
print out and send in to help the bugfixers?

Cheers and good night!
Jeff
 
Thanks for testing!

Your presentation of this bug is unique (as far as I've spotted) in that you
get this window, which should be invisible, and everything halts there--you
get no further presentation of the UI.

I'm sure there are folks at Microsoft who have some idea how this works, but
I don't. One source of clues might be the errors.log file in the directory
the program is installed in. I believe this is preserved even when you
uninstall, but I'm not certain. If this file is short, or you can delete
it, and then post the content from a single startup attempt, that might be
useful--I or some other user here might be able to suggest a a
fix--registering a DLL or OCX, for example, that might get the thing working
on your machine.

Of course, the real issue is why is it failing in the first place. The
general answer has consistently been "permissions". Some have found that
the DCOM service is not running, or has restrictive permissions set on it
somehow. In one case, someone found that reinstalling DAO got him past a UI
presentation-related issue. Some folks have found that installing to a
different directory (c:\msas, for example) has gotten them around some issue
with permissions under \program files.

So--there's a range of things people have described as fixing various issues
with installation or UI presentation after installation, but none of them
have presented with your precise symptoms, so I sure don't know which
direction to point you. And I'm not a developer. You may well know more
about how Windows works at least in a given area than I do--I'm here to help
manage the flow of things in the groups, but I'm a generalist, and there's a
good deal going on here that I don't understand the technical underpinnings
of.
 
Back
Top