Client is reporting that when scanning a 500+ page document, it isn't being created and transferred to the document tray; instead it returns an error that the resulting file was too large.
She also mentioned that she has a report that typically runs 1000-1500 pages that will need to be scanned each month, so we need to provide a solution for her.
Where can the maximum file size created from scanning be modified?
I ran the LogCollector and examined the logs.
I finally found, in the DocuWare.Desktop.CaptureService.Host log, the following error:
"Could not convert C:\Scanner\TestScan\.... - Copy.bmp to BMP file. Reason: Out of memory.....
To resolve it, I cleared the existing files, opened a new jpg and saved it as a brand new bmp.
It eliminated the error and I was able to successfully 'scan' new images.
Is there an updated version of this article that relates to v7.2?
Each attempt throws an error stating:
An unspecified error occurred. Please refer to the logging for further details.
Using the log viewer doesn't really help in determining what has occurred.
I have a client that needs support for a configuration issue and this client is using Cloud v7.1. My local DTA have upgraded to 7.2 for a new client so the admin tool isn't backward compatible. I started a VM containing 7.1 and connected the DTA to gain access to the admin tool. After restarting DTA and starting the admin tool, each connection attempt, whether it is using Desktop Apps Authentication or DW authentication, I receive the same error as evident in the screenshot provided. I can access the web client as well as configurations, but, not the admin tool.
Session not registered!
Has anyone seen this and been able to resolve it?
Yeah, I tried that as well, but no joy.
It appears that their single character barcode is malformed as it isn't recognized by even the one-click index engine.
Research has shown that others have had issues with single digit barcodes, but, that it is possible.
Oh well, the workaround seems to be working flawlessly.
Thanks Joe. Long time no see.
I tried this solution, but, didn't really see any change.
After further digging, it was determined that the problematic barcode was to have reflected a single digit and it wasn't being written as a valid barcode. Due to length, I'm sure.
In the end, we mitigated the issue by using a separate store dialog and prepopulating that field with the single digit the system was looking for, and when a new document was imported containing a valid barcode that could be translated by DW, it will overwrite that field so it would store correctly.
I appreciate the pointers on the VintaSoft settings file. I've tucked it away for future use.
Client bar code recognition is seeing a failure rate around 20%. After manipulating the import configuration multiple times, I can't seem to make much difference in the recognition rate.
I see there is an option available through v6.11 that could have significant impact on it.
Is this supported in v7.1? Or is there another option?
When attempting to create a new file cabinet, I'm seeing an error stating:
Cannot find matching source guid for Id: 72459 in relationship with type: OCRTemplate.
We can't seem to get beyond this error.
I'm unable to access the configurations panel on either of my cloud accounts this morning.
I'm receiving an error stating:
Sorry, an error occurred while processing your request.
If I close the error page and try again, I receive the same error or an error stating:
Login failed: Login token has expired. Contact your DocuWare administrator.
Is anyone else seeing the same?
On an installed v7.1 system, when attempting to open the document processing module, I'm getting the following error: Invalid URI: The format of the URI could not be determined.
So far, I've ensured the hostname is correct, the connection string appears correct as compared to other systems, 3 different browsers have presented the same error and even an installation repair has not resolved it.
I'm not seeing errors when accessing any of the other configuration modules, only document processing.
Has anyone seen this error and resolved it?