After updating to SAP PLM 2022, our CAD viewer plugin stopped working. Engineers can’t load 3D models in the browser anymore - the viewer window opens but shows a blank gray screen with “Plugin initialization failed” error. We’re using Chrome and Firefox on Windows 10. Before the update, the viewer worked perfectly for reviewing CAD assemblies. The browser extension requirements might have changed with the SAP PLM update, but I can’t find clear documentation on what’s needed now. This is disrupting our entire design review process since teams can’t visualize models without downloading and opening in native CAD software. Has the viewer plugin compatibility changed in the 2022 version?
SAP PLM 2022 introduced changes to the CAD viewer plugin architecture. The old NPAPI plugin is no longer supported in modern browsers. You need to install the new WebGL-based viewer component. Check SAP Note 3245678 for the updated installation package and browser requirements.
I found the extension in Chrome Web Store and installed it, but still getting initialization errors. Do I need to configure something on the SAP PLM server side as well? The CORS settings you mentioned - where are those configured?
Another thing to check: browser security settings. Chrome 90+ and Firefox 88+ have stricter content security policies that can block the viewer even with the correct extension installed. You might need to add your SAP PLM domain to the browser’s trusted sites list or adjust content security policy headers on the server. Also verify that JavaScript and WebGL are enabled in browser settings - the new viewer is entirely JavaScript-based unlike the old native plugin.
You’re experiencing the classic SAP PLM 2022 viewer migration issue. Let me walk through all three areas systematically:
1. Viewer Plugin Compatibility: SAP PLM 2022 completely replaced the legacy NPAPI plugin architecture with a modern WebGL-based viewer. This was necessary because:
- Chrome removed NPAPI support in version 45 (2015)
- Firefox removed NPAPI support in version 52 (2017)
- Modern browsers only support Web Extensions API
The old plugin (SAP PLM CAD Viewer Plugin v3.x) is incompatible with SAP PLM 2022. You must migrate to the new viewer:
- Name: SAP Visual Enterprise Viewer (VEV) Extension
- Chrome: Install from Chrome Web Store (search “SAP Visual Enterprise”)
- Firefox: Install from Firefox Add-ons (same search)
- Version required: 9.0 or higher for SAP PLM 2022 compatibility
Uninstall old plugin completely:
- Windows: Control Panel → Programs → Uninstall “SAP PLM CAD Viewer Plugin”
- Clear browser cache after uninstalling
- Restart browser before installing new extension
2. Browser Extension Requirements: The new viewer has specific browser and system requirements:
Minimum browser versions:
- Chrome 90+ (released April 2021)
- Firefox 88+ (released April 2021)
- Edge 90+ (Chromium-based)
System requirements:
- WebGL 2.0 support (verify at: get.webgl.org)
- Hardware acceleration enabled in browser
- Minimum 4GB RAM for complex assemblies
- Graphics card with OpenGL 3.0+ support
Browser settings to verify:
- JavaScript: Must be enabled globally
- Hardware acceleration: chrome://settings → Advanced → System → “Use hardware acceleration”
- WebGL: chrome://flags → search “WebGL” → ensure not disabled
- Pop-ups: Allow pop-ups from your SAP PLM domain
Extension permissions required:
- Access to your SAP PLM domain
- Local storage access (for caching model data)
- Cross-origin requests (for loading model files)
3. SAP PLM Update Impact - Server Configuration: The SAP PLM 2022 update requires server-side configuration changes:
CORS Configuration (critical):
Transaction SICF → Navigate to your PLM service → Edit → Security → Add CORS headers:
Access-Control-Allow-Origin: https://your-plm-domain.com
Access-Control-Allow-Methods: GET, POST, OPTIONS
Access-Control-Allow-Headers: Content-Type, Authorization
Access-Control-Allow-Credentials: true
Content Security Policy:
Modify CSP headers to allow WebGL viewer:
Content-Security-Policy:
script-src 'self' 'unsafe-inline' 'unsafe-eval';
worker-src 'self' blob:;
img-src 'self' data: blob:;
Viewer service configuration:
- Transaction SPRO → SAP PLM → CAD Integration → Viewer Settings
- Viewer Type: Change from “Native Plugin” to “Web Viewer”
- Streaming Mode: Enable “Progressive Streaming” for large assemblies
- Cache Settings: Set client-side cache to 500MB minimum
Firewall/proxy considerations:
- WebSocket connections must be allowed (viewer uses WSS protocol)
- Ports: Ensure 443 (HTTPS) and 8443 (WebSocket) are open
- Proxy whitelist: Add *.sap.com domains for license validation
Verification Steps:
- Test WebGL: Open get.webgl.org in browser - should show spinning cube
- Test extension: Browser toolbar should show SAP VEV icon
- Test CORS: Open browser console (F12) when loading viewer - check for CORS errors
- Test viewer: Transaction CV01N → Open any CAD document → Click viewer icon
Common Issues After Migration:
- Gray screen with no error: CORS misconfiguration
- “Plugin initialization failed”: Old plugin still installed
- Models load but rendering is slow: Hardware acceleration disabled
- Viewer opens but immediately closes: Pop-up blocker active
Rollback Plan: If you need temporary fallback while fixing configuration:
- Enable “Download and View” option in PLM settings
- Users can download models and view in free SAP 3D Visual Enterprise Viewer desktop app
- Not a permanent solution but unblocks design reviews during migration
The SAP PLM update impact is significant because it fundamentally changed how CAD visualization works. The new architecture is more secure and maintainable but requires proper server configuration. Most “viewer not working” issues after the 2022 update are due to missing CORS headers or incomplete old plugin removal.
CORS configuration is critical for the new viewer. The WebGL viewer makes cross-origin requests that older plugins didn’t. In your SAP PLM server, you need to configure allowed origins in the web.xml or through transaction SICF. Add your PLM domain to the Access-Control-Allow-Origin headers. Without this, browsers block the viewer from loading model data even if the extension is installed correctly.