G
Guest
Just in the last week we've had about five XP Professional SP1 systems start
getting this message at all domain logons only. (Local logons don't get the
error.) "One of the files containing the system's Registry data had to be
recovered by use of a log or alternate copy. The recovery was successful."
I found other forums suggesting "chkdsk /R" and memory checks. I did both,
but it didn't help. The only thing new in the last week was an update to the
"mssecure.cab" file used by SMS 2003. I completely removed SMS, but it
didn't help. We started using ScriptLogic a couple of months ago. Again I
removed ScriptLogic, but it didn't help. Because it only affects domain
logons, I removed the PC from the domain and then put it back into the
domain. It didn't help. I used a registry repair tool. It didn't help.
What steps can I take to isolate the cause of this problem? The MSDN
reference says just to "click OK" on the error message and that it is not a
problem and no further action is needed. It may not be a problem, but it
indicates to me that something is wrong when you get it every time. Again,
how can I isolate the cause of this problem and correct it? I'm afraid it is
going to spread to the hundreds of other Windows XP systems we have and I'm
not going to have an answer. Thank you.
getting this message at all domain logons only. (Local logons don't get the
error.) "One of the files containing the system's Registry data had to be
recovered by use of a log or alternate copy. The recovery was successful."
I found other forums suggesting "chkdsk /R" and memory checks. I did both,
but it didn't help. The only thing new in the last week was an update to the
"mssecure.cab" file used by SMS 2003. I completely removed SMS, but it
didn't help. We started using ScriptLogic a couple of months ago. Again I
removed ScriptLogic, but it didn't help. Because it only affects domain
logons, I removed the PC from the domain and then put it back into the
domain. It didn't help. I used a registry repair tool. It didn't help.
What steps can I take to isolate the cause of this problem? The MSDN
reference says just to "click OK" on the error message and that it is not a
problem and no further action is needed. It may not be a problem, but it
indicates to me that something is wrong when you get it every time. Again,
how can I isolate the cause of this problem and correct it? I'm afraid it is
going to spread to the hundreds of other Windows XP systems we have and I'm
not going to have an answer. Thank you.