Y2K Patch

Y2K Patch

Post by Robbin D » Fri, 10 Dec 1999 04:00:00



Hello, has anyone gotten errors when installing the SCO OSR 5.2/5.4 patch:

The Error when I try to install the patch from the software manager
(custom), first installing the software manager, then the Y2K patch:

"\Patch "sco:tcp OSS601a.tcp210 can not be applied to "SCO: tcp 2.1.0Eb".
Component is in an invalid state."  (When I go into Details...), this
appears:

"Component "SCO:tcp.2.1.0Eb" is corrupt, and therefore cannot be patched."

(The same occured with unixds):

"\Patch "sco:unixds OSS601a.unixds 5101 can not be applied to "SCO: tcp
2.1.0Eb".  Component is in an invalid state."  (When I go into Details...),
this appears:

"Component "SCO:unixds 5.1.0Ha" is corrupt, and therefore cannot be
patched."

Can you please help me, or if not could you forward this to the appropriate
party?

All suggestions/ideas are greatly appreciated.

Thank you very much.

 
 
 

Y2K Patch

Post by Bob Col » Sat, 11 Dec 1999 04:00:00



> Hello, has anyone gotten errors when installing the SCO OSR 5.2/5.4 patch:

> The Error when I try to install the patch from the software manager
> (custom), first installing the software manager, then the Y2K patch:

> "\Patch "sco:tcp OSS601a.tcp210 can not be applied to "SCO: tcp 2.1.0Eb".
> Component is in an invalid state."  (When I go into Details...), this
> appears:

> "Component "SCO:tcp.2.1.0Eb" is corrupt, and therefore cannot be patched."

> (The same occured with unixds):

> "\Patch "sco:unixds OSS601a.unixds 5101 can not be applied to "SCO: tcp
> 2.1.0Eb".  Component is in an invalid state."  (When I go into Details...),
> this appears:

> "Component "SCO:unixds 5.1.0Ha" is corrupt, and therefore cannot be
> patched."

> Can you please help me, or if not could you forward this to the appropriate
> party?

> All suggestions/ideas are greatly appreciated.

> Thank you very much.

Check ta 109370 at http://www.sco.com/ta/. It worked when one of our
customers cancelled
the oss601a install when they got a "Verification error" and then called
us,
(rather than call us before cancelling it).