When setting Spotfire server authentication to Windows NT, executing CLI commands result in error when running the graphical configuration tool on a local computer (non Spotfire server machine)

When setting Spotfire server authentication to Windows NT, executing CLI commands result in error when running the graphical configuration tool on a local computer (non Spotfire server machine)

book

Article ID: KB0081877

calendar_today

Updated On:

Products Versions
Spotfire Server 7.6, 7.7

Description

After executing a CLI command when running the graphical configuration tool on a local computer (non Spotfire server machine) it throws the following error:
------------------
Exception in thread "main" java.lang.NoClassDefFoundError: com/spotfire/server/util/win/WinConnector
at com.spotfire.server.userdir.ProviderFactory.createWindowsProvider(ProviderFactory.java:192)
at com.spotfire.server.userdir.ProviderFactory.createWindowsProvider(ProviderFactory.java:151)
at com.spotfire.server.userdir.UserDirectoryImpl.<init>(UserDirectoryImpl.java:169)
at com.spotfire.server.config.tool.AbstractUserDirectoryCommand.run(AbstractUserDirectoryCommand.java:89)
at com.spotfire.server.config.tool.ConfigApp.executeCommand(ConfigApp.java:369)
at com.spotfire.server.config.tool.ConfigApp.main(ConfigApp.java:458)
Caused by: java.lang.ClassNotFoundException: com.spotfire.server.util.win.WinConnector
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
... 6 more

-------------------

Issue/Introduction

For Spotfire Server 7.6 and 7.7, when executing CLI commands (e.g. 'export-library-content', 'enable-user' etc.) will result in an error when running the graphical configuration tool on a local computer (non Spotfire server machine). This issue happens when setting Spotfire Server authentication to Windows NT.

Resolution

The reason for this error is that not all classes related to Windows authentication are packaged in the configuration tool on the non Spotfire server machine. A workaround for a non Spotfire server machine is to add the missing classes to the unpacked spotfireconfigtool.

- Once you run the spotfireconfigtool.jar on the non Spotfire server machine, you get a directory structure (For example,  .\spotfireconfigtool/lib).

- In this directory all needed classes need to be present.

- You need to add the missing classes from the Spotfire server installation directory from your actual Spotfire server machine.
  For example,  <server installation root>/tomcat/webapps/spotfire/WEB-INF/lib

- There are several JAR files, the one which is lacking for this issue  is the "spotfire-native.jar".

- Copy this "spotfire-native.jar" file to the lib directory above (on the non Spotfire server machine) and execute the command.

- You also need to copy DLL file SfWinCon.dll  from <server installation root>/tomcat/bin/SfWinCon.dll to the lib directory above (on the non Spotfire server machine).