Yes, we had a problem that sounds similar, but I can't tell from your
description if it is the same. These were our symptoms:
* Problem occurs on Win95 only, never WinNT
* Occurs with ADSM V2 Win32 clients, or V3 clients up through PTF 3.
(We haven't seen the error with PTF 6 yet, but I'm not sure it can't still
happen..)
* Problem occurs when the ADSM incremental backup is actually running,
not just when the scheduler launches from the startup window.
* The message actually says "Error writing to the registry....." and
says you should restart the machine.
* It's a pretty scary message, however, if you just let that message
window sit there, you find that you can start and run other applications;
the ADSM backup continues OK to completion, and if you restart the machine,
there is never really any corruption.
If that matches your symptoms let me know, I have some suggestions.
> -----Original Message-----
> From: Moir,Betsy [SMTP:betsy.moir AT ABBOTT DOT COM]
> Sent: Monday, March 08, 1999 1:46 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: SMS and Registry Errors
>
> One of my customers is apparently installing(?) SMS and is having some
> problems with the registry being corrupted (see note below). Has anybody
> else seen this problem or have any suggestions as to whether or not ADSM
> executing from the startup file might be causing this? I've been running
> through the ADSM-L archives, but it's slow going.
>
> Thanks for any help or suggestions.
>
> ********************************************************************
> As you all know, we have had many of our SMS test clients experience
> Registry
> corruptions. One thing that I suspect may be conflicting and causing this
> error is ADSM launching at the same time as SMS. To try and isolate this
> problem, I have been removing ADSM from the Startup folder and placing on
> the
> desktop and asking users to manually start their back ups for a period of
> one
> week. Hopefully this trial period will help me isolate the problem. If any
> of
> you are working with complains of the registry corruption problem, please
> note if they are running ADSM from the startup.
> ******************************************************
|
