Product: TIBCO Spotfire®
Spotfire Web Player service fails to start after deployment of Revvity Signals Lead Discovery Premium 2.0.
Environment:
TIBCO Spotfire Server 7.11 and higher
Revvity Signals Lead Discovery Premium 2.0 and higher
Problem Description:
After Revvity Signals Lead Discovery Premium 2.0 is deployed on Spotfire Server and Web Player instance is updated, Web Player service fails to start. Spotfire web admin console displays error:
Details: Status notified as FAILED. Exited while initializing. Recent Logs: File name: 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' at System.ModuleHandle.ResolveMethod(RuntimeModule module, Int32 methodToken, IntPtr* typeInstArgs, Int32 typeInstCount, IntPtr* methodInstArgs, Int32 methodInstCount) at System.ModuleHandle.ResolveMethodHandleInternalCore(RuntimeModule module, Int32 methodToken, IntPtr[] typeInstantiationContext, Int32 typeInstCount, IntPtr[] methodInstantiationContext, Int32 methodInstCount) at System.ModuleHandle.ResolveMethodHandleInternal(RuntimeModule module, Int32 methodToken, RuntimeTypeHandle[] typeInstantiationContext, RuntimeTypeHandle[] methodInstantiationContext) at System.Reflection.CustomAttributeData..ctor(RuntimeModule scope, CustomAttributeRecord caRecord) at System.Reflection.CustomAttributeData.GetCustomAttributes Attempt to communicate with service was unsuccessful.
Resolution
This problem usually occurs because an older, unsupported version of .NET framework is installed on Spotfire Node Manager machine. Lead Discovery Premium 2.0 requires Microsoft .NET Framework 4.7.2 or higher.
To resolve the problem, download .NET 4.7.2, or more recent version, and install it on Node Manager machine. A full machine OS reboot will be required, but no further configuration changes will be necessary. After reboot, Web Player service should start without any errors.
Note: similar issue might occur on end user's machines that run Spotfire Analyst client with Lead Discovery Premium 2.0. In most cases, updating .NET version will resolve the problem.
If you're still seeing this or similar errors after updating .NET, please contact Support for assistance.
Comments
0 comments
Article is closed for comments.