MowGreen:
Well, we now have a count up to 12 systems INCLUDING a W2003 advanced
Server. We have not yet been successful at "cleaning" or repairing any of
them, we have backed up the Profiles, other key data files etc. On several,
the client could not locate the original CD's so we booted with Bart and ran
a Belarc to record the key data, then reformatted and re-installed ALL and
put the Profile back in....that worked and maybe 5 will be done today with 2
techs on it...not good.
Here are some of today's findings and specuations:
1. Registry corruption in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\R
oot\LEGACY XXX
We have searched these and found NO corruption at all, not to say its not
there, we have not found it.
2. Registry restores suggested by MWTI...
Escan did create zip files of these for 1 system we have here and when we
Import the HKLMRT.reg, HKLMSY.reg, or HKLMSW.reg they import, but do not
complete both in normal boot and Safe mode.
3. Services not started properly
We manually started every service possible and still no help. We clearly see
many Auto services that are not started that should be and cant get them
going since we cant see properties for their dependencies...
4. Msft Support down to an XP "repair" install
We started this about 2 hours ago on a portable after backing it up. This is
not a "recover" and its stuck with 28 mins to go for the last hour, so not
optimistic on this working.
5. MWTI escan help
The ONLY common thing with ALL systems was Updates set to Auto and Escan A/V
installed and active when the update took place.
6. Last Updates on ALL systems appear to be KB950749 Jet update on 05/14/08
and uninstalling this does not remove it on our system, but MWTI says this
did help another person with same symptoms.
Here are the answers to your questions:
1. @ Bob: Was Escan actively monitoring the systems when SP3 was applied ?
Yes, we assume it was active during the Auto Update process
2. > Were the issues occurring after the application of SP3 or, did the
> issues start occurring after the installation of KB947864?
We believe MWTI was mislead by KB947864, this is showing 04/09/08 long
before the problems. Also, SP3 shows no evidence of being installed at all
on any systems, so we have been "presuming" that it was auto installed, and
that may be true, but we do know
KB950749 WAS installed 05/14/08 and thats when the systems had problems. And
with the W2003 Server now in,
we are thinking it may NOT be SP3 but something else...like 950749 and Escan
.....
3. > Was IE7 installed PRIOR to SP3 being applied ?
> Can you attach or post the reg file MW provided ?
We know that IE 7 was installed on these system well ahead of SP3. The
HKLMSY.reg files are specific to each system and I have them from 1 of the
systems, its 14MB unzipped....
Thanks for the help!!!
--
Bob Aubry
Main Street Software, Inc.
email
boba@mssinc.com
voice (717) 898-2946
Sage/ACCPAC Manufacturing and Job Cost Certified
"MowGreen [MVP]" <mowgreen@nowandzen.com> wrote in message
news:%23s$sexpuIHA.2292@TK2MSFTNGP05.phx.gbl...
> The corrupted reg entries were caused by NIS or other Norton 'products'
> actively monitoring the system during the application of SP3.
>
> Bob clearly states that the installed AV is Escan. The registry subkey you
> posted is clearly related to Norton's CCProxy.
> What makes you think the solution to the 'Norton' issue is applicable here
> since Bob also stated that MicroWorld advised him to uninstall
> KB947864 ?
>
> @ Bob: Was Escan actively monitoring the systems when SP3 was applied ?
>
> Were the issues occurring after the application of SP3 or, did the issues
> start occurring after the installation of KB947864?
>
> Was IE7 installed PRIOR to SP3 being applied ?
> Can you attach or post the reg file MW provided ?
>
>
> MowGreen [MVP 2003-2008]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
>
>
> Fazal wrote:
>
>> Hello Bob
>>
>>
>> I had seen an almost similar problem when I pushed SP3 thru SMS...My
>> device manger went blank..,My IE would crash though I cud cut n
>> paste...
>>
>> Though I allready posted the solution in this forum too and it did work
>> fine for the others tooo...I"ll paste it again here and u see if it
>> helps..We need to delete the corrupted registries..
>>
>> Start>Run>Regedit
>>
>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\R oot\LEGACY_CCPROXY
>>
>> All the corrupt entries (begining with $%& ) Make sure you take a backup
>> of ur keys before proceeding and if
>> possible compare it with a working XP Machine...
>>
>> If this is not the case ..try downloading regmon from sysinternals.com
>> and run it..try running ur failed applications to see the registry they
>> are going thru...and compare them with a working machine..
>>
>>
>> Hope this works!!
>>
>>
>> Regards
>>
>>
>> Fazal
>>