F Troubleshooting

This appendix provides troubleshooting information.

This appendix includes the following sections:

F.1 General Troubleshooting Tips

If you encounter an error during installation:

  • Read the Oracle Fusion Middleware Release Notes for your platform for the latest updates.

  • Verify that your system meets the requirements specified in Section 2.1.3, "Reviewing System Requirements and Certification".

  • If you are installing a middle tier, check that the OracleAS Infrastructure with which you want to associate the middle tier is running during installation.

  • If you entered incorrect information on one of the installation screens, return to that screen by clicking Back until you see the screen.

  • If an error occurred while the installer is copying or linking files:

    1. Note the error and review the installation log files.

    2. Remove the failed installation by following the steps in Chapter 10, "Uninstalling Oracle WebCenter Content."

    3. Correct the issue that caused the error.

    4. Restart the installation.

F.2 Oracle WebCenter Content Installation and Configuration Troubleshooting

This section contains solutions to common problems that you might encounter while installing and configuring Oracle WebCenter Content.

If you are having problems with full-text search, Inbound Refinery conversions, Dynamic Converter, Oracle WebCenter Content: Desktop, or Content Categorizer on a Windows operating system, first make sure you have downloaded the correct version of the Visual C++ Redistributable Package, as described in Section 3.7.3, "Downloading Visual C++ Libraries for a Windows Operating System."

F.2.1 Oracle Fusion Middleware Installation and Configuration Log Files

The Oracle Fusion Middleware 11g WebCenter Content Installer and Fusion Middleware Configuration Wizard create their own sets of log files.

  • On a UNIX operating system, the installer writes the following log files:

    • oraInventory_location/logs/installActionstimestamp.log

    • oraInventory_location/logs/oraInstalltimestamp.err

    • oraInventory_location/logs/oraInstalltimestamp.out

    • ORACLE_HOME/install/make.log

  • On a Windows operating system, the installer writes the following log files:

    • inventory_location\logs\installActionstimestamp.log

    • inventory_location\logs\oraInstalltimestamp.err

    • inventory_location\logs\oraInstalltimestamp.out

    The default inventory_location value follows:

  • Fusion Middleware Configuration Wizard writes log files in the cfgtoollogs directory in your Oracle home directory.

If you want to access the log files created by the installer, you need to exit it first. The log files are inaccessible if the installer is still in use.

F.2.2 Oracle IRM Key Store Configuration Issues

If the Oracle Information Rights Management key store has not been configured correctly, then issues will occur during creation of a context. If you cannot create a context, check the server log for one of the following errors.

  • Missing key store file

    If the key store does not exist, you will see a FileNotFoundException message in the log:

    java.io.FileNotFoundException: C:\IRM\oracle\middleware\user_projects
    \domains\base_domain\config\fmwconfig\irm.jceks (The system cannot find the file specified)
  • Missing key

    If the key store exists, but the keys are missing, you will see an UnknownKeyException message in the log:

    The key oracle.irm.wrap does not exist in the key store 
  • Missing password

    If the password is missing or incorrect you will see the following exception in the log:

    java.security.UnrecoverableKeyException: Given final block not properly padded

F.2.3 Imaging Errors During Attempt to Connect to WebCenter Content 11g

When you attempt to connect Imaging to a WebCenter Content 11g repository, Imaging returns errors in these cases:

  • If WebCenter Content is installed in a domain that is later extended with Imaging and you have not restarted the Imaging Managed Server.

  • If the WebCenter Content and Imaging Managed Servers are configured to run on different machines and you have not performed the manual configuration.

For information about avoiding these errors, see Section, "Configuring WebCenter Content 11g to Work with Imaging."

F.3 Inbound Refinery Problems

If you are having problems with Inbound Refinery conversions on a Windows operating system, first make sure you have downloaded the correct version of the Visual C++ Redistributable Package, as described in Section 3.7.3, "Downloading Visual C++ Libraries for a Windows Operating System."

This section provides troubleshooting information for the following Inbound Refinery setup and run issues:

F.3.1 Cannot Log In to Refinery After Installation

When you attempt to log in to a refinery after installation, you get an error similar to the following one:

"Content Server Access Denied
Access denied to Content Server managed resource. Error getting user credentials from proxied user cache. Unable to open file
 c:/ucm/cs1/data/users/proxied/ref1/userdb.txt contains an invalid path."
Possible Causes Solutions

The refinery has been proxied to Content Server, but the InboundRefinerySupport component has not been installed and enabled on Content Server.

Install and enable the InboundRefinerySupport component on Content Server.

For more information, see Section, "Enabling Components for Inbound Refinery on Content Server."

F.3.2 Files Intermittently Stuck in GenWWW Status

When WebCenter Content is run on a Windows Server 2003 system, files intermittently get stuck in GenWWW. There are no conversion errors, and when resubmitted, the files are successfully converted.

Possible Causes Solutions

The problem is directly related to known file locking and deleting issues on a Windows Server 2003 system and typically occurs when Content Server runs on a UNIX operating system and Samba is used to connect to the Windows Server 2003 machine. However, the problem can also occur when you are using Inbound Refinery on the Windows Server 2003 system and Inbound Refinery resides on a separate physical machine from Content Server.

For more information about these Windows Server 2003 issues, see knowledge base articles 885451 and 811492 on the Microsoft Support website at


To confirm that you are experiencing the issues described in Microsoft's knowledge base articles, delete several files on your Windows Server 2003 machine using a remote client. If you witness a delay of up to 40 seconds in the file deletion, it is likely that the Windows Server 2003 locking/deleting issue is the problem. Microsoft offers two solutions to this issue.

  1. Microsoft has a hotfix for Windows Server 2003 that can be shipped on a request-only basis. However, Microsoft's recommendation is to wait until the next service pack unless you are 'severely' affected by the problem.

  2. The alternate solution from Microsoft is to disable opportunistic locking on the Windows Server 2003 server. The solution to disable opportunistic locking does not impact the normal file locking used when writing a file. Rather, opportunistic locking is a speed tweak to the file locking process that can be safely disabled if it is causing problems. Additional information on opportunistic locks is contained in the Samba help files.

If you need specific information on how to disable opportunistic locking on a Windows Server 2003 server, see knowledge base article 29624 on the Microsoft Support website at


F.4 Additional Help

If this appendix does not solve the problem you encountered, try these other sources:

If you do not find a solution for your problem, open a service request.