IIS 7.5抛出SC-win32的状态:995 60秒后的Web服务(ASMX)要求 [英] IIS 7.5 throws sc-win32-status: 995 after 60 seconds on web service (ASMX) request

查看:2393
本文介绍了IIS 7.5抛出SC-win32的状态:995 60秒后的Web服务(ASMX)要求的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我在.NET 4.0集成模式下一个Web应用程序通过本地主机在同一台服务器上调用.NET 2.0集成模式下一个Web服务(ASMX)。

I have a Web Application in .NET 4.0 Integrated mode calling a web service (ASMX) in .NET 2.0 Integrated mode on the same server via localhost.

9个10倍一切工作正常,但偶尔也会在Web应用程序中获取一个请求超时,并在通话过程中线程已被中止的错误。它详细介绍了这个code例子的最后一行的错误:

9 out of 10 times all works fine, but occasionally the Web Application get's a "Request timed out" and "Thread was being aborted" error during the call. It gives the error on the last line of this code example:

 Dim Service As New localhost.Service
 Dim Input As New localhost.InputProduct
 Dim Ret As New localhost.OutputProduct 
 Try
     Ret = Service.RequestProduct(Input) 
 Catch 
 Finally
   Service.Dispose()    
   If Ret.succesfull = True Then
      If Response.IsClientConnected = True Then
         Response.Redirect("success.aspx", False)
      End If    
   End If 
End Try

在Web服务的日志文件,我得到一个SC-win32的状态:995和SC-状态:200,通常时间采取总是一点点超过60秒(时间取:62743) 。通常这会坐14秒内没有错误才能完成。

In the log file of the web service I get a sc-win32-status: 995 and a sc-status: 200, typically the time-taken is always a little bit more than 60 seconds (time-take: 62743). Normally this would take 14 seconds to complete without errors.

通话是在一个按钮被点击后,ASPX页面背后的code。 在页面有一个UpdatePanel并且该按钮被用作PostBackTrigger

The call is made in the code behind of the ASPX page after a button is clicked. On the page there is an Updatepanel and the button is used as a PostBackTrigger.

问:为什么我得到这些Web服务调用后,请求超时的错误

Question: Why do I get these "request timed out" error after the web service call?

服务器:

  • 在Windows Server 2008 R2 SP1
  • 在IIS 7.5
  • 在微软的UrlScan 3.1
  • Windows防火墙

推荐答案

我终于找到了答案,这个问题。它原来是这片code在web.config:

I finally found the answer to this problem. It turned out to be this piece of code in the web.config:

<pages smartNavigation="true">

关闭这个功能后,我没有再收到任何超时错误。 究其原因,超时可能是该SmartNavigation的设置,在IE浏览器中生成IFRAME(而不是在Firefox / Chrome浏览器)

After turning this off I didn't receive any time-out errors anymore. The reason for the time-out is probably the IFRAME that the smartNavigation setting generates in IE browsers (not in Firefox/Chrome)

我已经使用这个在.NET 2.0的消除闪光灯造成的导航,升级到.NET 4.0之后的Visual Studio没有给出任何线索,这个设置是德precated。

I have used this setting in .NET 2.0 to eliminating the flash caused by navigation, after upgrading to .NET 4.0 Visual Studio didn't give any clue that this setting was deprecated.

我找到了答案,因为我有其他的问题来处理。采用了最新的 ajaxToolkit 以.NET 4.0之后,我同时使用了在IE7 / 8这个JavaScript警告错误在AutoCompleteExtender:

I found the answer, because I had an other problem to deal with. After using the latest ajaxToolkit for .NET 4.0 I had this javascript alert error in IE7/8 while using the AutoCompleteExtender:

堆栈溢出行:0

这竟然是相关的SmartNavigation设置。因此,除去此设置固定在一次两个问题。希望我帮助别人这个问题,因为对我来说是最讨厌错误的,我在网​​上的短暂历史中的一个。

This turned out to be related to the smartNavigation setting. So removing this setting fixed two problems at once. Hopefully I help someone with this, because for me it was one of the most annoying error's I've found in the short history of internet.

这篇关于IIS 7.5抛出SC-win32的状态:995 60秒后的Web服务(ASMX)要求的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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