Product |
Version |
Spotfire Lead Discovery Premium |
All Versions |
Keywords: substructure search, Spotfire WebPlayer, Lead Discovery Premium, ChemDraw JS, structure rendering, licensing, NullReferenceException, GetQueryStructureImage, chemical structure, error resolution, troubleshooting, configuration, WebPlayer services, ChemCharts.
Description
Users may encounter errors when performing substructure searches in Spotfire WebPlayer, even though the search functionality appears to work. This article outlines steps to resolve this issue, which is often related to licensing configuration.
Common Error Message: Users may see an error message similar to the following:
Sample Error:
LeadDiscovery.WebBase.StructurePanel.Commands.GetQueryStructureImage command is failed. '{"tableName":"Master Table","propertyName":"structureImage","width":165,"height":174}'. (6)
Object reference not set to an instance of an object.
System.NullReferenceException: Object reference not set to an instance of an object.
at System.Configuration.ConfigurationElementCollection.BaseGet(Object key)
This error typically indicates a problem with structure rendering permissions or configuration problems.
Potential Solution:
The issue was resolved by addressing a licensing problem. The "Allow structure rendering" option in the Lead Discovery Premium license was not checked for the WebPlayer user group.
Debugging Steps:
- Check the Lead Discovery Premium license settings in Administration Manager.
- Ensure the "Allow structure rendering" option is enabled for the WebPlayer user group.
- Restart the WebPlayer services after making changes to the license settings.
- Verify that ChemDraw JS is properly installed and configured on the server.
- Clear the browser cache and any server-side caches before retesting.
- Test the substructure search functionality in the WebPlayer after applying these changes.
If the issue persists:
- Review the Node Manager and WebPlayer log files for any related errors.
- Verify that all necessary components for chemical structure rendering are installed and up-to-date.
- Check the regional settings on the Node Manager server, ensuring they are set to a supported locale (e.g., English (United States)).
Note: This solution addresses a specific licensing configuration issue. If the problem continues after following these steps, further investigation may be required to identify other potential causes.
Comments
0 comments
Please sign in to leave a comment.