| Back | Main view
Invalid legacy configuration results in multiple errors during legacy client requests
| Product: | IMiS/ARChive |
| Release: | All |
| Date: | 12/27/2023 |
Case:
Invalid legacy configuration may cause multiple errors during legacy client communication with server. In this article we present different errors which may be logged in server log due to invalid legacy configuration and solution how to correct them.
Description:
Next examples demonstrate different errors which may happened due to invalid legacy configuration:
Example 1: Error during "object create" request:
12/22/23 12:43:19.234 [iarcd:70575:7f022ffff700] DBG[7] HandleOnRead(fd=294, len=1, state=1, err=0).
12/22/23 12:43:19.234 [iarcd:70575:7f022ffff700] DBG[7] Calling session's request handler with 1 request bytes...
12/22/23 12:43:19.234 [iarcd:70575:7f022ffff700] DBG[7] BeginRead(fd=294, buf_size=32767, timeout=86400000ms).
12/22/23 12:43:19.234 [iarcd:70575:7f022ffff700] DBG[7] HandleOnRead(fd=294, len=87, state=1, err=0).
12/22/23 12:43:19.234 [iarcd:70575:7f022ffff700] DBG[7] Calling session's request handler with 88 request bytes...
12/22/23 12:43:19.234 [iarcd:70575:7f022ffff700] DBG[7] Request ID 1 received.
12/22/23 12:43:19.234 [iarcd:70575:7f022ffff700] DBG[7] Request ObjCreate: Profile 'Dokumenti', ContentType 'application/msword'
12/22/23 12:43:19.234 [iarcd:70575:7f022ffff700] ERR[3] Unable to locate database record for entity '0'.
12/22/23 12:43:19.234 [iarcd:70575:7f022ffff700] DBG[7] Response ready to be dispatched (size=56, parts=1).
12/22/23 12:43:19.234 [iarcd:70575:7f022ffff700] DBG[7] BeginWrite(fd=294, buf_size=56, timeout=86400000ms).
12/22/23 12:44:02.319 [iarcd:70575:7f01fb7fe700] DBG[7] HandleOnRead(fd=294, len=87, state=1, err=0).
12/22/23 12:44:02.319 [iarcd:70575:7f01fb7fe700] DBG[7] Calling session's request handler with 88 request bytes...
12/22/23 12:44:02.319 [iarcd:70575:7f01fb7fe700] DBG[7] Request ID 1 received.
12/22/23 12:44:02.319 [iarcd:70575:7f01fb7fe700] DBG[7] Request ObjCreate: Profile 'Dokumenti', ContentType 'application/pdf'
12/22/23 12:44:02.319 [iarcd:70575:7f01fb7fe700] ERR[3] Unable to locate database record for entity '0'.
12/22/23 12:44:02.319 [iarcd:70575:7f01fb7fe700] DBG[7] Response ready to be dispatched (size=56, parts=1).
12/22/23 12:44:02.319 [iarcd:70575:7f01fb7fe700] DBG[7] BeginWrite(fd=294, buf_size=56, timeout=86400000ms).
12/22/23 12:45:21.671 [iarcd:70575:7f022e7fc700] DBG[7] HandleOnRead(fd=294, len=1, state=1, err=0).
12/22/23 12:45:21.671 [iarcd:70575:7f022e7fc700] DBG[7] Calling session's request handler with 1 request bytes...
12/22/23 12:45:21.671 [iarcd:70575:7f022e7fc700] DBG[7] BeginRead(fd=294, buf_size=32767, timeout=86400000ms).
12/22/23 12:45:21.671 [iarcd:70575:7f022e7fc700] DBG[7] HandleOnRead(fd=294, len=87, state=1, err=0).
12/22/23 12:45:21.671 [iarcd:70575:7f022e7fc700] DBG[7] Calling session's request handler with 88 request bytes...
12/22/23 12:45:21.671 [iarcd:70575:7f022e7fc700] DBG[7] Request ID 1 received.
12/22/23 12:45:21.671 [iarcd:70575:7f022e7fc700] DBG[7] Request ObjCreate: Profile 'Dokumenti', ContentType 'application/vnd.ms-outlook'
12/22/23 12:45:21.671 [iarcd:70575:7f022e7fc700] ERR[3] Unable to locate database record for entity '0'.
12/22/23 12:45:21.671 [iarcd:70575:7f022e7fc700] DBG[7] Response ready to be dispatched (size=56, parts=1).
12/22/23 12:45:21.671 [iarcd:70575:7f022e7fc700] DBG[7] BeginWrite(fd=294, buf_size=56, timeout=86400000ms).
Example 2: Error during "object close" request:
12/22/23 12:53:50.635 [iarcd:70575:7f022cff9700] DBG[7] HandleOnRead(fd=269, len=1, state=1, err=0).
12/22/23 12:53:50.635 [iarcd:70575:7f022cff9700] DBG[7] Calling session's request handler with 1 request bytes...
12/22/23 12:53:50.635 [iarcd:70575:7f022cff9700] DBG[7] BeginRead(fd=269, buf_size=32767, timeout=86400000ms).
12/22/23 12:53:50.635 [iarcd:70575:7f022cff9700] DBG[7] HandleOnRead(fd=269, len=11, state=1, err=0).
12/22/23 12:53:50.635 [iarcd:70575:7f022cff9700] DBG[7] Calling session's request handler with 12 request bytes...
12/22/23 12:53:50.635 [iarcd:70575:7f022cff9700] DBG[7] Request ID 4 received.
12/22/23 12:53:50.635 [iarcd:70575:7f022cff9700] DBG[7] Returning handle lock (handle '131085', lockable '0x7f01e0116c50')
12/22/23 12:53:50.635 [iarcd:70575:7f022cff9700] DBG[7] Request ObjClose, handle=0002000d
12/22/23 12:53:50.635 [iarcd:70575:7f022cff9700] DBG[7] Handle released (handle '139646566793229', id 'fae87f23-9fc2-4bf9-8b90-1f5a04f58e00', lockable '0x7f01e0116c50')
12/22/23 12:53:50.635 [iarcd:70575:7f022cff9700] DBG[7] Returning handle lock (handle '65549', lockable '0x7f01e01457f0')
12/22/23 12:53:50.635 [iarcd:70575:7f022cff9700] DBG[7] Opened entity handles; ro: 0, rw: 0
12/22/23 12:53:50.635 [iarcd:70575:7f022cff9700] DBG[7] Handle released (handle '139642271760397', id 'fe3f607d-5ed7-4bab-b4fc-7928308d55ac', lockable '0x7f01e01457f0')
12/22/23 12:53:50.636 [iarcd:70575:7f022cff9700] ERR[3] Resolving scope entity (type 'C', id 'C=99^C=01') failed while evaluating timestamping rule 'bffd3919-7bcf-48e5-9e03-771cc53332fe'. Reason: 'Unable to find entity with classification code 'C=99^C=01'.'.
12/22/23 12:53:50.636 [iarcd:70575:7f022cff9700] DBG[7] Response ready to be dispatched (size=12, parts=1).
12/22/23 12:53:50.636 [iarcd:70575:7f022cff9700] DBG[7] BeginWrite(fd=269, buf_size=12, timeout=86400000ms).
12/22/23 12:53:50.636 [iarcd:70575:7f022cff9700] DBG[7] HandleOnWrite(fd=269, len=12, state=2, err=0).
12/22/23 12:53:50.636 [iarcd:70575:7f022cff9700] DBG[7] Response dispatched (size=12).
12/22/23 12:53:50.636 [iarcd:70575:7f022cff9700] DBG[7] BeginRead(fd=269, buf_size=32768, timeout=86400000ms).
Next example demonstrates invalid (disabled) legacy configuration:
<ns1:StorageProfile xsi:type="ns1:LegacyArchivalStorageProfile" disabled="true" returnContentId="false">
<ns1:Name xsi:type="xsd:string">Legacy02</ns1:Name>
<ns1:Parent xsi:type="ns1:EntityId" type="ClassificationCode">C=99^C=01</ns1:Parent>
<ns1:TemplateName xsi:type="xsd:string">sys:LegacyObject</ns1:TemplateName>
<ns1:EntityTitle xsi:type="xsd:string">Legacy Document</ns1:EntityTitle>
<ns1:Status xsi:type="xsd:string">Opened</ns1:Status>
</ns1:StorageProfile>
To fix this issue, legacy configuration must be corrected to become enabled again. In most such cases, legacy configuration becomes invalid when parent container is changed (reclassification ...).
Related Documents:
| Back | Main view