By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,037 Members | 1,839 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,037 IT Pros & Developers. It's quick & easy.

Error: Thread was aborted from WaitForSingleObject

P: n/a
Hi,
I've a WebApp that calls Microsoft CRM WebServices to perform a
particular action. In my WebApp I am spawning a new async thread for
all the CRM related actions and sending the user to Thank you Page on
Parent thread. The Spawned thread aborts with the message "Thread Was
Aborted". This does not happen on development machines. Only production
machine seems to have this probelm. Is it related to the load on
production server? No idea..am stuck badly.

Error :Thread was being aborted.
Error Stack Trace :
at Microsoft.Win32.SafeNativeMethods.WaitForSingleObj ect(HandleRef
handle, Int32 timeout)
at
System.CodeDom.Compiler.Executor.ExecWaitWithCaptu reUnimpersonated(IntPtr
userToken, String cmd, String currentDir, TempFileCollection tempFiles,
String& outputName, String& errorName, String trueCmdLine)
at System.CodeDom.Compiler.Executor.ExecWaitWithCaptu re(IntPtr
userToken, String cmd, String currentDir, TempFileCollection tempFiles,
String& outputName, String& errorName, String trueCmdLine)
at System.CodeDom.Compiler.CodeCompiler.Compile(Compi lerParameters
options, String compilerDirectory, String compilerExe, String
arguments, String& outputFile, Int32& nativeReturnValue, String
trueArgs)
at
System.CodeDom.Compiler.CodeCompiler.FromFileBatch (CompilerParameters
options, String[] fileNames)
at
System.CodeDom.Compiler.CodeCompiler.FromSourceBat ch(CompilerParameters
options, String[] sources)
at
System.CodeDom.Compiler.CodeCompiler.FromSource(Co mpilerParameters
options, String source)
at
System.CodeDom.Compiler.CodeCompiler.System.CodeDo m.Compiler.ICodeCompiler.CompileAssemblyFromSource (CompilerParameters
options, String source)
at System.Xml.Serialization.Compiler.Compile()
at System.Xml.Serialization.TempAssembly..ctor(XmlMap ping[]
xmlMappings)
at System.Xml.Serialization.XmlSerializer.FromMapping s(XmlMapping[]
mappings)
at System.Web.Services.Protocols.SoapClientType..ctor (Type type)
at System.Web.Services.Protocols.SoapHttpClientProtoc ol..ctor()
at Microsoft.Crm.Platform.Proxy.CRMActivity..ctor()
at c360.WebConnect.CrmEntities.ᜀ(ICredentials A_0, CUserAuth A_1,
String A_2, String A_3, String A_4, String A_5, String A_6, String A_7,
String A_8, String A_9, String A_10, HttpContext A_11)
at c360.WebConnect.CrmEntities.ᜁ(ICredentials A_0, CUserAuth A_1,
String A_2, String A_3, String A_4, String A_5, String A_6, String A_7,
String A_8, String A_9, String A_10, HttpContext A_11)

Nov 19 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
I think that when your response ends all threads that you spawned get
aborted. You could try calling Response.Redirect("success.aspx",false) and
see if that helps. The false at the end tells asp.net to not abort the
thread.
Nov 19 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.