YES!!!
We have had it happen numerous times:
* always on Win95, not WinNT
* always JUST AFTER the scheduled backup starts.
* never reproducible
* the backup continues and completes OK
* never really corrupts the registry, system is OK after
reboot.
We are running the AIX server at 2.5.13; We are running on 16MB token
ring, all clients use the Win95 IP stack.
I am sure upgrading the server won't help; this has to be in the client
somewhere.
I have never reported to IBM, because it happens to us so infrequently
(maybe once a month, out of about 150 Win95 desktops doing daily
backups) that first I wasn't really sure it was associated with ADSM.
And I really haven't been able to get a handle on it.
You seem to have it happen MUCH more often than we do.
Here's an idea: I suspect that it has something to do specifically with
Win95 since we've never seen it on WinNT.
I know that Win95 writes data out from memory to the registry files on
disk "periodically" (meaning you have no clue when it can happen). It
also writes the registry out immediately after a successful reboot.
The error message says "Windows encountered an error accessing the
system registry."
What if Win95 is trying to get exclusive control of one of those files
to update it, just at the same time ADSM is trying to read it to back it
up? Would that trigger the error?
If I could reproduce this frequently, I would try putting in an EXCLUDE
for the Win95 registry files. NOT that I would want to exclude them
regularly, but just to test the idea.
Does anybody else on the list know anything about the guts of Win95 and
its registry that would explain some of this?
Cookie, PLEASE LET US KNOW if you get anymore information!
> ----------
> From: Cookie Nguyen[SMTP:cnguyen AT mail.arco DOT com]
> Sent: Wednesday, February 25, 1998 11:09 AM
> To: ADSM-L AT vm.marist DOT edu
> Subject: ADSM 32-bit client/Registry problem
>
> I am curious to know if anyone has experienced the "Registry problem"
> pop-up screen from time to time on desktops running Win95?
>
> As of last week, we were on MVS ADSM V2 level 12 server and several of
> our
> Win95 clients occassionally experienced the "Registry problem". This
> sometimes caused the machine to freeze up and resulted in a reboot.
> Other
> times, users can ignore the message and go on without rebooting.
> However,
> in all occasions, the registry seems to be OK after each reboot
> (without
> any corruption noticed!). The contents of the message is as follows:
>
> "Windows encountered an error accessing the system registry. You
> should
> restore the registry now and restart your computer. If you ignore
> this
> error and shut down your system, you may lose data. Restoring the
> registry
> will replace the faulty registry with a known good backup copy.
> However,
> this backup copy may not contain all the information recently added to
> your
> system."
> And the option give: "Restore from Backup and Restart".....
>
> Our users started to see the above message "from time to time" and the
> messages always associated with their scheduled backup time. Of
> course,
> this doesn't mean that the scheduler was the reason, since we started
> to
> see the message during manual backup as well.
>
> Because of the nature of the problem, and not being able to recreate
> it on
> demand, so far it has been hard to determine whether ADSM is the
> reason!!!
> I have opened a record with IBM and was advised to bring the server,
> as
> well as the client code to the latest level to see whether or not the
> problem will disappear.
>
> Last weekend, 2/22, we have upgraded our MVS server to version 3 and
> yesterday began to test the new version 3 Win95 client (IP21169S).
> Looks
> like the new client is not the answer. Here's what we did:
>
> Closed all applications.
> Installed the new client (on top of the same directory path...the
> previous
> dsm.opt remained in tact). By the way, we used TCP/IP as our
> commmethod.
> Initiated the GUI Admin client (everything looked OK, minimized it).
> Initiated the GUI client backup (selected the backup option, and
> started to
> backup one of the local drives.
> White (4) was running, we started another GUI client backup. We
> selected
> the backup option and started testing the "Find file(s) to backup"
> using
> filter list....while this was going on, the "Registry problem" screen
> popped up. At this time, the initial backup screen appeared to be
> working
> still. We then click on the "Registry problem", and press the
> CNTL+ALT+DEL
> keys. The resulting screen showed the first item selected was
> NETBIOS? At
> this time, we noticed that if we minimized the screen which contained
> the
> output from the filtered selection list (the result from the second
> GUI
> backup client), it labeled was NETBIOS next to the ADSM backup logo.
> A few
> seconds after that, the machine was frozen and we had to reboot.
> After the reboot, we attempted to recreate the problem without any
> success!!!
>
> To sum it up:
> Since we've determined that the "Registry problem" pop-up screen
> appeared
> when ADSM was the only running application, we've more reason to
> believe
> that ADSM was the cause.
> With the above in mind, has anyone seen anything like this?
>
>
> Cookie Nguyen
> ARCO
> cnguyen AT mail.arco DOT com
>
|
