Check The Paging File Disk For An I/o Error
Contents |
on March 22nd, 2011 Today, a user reported an issue connecting to a very old CRM application. I logged in to the system myself and saw no error. Since I'm not happy check paging file size with self-healing issues, I went digging into the event log on the server.
Check Paging File Usage
For the past five days, there have been over 15,000 entries added to the System event log with event ID 333: "An I/O operation initiated by the Registry failed unrecoverably. The Registry could not read in, or write out, or flush, one of the files that contain the system's image of the Registry." That doesn't sound good. My first stop for analyzing event log errors is eventid.net. The feedback on their site pointed me to a few possibilities. The /3GB switch on a system with 2GB or less of memory. Symantec AntiVirus (which is a potential culprit to every system problem, apparently). Insufficient Non Paged Memory or Paged Pool Memory. Disk or I/O subsystem errors. Overaggressive SQL Server memory usage or I/O affinity. I checked the server's memory capacity: 3GB. I checked memory usage in Task Manager: about the same. I checked the page file size, and saw the following (note the highlighted sections). Ouch! Microsoft has a nice knowledge base article, affectionately titled, RAM, Virtual Memory, Pagefile, and all that stuff, which suggests, as a baseline recommendation, that a pagefile should equal "1.5 times the amount of RAM that is in the computer." As always, your mileage may vary, but generally speaking, the recommendation is sound. Or, you can just click the "System managed size" option, and forget about it altogether. The lesson here: check your pagefile settings when setting up a computer, and always revisit them whenever the amount of physical RAM changes. Technology « Beer and Taxes A practical definition of C# constructors » Leave a Reply Cancel reply Name (required) Email (will not be published) (required) Website You can use these HTML tags
« Beer and Taxes A practical definition of C# construct
Microsoft Tech Companion App Microsoft Technical Communities Microsoft Virtual Academy Script Center Server and Tools Blogs TechNet Blogs TechNet Flash Newsletter TechNet Gallery TechNet Library TechNet Magazine TechNet Subscriptions TechNet Video TechNet Wiki Windows Sysinternals Virtual Labs Solutions Networking Cloud and Datacenter Security Virtualization Downloads Updates Service Packs Security Bulletins Windows Update Trials Windows Server 2012 R2 System Center 2012 R2 Microsoft SQL Server 2014 SP1 Windows 8.1 Enterprise See all trials » Related Sites Microsoft Download Center TechNet Evaluation Center Drivers Windows Sysinternals TechNet Gallery Training Training Expert-led, virtual classes Training Catalog Class Locator Microsoft Virtual Academy Free Windows http://www.sidesofmarch.com/index.php/archive/2011/03/22/insufficient-pagefile-size-can-cause-obscure-memory-errors/ Server 2012 courses Free Windows 8 courses SQL Server training Microsoft Official Courses On-Demand Certifications Certification overview MCSA: Windows 10 Windows Server Certification (MCSE) Private Cloud Certification (MCSE) SQL Server Certification (MCSE) Other resources TechNet Events Second shot for certification Born To Learn blog Find technical communities in your area Support Support options For business For developers For IT professionals For technical support Support offerings More support https://technet.microsoft.com/en-us/library/cc978735.aspx Microsoft Premier Online TechNet Forums MSDN Forums Security Bulletins & Advisories Not an IT pro? Microsoft Customer Support Microsoft Community Forums United States (English) Sign in Home Library Wiki Learn Gallery Downloads Support Forums Blogs We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. Windows 2000 Error Messages Reference Kernel System Resources System Resources Not enough storage is available to process this command. ... Not enough storage is available to process this command. ... Not enough storage is available to process this command. ... The RPC server is unavailable. ... A lock request was not outstanding for the supplied cancel region. ... The file name is too long. ... Some mapping between account names and security IDs was not done. ... Child windows cannot have menus. ... All pipe instances are busy. ... The network path was not found. ... System could not allocate the required space in a Registry log. ... The drive cannot find the sector requested. ... The operating system cannot run this application program. ... The format of the specified group name is invalid. ... The number of specified semaphore events for DosMuxSemWait is not correct. ... The
we highly recommend that you visit our Guide for New Members. Error Message: Not enough storage is available to complete this operation Discussion in 'Windows XP' started by The_Carlos, Feb 19, https://forums.techguy.org/threads/error-message-not-enough-storage-is-available-to-complete-this-operation.684846/ 2008. Thread Status: Not open for further replies. Advertisement The_Carlos Thread Starter Joined: Feb http://www.windowsdevcenter.com/pub/a/windows/2004/04/27/pagefile.html 19, 2008 Messages: 1 hi there i am trying to copy some media files from my mp3/videoplayer (Archos AV500) to my computer. However, when i try to do this i receive the following message "Not enough storage is available to complete this operation" Now i dont understand this as i have over 10gb of space on my computer and paging file the file size is only 1.85gb, i have also tried copying the file onto an external hard drive that has over 200gb of space and i still get the error message. The file is an avi file, my computer runs windows xp, i'm not sure what other info you require so if there is anything i left out please let me know so i can provide it. I googled my problem and found many check paging file people getting the same error message when they used word or other situations, one guy said that the error message was a very old message and sometimes it comes up when a file is corrupted could this have something to do with it? Many Thanks Carl The_Carlos, Feb 19, 2008 #1 Holden2008 Joined: Feb 21, 2008 Messages: 4 ok I don't know what experance you have so im guessing ok... Error Message: Not enough storage is available to complete this operation. Do one of the following, then retry the operation: (1) reduce the number of running programs; (2) remove unwanted files from the disk the paging file is on and restart the system; (3) check the paging file disk for an I/O error; or (4) install additional memory in your system. Holden2008, Feb 21, 2008 #2 This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue.View our Welcome Guide to learn how to use this site. Show Ignored Content As Seen On Welcome to Tech Support Guy! Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations. If you're not already familiar with fo
paging file (pagefile.sys) is a hidden system file that forms a key component of the Virtual Memory Manager (VMM) on Windows platforms. The origin of this file dates back to early 1990s when Windows ran on PC hardware that had limited physical memory due to the high cost of RAM and the limitations of motherboard design. (The concept of virtual memory itself, of course, is older, as this article describes.) The purpose of the pagefile was to allow memory-hungry applications to circumvent insufficient RAM by allowing seldom-used pages of RAM to be swapped to disk until needed (hence the term swapfile used on earlier Windows platforms). For example, if a Windows 3.1 machine had 8MB of RAM and a 12MB permanent swap file (386spart.par) on its C: drive, then the effective memory that applications could use was 8 + 12 = 20MB, or in other words: (physical memory) + (swapfile) = (virtual memory) The downside of the virtual memory architecture was that performance could be degraded as memory-hungry applications caused frequent swapping of pages between RAM and disk. But as motherboard design improved and RAM became cheaper, adding more RAM could improve performance by reducing the amount of disk thrashing caused by paging. The evolution of applications kept pace with these hardware developments, though, and as applications grew and became bloated, the need for improved paging architecture became paramount. Over the years Microsoft has tweaked the VMM architecture for each version of Windows until today it works quite well. But if you want to get the most out of your servers in terms of performance, you need to go beyond the default pagefile settings. Moving the Pagefile The most significant performance gain you can achieve with regard to the pagefile on Windows 2000 and Windows Server 2003 is to move the pagefile to a different partition or volume. By default, Windows creates a pagefile of size 1.5 x RAM and locates it on the root of the boot partition (usually C: drive). Unfortunately, this means the I/O subsystem must contend for access to operating system files (%systemroot% and %systemroot%\system32) and the pagefile (%systemdrive%\pagefile.sys), which increases disk activity and slows performance. By moving pagefile.sys to a different volume, this contention is reduced--especially if the