Hi guys,
Thanks for taking the time to post.
UPDATE: Problem seems to be with KB968389, not the others listed.
I should firstly note that I'm fairly sure the problem is resolved;
just posting here to find out whether anybody else had the same problem
or not. If you guys see a whole bunch of 'me too' (or not!) then I guess we'll know.
wabbit wrote:I'm not in front of my MS machine right now, but I know it is fully up-to-date with all the XP patches/updates (whether or not those specific KBs are installed?); when I left home this morning MS Pro9 w/QC was running normally.
Can you see whether you have the updates in the subject and/or KB968389 installed? Control Panel -> Add/Remove -> select 'Show Updates' checkbox, look for IDs.
wabbit wrote:
Do you get any error messages?
* Equis Data Server Initialization
Connecting to data vendor; please wait.
* EQDATSRV
Error enabling client interface object
The Equis Data Server will terminate when this message is cleared.
* EQDATSRV
Unable to initialize client interface object
The Equis Data Server will terminate when this message is cleared.
No error messages apart from the one listed; with update KB968389 installed EQDATSRV.exe will not start/run on my machine (and therefore MS cannot get data updates). With it removed, works fine. Tested install/remove a few times (not really going to spend any further time on it; this is really just a heads-up for other forum users that may or may not warrant further investigation).
Had to set automatic updates to -download only and prompt to install- in order to be able to deselect/permanently disable those specific updates, then reset to automatic.
Justin wrote:
Also, are you using MetaStock Pro for eSignal or QuoteCenter?
MS ProFX and QuoteCenter
Justin wrote:
I
installed one of the KB's you mentioned on my XP 32-bit machine here
and I launched both MetaStock Pro for eSignal and MetaStock Pro for
QuoteCenter.
With respect to the KBs: it may be that I supplied the wrong number in the subject (I uninstalled _all_ the updates that were done on the day it stopped working; then put them back one by one till I saw the problem).
Justin wrote:
I also wonder if possibly one of these KB's is
enabling something on your PC (like Windows Defender or Windows
Firewall) which might normally be disabled. I know I have seen updates
turn the Windows Firewall back on.
It's possible but I don't think it's related:
a) I have both those things on always; and
b) the problem seems to disappear with the uninstall of the related Update.
Regards,
Saliya