Our visualization workflow in Teamcenter 13.1 is failing to render 3D models during the design review stage. When the workflow reaches the visualization task, users receive an error message indicating the model cannot be displayed. The workflow continues but the visualization viewer shows only a blank canvas.
I’ve confirmed that the model files are properly attached to the design objects and can be downloaded manually. The issue only occurs within the workflow context when trying to invoke the visualization viewer. The visualization server seems to be running based on the service status, but something isn’t connecting properly.
This is severely impacting our design review process as engineers can’t view the 3D models during workflow approval stages. We need to understand if this is a visualization server configuration issue, a missing plugin, or a problem with how the workflow accesses the model files. Has anyone dealt with visualization rendering failures in workflow contexts?
Your visualization workflow rendering issue involves three interconnected areas that need systematic resolution.
Visualization Server Config: The core configuration problem is likely in the Teamcenter Visualization server’s connection to your TC environment. Access the visualization server admin console and verify these critical settings: First, confirm the dispatcher URL points to your TC 13.1 server with the correct port (typically 7070). Second, check the visualization cache configuration - the cache directory must have write permissions for the service account and at least 50GB free space. Third, validate the JT file conversion settings in the visualization server preferences. In TC 13.1, the visualization server requires explicit configuration for JT pipeline processing. Review the tcvis_server.properties file and ensure the jt.pipeline.enabled parameter is set to true. Also verify that the visualization mockup server service is running alongside the main visualization server - both services are required for workflow rendering.
Plugin Installation: Client-side plugin issues are common in TC 13.1 visualization workflows. All users must have the Active Workspace Visualization Plugin version 13.1.0 or higher installed. The plugin version must exactly match your TC server version - mismatches cause rendering failures. Verify installation by checking Help > About in Active Workspace and confirming “Visualization Services” is listed. Additionally, ensure the browser-based viewer is enabled in the visualization preferences. For workflow contexts, you need the server-side visualization components configured even if users access through browsers. Install the Visualization MockUp Server component on your application tier if it’s missing - this component handles server-side rendering for workflow tasks.
Model File Accessibility: This is often the root cause. The visualization server must have direct file system access to the Teamcenter volumes where model files are stored. Verify the visualization server service account has read permissions on all volume paths defined in your TC environment. Check the volume configuration in Teamcenter by navigating to Organization > Volumes and note the physical paths. Then log into the visualization server machine using the service account and verify you can access those paths. If volumes are on network storage, ensure the visualization server has proper network authentication and that no firewall rules block SMB/NFS traffic between the visualization server and storage. Review the visualization server logs at $TCVIS_ROOT/logs/server.log for file access errors - look for “FileNotFoundException” or “Access Denied” messages that indicate permission problems.
Implementation approach: Start by validating model file accessibility since that’s the most common issue. Use the visualization server’s diagnostic tool to test file retrieval for a specific model. Next, verify plugin versions on client machines and update if needed. Finally, review and correct the visualization server configuration settings. After making changes, restart both the Visualization Server and Visualization MockUp Server services. Test the workflow with a simple model first to confirm rendering works before processing complex assemblies. This comprehensive approach addresses all three focus areas and should resolve your workflow visualization failures.
Don’t overlook the workflow task configuration itself. The visualization task in your workflow template needs to have the correct action handler that invokes the viewer with proper parameters.
We experienced similar rendering failures and discovered that the visualization server wasn’t able to access the file storage location where the models were stored. Even though the files were attached to the objects, the visualization server needs direct file system access to process and render them. Check your volume configuration and ensure the visualization server has read permissions on the file volumes. Also verify that the file paths are correctly mapped in the visualization server configuration. Network path issues or firewall restrictions could also prevent the visualization server from accessing model files during workflow execution.
I suspect this might be a plugin issue. The visualization workflow task requires specific viewer plugins to be installed on the client machines. Verify that all users have the Active Workspace visualization plugin installed and updated to match your TC 13.1 version. Also check if the model file format is supported by your visualization configuration. Some CAD formats require additional translators to be installed on the visualization server.
Thanks for the insights. I checked the visualization server URL and it’s configured correctly. The plugins are installed on client machines. However, I’m not sure about the file system access for the visualization server. How do I verify that the visualization server can access the volume where model files are stored?
To verify file accessibility, log into the visualization server machine and try to access the file volume paths directly using the service account that runs the visualization server. You should be able to navigate to the volume directories and read files. If you get permission denied errors, that’s your problem. Also check the visualization server logs for any file access exceptions.