Receive virtual memory error when booting

[sda]

I get an error notice message that my virtual memory is to low when i start my pc, ive tryed 10 different combination and STILL get that dawn message everytime I boot.

I just formated that pc and i diden't came close to touch the virtual memory. I reload like 7-8 box a week and i have never seen that problem before.

When i go in the perfomance options to check my virtual memory, for a ?/$%?ed up reason, it says i got 20 mb of virtual memory as minimum while i have 192 in the minimum, i try to set it, but when i reboot it come back with the same error message.

If any1 can help me with that i would really appreciate (i know how to setup virtual memory)

[boent]

If you changed the security on the winnt folder and had all subfolders inherit permissions this happens. Login as administrator and goto you pagefile which is under c: and right click it and make sure everyone has full control. Everyone has to write to that pagefile. Then make sure you have enough vmemory to cover the recommended. Hope this helps.

[Whoever]

I get the same message. Also tried formatting (using the installation CD's option upon installment). The problem is still there. Now I also checked the security rights. I have all the rights I can have.

At first I thought this was a problem with some installed applications, but since the error message came up almost instantly after reinstallation, I guess I figured wrong. Also it came before I accessed the internet the first time....

Any suggestions as to how this is fixed. Its annoying as hell since most applications cant run properly due to memory failure.

[nmyggen]

I have this problem as well... HELP!!!!!!!!

[leakim]

I have also exact the same problem!

Leakim

[BertImmenschuh]

What Operating System, WinNT4 or Win2000? I found this on Microsoft at
<a target="_blank" href=http://msdn.microsoft.com/library/default.asp?url=/library/en-us/optimsql/odp_tun_1a_2rqx.asp>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/optimsql/odp_tun_1a_2rqx.asp</a>:

"Configuring Virtual Memory
Microsoft® Windows NT® or Windows 2000 virtual memory size should be configured based on the services concurrently running on the computer. When you are running Microsoft SQL Server™ 2000, consider setting the virtual memory size to 1.5 times the physical memory installed in the computer.

If you have additionally installed the Full-Text Search feature and plan to run the Microsoft Search service so that you can do full-text indexing and querying, consider configuring:

The virtual memory size to at least 3 times the physical memory installed in the computer.

The SQL Server max server memory server configuration option to 1.5 times the physical memory (half the virtual memory size setting).
If the virtual memory setting is configured too low, then the following Windows NT error can occur:

Your system is running low on virtual memory. Please close some applications. You can then start the System option in the Control Panel and choose the Virtual Memory button to create an additional paging file or increase the size of your current paging file.

Note For more information, see the Windows NT or Windows 2000 documentation."

[Lazzarus]

I had this problem too, my solution at the time was a full re-install (but this is a home computer and the system needed a nice clean up anyways) it will not recognize any new pagefiles created, i have a page of 989mbs and it told me i didn't have a large enough page so it made a temp one, i wish i could have figured out what to do then but i'd recomend making your page file, deleting the temp one created by w2k in c\, then disable deletion of the page file on reboot, if that works please let me know ;) other wise sorry and good luck

|||||||||||||
Lazzarus
|||||||||||||

[sasu]

I had the same problem in W2K. But to fix it I deleted my pagefile (which was possible, because W2K did not actually use it. Just remember to fix the file attributes before that). Then I HAD to give SYSTEM account full control to system (C:\) root directory. Then I created the pagefile from performance options and booted the machine even windows didn't ask me to. After this the problem disappeared. So I think the main thing here is to give appropriate SYSTEM account rights to C:\ root and to pagefile. Easiest way to make sure that all necessary rights are given to pagefile is to delete it and create a new one after the rights has been given to the folder where pagefile is (usually C:\). Hope you can get rid of the problem this way without having to re-install your machine...