I'm trying to configure a Web Scanning url shortcut for a user that will set the path, name, template and some field values. I have done this before for a different user and in their process it works perfectly. The current process is giving me an error once I try to store the scanned documents. 

It only gives the error when launching the Web Scanning client using the shortcut though. If I use the normal Scan button from the Web client, brows to the path, set the same Template and field values, the document stores successfully with any problem. Using the shortcut though, the interface is loaded with the correct path set, the correct template applied as well as the relevant field values. As soon as I click store the document remains and the follow error is displayed in the Error pane:

The Error details are as follows: 

Stack Trace

   at Laserfiche.Connection.Web.WebAccessServiceBase.ExecuteWebServiceOperation(IWebAccessService service, String method, Boolean requiredOperation, Object[] args)
   at Laserfiche.Connection.Web.WebAccessServiceBase.UpdateDocumentMetadata(IWebAccessService service, DocumentProperties document, Boolean isExistingDocument)
   at Laserfiche.Connection.Web.WebAccessServiceMTOM.UpdateDocumentMetadata(DocumentProperties document, Boolean isExistingDocument)
   at Laserfiche.Connection.Web.WebDocumentStore.CreateDocument(DocumentProperties document, FolderProperties parentFolder, CreateDocumentOptions options, Boolean silent, IDocumentStoreEvents storeEvents)
   at Laserfiche.BatchProcessor.Scanning.Output.ScanningOutputProcess.Store(Object document)
   at Laserfiche.BatchProcessor.ComponentModel.DocumentClass.StoreDocument(Document document)
   at Laserfiche.BatchProcessor.Runtime.SessionProcessor.OnStoreDocument(Document document)

I also tried changing the parameters to only connect and set the folder path without setting any other value but the error and behavior stays the same. 

I can use the same parameters and configure a custom button on the Laserfiche Desktop client and that works fine. It is only when using the configured shortcut to launch the Web scanning interface. What makes it even more confusing is that on a different process with different configured values it works fine. 

Here is the one that does not work:

lfwa80://scanning/http://vmdmslfqa1/laserfiche/App_Services/ScanningService.asmx?r=AFSLFQA&custom=path:'\\*Admin Restart\\Incoming MVA Back Scan Routing'volid:'11'name:'%(Fields.MVA Document Type) - %([Date/Time])'template:'MVA Folder Back Scan'[MVA Document Type]'Confirmation of Sale'[Document Date]'%(Date)'(ProtectedItems)'9'

the following one on the other process works without issue:

lfwa80://scanning/http://vmdmslfqa1/laserfiche/App_Services/ScanningService.asmx?r=AFSLFQA&custom=path:'\\*Scan Incoming'volid:'4'name:'%(Fields.LF Template Name) - %([Date/Time])'template:'Supplier Invoice Scanning'[LF Template Name]'Supplier Invoices DT'[Mailroom Capture Method]'SCAN'[Capture Method]'SCAN'(ProtectedItems)'9'

Is there something I might be missing? besides different storage paths and templates, the only other difference between the working and the problematic process is that in the problematic one there is a Date field that is configured with a default value. But as I mentioned, if I launch the default scanning client using the normal button provided, even with the Date field being filled by a default value, it works.