Please help

[Guest]

I have just installed a 2000 server and I deleted the everyone permission off of my c drive and I forgot to put the system permission on first, I am now locked out and now when I reboot I get a c00021a error, I have tried the recovery console and still no luck
Thanks
Dave

 

[Pegasus]

I have just installed a 2000 server and I deleted the everyone permission

off of my c drive and I forgot to put the system permission on first, I am
now locked out and now when I reboot I get a c00021a error, I have tried the
recovery console and still no luck

Thanks
Dave

You could try temporarily installing the server disk
as a slave disk in some Win2000/XP PC, then
allowing everybody full access.

You would probably get many more responses if
you took the trouble of composing a meaningful
Subject line, e.g. "Deleted all NTFS permissions".

 

[Guest]

Sorry, first post in this forum.
My problem with taking the drives out is they are in a raid 5 config and I don't have anything else to run the drives in.

 

[Pegasus]

In such cases I whip out my Bart WinXP PE CD (www.bootdisk.com).
You can make your own if you have
- A CD burner
- A WinXP Professional CD (no licence number required)

This CD lets you boot into a WinXP session, purely off the CD,
with no files required on the hard disk. You could then try to
run cacls.exe from it. Note that I have never tried this. I can
try it later today, in about two hours from now.

Sorry, first post in this forum.
My problem with taking the drives out is they are in a raid 5 config and I

don't have anything else to run the drives in.

 

[Guest]

Well, I have tried several times to try and create the cd but it keeps giving me this error when I do

bin/mkisofs.exe returned an error....
'and' is not recognized as an internal or external command,
operable program or batch file
bcd: aborting, removing iso file

I have tried doing many searches and I cannot figure out what I am doing wrong.

 

[Guest]

I figured it out, I am now trying to boot to it.

 

[Pegasus]

The Bart CD could have been a quick way out of your dilemma.
Seeing that you have problems creating it, here are two more
suggestions, arranged in order of preference.

a) Spare disk method
- Install a spare hard disk (4 GBytes will do)
- Disconnect your RAID array
- Boot with a Win98 boot disk from www.bootdisk.com
- Partition & format the spare disk
- Reboot from the Win98 boot disk
- Run this command: sys c:
- Reboot from the hard disk. Does it boot to a DOS prompt?
If no, make sure that the disk is set to "active", and try again.
- Reconnect your RAID array
- Reboot from the hard disk. Does it boot to a DOS prompt?
If no, can you force the machine to boot from your spare disk?
- Pop in a Win2000 CD.
- Install Win2000 to the spare disk.
- Boot into Win2000
- Reset your permissions

b) RAID method
Boot from a Win98 boot disk, then install Win2000 in
some folder other than c:\winnt. When Win2000 is up and
running, reset all permissions.

 

[Guest]

I got the CD Burned, I am now in the process of changing the permissions

 

[Guest]

I got the CD to burn, I am now in the process of changing the permissions.

 

[Pegasus]

Great! Please post the result.

I got the CD to burn, I am now in the process of changing the permissions.

 

[Guest]

I was able to change permissions and able to get back into the drive, but it is still giving me the c000021a error on bootup. My guess is that since it could not read it earlier something has been messed up, I have read up on how to fix this problem but how do you install a service pack if you cannot even boot into it. I have tried safe mode and that will not let me in either.

 

[Pegasus]

I assume you're referring to KB330303. If so then I agree: It's hard to
apply the latest service pack when you cannot log on.

If Terminal Server is running on the machine then you may be able to
log on to it by using Remote Desktop. The client is freely available
at http://support.microsoft.com/?id=306626.

Depending on your time frame I now suggest one of the following
courses of action:
- If time is short: Rebuild the server
- If you can afford to, create a new post in
microsoft.public.windows.server.general.
This would be a far more appropriate group than this one.

To protect yourself from this sort of accident, consider using your
Bart CD to create a zip file of drive C: once every two hours while
you're building up the machine. Use the -R -S -! switches. You could
then quickly restore an installation that's gone bad. Note that the
method only works if you use drive C: for nothing but the OS and the
apps. The data must reside elsewhere.

I was able to change permissions and able to get back into the drive, but

it is still giving me the c000021a error on bootup. My guess is that since
it could not read it earlier something has been messed up, I have read up on
how to fix this problem but how do you install a service pack if you cannot
even boot into it. I have tried safe mode and that will not let me in
either.

 

[Guest]

First, I want to thank you for all your help.

I am currently trying a parallel install to see if I can reset there, I should know here in a little while.

 

[Guest]

It worked, I am back up and running. Thankyou for your time and effort.

 

[Pegasus]

I'm curious. How did a parallel installation resolve the
c000021a error?

 

[William W. Plummer]

I'm curious. How did a parallel installation resolve the
c000021a error?




should know here in a little while.


drive, but


up on


permission on


error, I

I tackled this situation in the past. You need to know about "dir /q"
to a CMD box. This displays the file or directory owner. Only the
owner can change protections. The owner of most system files is
BULTIN\Administrators . Your system cannot start unless that is true.

 

[jay somerset]

On Sun, 01 Aug 2004 18:08:58 GMT, "William W. Plummer"

[[[ SNIP ]]]

I tackled this situation in the past. You need to know about "dir /q"
to a CMD box. This displays the file or directory owner. Only the
owner can change protections. The owner of most system files is
BULTIN\Administrators . Your system cannot start unless that is true.

That's strange -- EVERYONE is the "owner" of all files on most systems
I have ever looked at with DIR /Q. BULTIN\Administrators sounds like
a local peculiarity of your system

 

[Gary Smith]

That's strange -- EVERYONE is the "owner" of all files on most systems
I have ever looked at with DIR /Q. BULTIN\Administrators sounds like
a local peculiarity of your system

On my system, BUILTIN\Administrators is the owner of all files created by
users in the Administrators group. Files created by non-Administrator
users are owned by the creator's username.