Harry
06-12-2004, 03:23 AM
This is incredible. I just went through a rigamarole of about 50 steps to fix one lousy problem. At least now maybe I can get some bad files restored but wow what a list of instructions to follow. I wouldn't even know where to begin without these instructions.
When you attempt to use the sfc /scannow command, the command may not work, and you may receive the following error message:
Windows File Protection could not be initiate a scan of protected system files. The specific code is 0x000006ba [The RPC Server is unavailable.].
CAUSE
This behavior can occur if the certificate for Verisign time stamping has been removed from the computer. This certificate is listed as: "Issued To: No Liability Accepted, (c)97 Versign, Inc.".
RESOLUTION
To resolve this behavior, the certificate needs to be restored to the original location. You need to export the certificate from a Windows 2000-based computer:
Locate a Windows 2000-based computer.
Click Start, and then click Run.
In the Open box, type: MMC.
When Microsoft Management Console (MMC) is displayed, click Console, and then click Add/Remove Snap-in.
On the Add/Remove window, click Add.
When the list of available snap-ins are displayed, click Certificates, and then click Add.
Click Computer Account.
Click Next.
Click Local Computer, and then click Finish.
Click Close, and then click OK to close out the Add/Remove Snap-in window.
Under Console Root, double-click Certificates (Local Computer).
Double-click Trusted Root Certificate Authorities, and then double-click Certificates.
In the right pane, the installed certificates are displayed. Scroll down the list until you locate the No Liability Accepted certificate.
Right-click this certificate, click All Tasks, and then click Export.
On the Export Wizard, click Next, click DER encoded Library X.509, and then click Next.
In the File name box, enter a file name to save the file (for example, C:\Cert). A .cer extension is added to the file name.
Transfer this file to the computer that is receiving the error message.
When the file is transferred to the computer that is receiving the error message, use the following steps to import the file:
Click Start, and then click Run.
In the Open box, type: MMC.
When the MMC starts, click Console, and then click Add/Remove Snap-in.
On the Add/Remove Window, click Add.
When the list of available snap-ins are displayed, click Certificates, and then click Add.
Click Computer Account.
Click Next.
Click Local Computer, and then click Finish.
Click Close, and then click OK to close out the Add/Remove Snap-In window.
Under Console Root, double-click Certificates (Local Computer).
Right-click Trusted Root Certificate Authorities, click All Tasks, and then click Import.
On the wizard, click Next, and then locate the file that you transferred from the other computer. (You may have to change the "Files of Type" field to display the X.509 certificates.)
When the file is selected, click Next.
Place the certificate in the Trusted Root Certificate Authorities Store, and then click Next.
Click Finish. A dialog box is displayed that indicates if the import operation had been successful or not.
When the certificate has been transferred, restart the computer, and then observe if the behavior is resolved.
When you attempt to use the sfc /scannow command, the command may not work, and you may receive the following error message:
Windows File Protection could not be initiate a scan of protected system files. The specific code is 0x000006ba [The RPC Server is unavailable.].
CAUSE
This behavior can occur if the certificate for Verisign time stamping has been removed from the computer. This certificate is listed as: "Issued To: No Liability Accepted, (c)97 Versign, Inc.".
RESOLUTION
To resolve this behavior, the certificate needs to be restored to the original location. You need to export the certificate from a Windows 2000-based computer:
Locate a Windows 2000-based computer.
Click Start, and then click Run.
In the Open box, type: MMC.
When Microsoft Management Console (MMC) is displayed, click Console, and then click Add/Remove Snap-in.
On the Add/Remove window, click Add.
When the list of available snap-ins are displayed, click Certificates, and then click Add.
Click Computer Account.
Click Next.
Click Local Computer, and then click Finish.
Click Close, and then click OK to close out the Add/Remove Snap-in window.
Under Console Root, double-click Certificates (Local Computer).
Double-click Trusted Root Certificate Authorities, and then double-click Certificates.
In the right pane, the installed certificates are displayed. Scroll down the list until you locate the No Liability Accepted certificate.
Right-click this certificate, click All Tasks, and then click Export.
On the Export Wizard, click Next, click DER encoded Library X.509, and then click Next.
In the File name box, enter a file name to save the file (for example, C:\Cert). A .cer extension is added to the file name.
Transfer this file to the computer that is receiving the error message.
When the file is transferred to the computer that is receiving the error message, use the following steps to import the file:
Click Start, and then click Run.
In the Open box, type: MMC.
When the MMC starts, click Console, and then click Add/Remove Snap-in.
On the Add/Remove Window, click Add.
When the list of available snap-ins are displayed, click Certificates, and then click Add.
Click Computer Account.
Click Next.
Click Local Computer, and then click Finish.
Click Close, and then click OK to close out the Add/Remove Snap-In window.
Under Console Root, double-click Certificates (Local Computer).
Right-click Trusted Root Certificate Authorities, click All Tasks, and then click Import.
On the wizard, click Next, and then locate the file that you transferred from the other computer. (You may have to change the "Files of Type" field to display the X.509 certificates.)
When the file is selected, click Next.
Place the certificate in the Trusted Root Certificate Authorities Store, and then click Next.
Click Finish. A dialog box is displayed that indicates if the import operation had been successful or not.
When the certificate has been transferred, restart the computer, and then observe if the behavior is resolved.