FileNotFoundException, could not find file ' C:\WINDOWS\TEMP\wpbzwlwo.dll '.

Today's service anomaly throws a weird question. Prompt in XML serialization: FileNotFoundException, could not find file ' C:\WINDOWS\TEMP\wpbzwlwo.dll '.

    Stack trace: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, Fileop tions 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.FromFileBa TCH (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) at Solutionname.commonclassname.xmlhelper.serialize[t] (T entity) at SolutionName.Bizprocess.Classnam
  E.methodname (Int32 paramter)

On the Internet, it turns out that this is a server execution permissions issue. The site process is created by Inetinfo.exe as administrator, and w3wp is attached to the site (window station) when it is started, but it is not a console process, and the default window is used when the child process csc.exe starts processing the request Station service-0x0-luid$ to recreate the console information, causing insufficient permissions to run.

Therefore, you can resolve this problem by configuring the application pool identity to set up the Administrators group.