Thank you Tobias for the quick response.
I am creating the stamps manually in a new system and replicating the upgraded system seen in the screenshot attached.
As you can see from the screenshots, within the designer tab all options are identical.
PDF was updated here.
A recent DW upgrade from v6.10 > v6.12 > v7.1 > v7.3 uncovered something that, either was an oversight or a design change that I wasn't aware of.
Under stamp configurations, the upgraded machine, during stamp creation offers the db field 'Fill with' options of "Fixed, User & Predefined".
Conversely, a clean newly installed v7.3 system offers the db field 'Fill with' options of "Fixed & Predefined".
Was this a design choice or an unintentional upgrade bug?
The difference can be seen in the attached screenshots of the upgraded system options and then the clean install options.
Clearing the message bus didn't help either.
Server restart didn't accomplish anything.
The issue isn't affecting search and retrieval, only storage.
In v7.0, the client is complaining of her inability to store anything to either of her 2 file cabinets when logged into her Windows acct. She is getting an error stating: Logon Failure. Unknown user or bad password.
I gained remote access and logged into the dwadmin acct, which is a DocuWare local account and am receiving the same error. So it seems that all access accounts, whether AD accts or local accts are unable to store anything, even when logged into DW using the same acct.
I have restarted all of the DW system servers to no avail. I'm requesting the client to perform a physical server restart.
Is there something else I need to be investigating?
The only way to resolve this error was to create a support ticket and have the support team assist. Even if I had seen this previously, I couldn't have done it without their assistance.
I've been attempting to perform a test restore to determine if it will perform as expected in a DR environment, but, I continually receive errors as seen in the attached image.
Initially I assumed it was due to different credentials for the db, so, since this is a test environment, I uninstalled and reinstalled using the same windows admin acct as well as the db acct, but, still receive the same errors.
I'd like to explore the built in functionality of the the back up and restore process for future reference.
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?