Technical FAQs

Question

In PrizmDoc, why do I fail to load/convert Excel documents with the error “Exception from HRESULT: 0x800AC472”?

Answer

The error message Exception from HRESULT: 0x800AC472 is usually associated with a failure involving an Excel document, found in the MsOfficeConverter.log. Below are some known triggers of it:

If the user is logged in as “SYSTEM”, “LocalSystem”, or any other non-user-account variant, this will cause PrizmDoc to fail when using MSO services. This is expected behavior when working with Microsoft Office documents in PrizmDoc. Please see step 6 of the Windows Installation documentation regarding this:

http://help.accusoft.com/PrizmDoc/latest/HTML/webframe.html#windows-installation.html

“Specify the login account (account name and password) that PrizmDoc Server will run under. If you are using the Microsoft Office (MSO) Conversion add-on, please make sure that the “login account” is a real user account with Administrator rights. Running PrizmDoc under the LocalSystem user or another Microsoft Windows integrated service account is not supported for this option.”

It’s also crucial that the copy of Microsoft Office on the system has been activated. A not-licensed, not-activated, expired, or trial license will all cause Microsoft Office to not work with PrizmDoc.

More information: https://help.accusoft.com/PrizmDoc/latest/HTML/windows-requirements.html

“The installed copy of Microsoft Office must be activated in order for PrizmDoc’s Microsoft Office Conversion Service to work properly. Not licensed, not activated, an expired or trial version of Microsoft Office will not work with PrizmDoc.”

Your default printer must be the Microsoft XPS Document Writer when working with Excel documents in PrizmDoc. Specifying another printer could possibly lead to this exception.

More information: http://help.accusoft.com/PrizmDoc/latest/HTML/natively-render-mso-documents.html

“The Microsoft Office Conversion Service requires the Microsoft XPS Document Writer printer driver to be installed for the best conversion performance and rendering fidelity of MS Excel documents”

Ensure the Print Spooler service is started and the Microsoft XPS Document Writer is the default printer.

There is a known issue with version 13.3 of PrizmDoc where completely blank Excel files are not loadable in the Viewer. They will fail to load and throw the aforementioned HRESULT exception. This has been fixed in PrizmDoc version 13.6.

In short, please set up the PrizmDoc service correctly to run with a real user account, ensure the copy of Microsoft Office has been activated, and make sure the default printer is set to “Microsoft XPS Document Writer”, then restart the service. This should fix this particular issue in most cases.


For more reading on considerations that Microsoft recommends when running their client-side MSO applications on the server, see this article:

Considerations for server-side Automation of Office

 

The financial industry has made significant investments in document lifecycle management solutions to enhance their productivity, accuracy, and flexibility. There is broad recognition that paper-based processes are a huge source of waste and inefficiency, but simply transitioning away from paper often isn’t enough on its own to achieve true digital transformation. That’s because performing a digital-based process manually still presents many of the same problems. In order to leverage the true benefits of digital document management, FinTechs need to implement data capture and document generation capabilities as part of a broader process automation solution.

A Quick History of Data Capture & Document Generation

To understand how FinTechs can use data capture and document generation technology to enable their digital transformation, it’s helpful to take a moment to understand the history of these tools and how they’ve developed since their origins.

Data Capture

The financial industry was an early innovator in data capture technology with the development of the specialized OCR-A font in the 1960s. This simple monospace font is still used today for the account and routing numbers on an ordinary bank check. Early data capture technology relied on pattern recognition, so an exact pixel match was needed to read the characters electronically and match them to a corresponding character in a font library. While this worked well enough for scanning printed bank checks into a computer system to track transactions, reading anything else on the check with an automated system required further developments in data capture tools.

Modern character recognition technology utilizes a more sophisticated feature detection approach that uses the component elements of each character to distinguish them from one another. An “A,” for example, usually consists of the same basic elements (two angular lines that come to a point with a horizontal line crossing them) regardless of the font used. Breaking characters down into their component elements has even made it possible for software to read handwritten characters as well as machine-printed text.

Document Generation

Document generation technology emerged in the 1970s in the form of document assembly, which was originally used by lawyers to streamline contract creation. Contracts are highly structured and rules-oriented, which made it easy to build a decision-tree logic that could be understood by the software tools of that era. Early document assembly programs used a collection of document templates that incorporated conditional fields the software could replace automatically each time it generated a contract.

Modern document assembly is typically used as part of a more robust document automation solution. Software extracts information from a database and inserts it into a template to generate unique documents quickly, easily, and accurately. These programs are much more sophisticated and flexible than early document assembly tools, allowing organizations to programmatically generate a wide range of documents without ever having to look at the contents prior to the final review process.

Data Capture & Document Assembly in FinTech Today

Despite being an early innovator in OCR technology, the financial industry has been slow to implement more robust data capture capabilities throughout their operations. According to a recent study, 63% of banks are still collecting information from documents manually, a process that’s not only time consuming, but also incredibly prone to error. They’ve been slightly faster to adopt document generation, with 49% of banks still relying on manual processes to create documents. 

Ironically, FinTech organizations are even more dependent upon manual practices than traditional banks. When it comes to data capture, 75% of FinTechs are reviewing documents and entering their data manually rather than using an automated solution. The story is largely the same for document generation, as 79% of them are still creating documents manually.

Understandably, most of these organizations are planning to implement some form of automated data capture and document generation solution within the next two to three years. That’s because they recognize that it will be difficult to achieve true digital transformation without them.

Why Data Capture and Document Generation Are So Important for FinTech

FinTech companies have developed a wide range of innovative financial tools that allow consumers to take better control of their finances and help organizations manage their resources more efficiently. In order to deliver those streamlined solutions, however, FinTechs need to have the capabilities in place to make their own processes more efficient.

Data capture and document generation work together to help these organizations maximize the value and potential of their document management systems. Financial information can be submitted in many different formats, ranging from digital forms and fillable PDFs to images, flattened PDFs, and scanned documents. Extracting information from each of these formats requires a sophisticated understanding of data capture that few software developers possess. 

Once that data is extracted, it can be routed anywhere it’s needed by workflow automation tools. That could be a new document that’s being generated, but more often it will be sent to a database. When the time comes to generate a new document, previously captured information can be inserted wherever it’s needed programmatically. Multiple documents (or just sections of them) can also be merged or split apart to create entirely new ones filled with information drawn from several sources.

All of this can be done in a matter of seconds with the right software integrations, which saves a tremendous amount of time for FinTech teams who have many other priorities to focus on. By incorporating robust data capture and document generation capabilities into their platforms, they can provide faster, better functionality to their customers. Rather than uploading a document and waiting for it to be processed, information can be extracted and routed wherever it’s needed instantly to facilitate faster reviews and resolutions.

Another key benefit of data capture and document generation is accuracy. Between manually reviewing information, entering it by hand into a system, and then retrieving it to create new documents, there are plenty of opportunities for mistakes to be made. In a financial context, those errors often have the potential to be systemic, creating additional errors that are time consuming and expensive to remediate. Automated extraction and assembly remove the risk of human error, which enables FinTechs to accelerate and scale their processes more effectively.

Integrating Data Capture and Document Generation with Accusoft

For over 30 years, Accusoft has been a pioneer in building software integrations that expand application functionality. We provide a variety of data capture and document generation solutions that meet the needs of today’s FinTech platforms. Whether you’re incorporating functionality directly into your application with an SDK or deploying a cloud-based solution that connects to one of our APIs, we have the flexibility to help you integrate the features you need to complete your digital transformation.

To learn more about how Accusoft can enhance your FinTech application with data capture and document generation, talk to one of our solutions experts today.

 

The Top 4 Benefits of On-Premise Document Viewing
 

The infamous cloud and its capabilities has quickly gained popularity in the average household as tech giants like Google, Apple and Amazon have created an expectation that cloud storage services are standard features.  But while cloud storage may be convenient and cost-effective for personal use, there are many business cases where on-premise servers and storage remain the primary choice. 

Today, the debate for ‘cloud storage vs. on-premise’ seems like it would be similar to ‘tablet vs. desktop,’ but many would be surprised to find that in a survey done by IDG Communications and referenced in an article by EnterpriseCIO.com, 56% of respondents, say their on-premises applications are here to stay.  Cloud storage and viewing have many benefits that appeal to today’s mass-market: simple set-up, easily accessible, cost-saving – but when it comes to the most highly regulated industries in the world the benefits of on-premise provide are second to none. 

The same goes for document viewing.  In a world where the average person sends and receives 121 business emails per day, according to a report by DMR, we can imagine the number of attachments shared between colleagues and professionals in a year. Secure document viewing has become a necessity for several industries, but particularly those highly regulated. While companies may find it a tall order to create an on-premise environment with secure document viewing capabilities, Accusoft’s HTML5 document viewer can be deployed on your own infrastructure to create security and compliant-friendly document viewing.

Integrating a document and image viewer on your own server allows an organization to have confidence that even their most sensitive information is protected at all times. The top 4 benefits of on-premise viewing include:

  • Control
    Maintain complete control over your data using on-premise servers and increase the functionality within documents.  By integrating  HTML5 viewing capabilities into an application, it ensures that documents never have to leave a secure environment, even when they’re being shared with people outside your organization. Highly regulated industries and organizations can’t afford a data breach, so the added benefit of physical security of servers weighs heavily on the decision between on-premise vs. cloud.
  • Security
    A document viewer API integration into the on-premise server adds multi-level data protection with 256-bit AES encryption and configurable user permissions for privacy and protection. Companies are able to use in-house security features and systems that allow them to deploy firewalls, anti-malware, etc. when their data is stored on-premise infrastructure.
  • Compliance
    Instead of adding risk by bouncing off third-party servers, integrating an HTML5 viewer into your current application provides added flexible across  many platforms.  The self-hosted version resides on any organization’s servers. The key features of Accusoft’s HTML 5 viewer support secure, GDPR compliant efforts.
  • Speed & Accessibility
    Since the data is stored on the local network and not reliant on an internet connection, if network problems occur, data can still be accessed. The local server also allows for faster file transfer and seamless document sharing. Adding a image and document viewer API empowers developers to provide users with responsive filing viewing without the need to download plugins or open any other applications.

Get Started Today
To learn more about PrizmDoc, Accusoft’s HTML 5 image and document viewing API and the on-premise server integration, click on the resources below or, contact us today.

The lifeblood of transportation companies is the ability for clients to check their shipping order status. For Manitoulin, they enhanced their web portal for customers to retrieve and view scanned documents including, bills of lading, proofs of delivery, and invoices. Shortly after its launch, the portal was accommodating over 35,000 visits per month, and challenges with viewing speed arose. Learn how Manitoulin solved this problem with Accusoft’s PrizmDoc® for Java, formerly VirtualViewer®.

Hampden County is one the most industrialized counties of western Massachusetts, with a population of 462,718 residents living in 197,318 households. Whenever any of those houses or plots of land change hands, documents must be created to record the transaction and it’s the job of the county registrar to keep it all straight. With hundreds of thousands of documents being processed every year, their system finally started to slow down.  Hampden County was looking for a better document processing solution.  Learn how PrizmDoc® for Java, formerly VirtualViewer®, from Accusoft was able to speed up viewing times as well as improve viewing quality.

Question

In PrizmDoc, why do I fail to load/convert Excel documents with the error “Exception from HRESULT: 0x800AC472”?

Answer

The error message Exception from HRESULT: 0x800AC472 is usually associated with a failure involving an Excel document, found in the MsOfficeConverter.log. Below are some known triggers of it:

If the user is logged in as "SYSTEM", "LocalSystem", or any other non-user-account variant, this will cause PrizmDoc to fail when using MSO services. This is expected behavior when working with Microsoft Office documents in PrizmDoc. Please see step 6 of the Windows Installation documentation regarding this:

http://help.accusoft.com/PrizmDoc/latest/HTML/webframe.html#windows-installation.html

"Specify the login account (account name and password) that PrizmDoc Server will run under. If you are using the Microsoft Office (MSO) Conversion add-on, please make sure that the "login account" is a real user account with Administrator rights. Running PrizmDoc under the LocalSystem user or another Microsoft Windows integrated service account is not supported for this option."

It’s also crucial that the copy of Microsoft Office on the system has been activated. A not-licensed, not-activated, expired, or trial license will all cause Microsoft Office to not work with PrizmDoc.

More information: https://help.accusoft.com/PrizmDoc/latest/HTML/windows-requirements.html

"The installed copy of Microsoft Office must be activated in order for PrizmDoc’s Microsoft Office Conversion Service to work properly. Not licensed, not activated, an expired or trial version of Microsoft Office will not work with PrizmDoc."

Your default printer must be the Microsoft XPS Document Writer when working with Excel documents in PrizmDoc. Specifying another printer could possibly lead to this exception.

More information: http://help.accusoft.com/PrizmDoc/latest/HTML/natively-render-mso-documents.html

"The Microsoft Office Conversion Service requires the Microsoft XPS Document Writer printer driver to be installed for the best conversion performance and rendering fidelity of MS Excel documents"

Ensure the Print Spooler service is started and the Microsoft XPS Document Writer is the default printer.

There is a known issue with version 13.3 of PrizmDoc where completely blank Excel files are not loadable in the Viewer. They will fail to load and throw the aforementioned HRESULT exception. This has been fixed in PrizmDoc version 13.6.

In short, please set up the PrizmDoc service correctly to run with a real user account, ensure the copy of Microsoft Office has been activated, and make sure the default printer is set to "Microsoft XPS Document Writer", then restart the service. This should fix this particular issue in most cases.


For more reading on considerations that Microsoft recommends when running their client-side MSO applications on the server, see this article:

Considerations for server-side Automation of Office

Question

We are planning to upgrade our PrizmDoc Server and PrizmDoc Client to the latest major version. What is the best practice for doing so?

Answer

For best results, you will want to follow the instructions below to ensure the cleanest upgrade of the newest version:

NOTE: Before starting, make a backup of the following configuration files for use as reference when re-configuring your new version installation. This should be done before the PrizmDoc installer is run, as all configuration files will be replaced with new ones (resetting them to their default configuration).

  • Prizm Server Configuration: prizm\prizm-services-config.yml

  • Prizm Client Configuration (Windows): prizm\pas\pcc.win.yml

  • Prizm Client Configuration (Linux): /usr/share/prizm/pas/pcc.nix.yml

  • ServiceHost Configuration: prizm\PCCIS\ServiceHost\pcc.config

How To:

  1. Uninstall the previous version of PrizmDoc Server and PrizmDoc Client. Be sure to delete all PrizmDoc folders that are still present. For Windows you can Find PrizmDoc Server and Prizm Client under Add/Remove Programs. For Linux, please follow instructions below for uninstall instructions.

Linux Prizm/PAS Service Uninstall:

https://help.accusoft.com/PrizmDoc/latest/HTML/webframe.html#linux-uninstall-prizmdoc-serve.html

https://help.accusoft.com/PrizmDoc/v13.10/HTML/webframe.html#pas-linux-uninstallation.html

  1. Download the latest version of PrizmDoc for your operating system from https://www.accusoft.com/products/prizmdoc-suite/prizmdoc-viewer-builds/

  2. Install PrizmDoc Server first and then the PrizmDoc Client.

  3. At the end of the server installation, the install may request a reboot.

  4. Make a backup of your new configuration files as listed above.

  5. Modify each of the new configuration files and make the same changes as you did in the older configuration files.

NOTE: Do not just replace the new configuration files with the old version configuration files, as new configurations may have been introduced in the new version and they would be lost.

  1. Restart the Prizm Services and Prizm Application Services to ensure the newly configured file changes take affect.

NOTE: If either service fails to start with an error after modifying the configuration files, replace the configuration files with the original copy of the configuration files and try making the changes again.

NOTE: If you are using viewing packages and have an existing database, we provide additional scripts in the \prizm\pas\db folder to modify your existing database. For example, upgrading from PrizmDoc 12.x to PrizmDoc 13.x we provide an additional script addTenantId to add a new field to one of the existing tables.

Question

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.

Is this possible?

Answer

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: