SRVR2003 R2 Quota / File screening errors

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Help!

Windows Server 2003 Enterprise Edition R2 (via in place upgrade).

F:\ drive holds around 1700 home directories.

Last week we had a server lockup that required the power to be pulled on the
server. On checking I found that NTFS permissions on user folders had been
corrupted. Not all but maybe a hundred or so.

Some users had no rights to their own files, others had rights to some files
but not others. On some folders the administrator had no access.

I ran a script to reset NTFS permissions but got access denied on some
folders. Had to take ownership of all files and folders and ran script
again. Returned ownership to users.

Went to setup File Screening and got an "unexpected error occured please see
the event log" which includes the following entries.

An unexpected error occurred in the File Server Resource Manager MMC snap-in
at Microsoft.Storage.SrmMmc.NewFileScreenDialog.CheckInputValues()
at Microsoft.Storage.SrmMmc.NewFileScreenDialog.UpdateFileScreenObject()
at Microsoft.Storage.SrmMmc.NewFileScreenDialog.OnCreateButtonClicked(Object
sender, EventArgs eventArgs)
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
at Microsoft.Storage.ISrmDataScreenManager.GetDataScreen(String strPath)
at Microsoft.Storage.SrmMmc.NewFileScreenDialog.CheckInputValues()

\\?\Volume{7a452e38-5da1-4a0f-ad96-0a0d836edd96}\System Volume
Information\SRM\quota.xml,
Operation:
Getting file screen object on folder 'F:\'..

I can set file screens & quotas on any other volume on the same server
without these errors being logged. When I connect remotely from another R2
server I get exactly the same error when creating the file screen / quota
policy on the F: drive. I have removed the R2 components and re installed. I
have reinstalled R2 CD 2.
I am presuming that their is a registry entry, file or other object relating
to the F volume that is preventing files screens & quotas from working on
this drive. Other than reformatting and re-installing windows which I do not
wish to do at the moment can anyone recommend a way to resolve this error?
Are there some volume specific registry entries or files that I could edit?
We were wanting to use File Screening to prevent students saving executable
files in their home folders. (UK Secondary school)
Thanks,
Andy.
 
Registry corruption might have occured.

Please try:

chkdsk f: /f

If the above doens't fix, please recreate the registry (backup before
doing!!)

This can be done by creating a series of repair floppies for Windows 2000.

Download the Windows XP Pro Setup disks creation utility (4287KB):
http://www.microsoft.com/downloads/...familyid=55820EDB-5039-4955-BCB7-4FED408EA73F

Download the Windows 2000 Setup disks Registry repair addition (93KB):
http://www.microsoft.com/downloads/...01-2c68-4de8-9229-ca494362419c&displaylang=en
The simple instructions are on the download page.

You will need 6 blank floppy disks.

Create the 6 XP Setup floppies, but leave the last one in the drive after it
has been created.
Run the downloaded Windows 2000 Registry repair addition file to replace and
add two files to this floppy that are particular to Windows 2000.

Use these 6 floppies to start Windows 2000.
 
Jabez Gan said:
Registry corruption might have occured.

Please try:

chkdsk f: /f

If the above doens't fix, please recreate the registry (backup before
doing!!)

This can be done by creating a series of repair floppies for Windows 2000.

Download the Windows XP Pro Setup disks creation utility (4287KB):
http://www.microsoft.com/downloads/...familyid=55820EDB-5039-4955-BCB7-4FED408EA73F

Download the Windows 2000 Setup disks Registry repair addition (93KB):
http://www.microsoft.com/downloads/...01-2c68-4de8-9229-ca494362419c&displaylang=en
The simple instructions are on the download page.

You will need 6 blank floppy disks.

Create the 6 XP Setup floppies, but leave the last one in the drive after
it
has been created.
Run the downloaded Windows 2000 Registry repair addition file to replace
and
add two files to this floppy that are particular to Windows 2000.

Use these 6 floppies to start Windows 2000.
Click to expand...

CHKDSK /F running as we speak. probably going to take some time to complete.

Worried about using XP PRO / 2000 setup disks / registry repair tools
especially as the links warn that some registry loss may result. Are there
not specific keys within the registry that I could manually edit to resove
the problems that I am experiencing?

This is our main fileserver and even with backups the prospect of any down
time is a real worry.

Can you provide some context to your advice to run a registry repair?

Thanks,

Andy.
 
Well, that tool will just try to rebuild the corrupted registry, but whether
it will fix your issue, it's another thing. What i would do, is to take down
the server evening when nobody is using the server and try using the tool to
fix the problems. If it doesn't work or it creates more trouble, just
restore back the registry, reboot and everything should be the same.

Update us if chkdsk works. :)

--
Jabez Gan [MVP]
Microsoft MVP: Windows Server
http://www.blizhosting.com
MSBLOG: http://msblog.resdev.net
 
CHKDSK /F running as we speak. probably going to take some time to
complete.

Worried about using XP PRO / 2000 setup disks / registry repair tools
especially as the links warn that some registry loss may result. Are there
not specific keys within the registry that I could manually edit to resove
the problems that I am experiencing?

This is our main fileserver and even with backups the prospect of any down
time is a real worry.

Can you provide some context to your advice to run a registry repair?

Thanks,

Andy.
Click to expand...

chkdsk /f completed

Error remains.is there any other method I could try other than via the
recovery disks?

Thanks

Andy

PS. Please don't interpret me as being ungrateful or not trusting what I am
told. I am very grateful for all the help you have provided but you will
understand that if it's a choice between having file screening filters or
the risk of loosing my main failserver during school time when I don't have
a backup server. Well I am playing safe. If I could find out which keys are
affected I could try a manual repair.

I can see this going to PSS


Thanks,

Andy.
 
For anyone else that faces this issue in the future here is how I fixed it.

The volume that I wished to apply file screens to had caused a couple of
events to be logged 55 ntfs. After running chkdisk /f and chkdisk /x I was
still seeing 55 errors and still unable to put file screens or quotas in
place.

So, I uninstalled the R2 components using add/remove windows components.

Then I opened the folder I wished to screen and configured explorer so that
I could see system folders and files.

I saw a new folder System Volume Information. I add to give the admin full
rights before I could view the contents of this folder.

Inside I found a folder called SRM which contained all the settings,
policies and quotas that had been in place on this volume before (but were
now not working and preventing new screens being setup).

I backed up the SRM folder and then deleted it.

Next step was to re-install the RS components and allow the server to
restart.

Fire up the MMC console and configured a file screen policy without any
errors and it works!

So, unless someone else tells me different problem solved!

Andy.
 
Back
Top