000030522 - Chimney offload network settings creates problems with SQL Server calls in RSA Archer

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000030522
Applies ToRSA Product Set: Archer
RSA Product/Service Type: Chimney
Platform: Windows
Platform (Other): SQL Server 2008
IssueWhen the Chimney offload is turned on in SQL Server (app and service boxes) some of the pages won't display the ellipsis and calendar controls. Below is an example from the Archer log:
 
<E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent">
<System xmlns="http://schemas.microsoft.com/2004/06/windows/eventlog/system">
<EventID>0</EventID>
<Type>3</Type>
<SubType Name="Error">0</SubType>
<Level>2</Level>
<TimeCreated SystemTime="2015-04-02T18:40:41.6434899Z" />
<Source Name="Archer.Web" />
<Correlation ActivityID="{00000000-0000-0000-0000-000000000000}" />
<Execution ProcessName="w3wp" ProcessID="6264" ThreadID="57" />
<AssemblyVersion>5.4.10200.1013</AssemblyVersion>
<Channel />
<Computer>VSIN8U0873</Computer>
</System>
<ApplicationData>
<TraceData>
<DataItem>
<TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
<TraceIdentifier>Archer.Web</TraceIdentifier>
<LogReferenceId>040215-184041-6122</LogReferenceId>
<Description>A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.)
SQL statement: usp_ui_session_state @userToken = '4FBC73790B7CD8B8A2B888B54700CC70', @requestId = 5dbf0967-e22e-49c2-8c9f-4cfc54b550dc, @state = System.Byte[], @date = '4/2/2015 6:40:22 PM'</Description>
<AppDomain>/LM/W3SVC/1/ROOT/Archer-2-130724713051589687</AppDomain>
<ContextData>
<BaseUrl>https://controllink-uat-new.jpmchase.net/archer/foundation/Workspace.aspx</BaseUrl>
<requestUrl>
</requestUrl>
</ContextData>
<Exception>
<ExceptionType>ArcherTech.Kernel.Utility.Data.ArcherDbException, ArcherTech.Kernel, Version=5.4.10200.1013, Culture=neutral, PublicKeyToken=null</ExceptionType>
<Message>A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.)
SQL statement: usp_ui_session_state @userToken = '4FBC73790B7CD8B8A2B888B54700CC70', @requestId = 5dbf0967-e22e-49c2-8c9f-4cfc54b550dc, @state = System.Byte[], @date = '4/2/2015 6:40:22 PM'</Message>
<Source>ArcherTech.Kernel</Source>
<ContextData>
<ASPIMPERSONATING>
</ASPIMPERSONATING>
</ContextData>
<StackTrace> at ArcherTech.Kernel.Utility.Data.ArcherSqlDatabase.WrapDatabaseCall(DbCommand command, Action methodToWrap)
at ArcherTech.Kernel.Utility.Data.ArcherSqlDatabase.ExecuteNonQuery(DbCommand command)
at ArcherTech.Kernel.DataSource.Db.SessionStateDataSource.Save(SessionState state)
at ArcherTech.Kernel.Managers.SessionStateManager.Save(SessionContext sessionContext, SessionState state)
at ArcherTech.Web.UI.RequestStateManager.DBRequestStatePersister.Save(RequestStateHolder holder)
at ArcherTech.Web.UI.RequestStateManager.AfterProcessRequest()
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&amp; completedSynchronously)</StackTrace>
<InnerException>
<ExceptionType>System.ComponentModel.Win32Exception, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
<Message>The semaphore timeout period has expired</Message>
<Source />
<StackTrace />
</InnerException>
</Exception>
</TraceRecord>
</DataItem>
</TraceData>
</ApplicationData>
</E2ETraceEvent>
<E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent">
<System xmlns="http://schemas.microsoft.com/2004/06/windows/eventlog/system">
<EventID>0</EventID>
<Type>3</Type>
<SubType Name="Error">0</SubType>
<Level>2</Level>
<TimeCreated SystemTime="2015-04-02T18:40:41.6434899Z" />
<Source Name="Archer.Web" />
<Correlation ActivityID="{00000000-0000-0000-0000-000000000000}" />
<Execution ProcessName="w3wp" ProcessID="6264" ThreadID="57" />
<AssemblyVersion>5.4.10200.1013</AssemblyVersion>
<Channel />
<Computer>VSIN8U0873</Computer>
</System>
<ApplicationData>
<TraceData>
<DataItem>
<TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
<TraceIdentifier>Archer.Web</TraceIdentifier>
<LogReferenceId>040215-184041-6122</LogReferenceId>
<Description>A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.)
SQL statement: usp_ui_session_state @userToken = '4FBC73790B7CD8B8A2B888B54700CC70', @requestId = 5dbf0967-e22e-49c2-8c9f-4cfc54b550dc, @state = System.Byte[], @date = '4/2/2015 6:40:22 PM'</Description>
<AppDomain>/LM/W3SVC/1/ROOT/Archer-2-130724713051589687</AppDomain>
<ContextData>
<BaseUrl>https://controllink-uat-new.jpmchase.net/archer/foundation/Workspace.aspx</BaseUrl>
<requestUrl>
</requestUrl>
</ContextData>
<Exception>
<ExceptionType>ArcherTech.Kernel.Utility.Data.ArcherDbException, ArcherTech.Kernel, Version=5.4.10200.1013, Culture=neutral, PublicKeyToken=null</ExceptionType>
<Message>A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.)
SQL statement: usp_ui_session_state @userToken = '4FBC73790B7CD8B8A2B888B54700CC70', @requestId = 5dbf0967-e22e-49c2-8c9f-4cfc54b550dc, @state = System.Byte[], @date = '4/2/2015 6:40:22 PM'</Message>
<Source>ArcherTech.Kernel</Source>
<ContextData>
<ASPIMPERSONATING>
</ASPIMPERSONATING>
</ContextData>
<StackTrace> at ArcherTech.Kernel.Utility.Data.ArcherSqlDatabase.WrapDatabaseCall(DbCommand command, Action methodToWrap)
at ArcherTech.Kernel.Utility.Data.ArcherSqlDatabase.ExecuteNonQuery(DbCommand command)
at ArcherTech.Kernel.DataSource.Db.SessionStateDataSource.Save(SessionState state)
at ArcherTech.Kernel.Managers.SessionStateManager.Save(SessionContext sessionContext, SessionState state)
at ArcherTech.Web.UI.RequestStateManager.DBRequestStatePersister.Save(RequestStateHolder holder)
at ArcherTech.Web.UI.RequestStateManager.AfterProcessRequest()
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&amp; completedSynchronously)</StackTrace>
<InnerException>
<ExceptionType>System.ComponentModel.Win32Exception, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
<Message>The semaphore timeout period has expired</Message>
<Source />
<StackTrace />
</InnerException>
</Exception>
</TraceRecord>
</DataItem>
</TraceData>
</ApplicationData>
</E2ETraceEvent>
<E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent">
<System xmlns="http://schemas.microsoft.com/2004/06/windows/eventlog/system">
<EventID>0</EventID>
<Type>3</Type>
<SubType Name="Error">0</SubType>
<Level>2</Level>
<TimeCreated SystemTime="2015-04-02T18:40:41.6434899Z" />
<Source Name="Archer.Web" />
<Correlation ActivityID="{00000000-0000-0000-0000-000000000000}" />
<Execution ProcessName="w3wp" ProcessID="6264" ThreadID="57" />
<AssemblyVersion>5.4.10200.1013</AssemblyVersion>
<Channel />
<Computer>VSIN8U0873</Computer>
</System>
<ApplicationData>
<TraceData>
<DataItem>
<TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
<TraceIdentifier>Archer.Web</TraceIdentifier>
<LogReferenceId>040215-184041-6122</LogReferenceId>
<Description>A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.)
SQL statement: usp_ui_session_state @userToken = '4FBC73790B7CD8B8A2B888B54700CC70', @requestId = 5dbf0967-e22e-49c2-8c9f-4cfc54b550dc, @state = System.Byte[], @date = '4/2/2015 6:40:22 PM'</Description>
<AppDomain>/LM/W3SVC/1/ROOT/Archer-2-130724713051589687</AppDomain>
<ContextData>
<BaseUrl>https://controllink-uat-new.jpmchase.net/archer/foundation/Workspace.aspx</BaseUrl>
<requestUrl>
</requestUrl>
</ContextData>
<Exception>
<ExceptionType>ArcherTech.Kernel.Utility.Data.ArcherDbException, ArcherTech.Kernel, Version=5.4.10200.1013, Culture=neutral, PublicKeyToken=null</ExceptionType>
<Message>A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.)
SQL statement: usp_ui_session_state @userToken = '4FBC73790B7CD8B8A2B888B54700CC70', @requestId = 5dbf0967-e22e-49c2-8c9f-4cfc54b550dc, @state = System.Byte[], @date = '4/2/2015 6:40:22 PM'</Message>
<Source>ArcherTech.Kernel</Source>
<ContextData>
<ASPIMPERSONATING>
</ASPIMPERSONATING>
</ContextData>
<StackTrace> at ArcherTech.Kernel.Utility.Data.ArcherSqlDatabase.WrapDatabaseCall(DbCommand command, Action methodToWrap)
at ArcherTech.Kernel.Utility.Data.ArcherSqlDatabase.ExecuteNonQuery(DbCommand command)
at ArcherTech.Kernel.DataSource.Db.SessionStateDataSource.Save(SessionState state)
at ArcherTech.Kernel.Managers.SessionStateManager.Save(SessionContext sessionContext, SessionState state)
at ArcherTech.Web.UI.RequestStateManager.DBRequestStatePersister.Save(RequestStateHolder holder)
at ArcherTech.Web.UI.RequestStateManager.AfterProcessRequest()
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&amp; completedSynchronously)</StackTrace>
<InnerException>
<ExceptionType>System.ComponentModel.Win32Exception, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
<Message>The semaphore timeout period has expired</Message>
<Source />
<StackTrace />
</InnerException>
</Exception>
</TraceRecord>
</DataItem>
</TraceData>
</ApplicationData>
</E2ETraceEvent>

The network stack traces reveal that some of the SQL Server stored procedures have returned the record sets but the result did not reach the application boxes.
ResolutionTCP Chimney has been known to cause issues with SQL Server systems such as general network errors and working set trimming, as documented by Microsoft in the link below.
If you observe a similar pattern and suspect TCP Chimney, you may wish to disable TCP Chimney to provide immediate relief.
Another option is to follow up with your network adapter vendor to see if they have an updated driver that will address the problem and allow for use of TCP Chimney.
NotesFor additional information see http://support.microsoft.com/default.aspx?scid=kb;EN-US;948496.

Attachments

    Outcomes