Receiving 'RU.CF2R: Copy File To Repository Failed' When Using \\ Slashes In Destination URL

(Doc ID 2121605.1)

Last updated on OCTOBER 25, 2017

Applies to:

Oracle Insurance Istream - Version 4.3.0 and later
Information in this document applies to any platform.

Symptoms

On : 4.3.2 version, IStream Publisher

After applying Patch 20114826 Oracle Insurance IStream Publisher 4.3 SP2 Patch 2. the following error occurs.

ERROR
-----------------------

  <errorDetails
  text="RU.CF2R: Copy file to repository failed, Please check file permission./No file found at: file:/file:\\testcase\test1.pdf"
  messageKey="RU.CF2R">com.insystems.distributor.services.rendering.RenderingServiceException: RU.CF2R: Copy file to repository failed, Please check file permission./No file found at: file:/file:\\testcase\test1.pdf/com.insystems.repository.RepositoryException
at com.insystems.distributor.services.util.RepositoryUtils.copyFileToRepository2(RepositoryUtils.java:677)
at com.insystems.distributor.services.util.RepositoryUtils.access$100(RepositoryUtils.java:68)
at com.insystems.distributor.services.util.RepositoryUtils$3.run(RepositoryUtils.java:604)
at com.insystems.distributor.util.common.RepositoryRetryUtils.retry2(RepositoryRetryUtils.java:108)
at com.insystems.distributor.util.common.RepositoryRetryUtils.retry2(RepositoryRetryUtils.java:87)
at com.insystems.distributor.services.util.RepositoryUtils.copyFileToRepository(RepositoryUtils.java:598)
at com.insystems.distributor.services.rendering.BaseRenderingService.copyFileToRepository(BaseRenderingService.java:471)
at com.insystems.distributor.services.rendering.BaseRenderingService.run(BaseRenderingService.java:302)
at com.insystems.distributor.services.word2pdf.Word2Pdf.run(Word2Pdf.java:166)
at com.insystems.distributor.FailureDetector.run(FailureDetector.java:299)
at com.insystems.distributor.FailureDetector$RunThread.run(FailureDetector.java:776)
  caused by: com.insystems.repository.RepositoryException: No file found at: file:/file:\\testcase\test1.pdf



STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Confirm all Publisher services are running.
2. Submit request.
3. Monitor the behavior.




Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms