Posted by Jayce Ooi as Web
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 106482 bytes) in…
I was playing with new WordPress plugin. The plugin does not have any issue. However, I faced above issue when I tried to publish a new post. Hmm… Seem like the default 32M WordPress limit was exceeded with this new plugin. How to fix this “Fatal error: Allowed memory size of 33554432 bytes exhausted” issue?
Simple… Just edit your wp-config.php to include the line below:
Do you know to generate error information to Windows Event Log? Most of the Windows application will output error information to Windows Event Logs if there are issues in that application. How do we do that in C#?
We need to use System.Diagnostics namespace.
Codes to generate information to output to Windows Event Logs
EventLog myLog = new EventLog();
myLog.Source = “YourApplication”;
myLog.WriteEntry(“Error Description”, EventLogEntryType.Error);
Posted by Jayce Ooi as Hardware
Warning, Seagate Barracuda 7200.11, DiamondMax 22, Barracuda ES.2 SATA hard drive owners. Yes, this is a very serious warning coming out from Seagate itself. Because your hard drive might become inaccessible when you power up your PC system. I got an error comment from an anonymous on January 11th, 2009. At first, I thought just an anti-Seagate wondering around and doing some damages to Seagate branding. However, I changed my mind after seeing this announcement.
Oh no… My hard drive is on the list!
System.Configuration.ConfigurationErrorsException: Could not load file or assembly ‘Microsoft.ReportViewer.WebForms, Version=18.104.22.168, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies. The system cannot find the file specified.
Do you ever see this problem when you try to load ASP.NET web application? Well, based on the error code. It should have something related to ReportViewer. It seem like the ReportViewer component is not found.
I don’t have the problem during development at my development server. However, I faced this problem when I deploy to another machine. Why is this happening?
Here is the solution…
This should do the trick.
Do you get Parser Error Message: Unrecognized attribute ‘xmlns’ when you try to deploy web application? Line 2: <configuration xmlns=”http://schemas.microsoft.com/.NetConfiguration/v2.0″></configuration> is red in colour.
Well, it happens all the time when I deploy ASP.NET 2.0 web application on a server with both ASP.NET 1.1 and 2.0 installed. What you need to do? By selecting the correct ASP.NET version at Internet Information Services (IIS) will solve the problem.