Prev: Msbuild - Multiple Reference Paths via commandline
Next: rtsp streaming
From: j055 on 18 Mar 2010 05:23
Hi

We are getting a lot of errors when the ASP.NET application tries to use
XmlSerialization

System.IO.FileNotFoundException: Could not find file
'C:\WINDOWS\TEMP\bffti4me.dll'

Stack example:
System.IO.FileNotFoundException: Could not find file
'C:\WINDOWS\TEMP\bffti4me.dll'.
File name: 'C:\WINDOWS\TEMP\bffti4me.dll'
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess
access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize,
FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean
bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess
access, FileShare share)
at Microsoft.CSharp.CSharpCodeGenerator.FromFileBatch(CompilerParameters
options, String[] fileNames)
at
Microsoft.CSharp.CSharpCodeGenerator.FromSourceBatch(CompilerParameters
options, String[] sources)
at
Microsoft.CSharp.CSharpCodeGenerator.System.CodeDom.Compiler.ICodeCompiler.CompileAssemblyFromSourceBatch(CompilerParameters options, String[] sources)
at
System.CodeDom.Compiler.CodeDomProvider.CompileAssemblyFromSource(CompilerParameters options, String[] sources)
at System.Xml.Serialization.Compiler.Compile(Assembly parent, String ns,
XmlSerializerCompilerParameters xmlParameters, Evidence evidence)
at System.Xml.Serialization.TempAssembly.GenerateAssembly(XmlMapping[]
xmlMappings, Type[] types, String defaultNamespace, Evidence evidence,
XmlSerializerCompilerParameters parameters, Assembly assembly, Hashtable
assemblies)
at System.Xml.Serialization.TempAssembly..ctor(XmlMapping[] xmlMappings,
Type[] types, String defaultNamespace, String location, Evidence evidence)
at System.Xml.Serialization.XmlSerializer.GenerateTempAssembly(XmlMapping
xmlMapping, Type type, String defaultNamespace)
at System.Xml.Serialization.XmlSerializer..ctor(Type type, String
defaultNamespace)
at System.Xml.Serialization.XmlSerializer..ctor(Type type)


IIS requires a restart to fix the problem and things seem to work normally
for between 24 to 48 hours, then the problems surface again.

Tried clearing the C:\WINDOWS\TEMP folder which doesn't seem to help.
There's plenty of disk space.

The application has been running successfully for some months. The problems
seem to have started without any change to hardware or software on the
server. The problem only seems to occur in a production environment (Windows
2K3, IIS6, etc. etc)

What do we need to do?
Thanks
Andrew

From: Mr. Arnold on 18 Mar 2010 06:35
j055 wrote:
> Hi
>
> We are getting a lot of errors when the ASP.NET application tries to use
> XmlSerialization
>
> System.IO.FileNotFoundException: Could not find file
> 'C:\WINDOWS\TEMP\bffti4me.dll'
>

It needs to find a dll in the temp folder? bffti4me.dll? If it's there
on the machine, then right click it and look at the properties and find
out. What it is if possible? Who made it?

This sounds suspicious. Possible malware? Why would XMLSerlization need
to use a DLL in the temp folder? It doesn't make sense.

Maybe, the AV running on the machine sees it as a threat and is taking
bffti4me.dll out.

If it's legit, and I would certainly get on the phone to MS and find out
if it's legit, then fine and find out what is taking it out.




From: Patrice on 18 Mar 2010 13:04
Hello,

AFAIK this is legit. Serialization is able to create an assembly on the fly
to speed up the serialization...

Not sure why this file is suddenly deleted or not found but a possible
workaround could be to create this assembly once for all.

See :
http://support.microsoft.com/kb/913668/en-us
(for SQL Server 2005 but the big picture is the same)

--
Patrice



 | 
Pages: 1
Prev: Msbuild - Multiple Reference Paths via commandline
Next: rtsp streaming