Differences

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

--- troubleshooting:diagnosing_connection_problems [2021/09/01 01:08] – [Check TapeTrack Service is running.] Scott Cunliffe
+++ troubleshooting:diagnosing_connection_problems [2025/01/21 22:07] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ======Diagnosing Connection Problems======
-=====Check  TapeTrack Service is running.=====
+=====Check  TapeTrack Service is running=====
-Service is running.
+Check the status of the TapeTrack Framework Server by running the following commands (operating system dependant) directly from the server the TapeTrack is installed on.
+==== Windows ====
+From a [[technote:commandline|command prompt]] run:
 <code>
-C:\WINDOWS\system32>sc query "TMSS10SVC"
+sc query "TMSS10SVC"
+</code>
+Service is running.
+<code>
 SERVICE_NAME: TMSS10SVC
         TYPE               : 10  WIN32_OWN_PROCESS
@@ Line 22: / Line 30: @@
 <code>
-C:\Users\diffl>sc query "TMSS10SVC"
 SERVICE_NAME: TMSS10SVC
         TYPE               : 10  WIN32_OWN_PROCESS
@@ Line 32: / Line 38: @@
         WAIT_HINT          : 0x0
-/code>
+</code>
-Attempt to [[server:start_stop|start the Framework Server]].
+If the Framework Server is not running, attempt to [[server:start_stop|start the Framework Server]] and then check your connection again.
-=====Ping with TMSS10Ping=====
+If the Framework Server wont start see [[troubleshooting:Rebuild Database Environment Files]].
-Ping the TapeTrack Framework Server with TMSS10Ping, using localhost if run on the same server or the IP or DNS of the server if run from another computer.
+If the Framework Server still wont start see [[server:reload|Reloading Server]]
+==== Linux  ====
+From a command prompt run:
+<code>
+systemctl list-units --type=service
+</code>
+Look through the output to find the ''tapetrack.service'' and the status next to it.
+Service is running
+<code>
+tapetrack.service                  loaded active running SYSV: TapeTrack server daemon
+</code>
+Service is not running
+<code>
+tapetrack.service                  loaded failed failed  SYSV: TapeTrack server daemon
+</code>
+If the Framework Server is not running, attempt to [[server:start_stop#linux|start the Framework Server]] and then check your connection again.
+=====Ping with TMSS10Ping=====
+If the TapeTrack Framework Server is running, use [[cli:tmss10ping|TMSS10Ping]] to check the connection to the server.
+Ping the TapeTrack Framework Server with [[cli:tmss10ping|TMSS10Ping]], using localhost on the server that TapeTrack Framework Server is installed on with:
 <code>
 C:\WINDOWS\system32>TMSS10Ping localhost
+</code>
+Successful connection will return packets and display as shown below.
+<code>
 bytes from 127.0.0.1: seq=1 time=6.00 ms
 bytes from 127.0.0.1: seq=2 time=0.00 ms
@@ Line 51: / Line 91: @@
 </code>
+Unsuccessful connection returns
+<code>
+TMSS10Ping: Connect to TapeTrack Server failed: WSAError(10061)
+</code>
+An unsuccessful connection from the computer TapeTrack Framework Server is installed on (localhost), while the TapeTrack Framework Server is running, suggests a port problem and should be referred to your network department to remedy the problem.
+A successful connection from localhost but not from client computers suggests a firewall issue not letting TapeTrack communications through and should be referred to your network department to remedy the problem.
 =====Check TapeTrack is listening on port 5000.=====
 <code>
@@ Line 69: / Line 118: @@
 If you do not have access to change the Windows Firewall rules check with your Windows Admin team.
+{{tag> server troubleshooting connection }}