"Insufficient system resources..." msg on Add Permissions

[pvanos]

On a NT4 SP6 server, for any file going into Properties > Tab Security, button [Permissions]: as soon as I click on the [Add...] button, I obtain following message :

Windows NT
X Insufficient system resources exist to complete the requested service.
[OK]

In other words, I cannot change the permissions for any of the files.
The server has 128MB RAM and a PII-350MHz, and used to run a lot more services than it does now.

The funny thing is after rebooting the server, the problem is solved for a while, until at a certain point the permission problem is back again.

Before a demoted it from PDC to BDC, it also generated a similar problem when opening USRMGR. Message showing up mentioning not enough resources and suggesting to select a different domain. But since the server is demoted to BDC, the USRMGR runs fine.

Any suggestions ?
Paul

 

[Marcs41]

128? Start adding memory FAST.
You are lucky it ran this long!

Marc
_{If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all. Please specify details.
Free Tip: The F1 Key does NOT destroy your PC!}

 

[pvanos]

Could it have to do with my Swap file now being split as follows:
2-2 MB on C: (Initial - Maximum Size)
139-189 MB on E:

I inherited the server with 1 MB system volume size, originally including the entire swap file !! But then I ran out of disk space... So I decided to move the swap file (as much as possible) away to a different partition.

Unfortunately I have no tools to change the partition size on a server.
Besides, merging volumes and rearranging data drive letters causes a lot of trouble with usrmgr, currently running apps and login scripts ...

 

[Marcs41]

Even that swapfile is small for a server.
You better start doing some maintenance before you really hit the wall.
Servers require memory and space, give it to them. Don't struggle with workarounds if adding memory and maybe a larger harddisk will do the trick. At todays prices, that should not even be questioned.

 

[JimPonder]

Here's your answer: You need to increase the available size of registry memory used.

Right Click 'my computer'
Select Properties
Select the 'advanced' tab
Select the 'performance options'
Under virtual memory, 'change...'
Under Registry Size, change it to a number greater than what it is...
By default, I think it is set to 18. I usually swing it up to 48.
Save all of the settings, then reboot and it should be all good.
If you have problems, let me know...
jponder@bathcsd.org
6/4/03

 

[pvanos]

Jim,

thanks for your answer.
The current registry size is currently 10 MB.
The maximum registry size is currently set to 26 MB.
Do you think that could have to do with this problem ?

Thanks,
Paul

 

[popol]

We are experiencing the same problem on one of our servers.
Please tell me which one of the solution if any solved your problem.

 

[Cleopatre]

Try to Stop/Start your Antivirus service

 

[pvanos]

Popol,

when I got this problem, the server was a PDC.
To get rid of it, I created a new BDC, and promoted this machine to PDC. At this moment the former PDC was demoted to BDC.
Since then, I haven't seen this problem anymore.
The only strange phenomena I still have on this server are :
1) After rebooting, and WinNT4.0SRV is initializing, I obtain a msg "spoolss.exe - Entry Point Not Found : The procedure entry point SetPrinterDataA could not be located in the dynamic link library SPOOLSS.dll [OK]"
2) When trying to update the Symantec AntiVirus Corporate Edition 7 to 8, for some reason, it does not seem to work.

Yesterday, I installed 512 MB in the machine (it had only 128 MB so far). I plan to format the server, and turn it into a Windows2000 domain controller...