You searched for the word(s): userid:91

More Search Options

RSS Available

• Re: System.IO.IOException: Insufficient system resources exist to complete the requested service

  The error message “ Insufficient system resources exist to complete the requested service. ” corresponds to system error code 1450 (ERROR_NO_SYSTEM_RESOURCES). This is HRESULT 0x800705aa. In 1.1, HttpPostedFile.SaveAs reads the entire posted content into a byte[ ], and then attempts to write that to a file. If the file is on a UNC share and the posted content is larger than approximately 64 MB, we will fail with the error above. This problem was fixed in 2.0, where the posted content is read in chunks

  Posted to Web Forms (Forum) by tmarq on 7/12/2006

• Re: can caching trigger System.OutOfMemoryException ?

  Yes, only objects >= 85,000 bytes are allocated in the Large Object Heap. The perfmon description for the performance counter is incorrect. It is 85,000 in .NET Framework 1.0, 1.1, and 2.0. In ntsd.exe ( http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx ), using .NET Framework v2.0, you can set a break point on the following functions. Everytime a large object is allocated, the break point will be hit. After you attach ntsd.exe to the worker process, run these commands inside the

  Posted to State Management (Forum) by tmarq on 4/30/2006

• Re: can caching trigger System.OutOfMemoryException ?

  The ASP.NET 2.0 cache memory manager will drop cache entries for two reasons: 1) First, it drops entries if the amount of RAM in use is close to 90%. To be more specific, it checks the value of dwMemoryLoad (obtained via a call to GlobalMemoryStatusEx) and drops entries when this is close to 90%. This percentage can also be calculated by subtracting the "Memory\Available MBytes" performance counter from the total amount of physical RAM in megabytes, and dividing by the total amount of physical RAM

  Posted to State Management (Forum) by tmarq on 4/30/2006

• Re: Web Caching size question ( optimal and maximous )

  Hello Ariel, The sizes that you suggest are fine. Just be careful not to allocate short-lived objects that are larger than 85000 bytes, because these are allocated in the Large Object Heap and are very expensive to collect. You can use the CLR Profiler to see if all your objects are smaller than 85000 bytes (see the Histogram Allocated Types view). Here are a few more things to consider: 1. The ASP.NET Cache will drop entries and induce garbage collections when "Memory\Available MBytes" is less than

  Posted to State Management (Forum) by tmarq on 2/16/2006

• Re: Application Pool Terminating Unexpectedly

  The root web.config applies to all applications, and there is a possibility putting it there might help you. <legacyUnhandledExceptionPolicy/> belongs in %WINDIR%\Microsoft.NET\Framework\v2.0.50727\ aspnet.config . If the module continues not to catch the exception, can you do the following? 0) Install the current build of Windows Debugging Tools from http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx 1) ntsd.exe -g -G -p <pid>, where pid is the process id for worker process

  Posted to Migrating from ASP.NET 1.x to ASP.NET 2.0 (Forum) by tmarq on 1/24/2006

• Re: Application Pool Terminating Unexpectedly

  Is the module installed in the root web.config file? The one at %WINDIR%\Microsoft.NET\Framework\v2.0.50727\config\web.config. Thanks, Thomas

  Posted to Migrating from ASP.NET 1.x to ASP.NET 2.0 (Forum) by tmarq on 1/23/2006

• Re: Problems on install .net framework 2.0

  Vatic, Sorry for the delayed response. To understand the first two event log messages, it would help to have the Record Data for those messages. Since the call to lodctr succeeded, I suspect that I have overlooked something in regard to the state of the registry keys on your machine. Can you compare your registry settings with the ones listed below? Are yours the same? [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ASP.NET_2.0.50727\Performance] "Library"="C:\WINDOWS\Microsoft.NET\Framework

  Posted to Installation and Setup (Forum) by tmarq on 1/6/2006

• Re: Problems on install .net framework 2.0

  We tried to reproduce this problem using a clean install of SBS 2000. We installed .NET Framework v2.0, followed the 8 steps I posted to this forum earlier, and the perf counters work. We logged on to SBS 2000 as an administrator when performing this work. You can create First Counter, Last Counter, etc beneath HKLM\System\CurrentControlSet\Services\ASP.NET_2.0.50727\Performance by following these steps: 1. cd %WINDIR%\Microsoft.NET\Framework\v2.0.50727 2. lodctr.exe aspnet_perf.ini This should create

  Posted to Installation and Setup (Forum) by tmarq on 12/21/2005

• Re: Problems on install .net framework 2.0

  A QFE is what we call a hotfix, or a patch. It stands for Quick Fix Engineering. Perhaps we should make sure there is no simple workaround to get the perf counters working. There are two issues: 1) You are missing several registry values. The aspnet_regiis log says the perf counter installation succeeded, and yet you are missing First Counter, Last Counter, First Help, and Last Help beneath HKLM\System\CurrentControlSet\Services\ASP.NET_2.0.50727\Performance. The perf counter installation clearly

  Posted to Installation and Setup (Forum) by tmarq on 12/19/2005

• Re: Problems on install .net framework 2.0

  Earlier in this forum, I posted 8 steps that you can follow to make the perf counters work. In step 2, since your worker process identity is IWAM_<machine name>, you need to add that account to IIS_WPG. However, earlier you said that your machine is missing some of the values beneath HKLM\System\CurrentControlSet\Services\ASP.NET_2.0.50727\Performance, which tells me that the installation of perf counters failed the last time aspnet_regiis /i ran. You should be able to confirm this by looking

  Posted to Installation and Setup (Forum) by tmarq on 12/19/2005