I am getting this error on a community installed at a hosting company. It has been working and live for about a month at that hosting provider and working without any problems. I am not sure if this is user error, or the hosting provider. I also have been searching
for anyone reporting this error anywhere, and have not found a thing. Anyone ever seen this? Here is the error: Server Error in '/' Application. -------------------------------------------------------------------------------- The file or directory is corrupted
and unreadable. Description: An unhandled exception occurred during compilation using the CodeDomProvider 'Microsoft.CSharp.CSharpCodeProvider'. Please review the stack trace for more information about the error and where it originated in the code. Exception
Details: System.IO.IOException: The file or directory is corrupted and unreadable. Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified
using the exception stack trace below. Stack Trace: [IOException: The file or directory is corrupted and unreadable. ] System.IO.__Error.WinIOError(Int32 errorCode, String str) +723 System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access,
FileShare share, Int32 bufferSize, Boolean useAsync, String msgPath, Boolean bFromProxy) +888 System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share) +45 System.CodeDom.Compiler.CodeCompiler.FromDomBatch(CompilerParameters
options, CodeCompileUnit[] ea) +272 System.CodeDom.Compiler.CodeCompiler.FromDom(CompilerParameters options, CodeCompileUnit e) +90 System.CodeDom.Compiler.CodeCompiler.System.CodeDom.Compiler.ICodeCompiler.CompileAssemblyFromDom(CompilerParameters options,
CodeCompileUnit e) +37 System.Web.Compilation.BaseCompiler.GetCompiledType() +227 -------------------------------------------------------------------------------- Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET Version:1.1.4322.903
yeah, they are looking at it supposedly. "It looks like the framework got hosed" I have been trying to find articles about the errors it is giving, but have not been able to. Do you have any technical keywords that I could search for articles about this so
that I can understand what is going on? Or is "hosed" a keyword used in microsoft knowledge base articles? :o) hehehe justkiddin
Try looking at the following: 5503 As far as word lookups I usually try the stuff in the error message on google. For instance "System.CodeDom.Compiler.CodeCompiler.System.CodeDom.Compiler.ICodeCompiler.CompileAssemblyFromDom(CompilerParameters options, CodeCompileUnit
e)" as the search term found the above post. Other than that, "hosed" is a non-techinical, but fully discriptive, word commonly used in the USA. ;-)
Keith Barrows
Ad Astra Per Aspera - "To the stars thru difficulties"
Well, as of today, the site is working. So I emailed the hosting company asking them what they did to fix it, and what caused the whole issue. This is their response: "We simply removed the cache from the ASP.NET temporary directory." So what is that supposed
to mean? I am trying to figure out where to point the finger as to what caused our site to go down for a couple days. The host is not giving me very straight answers it seems.
None
0 Points
16 Posts
ERROR: The file or directory is corrupted and unreadable
Feb 13, 2004 02:11 PM|kenzie|LINK
Member
30 Points
241 Posts
ASPInsiders
Re: ERROR: The file or directory is corrupted and unreadable
Feb 13, 2004 04:15 PM|StarPilot|LINK
Ad Astra Per Aspera - "To the stars thru difficulties"
None
0 Points
16 Posts
Re: ERROR: The file or directory is corrupted and unreadable
Feb 13, 2004 04:36 PM|kenzie|LINK
Member
30 Points
241 Posts
ASPInsiders
Re: ERROR: The file or directory is corrupted and unreadable
Feb 16, 2004 12:43 PM|StarPilot|LINK
Ad Astra Per Aspera - "To the stars thru difficulties"
None
0 Points
16 Posts
Re: ERROR: The file or directory is corrupted and unreadable
Feb 16, 2004 03:27 PM|kenzie|LINK