Some Spotfire Server may have system environment variable CLASSPATH already being set and pointing to jars used by other products. These jars may conflict with Spotfire Server and hence though the TSS service starts successfully but may not be functional.

The CLASSPATH defines the path, to find third-party and user-defined classes that are not extensions or part of the Java platform. 

The embedded Tomcat with the TIBCO Spotfire Server is dependent on the classes it has in its own location. Adding other Classpath variables for anything from elsewhere will get class collisions etc.
The reason the scripts (setenv.bat file for windows and setenv.sh file for Linux environment) refer to the "global" CLASSPATH is for the cases where we assume that only the Spotfire Server application is using that Classpath variable, and Spotfire is using a different JAVA instead of the embedded JAVA.



For cases where the Classpath is used by different applications, and to avoid a class collision you need to comment out that use of the global CLASSPATH and only use the paths set within the tomcat folder (<installation_directory> \tomcat\bin\setenv.bat, use setenv.sh in case of LINUX). Please refer to the below lines for your reference.

The solution is to modify setenv.bat as below to ignore  system environment variable CLASSPATH and re-install TSS service once again.

before:

if CLASSPATH == "" (set CLASSPATH=D:\tibco\tss\10.10.6\tomcat\spotfire-boot-lib\*) else (set CLASSPATH=%CLASSPATH%;D:\tibco\tss\10.10.6\tomcat\spotfire-boot-lib\*)

aflter:

if CLASSPATH == "" (set CLASSPATH=D:\tibco\tss\10.10.6\tomcat\spotfire-boot-lib\*) else (set CLASSPATH=D:\tibco\tss\10.10.6\tomcat\spotfire-boot-lib\*)

How Global CLASSPATH behaves when any other Product is installed on the same machine as the TIBCO Spotfire Server is Installed.