Also, in Firefox I am getting this error now: XML Parsing Error: no element found
Location: http://www.karldewazien.com/Host/Host%20Settings/tabid/16/portalid/0/language/en-US/Default.aspx
Line Number 1, Column 1: I'm getting page not found almost 1 in 3 tries on Internet Explorer and an error similar to above in Firefox slightly less frequently. It appears that pages are caching, but I'm not seeing any portal replacement rules in effect. I'm hosting with discountasp.net and i know they have a 100MB memory cap. I had them add SQL session state a while back because my site kept recycling due to a newletter module I was using. This appears to be the same kind of thing now. Will page blaster cause me to require more memory usage? It almost seems that there is an issue with compression. Prior to install PB, I turned off core compression via host settings and almost instantly, the site stopped giving me so many page not found errors. Then, I installed PB and seems to be doing the same thing. I can definitely see the performance improvement in pages that will actually display, but at this rate, that doesn't much matter right now. I'm in a medium trust environment and i have the PB reference in two sections on the web.confg - once for IIS 6 and once for IIS7...could that be causing an issue also? I'm using PB 2.4 btw. Any help at all would be greatly appreciated! Thanks!! |