Featured Content
eGuide: Digital Transformation
Enable your employees to remain productive throughout the document management process.
Read More
SDK Technologies
Accusoft SDKs
Improve Form Processing Text Recognition Results with Regular Expressions
Learn how SmartZone uses a regular expression engine integrated into the recognition engine to achieve the best possible accuracy on data that can be defined by a regular expression.
Experience Docubee
Meet Docubee
Docubee is an intelligent contract automation platform built to help your team success
We are running PrizmDoc on a Windows operating system and we noticed that our ms-office-conversion-service remained unhealthy even through a restart of the service. We also noticed an error in the MsOfficeConverter.log referencing the following error. What could be the cause?
“WARN – COM error occurs on 1 initialization attempt. Retrieving the COM class factory for component with CLSID {000209FF-0000-0000-C000-000000000046} failed due to the following error: 80080005 Server execution failed (Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE))”
The PrizmDoc MSO feature requires either Microsoft Office 2013 or 2016 to be installed in order to function properly. Based on the error, there is a Microsoft Office specific .dll file which is not registered properly.
The following process will re-register the .dll files and potentially resolve this issue (Note: for Step 2, this may vary depending on what directory you used to install Microsoft Office and the version of Office. You want to find the directory containing winword.exe):
Run Command Prompt as Admin. Type cd C:\Program Files\Microsoft Office\Office15 or cd C:\Program Files\Microsoft Office\root\Office16 Run winword.exe -regserver. Reboot the server.
If you don’t have the Prizm service set up to run on boot then make sure that Office applications are started by PrizmDoc, or from the command line, before being opened manually.
Is it possible to make a call to an external API when annotation saving is complete?
In the Viewer, you can bind functions to the MarkupSaved event mentioned on the following documentation page in order to execute code when annotations are saved to the server:
MarkupSaved
https://help.accusoft.com/PrizmDoc/latest/HTML/webframe.html#Subscribing_to_Events.html
A full list of events exposed by the Viewer can be found here:
https://help.accusoft.com/PrizmDoc/latest/HTML/webframe.html#PCCViewer.html#.EventType
For reporting purposes, we want to rename the markup layer JSON files to help identify which tenant made the markup. For example:
c1fea5868607402c1b664272e5b82aeb7fff7390_0_0hg91gTqSCeg_P9B2Ko7BaH-YxkaazjH.json
rename to:
accusoft_c1fea5868607402c1b664272e5b82aeb7fff7390_0_0hg91gTqSCeg_P9B2Ko7BaH-YxkaazjH.json.
accusoft_c1fea5868607402c1b664272e5b82aeb7fff7390_0_0hg91gTqSCeg_P9B2Ko7BaH-YxkaazjH.json
Is this possible?
The actual filename for an annotation .json file contains an encrypted value of the file path and document name. This is what is used to associate the JSON markup layer file with the document.
If you make changes to the first part of the file, PrizmDoc will no longer be able to associate those markups to the actual file.
As a alternative, you can set up a separate PAS instance for each tenant, which will provide a different markup layer for each tenant.
Or you can programmatically handle the markups and store them specifically for each tenant. The following articles outline our Markup JSON specifications: