TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools


troubleshooting:server_outages

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
troubleshooting:server_outages [2019/02/27 16:10] – created dcummingtroubleshooting:server_outages [2019/02/27 16:13] (current) – removed dcumming
Line 1: Line 1:
-Checked TapeTrack Service was running. 
-Pinged with TMSS10Ping 
-Checked TapeTrack was listening on port 5000. 
-C:\WINDOWS\system32>sc query "TMSS10SVC" 
  
-SERVICE_NAME: TMSS10SVC 
-        TYPE               : 10  WIN32_OWN_PROCESS 
-        STATE              : 4  RUNNING 
-                                (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN) 
-        WIN32_EXIT_CODE    : 0  (0x0) 
-        SERVICE_EXIT_CODE  : 0  (0x0) 
-        CHECKPOINT         : 0x0 
-        WAIT_HINT          : 0x0 
-C:\WINDOWS\system32>TMSS10Ping localhost 
-44 bytes from 127.0.0.1: seq=1 time=6.00 ms 
-44 bytes from 127.0.0.1: seq=2 time=0.00 ms 
-44 bytes from 127.0.0.1: seq=3 time=0.00 ms 
-44 bytes from 127.0.0.1: seq=4 time=0.00 ms 
- 
---- localhost TMSS10Ping statistics --- 
-4 packets transmitted 
-round-trip min/avg/max = 0.00/1.50/6.00 ms 
-netstat -abn | more 
-... 
-[svchost.exe] 
-  TCP    0.0.0.0:5000           0.0.0.0:             LISTENING 
- [TMSS10Server.exe] 
-... 
-In Ali's case: 
- 
-The service was running. 
-TMSS10Ping was blocking (hanging) 
-TapeTrack was on port 5000, which means it was up AND listening. 
-This is most definitely a firewall problem. 
troubleshooting/server_outages.1551283838.txt.gz · Last modified: 2025/01/21 22:07 (external edit)