Computing.Net > Forums > Windows 2000 > sfc /scannow error - RPC server

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

sfc /scannow error - RPC server

Reply to Message Icon

Name: crazyboy
Date: August 30, 2006 at 06:44:56 Pacific
OS: Windows 2000 Professional
CPU/Ram: P2 256KB
Product: Dell Latitude
Comment:

Hello

I have tried running sfc /scannow on my Win 2000 Prof laptop but it will not work. I get a box flash briefly and then nothing. When I run cmd and re-type I get the follwoing: -

SFC /SCANNOW in a command prompt window gives:
Windows File Protection could not initiate a scan..

The specific error code is 0x000006ba [The RPC server is unavailable']

I've looked at Q296241 Windows File Protection May Not Start on Microsoft support which recommends getting a Verisign certificate from another PC, which I have now done. However, i'm still getting the same problem. I've checked that the RPC is running in the services folder (Administrative Tools), which confirms it is enabled!

Any help would be appreciated. Many thanks



Sponsored Link
Ads by Google

Response Number 1
Name: ccfrank
Date: September 8, 2006 at 10:43:40 Pacific
Reply:

do you go to start ... run ... type cmd .. enter .. then sfc /scannow?

best of luck Frank :


0
Reply to Message Icon

Related Posts

See More


power managament Trouble installing AVG



Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows 2000 Forum Home


Sponsored links

Ads by Google


Results for: sfc /scannow error - RPC server

SFC 'RPC server is unavailable' www.computing.net/answers/windows-2000/sfc-rpc-server-is-unavailable/58725.html

Net time + RPC server error www.computing.net/answers/windows-2000/net-time-rpc-server-error/41670.html

RPC server error message www.computing.net/answers/windows-2000/rpc-server-error-message/43726.html