Printer FriendlyEmail Article Link

Spirent Testcenter: Crash frequently with Windows 2008 server R2 standard version.

Answer
  • 6/7/2012
    • It was reported that STC lost connection frequently. They are using windows 2008 server R2 standard version. To locate this problem, here are the following area to be looked at:
      • 1. networking issues --> please check the network between chassis and PC e.g. firewall
      • 2. Chassis instability --> please get the chassis and test module logs
      • 3. PC network link issue --> please look into the Windows event logs if you find an network link down event
      • 4. Any other PC events that could cause this instability e.g. windows or firewall upgrades
    • From customer's exception log, the following PC events logs were found:
      • 23:50:57.904 INFO 2776     - fmwk.bll.core.utils - Displaying contents of windows Application event log...
      • 23:50:57.904 ERROR 2776     - fmwk.bll.core.utils - RegQueryValueEx() failed for key = System\CurrentControlSet\Services\EventLog\Application\WinMgmt, value = EventMessageFile
      • 23:50:57.904 ERROR 2776     - fmwk.bll.core.utils - RegQueryValueEx() failed for key = System\CurrentControlSet\Services\EventLog\Application\WinMgmt, value = EventMessageFile
      • 23:50:57.904 ERROR 2776     - fmwk.bll.core.utils - RegQueryValueEx() failed for key = System\CurrentControlSet\Services\EventLog\Application\WinMgmt, value = EventMessageFile
      • 23:50:57.904 ERROR 2776     - fmwk.bll.core.utils - RegQueryValueEx() failed for key = System\CurrentControlSet\Services\EventLog\Application\WinMgmt, value = EventMessageFile
      • 23:50:57.904 ERROR 2776     - fmwk.bll.core.utils - RegQueryValueEx() failed for key = System\CurrentControlSet\Services\EventLog\Application\WinMgmt, value = EventMessageFile
      • 23:50:57.904 ERROR 2776     - fmwk.bll.core.utils - RegQueryValueEx() failed for key = System\CurrentControlSet\Services\EventLog\Application\WinMgmt, value = EventMessageFile
    • From these information we found that this issue was caused by duplicate IP address in customer's network and it cause the PC lost connection frequently.
  • 2/7/2019 - CIPCD-15062/CIPCD-15011 
    • Engineering investigated the logs.
      • The symptoms looks like CIPCD-15062/CIPCD-15011. ACE recv_n() failed with error 10053 and 10054.
        19/03/13 06:54:54.400 ERROR - [PeerSocket::ReadData] ACE recv_n() failed on slot = 2, ccpu = 7 with error 10054, Unknown error.
        19/03/13 06:54:54.400 ERROR - [PeerSocket::ReadData] ACE recv_n() failed on slot = 2, ccpu = 6 with error 10054, Unknown error.
        19/03/13 06:54:54.400 ERROR - [PeerSocket::ReadData] ACE recv_n() failed on slot = 2, ccpu = 5 with error 10054, Unknown error.
        19/03/13 06:54:54.400 ERROR - [PeerSocket::ReadData] ACE recv_n() failed on slot = 2, ccpu = 8 with error 10054, Unknown error.
      • Line 23036: 19/02/27 22:25:40.353 ERROR - [PeerSocket::ReadData] ACE recv_n() failed on slot = 2, ccpu = 7 with error 10053, Unknown error.
      • Line 23045: 19/02/27 22:25:40.355 ERROR - [PeerSocket::ReadData] ACE recv_n() failed on slot = 2, ccpu = 5 with error 10053, Unknown error.
      • Line 23054: 19/02/27 22:25:40.358 ERROR - [PeerSocket::ReadData] ACE recv_n() failed on slot = 2, ccpu = 8 with error 10053, Unknown error.
      • Line 23055: 19/02/27 22:25:40.359 ERROR - [PeerSocket::ReadData] ACE recv_n() failed on slot = 2, ccpu = 6 with error 10053, Unknown error.
    • Suggest customer to upgrade to 4.96 as well as apply the DisableDHCPMediaSense registry patch
      • Steps of Windows registry DisableDHCPMediaSense:
        • Start the registry editor (regedit.exe)
        • Move to      HKEY_LOCAL_MACHINE
        • Right click  , go      to EXPORT. Save HKEY_LOCAL_MACHINE to a file 
        • Move to      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters.
        • From the Edit menu      select New - DWORD value.
        • Enter a name of DisableDHCPMediaSense      and press Enter.
        • Double click the new      value and set to 1.
        • Click OK.
        • Reboot the computer.
  • 4/3/2019 - SR-01370210 (v4.94)
    • The issue is introduced by a Microsoft bug - https://support.microsoft.com/en-us/help/981344/an-application-may-receive-the-10054-error-when-the-application-receiv.
      • Please make sure the follow update has been installed on customer machine.
      • Issue seen in a fresh install of Windows Server 2008 and the issue’s been fixed after the hotfix been patched.
      • And please check the registry setting on customer machine.
      • Open regedit, go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters.
      • There should be the following 3 registry entries. They are set as long as STC application installed.

Product : Spirent TestCenter