G
Guest
Can anyone advise on following issue
I work as part of an infrastructure team which manages a set of COM DLL's
that are
distributed across the enterprise onto file servers, which are then shared
by all clients. Problem we have is that since our move to XP, we have
started getting this error. I know how to correct the problem, by
unregistering and registering the COM dll in question, but am unclear as to
what part of the registry entry is missing or corrupt. What confuses the
issue is that this will happen seamingly at randon even though the files in
question have not been changed. The error can effect individual boxes that
worled previously (where perhaps 1000+ pc's are using the file with no probs)
I am going to examine the registry of a box that has this prob, next time it
happens, but I was wondering if XP had introduced a subtle change or if
anyone else had investigated this already.
I work as part of an infrastructure team which manages a set of COM DLL's
that are
distributed across the enterprise onto file servers, which are then shared
by all clients. Problem we have is that since our move to XP, we have
started getting this error. I know how to correct the problem, by
unregistering and registering the COM dll in question, but am unclear as to
what part of the registry entry is missing or corrupt. What confuses the
issue is that this will happen seamingly at randon even though the files in
question have not been changed. The error can effect individual boxes that
worled previously (where perhaps 1000+ pc's are using the file with no probs)
I am going to examine the registry of a box that has this prob, next time it
happens, but I was wondering if XP had introduced a subtle change or if
anyone else had investigated this already.