An important message to our customers about the current COVID-19/Coronavirus situation. LEARN MORE.
We have just applied the solution name and key for our cloud license, however, when trying to start the Prizm service, it fails to start.
What could be causing this issue?
There are a few reasons why this would occur:
As a customer, I want to know the anticipated amount of time that you will continue supporting my specific version so that I can plan our releases ahead of time.
We currently have our Support Policy located below.
Please see the section named Product Versions:
I am integrating PrizmDoc using just the API to convert documents, and I am noticing an initial delay of about 10 seconds before the conversion starts.
Why is this happening?
One of the likely reasons this could happen is if your PrizmDoc Server is not licensed properly or if you are running in the Evaluation mode. In such cases, there are restrictions in place.
Among those restrictions is an artificial delay of 10 seconds imposed before viewing or conversion operations begin. A dialog window normally indicates this in the Viewer interface, but if you are just making API calls to the server, it will not be apparent.
A valid product license is required to eliminate these restrictions, which can be done as follows: https://help.accusoft.com/PrizmDoc/latest/HTML/prizmdoc-server-docker.html#2-configure-your-license.
We just installed the PrizmDoc client and noticed that when we run Prizm Application Services, the service states that it is started, but it is not listening on 3000, and there are no logs written to the Prizm\logs\pas folder. What might the issue be?
A possible reason for this issue can be due to the Windows system environment variable called PATHEXT. By default, .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC are configured.
What this variable does is allow commands to be executed without needing to add the extension to them.
For example, PM2, which runs with PAS, has a file extension of .CMD, so when executing PM2 in a command line you just need to type PM2 instead of the full name PM2.CMD.
If .CMD is not in the PATHEXT environment variable, then just typing PM2 would return a command not found error, and you would need to use the full PM2.CMD for it to work.
To fix the issue, ensure the following:
to the end of the current string
We are currently using PrizmDoc Cloud licensing. After applying our cloud license, the Prizm services started and show healthy, however, I see “CloudLicenseValidationFailed” errors in the PccErrors.log file. Is this normal, and do I have to worry about Prizm functionality?
Currently the licensing messages referencing “CloudLicenseValidationFailed” in PccErrors.log are a false positive and should not be taken as an issue with PrizmDoc Cloud licensing.
The more accurate way to check whether the license has been validated successfully would be to use watchdog.log and look for “Cloud License Validation” – “isValid”:true which indicates that the license is valid.
The issue regarding that error in pccerrors.log is in our product backlog to consider addressing in a future release, but it is not yet prioritized on our roadmap.
We entered our S3 bucket name in the customer portal, but used a capital letter for the first character; however, the S3 bucket name is all lowercase in AWS (Amazon Web Services).
Will this cause an issue with starting the service?
Yes, the bucket name is case-sensitive and must be entered exactly the same as the S3 bucket is named in AWS (Amazon Web Services).
AWS recommends you do not use uppercase letters in your bucket name.
If you made the first character of the name uppercase in the Accusoft Customer Portal, then the service will fail to start.
You will need to contact your Account Manager or Accusoft Technical Support to have the license re-created so that you can re-enter the S3 bucket name properly.
We are adding files to the viewing session with HttpWebRequests. We noticed with larger files the response is:
(413) Request Entity Too Large. - at System.Net.HttpWebRequest.GetResponse().
What could be the cause?
A 413 request entity too large error occurs when a request made from a client is too large to be processed by the web server. If your web server is setting a particular HTTP request size limit, clients may come across a 413 request entity too large response. An example request that may cause this error would be if a client was trying to upload a large file to the server (e.g., a large media file).
Depending on which web server you use, implement the necessary changes described below to configure your web server’s maximum HTTP request size allowance. Below are some suggestions for popular Web Servers:
For Nginx users:
The directive that determines the allowable HTTP request size is client_max_body_size. This directive can be defined in your nginx.conf file located at /etc/nginx/nginx.conf
For Apache users:
The directive is LimitRequestBody which can be defined in your http.conf file or in an .htaccess file.
For IIS users:
We have been noticing in our PrizmDoc environment that the viewer seems to take longer and longer to view documents over time. After a few days, we restart the Prizm services, and the Viewer processes faster. What might be the reason for this issue?
This issue is typically caused by a change in the core count of the server after PrizmDoc has been installed. Specifically, the non-interactive heap size will not automatically update if the core count is changed after PrizmDoc has been installed. We update this value during install.
If you have made changes to the core count of the server after installation, please see the following page for correlation between the non-interactive heap size and the CPU cores count:
The reason the non-interactive heap size matters here is because it affects performance of the Office and HTML conversion services, and the symptom of insufficient non-interactive heap size is soffice.bin crashing.
When installing PrizmDoc, we specified the wrong user ID and password for the 3 PrizmDoc services. Can we safely change them to another account?
It is possible to change the Login User account on the three PrizmDoc services: Prizm, PrizmDemo, and Prizm Application Services.
You will need to ensure the user id you use is in the local administrators group on the server, as well as a part of the Login As a Service rights in the machine’s local security policy.
To verify the user ID is added to the Local Administrators group:
To verify the user Id has “Log on as a Service” rights in the Local Security Policy:
Changing the service “Log on As” user id:
In PrizmDoc Viewer, when viewing Excel documents that have pictures on certain spreadsheets within that document, the pictures are not displayed.
This appears to happen only if PrizmDoc has the Microsoft Office Conversion (MSO) feature enabled. This issue does not occur if PrizmDoc is using LibreOffice.
The issue is related to an Excel “Page Setup” option called “Black and white”. The option is located in Excel under File, Print, Page Setup and is only respected when PrizmDoc has the MSO feature enabled.
File, Print, Page Setup
When using LibreOffice, this setting does not exist and is ignored, which is why you can see the pictures.
By default, this option is disabled in Excel, so that specific option would have to be manually set by the creator of the document.
As a workaround, ensure that the “Page Setup” option for “Black and white” is not checked on any spreadsheets in an Excel document that has pictures.
How can I make significant changes to the UI of a PrizmDoc sample?
While jQuery can be used to make some small changes to the samples UI, it does not always make sense to make your changes programmatically on the front-end.
In this case, you will want to make your UI changes to the HTML templates used to compile the template that is passed in during viewer initialization.
To make changes and recompile the templates, you can utilize the following GitHub repository:
With PrizmDoc Viewer (Self-Hosted), you need to purchase specific licenses to include certain functionality such as OCR, MSO, etc. With this in mind, are all features of PrizmDoc Cloud included with transaction and subscription purchases?
All features that PrizmDoc Cloud has to offer are available with either transaction or subscription purchases.