PDA

Visualizza versione completa : Problemi con SFC /scannow


Sbrez81
19-02-2004, 00.37.14
Ciao a tutti
Quando tento di eseguire il comando sfc /scannow mi appare l'errore:

Impossibile avviare l'analisi dei file di sistema protetti.
Il codice errore specifico è 0x000006ba (server RPC non disponibile)

Qualcuno ha un idea di quale sia il problema??????
Grazie a tutti

albe76
19-02-2004, 15.00.39
il problema sembra essere provocato dall'assenza di un certificato della Verisign.

dai un'occhiata qui:

http://support.microsoft.com/default.aspx?scid=kb;en-us;296241

Ciao ;)

Sbrez81
19-02-2004, 22.59.25
Grazie mille adesso lo provo poi ti faccio sapere

Sbrez81
25-02-2004, 00.21.02
Scusa il ritardo
Ho seguito le istruzioni. Mi sono scaracato il certificato dal sito microsoft il nome del file è clrupd.exe e ho provato a installarlo ma niente. Tra l'altro questo certificato scade l' 08/01/2004 e quindi ho provato a portare la data al 2003. Il certificato era apposto ma non partiva comunque, sempre lo stesso errore... Cosa può essere ancora??? Tanto per provare potresti allegarmi il tuo certificato ma non seguire le istruzioni che dicono loro perchè è un casino lo puoi fare anche da internet explorer. Vai su strumenti > opzioni internet > cotenuto > certificati > autorità di certificazioni fonti attendibili > seleziona NO LIABILITY ACCEPTED e fai esporta lascia il formato x.509.
Grazie di nuovo Ciao
:) :) :)

Sbrez81
26-02-2004, 23.23.24
Help me please
Qualche idea??????

nana_d
27-02-2004, 00.20.04
Guarda i log di sistema, che cosa ti dicono?

Sbrez81
27-02-2004, 22.52.03
Quali log di preciso???
Perchè ce ne sono un bel po'.....

nana_d
28-02-2004, 15.36.54
Allora sbrez ho trovato il tuo errore e fà riferimento all'errore KB296241 Windows File Protection May Not Start...

Tieniti forte, sai l'inglese?

Knowledge Base

Windows File Protection May Not StartPSS ID Number: 296241

Article Last Modified on 11/18/2003


--------------------------------------------------------------------------------
The information in this article applies to:


Microsoft Windows 2000 Server
Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Professional

--------------------------------------------------------------------------------

This article was previously published under Q296241
SYMPTOMS
When you log on to a Windows 2000-based computer, you may receive the following message from Windows File Protection:
Files that are required for Windows to run properly have been replaced by unrecognized versions. To maintain system stability, Windows must restore the original versions of these files.

Insert your Windows 2000 Server CD-ROM now.
When you insert the Windows 2000 CD-ROM, the message box closes.

When you examine the System event log, the following event may be logged:
Source: Windows File Protection
Event ID: 64033
Description: Windows File Protection could not be initialized. The specific error code is 0xc000000f.
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.
MORE INFORMATION
For additional information about Trusted Root certificates, click the article numbers below to view the articles in the Microsoft Knowledge Base:
293781 Trusted Root Certificates That Are Required by Windows 2000

222193 Description of the Windows 2000 Windows File Protection Feature

Sbrez81
29-02-2004, 12.46.03
Ciao
Questa soluzione me l'aveva gia proposta albe76 all'inizio della discussione e avevo gia provato a farla come ho scritto precedentemente ma senza successo..,
Qualcuno mi può allegare il proprio certificato "No Liability Accepted, (c)97 Versign, Inc." tanto per provare.
Se potessi evitare di formattare, considerando che sembra tutto funzionare, tranne che per questo problema ve ne sarei grato
Ciao e grazie