Hi Miruna - 

Here's the block:

        'Assign the document to the importer
        Try
            LF_Document = LFDB.GetEntryByID(lDocID)
            Importer.Document = LF_Document
            ' Locks the object for modification.
            LF_Document.LockObject(Lock_Type.LOCK_TYPE_WRITE)

            'Test the first page
            'Alternative
            'If bDocIsImage = True Then
            'Since we have already tested this.

            If Importer.IsAnImageFile(sDocumentFile) Then
                Importer.ImportImagesFromFile(sDocumentFile)
            Else
                Importer.ImportElectronicFile(sDocumentFile)
            End If

            'Clean Up and Return a Status
            Importer = Nothing
            LF_Document.Dispose()
            Return True

        Catch Ex As Exception
            sMessage = "Error in AddPagetoLFDocument for " & sDocumentFile & _
                                     " " & (Err.Description)
            WriteLog.WriteMessage(Now & " " & sMessage)
            AddPageToLFDocument = False
            Err.Clear()
            LF_Document.Dispose()
            Return False
        End Try

The boolean goes back to the calling routine:

        'Next, add the pages
        bRet = AddPageToLFDocument(lDocID, sDocumentFile)
        'Check to see if it worked
        If bRet = False Then
            sMessage = Now & " Create Document failed at step AddPageToLFDocument for: " & sDocName & ". "
            WriteLog.WriteMessage(Now & " " & sMessage)
            Return False
        End If

        'Add Messages about the overall result
        If bRet = True Then
            sMessage = ("Successfully created LFDocument # " & lDocID & " for " & sImportTemplate & ".")
            WriteLog.WriteMessage(Now & " " & sMessage)
        Else
            'Add Messages
            sMessage = ("Failed to create LFDocument # " & lDocID & ".")
            WriteLog.WriteMessage(Now & " " & sMessage)
        End If

So there are two places where an error would be written.  However, the log always reads:

9/26/2016 2:02:13 PM Entering AddPageToLFDocument for TocID #: 8336837 using U:\Mhf\From Corvel\CorvelBills\IN\015035437241_400009869338_NO_ALT_DCN_16266015065063759497.tif.
9/26/2016 2:02:14 PM Successfully created LFDocument # 8336837 for Claims.
9/26/2016 2:02:14 PM Successfully imported U:\Mhf\From Corvel\CorvelBills\IN\015035437241_400009869338_NO_ALT_DCN_16266015065063759497.tif with Claim Number: 400009869338.
9/26/2016 2:02:14 PM Moved file, U:\Mhf\From Corvel\CorvelBills\IN\015035437241_400009869338_NO_ALT_DCN_16266015065063759497.tif to U:\Mhf\From Corvel\CorvelBills\OUT\with a workflow status of File Room.
 

Thanks for taking a look.

Bill,

Not sure if this is the problem but in your Catch block if you are concatenating a message to write to the error log you should be referencing the ex.Message property of the exception object instead of Err.Description.  Perhaps the importer is failing and running the Catch block but the Catch block code is failing before the error log entry is written?

Have you tried to explicitly run your code to force an error to make sure the code in the Catch block works as anticipated?

That won't fix the problem but at least it might log why the code is failing...

Good catch, Cliff - It's all worth a try.  I am a little skeptical only because the value is set to False at the beginning of the routine.  ( AddPageToLFDocument = False) The only way we return True is if we hit line 22 in the first example.  But when you have a mystery everything is fair game.

I don't see any problems with the code that would lead to this behavior. It seems clear that no exception is being thrown since the function returns true, and the DocumentImporter code shouldn't silently fail. This sounds more like a bug in the LF server. Are you importing into a volume with encryption, compression, or checksums enabled? Do you have any workflows running that could be interfering?

Hi Robert - 

The volumes are plain vanilla, and are just roll overs based on size, no compression, and no encryption. There are times when I've traced this to the folder and file level, and it fails in the middle of a volume - that is, at times other than when it is rolling over.  I'll change the exception, and built a WF rule in the meantime that will help us get the documents into the system.  To be continued, I have no doubt.