Project and Portfolio Management Practitioners Forum
cancel

9.14 Upgrade: Error: Unable to find exact physical document. Duplicate found

Highlighted
ppm914
Respected Contributor.

9.14 Upgrade: Error: Unable to find exact physical document. Duplicate found

We recently upgraded from 8.03 to 9.14.  This upgrade also involves moving to new hardware.

We refreshed the database and filesystem from production and upgraded to 9.14.

 

Now, whenever we attach a document to attachment field and submit the request it throws error: "Error: Unable to find exact physical document. Duplicate found"

 

Any idea what is causing this error?

 

Thank you.

3 REPLIES
Celil
Acclaimed Contributor.

Re: 9.14 Upgrade: Error: Unable to find exact physical document. Duplicate found

Hi,
PPM Documentation index fail. PPM automaticly create a number for attachments. Then create a wolder using the number and store the attachment here.
Celil

IT Governance Professional
& PPM Solution Architect
Kerim KILIC
Honored Contributor.

Re: 9.14 Upgrade: Error: Unable to find exact physical document. Duplicate found

the problem is the sequence on knta_documents is not same as the latest doc id in file system, the cause is may be you take db clone before file system. can you try to increase sequence number a bit more then run cachemanager and try to attach document again.
Oscar_Pereira
Honored Contributor.

Re: 9.14 Upgrade: Error: Unable to find exact physical document. Duplicate found

Generally, this gets solve by incrementing the corresponding Sequence in the database a few 100's up

 

Make sure to bounce the server after increasing the KNTA_DOCUMENTS_S sequence

please try the following:

1- Check the DOCUMENT_ID higher value in the KNTA_DOCUMENTS table.
2- Set the KNTA_DOCUMENTS_S sequence higher than value in 1 (KNTA_DOCUMENTS_S.currval, KNTA_DOCUMENTS_S.next_val)
3. Stop the application.
4. Run sh kUpdateHtml.sh command.
5. Start the server.
6. Check functionality again

 

 

set ENABLE_DOCUMENT_CLEANUP_SERVICE to true in the server.conf file, then run kUpdateHTml.sh and restart the server

 

The ENABLE_DOCUMENT_CLEANUP_SERVICE enables a server thread that periodically checks for documents that are no longer attached to a PPM Center entity, and removes those it finds from the PPM Center file system. This parameter is associated with the parameter DOCUMENT_CLEANUP_SERVICE_DELAY, which determines the frequency with which this thread runs.

Add the ENABLE_DOCUMENT_CLEANUP_SERVICE param to the server.conf file and set its value to "true". By default, the delay (DOCUMENT_CLEANUP_SERVICE_DELAY) is 1440 (minutes...which equals 1 day).

 

If steps above don't help you can add the following debug line, to get a more detailed error in the log.

1. Add the following paramameter to the loggin.conf file:
com.kintana.core.logging.PRODUCT_FUNCTION_LOGGING_LEVEL = com.kintana.core.attachments, DEBUG
2. Wait 10 mins.
3. Reproduce the error and send us last server.log file.

Please check this and let us know.

 

 

Oscar Pereira