The GOC network Hub was restricting the network speed.
Symptom
Network Transmission Time is Slow. Takes 1/2 hour to transfer 1 series to the PACS. See long description The system is a 1.5T with Excite, running 11.0 M4 software. Network transfer is really slow. Sending an exam to the PACS and it took 1/2 hour for 1 series. We also see some packet loss when pinging the PACS (see results below). The FE connected his laptop to the hospital network port and was able to ping with no packet loss. It appears the problem is in the GOC. {sdc@VHALASMR2}[3] cd ~sdc/Prefs {sdc@VHALASMR2}[4] more SdCRHosts 10.176.12.13? vhalasnwg2 # 1 104 VHALASNWG2? PACS? 0 1 1 0 {sdc@VHALASMR2}[5] ping -s 1024 10.176.12.13 PING 10.176.12.13 (10.176.12.13) from 10.176.12.31 : 1024(1052) bytes of data. 1032 bytes from 10.176.12.13: icmp_seq=1 ttl=255 time=0.918 ms 1032 bytes from 10.176.12.13: icmp_seq=2 ttl=255 time=0.919 ms 1032 bytes from 10.176.12.13: icmp_seq=3 ttl=255 time=0.824 ms 1032 bytes from 10.176.12.13: icmp_seq=7 ttl=255 time=0.914 ms 1032 bytes from 10.176.12.13: icmp_seq=8 ttl=255 time=0.911 ms 1032 bytes from 10.176.12.13: icmp_seq=9 ttl=255 time=1.03 ms 1032 bytes from 10.176.12.13: icmp_seq=10 ttl=255 time=0.900 ms 1032 bytes from 10.176.12.13: icmp_seq=11 ttl=255 time=1.02 ms 1032 bytes from 10.176.12.13: icmp_seq=14 ttl=255 time=0.887 ms 1032 bytes from 10.176.12.13: icmp_seq=15 ttl=255 time=0.886 ms 1032 bytes from 10.176.12.13: icmp_seq=17 ttl=255 time=0.881 ms 1032 bytes from 10.176.12.13: icmp_seq=18 ttl=255 time=0.880 ms 1032 bytes from 10.176.12.13: icmp_seq=19 ttl=255 time=0.843 ms 1032 bytes from 10.176.12.13: icmp_seq=21 ttl=255 time=0.837 ms 1032 bytes from 10.176.12.13: icmp_seq=22 ttl=255 time=0.947 ms 1032 bytes from 10.176.12.13: icmp_seq=23 ttl=255 time=0.900 ms 1032 bytes from 10.176.12.13: icmp_seq=24 ttl=255 time=0.895 ms --- 10.176.12.13 ping statistics --- 25 packets transmitted, 17 received, 32% loss, time 24041ms <--- 32% packet loss! Round trip times look slightly higher rtt min/avg/max/mdev = 0.824/0.905/1.034/0.066 ms than expected as well.
Error message
11017 Failure to deinit DCM DCM has not been initialized (101) 11002 DCM low level error: Application error (505): unknown error - probable r emote abort (175) 11002 Host: BAY2OC0 Process: dcserver File: dcscommon.c Line: 227 DCM low level error: Application error (505): unknown error - probable remote abort (175)
Applies to
- Models
- Excite, Signa
- Product
- Profile with Excite
- Software
- Profile5 Applies to Profile5 (Excite) only. Profile5 is 12.x based software, not ProfileHD.
- Component
- 2272740-3 8 PORT 10/100 INTEL HUB SERVICE KIT 2272740-3 8 PORT 10/100 INTEL HUB SERVICE KIT.
- Area
- MR
Full cause & step-by-step resolution
The complete cause analysis, the step-by-step remedy for this GE Healthcare MR issue are available to FSELIB subscribers — re-authored, web-first, searchable.
7-day free trial · no credit card required
Related GE Healthcare MR issues
- Running grafidy3, and find there are spikes on the waveforms in the manual prescan display, both windows.
- TPS/MGD fails to download or reset. mgd_term windows fail to mount file system.
- Fails to Scan with TORSO Coil.
- The Carriage Fails to Advance to Latch to the Table and to Retract When it is Raised, Undocked or Lowered.
- AE title has changed on destination host.
- Unable to Load Applications Software during restoreinfo Due to Corrupt saveinfo Disk.