6/30/2025 5:29:55 PM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss the use of the SalesLogix Web Platform, Client and Customer Portals, and the Application Architect (For version 7.2 and higher only). View the code of conduct for posting guidelines.
|
|
|
|
SLX Web platform keeps crashing the IIS Thread
Posted: 21 Mar 10 4:33 PM
|
we have version 7.5.1 running so maybe this is fixed in 7.5.2 but the event I see correlating to the IIS thread crashing is
Exception: System.InvalidOperationException
Message: SLXSystemPool cannot be initialized
StackTrace: at Sage.SalesLogix.SLXSystemPool.GetInstance()
at Sage.SalesLogix.SLXSystemProvider.PingClients(String alias, PingInfo[] pingInfo)
at Sage.SalesLogix.Web.SLXWebDataService.LicensePingingRoutine()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
And this only happens during high usage.. We have SLX web running in a webfarm of 4 servers and during the weekends and nights nothing crashes but during the weekdays each server reports this error and IIS crashes at least 4 maybe 5 time a day
Through WINDBG I found that this exception is happening at the point someone is trying to login
01cfefb0 7c82860c [HelperMethodFrame_PROTECTOBJ: 01cfefb0] System.RuntimeType.InvokeDispMethod(System.String, System.Reflection.BindingFlags, System.Object, System.Object[], Boolean[], Int32, System.String[])
01cff038 7928e3a2 System.RuntimeType.InvokeMember(System.String, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object, System.Object[], System.Reflection.ParameterModifier[], System.Globalization.CultureInfo, System.String[])
01cff184 7973ebbd System.Type.InvokeMember(System.String, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object, System.Object[])
01cff19c 18cad888 Sage.SalesLogix.SLXSystemProvider.IsLicenseAvailable(Int32, System.String)
01cff1d4 18cad698 Sage.SalesLogix.Security.SLXWebHostLicenseProvider.GetLicense(System.ComponentModel.LicenseContext, System.Type, System.Object, Boolean)
01cff210 7a8d935a System.ComponentModel.LicenseManager.ValidateInternalRecursive(System.ComponentModel.LicenseContext, System.Type, System.Object, Boolean, System.ComponentModel.License ByRef, System.String ByRef)
01cff23c 7a8d925a System.ComponentModel.LicenseManager.ValidateInternal(System.Type, System.Object, Boolean, System.ComponentModel.License ByRef)
01cff258 7a8d9478 System.ComponentModel.LicenseManager.Validate(System.Type, System.Object)
01cff270 175a2e84 Sage.SalesLogix.Web.SLXMembershipProvider.ValidateUser(System.String, System.String)
01cff2dc 667e95e1 System.Web.UI.WebControls.Login.AuthenticateUsingMembershipProvider(System.Web.UI.WebControls.AuthenticateEventArgs)
01cff2f4 667e9b28 System.Web.UI.WebControls.Login.OnAuthenticate(System.Web.UI.WebControls.AuthenticateEventArgs)
01cff30c 667e94bc System.Web.UI.WebControls.Login.AttemptLogin()
01cff320 667e9c1a System.Web.UI.WebControls.Login.OnBubbleEvent(System.Object, System.EventArgs)
01cff338 66095ee6 System.Web.UI.Control.RaiseBubbleEvent(System.Object, System.EventArgs)
01cff350 66799f4f System.Web.UI.WebControls.Button.OnCommand(System.Web.UI.WebControls.CommandEventArgs)
01cff368 66799d67 System.Web.UI.WebControls.Button.RaisePostBackEvent(System.String)
01cff380 66799f6b System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(System.String)
01cff388 66095d9e System.Web.UI.Page.RaisePostBackEvent(System.Web.UI.IPostBackEventHandler, System.String)
01cff394 66095cf5 System.Web.UI.Page.RaisePostBackEvent(System.Collections.Specialized.NameValueCollection)
01cff3a8 660a7f1e System.Web.UI.Page.ProcessRequestMain(Boolean, Boolean)
01cff500 660a77a4 System.Web.UI.Page.ProcessRequest(Boolean, Boolean)
01cff538 660a76d1 System.Web.UI.Page.ProcessRequest()
01cff570 660a7666 System.Web.UI.Page.ProcessRequestWithNoAssert(System.Web.HttpContext)
01cff57c 660a7642 System.Web.UI.Page.ProcessRequest(System.Web.HttpContext)
01cff590 172cdea6 ASP.login_aspx.ProcessRequest(System.Web.HttpContext)
01cff5a0 660adb16 System.Web.HttpApplication+CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
01cff5d4 6608132c System.Web.HttpApplication.ExecuteStep(IExecutionStep, Boolean ByRef)
01cff614 6608c5c3 System.Web.HttpApplication+ApplicationStepManager.ResumeSteps(System.Exception)
01cff664 660808ac System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(System.Web.HttpContext, System.AsyncCallback, System.Object)
01cff680 66083e1c System.Web.HttpRuntime.ProcessRequestInternal(System.Web.HttpWorkerRequest)
01cff6b4 66083ac3 System.Web.HttpRuntime.ProcessRequestNoDemand(System.Web.HttpWorkerRequest)
01cff6c4 66082c5c System.Web.Hosting.ISAPIRuntime.ProcessRequest(IntPtr, Int32)
01cff8d8 79f9811e [ContextTransitionFrame: 01cff8d8]
01cff90c 79f9811e [GCFrame: 01cff90c]
01cffa68 79f9811e [ComMethodFrame: 01cffa68]
OS Thread Id: 0x260 (11)
I don't know if the logging in method isn't thread safe or what's going on...
Any thoughts?
|
|
|
|
Re: SLX Web platform keeps crashing the IIS Thread
Posted: 22 Mar 10 3:38 AM
|
We have a similar situation when crystal reports are open for more than 20 Minutes and then a subreport is opened.
But I did not checked the log. In the end nowbody can use SLX at all. A reboot of IIS is helping.
We reported this to Sage, but have no defect right now.
We could reproduce this in 7.5.1 and 7.5.2 EVAL.
Does this help?
Best regards,
Lukas Richter
|
|
|
|
Re: SLX Web platform keeps crashing the IIS Thread
Posted: 22 Mar 10 3:49 PM
|
You have 4 servers, but how many instances per Server?
How many Concurrent Users do you have hitting each instance?
How much RAM do you have on the Servers?
If you have available RAM/CPU Cycles, keep on adding additional Instances per server.
|
|
|
|
Re: SLX Web platform keeps crashing the IIS Thread
Posted: 25 Mar 10 5:42 AM
|
Originally posted by Lukas Richter
We have a similar situation when crystal reports are open for more than 20 Minutes and then a subreport is opened.
But I did not checked the log. In the end nowbody can use SLX at all. A reboot of IIS is helping.
We reported this to Sage, but have no defect right now.
We could reproduce this in 7.5.1 and 7.5.2 EVAL.
Does this help?
Best regards,
Lukas Richter
|
|
There is a hotfix on SP2 for the Crystal Reports session dying issue..cant remember the number but take a look on the SLX support site. |
|
|
|
Re: SLX Web platform keeps crashing the IIS Thread
Posted: 25 Mar 10 5:46 AM
|
Originally posted by Shane
we have version 7.5.1 running so maybe this is fixed in 7.5.2 but the event I see correlating to the IIS thread crashing is
Exception: System.InvalidOperationException
Message: SLXSystemPool cannot be initialized
StackTrace: at Sage.SalesLogix.SLXSystemPool.GetInstance()
at Sage.SalesLogix.SLXSystemProvider.PingClients(String alias, PingInfo[] pingInfo)
at Sage.SalesLogix.Web.SLXWebDataService.LicensePingingRoutine()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
And this only happens during high usage.. We have SLX web running in a webfarm of 4 servers and during the weekends and nights nothing crashes but during the weekdays each server reports this error and IIS crashes at least 4 maybe 5 time a day
Through WINDBG I found that this exception is happening at the point someone is trying to login
01cfefb0 7c82860c [HelperMethodFrame_PROTECTOBJ: 01cfefb0] System.RuntimeType.InvokeDispMethod(System.String, System.Reflection.BindingFlags, System.Object, System.Object[], Boolean[], Int32, System.String[])
01cff038 7928e3a2 System.RuntimeType.InvokeMember(System.String, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object, System.Object[], System.Reflection.ParameterModifier[], System.Globalization.CultureInfo, System.String[])
01cff184 7973ebbd System.Type.InvokeMember(System.String, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object, System.Object[])
01cff19c 18cad888 Sage.SalesLogix.SLXSystemProvider.IsLicenseAvailable(Int32, System.String)
01cff1d4 18cad698 Sage.SalesLogix.Security.SLXWebHostLicenseProvider.GetLicense(System.ComponentModel.LicenseContext, System.Type, System.Object, Boolean)
01cff210 7a8d935a System.ComponentModel.LicenseManager.ValidateInternalRecursive(System.ComponentModel.LicenseContext, System.Type, System.Object, Boolean, System.ComponentModel.License ByRef, System.String ByRef)
01cff23c 7a8d925a System.ComponentModel.LicenseManager.ValidateInternal(System.Type, System.Object, Boolean, System.ComponentModel.License ByRef)
01cff258 7a8d9478 System.ComponentModel.LicenseManager.Validate(System.Type, System.Object)
01cff270 175a2e84 Sage.SalesLogix.Web.SLXMembershipProvider.ValidateUser(System.String, System.String)
01cff2dc 667e95e1 System.Web.UI.WebControls.Login.AuthenticateUsingMembershipProvider(System.Web.UI.WebControls.AuthenticateEventArgs)
01cff2f4 667e9b28 System.Web.UI.WebControls.Login.OnAuthenticate(System.Web.UI.WebControls.AuthenticateEventArgs)
01cff30c 667e94bc System.Web.UI.WebControls.Login.AttemptLogin()
01cff320 667e9c1a System.Web.UI.WebControls.Login.OnBubbleEvent(System.Object, System.EventArgs)
01cff338 66095ee6 System.Web.UI.Control.RaiseBubbleEvent(System.Object, System.EventArgs)
01cff350 66799f4f System.Web.UI.WebControls.Button.OnCommand(System.Web.UI.WebControls.CommandEventArgs)
01cff368 66799d67 System.Web.UI.WebControls.Button.RaisePostBackEvent(System.String)
01cff380 66799f6b System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(System.String)
01cff388 66095d9e System.Web.UI.Page.RaisePostBackEvent(System.Web.UI.IPostBackEventHandler, System.String)
01cff394 66095cf5 System.Web.UI.Page.RaisePostBackEvent(System.Collections.Specialized.NameValueCollection)
01cff3a8 660a7f1e System.Web.UI.Page.ProcessRequestMain(Boolean, Boolean)
01cff500 660a77a4 System.Web.UI.Page.ProcessRequest(Boolean, Boolean)
01cff538 660a76d1 System.Web.UI.Page.ProcessRequest()
01cff570 660a7666 System.Web.UI.Page.ProcessRequestWithNoAssert(System.Web.HttpContext)
01cff57c 660a7642 System.Web.UI.Page.ProcessRequest(System.Web.HttpContext)
01cff590 172cdea6 ASP.login_aspx.ProcessRequest(System.Web.HttpContext)
01cff5a0 660adb16 System.Web.HttpApplication+CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
01cff5d4 6608132c System.Web.HttpApplication.ExecuteStep(IExecutionStep, Boolean ByRef)
01cff614 6608c5c3 System.Web.HttpApplication+ApplicationStepManager.ResumeSteps(System.Exception)
01cff664 660808ac System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(System.Web.HttpContext, System.AsyncCallback, System.Object)
01cff680 66083e1c System.Web.HttpRuntime.ProcessRequestInternal(System.Web.HttpWorkerRequest)
01cff6b4 66083ac3 System.Web.HttpRuntime.ProcessRequestNoDemand(System.Web.HttpWorkerRequest)
01cff6c4 66082c5c System.Web.Hosting.ISAPIRuntime.ProcessRequest(IntPtr, Int32)
01cff8d8 79f9811e [ContextTransitionFrame: 01cff8d8]
01cff90c 79f9811e [GCFrame: 01cff90c]
01cffa68 79f9811e [ComMethodFrame: 01cffa68]
OS Thread Id: 0x260 (11)
I don't know if the logging in method isn't thread safe or what's going on...
Any thoughts?
|
|
Are users reporting outages? In 7.5.0 and 7.5.1 SLX had a habit of reporting almost anything as a major error when in reality no users are actually affected. I believe the error handling was updated in SP2 to stop that. I seem to recall that even a user putting in the wrong password would put a major error in the event logs, like "Cannot access SLXSystemPool, thread error." |
|
|
|
Re: SLX Web platform keeps crashing the IIS Thread
Posted: 25 Mar 10 10:29 AM
|
Yes we have this running as a webfarm load balanced between four servers. Each server is 2k3 and has 4 gigs of ram. When this error occurs iis physically crashes and our load balancer has to reroute traffic to one of the other 3 servers. Which typically will throw an error message for the user or cause a wait time of 30 seconds or so while iis crashes and the connection is rerouted.
As far as i know We aren't using CR. |
|
|
|
Re: SLX Web platform keeps crashing the IIS Thread
Posted: 25 Mar 10 11:03 AM
|
Originally posted by Raul A. Chavez
You have 4 servers, but how many instances per Server?
How many Concurrent Users do you have hitting each instance?
How much RAM do you have on the Servers?
If you have available RAM/CPU Cycles, keep on adding additional Instances per server.
|
|
What do you mean exactly by instances per server? We have one instance of the webDLL slxsystem service running on each server. Are you talking about running more slxsystem services or what? |
|
|
|
Re: SLX Web platform keeps crashing the IIS Thread
Posted: 25 Mar 10 12:56 PM
|
In each server, you could have multiple Sites running SLX Client on it, each one running on its own Application pool.
An SLX Instance typically has a max load of users (count would depend on usage, customizations, etc), but typically would use about 1 Gig of RAM.
To better handle resources, put less stress on each instance, it is wiser to create Multiple Instances on each server. You could probably have 3 Instance running on 4 Gig of RAM, making better use of RAM and CPU (specially if you have multiple CPU/Cores on your server).
And not only that you get better usage of your Hardware Investment, but you also reduce the number of affected users when an instance crashes. For instance, if you typically have 60 concurrent users on 3 instances, and one crashes, you loose 20 users, and the surviving Instances will get a heavier load (30 users) while the downed instance recovers. On the other hand, if you have now 60 users on 9 instance, a given crash affects 7 or 8 users, and the additional load per surviving instance would be about an extra user.
The biggest challenge may be how to Load Balance. I am not sure what technology you are using. If you are using the Windows Load Balancer you may have to look for options, but if you are using an External Load Balancer (e.g. F5) you may be able to Implement quite easily either with multiple Ports per Server of with Each Instance running on its own IP address.
Overall, this reduces the load per Instance, which typically reduces the number of crashes if they are due to the Instance system running out of resources. |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|