Spotfire Node Manager or Web Player fail to start after upgrade

There could be various issues that could cause Spotfire Node Manager service and Web Player service instance to fail to start after an upgrade. The first step is always to check system requirements and make sure that Node Manager machine meets all Web Player requirements:

https://docs.tibco.com/pub/spotfire/general/sr/sr/topics/tibco_spotfire_web_player.html

One example of a system requirement issue is an outdated .NET framework. When this requirement is not met, the following error might be found in nm.log file:

INFO 2024-02-08T18:41:36,097+0000 [] nodemanager.control.DeploymentCommandCommunicator: Process: * Configuring service.
INFO 2024-02-08T18:41:36,097+0000 [] nodemanager.control.DeploymentCommandCommunicator: Process: . Using command: '"D:\tibco\tsnm\12.0.8\nm\services\webworker-56.7.18917.4154-9043e743-7b17-4216-b04e-a0d5cf963351\Tools\Update\Spotfire.Dxp.Web.UpgradeTool.exe" -configOnly -webRootPath "D:\tibco\tsnm\12.0.8\nm\services\webworker-56.7.18917.4154-9043e743-7b17-4216-b04e-a0d5cf963351\Tools\Update\..\.."'
INFO 2024-02-08T18:41:36,252+0000 [] nodemanager.control.DeploymentCommandCommunicator: Process: ERROR: '-48' - .NET 4.8 not installed, so exit script
WARN 2024-02-08T18:41:36,262+0000 [4959c015-81f2-4161-8d80-41c3dc14a6f0] nodemanager.control.DeploymentCommandCommunicator: Step 7: Failure to perform upgrade on service. Process exit code: -48
...
INFO 2024-02-08T18:41:36,522+0000 [] server.nodemanager.ServiceMonitor: Notifying about service: 5a725226-7ecd-4e5c-8483-7703f6ba091b in state FAILED/STARTING. Last status message: The service exited with error code -2146232576.

To resolve this issue, please update .NET version on Node Manager machine and then restart Node Manager service. Here is another article with more information about this issue:

https://support.revvitysignals.com/hc/en-us/articles/8059381977108-TIBCO-Spotfire-Webplayer-service-installation-may-fail-post-upgrade-to-11-5-0-and-above-versions

It's also possible to run into System.IO.FileNotFoundException errors in nm.log or service-<ID>-stdout.log:

Example 1:

ERROR 2024-02-08T19:26:56,148+0000 [] server.nodemanager.ServiceMonitor: (FAILED) Process 33abfeca-0cd7-4629-be94-d930e31055c4 notified. Next Status STARTING
INFO 2024-02-08T19:26:56,148+0000 [] server.nodemanager.ServiceMonitor: Notifying about service: 33abfeca-0cd7-4629-be94-d930e31055c4 in state FAILED/STARTING. Last status message: The service exited with error code -532462766. Recent Logs: Error:
Error: Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'Spotfire.Dxp.Internal, Version=56.7.18917.4154, Culture=neutral, PublicKeyToken=789861576bd64dc5' or one of its dependencies. The system cannot find the file specified.
Error: at Spotfire.Dxp.Worker.Host.Program.CreateProgramRunner()
Error: at Spotfire.Dxp.Worker.Host.Program.Main(String[] args)

Example 2:

INFO 2024-02-08T19:26:54,268+0000 [] 33abfeca-0cd7-4629-be94-d930e31055c4: Error:
INFO 2024-02-08T19:26:54,691+0000 [] 33abfeca-0cd7-4629-be94-d930e31055c4: Error: Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'Spotfire.Dxp.Internal, Version=56.7.18917.4154, Culture=neutral, PublicKeyToken=789861576bd64dc5' or one of its dependencies. The system cannot find the file specified.
INFO 2024-02-08T19:26:54,691+0000 [] 33abfeca-0cd7-4629-be94-d930e31055c4: Error:    at Spotfire.Dxp.Worker.Host.Program.CreateProgramRunner()
INFO 2024-02-08T19:26:54,691+0000 [] 33abfeca-0cd7-4629-be94-d930e31055c4: Error:    at Spotfire.Dxp.Worker.Host.Program.Main(String[] args)
ERROR 2024-02-08T19:26:56,143+0000 [] 33abfeca-0cd7-4629-be94-d930e31055c4: 33abfeca-0cd7-4629-be94-d930e31055c4 [WEB_PLAYER] process state switched to failure with exit value -532462766

The cause of these types of errors is usually external to Spotfire, but the most effective solution is usually a simple reinstall of Spotfire Node Manager by following these steps:

1. "Untrust" the problem Node Manager node in Spotfire Server's web admin console.
2. Stop Node Manager service in Windows' Services control panel and then uninstall it (on Node Manager machine).
3. Remove all contents of <install directory>\tsnm\ folder and then install Node Manager again.
4. Start Node Manager service in Windows' Services control panel.
5. Check Spotfire Server web admin console and "trust" the newly installed Node Manager node.

The FileNotFoundException errors could be thrown due to file system corruption issues or system security / anti-virus software preventing access to specific files. But, if the Windows account has sufficient privileges to manage the system and install new software, then a simple Node Manager reinstall usually resolves these types of issues.