Do you have an issue with a specific file(s)?
Can you reproduce using one of our samples or online demos?
Are you using the WebViewer server?
Does the issue only happen on certain browsers?
Is your issue related to a front-end framework?
Is your issue related to annotations?
Please give a brief summary of your issue:
(Think of this as an email subject)
Office Addon can’t open native word files
Please describe your issue and provide steps to reproduce it:
(The more descriptive your answer, the faster we are able to help you)
Have following error on loading a native office doc in webviewer “License Key Error: no office addon”, documentType is set to ‘office’. It suggest that I need a new license key which will allow native office files to be viewed? Was a demo license and also used our work license, both gave this error. It’s happening in multiple document comparison webviewer. Native PDF loading works fine
This is on Google Chrome Version 137.0.7151.56 (Official Build) (64-bit). and happens transiently
Please provide a link to a minimal sample where the issue is reproducible:
Hello, I’m AiRon, an automated tech support bot While you wait for one of our customer support representatives, I can help you with your question.
It seems you are encountering a licensing issue when attempting to load native Word files in WebViewer. The error message “License Key Error: no office addon” suggests that your current license key may not include the necessary permissions to handle Office files. This issue is unrelated to the browser or the document type setting but rather to the license configuration.
Some things you can try:
Verify that your license key includes permissions for Office file viewing. You may need to contact Apryse support to ensure that your license has the necessary features enabled for Office documents.
Ensure that the documentType is correctly set to ‘office’ and that you are not missing any configuration parameters required for Office file processing.
Check if the WebViewer Server is being used and properly configured as it might be necessary for handling certain document types like native Office files.
Ensure that your server is correctly set up, and the webviewerServerURL is configured if WebViewer Server is needed for Office file support.
If this occurred with both a production and demo license key, this could be an issue with how the license key is applied. To investigate further, please provide the following:
Sample Office file used for testing
WebViewer constructor with all options defined, as well as any code related to loading documents (please do not post the exact license key in the code snippet)
JavaScript console output showing all warnings and errors.
Network panel showing all failed network traffic
Can you reproduce the issue using our samples (especially on our site)?
Does the issue only occur in certain browsers and/or devices? If so what are the details?
Are you using WebViewer Server? If so, what version of WebViewer Server?
