http://ola.kodar.se/ Sharing is caring ola.kodar.se 2010-04-25T14:30:59Z http://ola.kodar.se/blog/strangest-cannot-resolve-symbol-error-ever/ Fri, 16 Feb 2018 14:28:05 GMT Sun, 25 Apr 2010 14:30:59 GMT Ola Herrdahl test@example.com <p>This is a not so uncommon error: <a href="/files/2010/03/cannot-resolve-symbol-wtf.png"><img title="Cannot resolve symbol &#39;PooledHttpClient&#39;" class="size-full wp-image-146" alt="" src="/files/2010/03/cannot-resolve-symbol-wtf.png" width="470" height="132" /></a> <br /> But when I switched to PooledHttpClient.java I got a bit confused: <br /><a href="/files/2010/03/PooledHttpClient.png"><img title="PooledHttpClient.java" class="size-full wp-image-147" alt="" src="/files/2010/03/PooledHttpClient.png" width="559" height="163" /></a> </p> <p>Seriously w t f happened here? Has my RAID controller gone berserk on the poor file? </p> <p> A couple of weeks ago I saw something similary happend on a production server (VPS). <br /> Suddenly one of my static HTML-files contained fragments of code from something completely different. <br /> As far as I can tell, these errors seems to originate from a broken file system. <br />Perhaps one should take stuff like this as a sign that it might be wise to start replacing the disks in the raid array.</p> http://ola.kodar.se/blog/aspnet-systemioioexception-the-file-or-directory-is-corrupted-and-unreadable/ Fri, 16 Feb 2018 14:09:53 GMT Sun, 25 Apr 2010 13:39:59 GMT Ola Herrdahl test@example.com <p>A couple of month ago all sites died on one of my old servers (a Windows 2003 based Virtuozzo VPS). <br />I wrote a line about it in one of my previous <a href="/2010/03/19/strangest-cannot-resolve-symbol-ever/cannot-resolve-symbol-wtf">posts</a>, at least one static HTML-file contained fragments of code from something completely different. </p> <p>One of the first observation I did on the server was that every site had their own strange error even though almost everyone was running the same version of <a href="http://umbraco.org/">Umbraco</a>. <br />As an example, one site did not start at all while another could start but would end up crashing after a couple of hours and bringing down the whole server again. (Not just the application pool.) </p> <p>I quickly migrated all critical sites from the server leaving just one behind. Today I decided to fix the one that was left behind and also try and determine what was wrong with the server. After a bit of digging I managed to find one useful error message. </p> <blockquote>Exception Details: System.IO.IOException: The file or directory is corrupted and unreadable.</blockquote> And my good friend google told me that this might just be an issue with the ASP.NET file cache. I quickly located the cache in : <pre lang="text"> C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\root </pre> <p>Deleted all folders in it... <br />..and IT WORKED! </p> <p>So note to self, next time IIS/ASP.NET starts behaving strange, try cleaning up the temp files first. </p>