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?
I have begun to receive the following error when launching Workflow designer:
The requested service, 'http://irvwinvapp-134.clientname.local/DocuWare/Settings/BpwDesitnService.svc' could not be activated. See the servicer's diagnostic trace logs for more information.
I've reviewed the attached DocuWare.Bpw.Designer.log, but, can't seem to find the root cause.
Has anyone else seen this behavior?
This was resolved once it was discovered that the DW installation routine did not populate the fulltext port to be used in the admin tool fulltext server path. Once that was in place, it began to work.
I have several import jobs that run constantly. 2 of the jobs stop randomly.
There doesn't seem to be anything wrong with the configuration, as both function as expected when started.
How can I determine the cause of the stoppage?
Nobody has a reply, even DW support?