You are viewing limited content. For full access, please sign in.

Question

Question

Operation or command invalid for the requested type of document

asked on August 28, 2017

Trying to store documents from QuickFields into the repository and it gives me this error:

Operation or command invalid for the requested type of document. It is not giving me a code. I have tried to look at security on the volume, the folder, the user that is running the QF job and I'm coming up empty. Has anyone seen this generic error message before and might know in which area I need to concentrate my search for the incorrect setting that may be causing this? 

 

0 0

Answer

SELECTED ANSWER
replied on August 29, 2017

No problem. That's what the details were indicating, some sort of problem with the parent folder that was making Quick Fields think it's a document and fail when it was trying to create a new document in it.

1 0

Replies

replied on August 29, 2017

What type of document are they trying to save?  Word, PDF, Tiff?

0 0
replied on August 29, 2017 Show version history

tif, tiff, pdf. But once they are in QF they will obviously be imported into LF as TIF.

0 0
replied on August 29, 2017

What version of Quick Fields are you using? If Quick Fields 10, does this message occur in Quick Fields or Quick Fields Scanning or both?

Can you post the full error message?  If you press F12 to open the application errors pane, you can copy the details of the error message.

0 0
replied on August 29, 2017 Show version history

QF 10. message occurs only when I try to store the documents. The error message text that I typed in the subject field is the full error message. That is why it is so generic. No code, nothing. It will not store any document. The only thing I have changed is added a volume to the system. I have checked the security on the volume and it is identical to a few jobs that I already have running without issues.

qferror.jpg
qferror2.jpg
qferror.jpg (12.34 KB)
qferror2.jpg (46.11 KB)
0 0
replied on August 29, 2017

It's not quite the same though. Could you try opening the Application Errors pane and checking if there's a more detailed message after storing documents failed?

 

0 0
replied on August 29, 2017

Operation or command invalid for the requested type of object.

Exception
        System.Runtime.InteropServices.COMException:
Operation or command invalid for the requested type of object.

Stack Trace
        at LFSO100Lib.ILFDocument.Create(String Name, LFFolder ParentFolder, LFVolume Volume, Boolean AutoRename)
        at Laserfiche.BatchProcessor.ComponentModel.LFSO90.DocumentStore.CreateDocument(DocumentProperties document, FolderProperties parentFolder, CreateDocumentOptions options, UpdatePageOptions pageOptions, MetadataUpdateOptions metaOptions, Boolean silent, OnPageStoredEventHandler OnPageStored)

Data items: 2
Stage: Stage2, ErrorStage, CreateNewDoc
AlreadyLogged: True
 

qferror3.jpg
qferror3.jpg (144.63 KB)
0 0
replied on August 29, 2017

Is there a folder with the same name as the document in the folder you're trying to send this document to?

1 0
replied on August 29, 2017

No. The folder is empty.

0 0
replied on August 29, 2017 Show version history

But.... thanks for putting me on the right track though, because once I deleted the destination folder and re-added it (using the same name) it works. So either way thanks so much for your help! smiley There must have been something in the name that was not visible or was corrupt.

0 0
SELECTED ANSWER
replied on August 29, 2017

No problem. That's what the details were indicating, some sort of problem with the parent folder that was making Quick Fields think it's a document and fail when it was trying to create a new document in it.

1 0
replied on August 30, 2017

Yes it works like a charm now. I'm ever so grateful!

0 0
replied on January 19, 2023

Thank You. This also helped me. My document failed in quickfields and did not properly read my field for "Date Processed" which was the field that Identified the subfolder of the document path. I had to add the date year to my folder path in the Document Revision pane and it then stored properly, 

0 0
replied on August 29, 2017

But.... thanks for putting me on the right track though, because once I deleted the destination folder and re-adding it (using the same name) it works. So either way thanks so much for your help! smiley There must have been something in the name that was not visible or was corrupt.

You are not allowed to follow up in this post.

Sign in to reply to this post.