已发生多次Web服务错误 [英] Web Service error that has occurred several times

查看:261
本文介绍了已发生多次Web服务错误的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在多台机器(有Asp.net 1和2)我们已经看到下面的错误与随机文件名(以的.dll 扩展)每次产生我们试图让Web服务调用。

在过去,我们不得不重新安装 asp.net 这似乎已经固定它。

但是,有一次,我们试图让命令提示符窗口,并用约低资源错误回来。重新启动服务器似乎已经修复了这个问题。

任何想法是什么原因造成这个错误?

以下错误:

  System.Web.Services.Protocols.SoapException:服务器无法处理请求。 ---> System.IO.FileNotFoundException:未能找到文件'C:\\ WINDOWS \\ TEMP \\ aweww1ss.dll。
文件名:C:\\ WINDOWS \\ TEMP \\ aweww1ss.dll
   在System.IO .__ Error.WinIOError(的Int32错误code,字符串maybeFullPath)
   在System.IO.FileStream.Init(字符串路径,模式的FileMode,FileAccess的访问,的Int32权利,布尔useRights,文件共享份额,缓冲区大小的Int32,FileOptions选项,SECURITY_ATTRIBUTES secAttrs,字符串MSGPATH,布尔bFromProxy)
   在System.IO.FileStream..ctor(字符串路径,模式的FileMode,FileAccess的访问,文件共享份额)
   在Microsoft.CSharp.CSharp codeGenerator.FromFileBatch(CompilerParameters选项,字符串[]文件名)
   在Microsoft.CSharp.CSharp codeGenerator.FromSourceBatch(CompilerParameters选项,字符串[]来源)
   在Microsoft.CSharp.CSharp$c$cGenerator.System.$c$cDom.Compiler.I$c$cCompiler.CompileAssemblyFromSourceBatch(CompilerParameters选项​​的String []源)
   在系统,codeDom.Compiler。codeDomProvider.CompileAssemblyFromSource(CompilerParameters选项,字符串[]来源)
   在System.Xml.Serialization.Compiler.Compile(大会父,字符串NS,XmlSerializerCompilerParameters xmlParameters,证据证据)
   在System.Xml.Serialization.TempAssembly.GenerateAssembly(XmlMapping [] xmlMappings,类型[]类型,字符串defaultNamespace,证据证据,XmlSerializerCompilerParameters参数,装配装配,装配哈希表)
   在System.Xml.Serialization.TempAssembly..ctor(XmlMapping [] xmlMappings,类型[]类型,字符串defaultNamespace,字符串位置,证据证据)
   在System.Xml.Serialization.XmlSerializer.FromMappings(XmlMapping []映射,证据证据)
   在System.Web.Services.Protocols.SoapServerType..ctor(类型类型,WebServiceProtocols protocolsSupported)
   在System.Web.Services.Protocols.SoapServerProtocol.Initialize()
   在System.Web.Services.Protocols.ServerProtocol.SetContext(泰


解决方案

如果重启解决,这意味着你的机器基本上都是跑出来的临时文件存储空间的问题,常规的前pressions和很多工具,包括动态编译(ASPX等),产生大量的临时文件,并重新启动服务器或清洁的临时文件应该可以解决问题。

.NET应用程序是有点不好,为运行很长时间,我们有服务器的问题时,我们并没有重新启动他们的天......那么作为天通经,日志,内​​存碎片整理等的推移越来​​越大,我想有时减缓都记录下来。 .NET应用程序通常不去除他们打开,资源上的锁它不是开发商的过错,而是.NET垃圾收集的心不是,如果文件关闭的werent或删除聪明,所以你的临时文件可能增长。

最好是做定期软重启喜欢每周一次在周日晚上等将有助于管理.NET应用程序很好。

On a number of machines (with Asp.net 1 and 2) we have seen the below error with a random file name (with .dll extension) produced each time we try to make the web service call.

In the past we have had to reinstall asp.net and that seems to have fixed it.

However, on one occasion we tried to get the command prompt and windows came back with a error about low resources. Rebooting the server seemed to have fixed this issue.

Any ideas what is causing this error?

Error below:

System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.IO.FileNotFoundException: Could not find file 'c:\windows\Temp\aweww1ss.dll'.
File name: 'c:\Windows\Temp\aweww1ss.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.FromMappings(XmlMapping[] mappings, Evidence evidence)
   at System.Web.Services.Protocols.SoapServerType..ctor(Type type, WebServiceProtocols protocolsSupported)
   at System.Web.Services.Protocols.SoapServerProtocol.Initialize()
   at System.Web.Services.Protocols.ServerProtocol.SetContext(Ty

解决方案

If rebooting solved the issue that means your machine basically ran out of temp file storage space, your regular expressions and lot of tools that involve dynamic compilation (aspx etc), creates lot of temp files, and rebooting server or cleaning temp file should solve issue.

.NET apps are little bad to run for long time, we had server issues when we were not restarting them for days... then as days pass by, the logs, the memory defragmentation etc goes bigger and bigger and i think that sometimes slows everything down. .NET apps usually dont remove locks on resources they opened, its not developer's fault but .net garbage collection isnt that smart, so your temp files may grow if files werent closed and deleted.

Best is to do soft reboot on regular intervals like once a week on sunday night etc will help managing .net apps well.

这篇关于已发生多次Web服务错误的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆