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:

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."

This section provides troubleshooting information for the following Oracle WebCenter Content installation and configuration issues:

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:

    %PROGRAMFILES%\Oracle\Inventory

  • 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 Keystore Configuration Issues

If the Oracle Information Rights Management keystore 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 keystore file

    If the keystore 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 keystore exists, but the keys are missing, you will see an UnknownKeyException message in the log:

    oracle.irm.engine.content.store.UnknownKeyException: 
The key oracle.irm.wrap does not exist in the key store 
C:\IRM\oracle\middleware\user_projects\domains\base_domain\config\fmwconfig\irm.jceks

  • 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 Oracle WebCenter Content: 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 6.1.1.1, "Configuring WebCenter Content 11g to Work with Imaging."

F.2.4 Imaging Errors from AXF If Oracle SOA Suite Not Installed

If you use Oracle WebCenter Content: Imaging without Oracle SOA Suite in a single-machine environment, Imaging generates errors AXF errors when you start the Imaging Managed Server. The AXF product require Oracle SOA Suite to be installed in the same WebLogic Server domain as Oracle WebCenter Content in a single-machine environment. You can ignore these errors if you do not plan to use AXF for BPEL or AXF for BPM with Imaging.

You can also get these AXF errors if the Oracle SOA Suite Managed Server is not running when you start the Imaging Managed Server.

For more information, see Chapter 6, "Completing the Imaging Configuration."

F.2.5 Content Server Errors Connecting to Oracle WSM Policy Manager in Domain with Oracle SOA Suite or Oracle BAM

If you get connection errors from Web Services Manager (Oracle WSM) Policy Manager when you start Oracle WebCenter Content Server in a domain that includes Oracle SOA Suite or Oracle Business Activity Monitoring (Oracle BAM), you need to start the Oracle SOA Suite or Oracle BAM Managed Server before you start the WebCenter Content Managed Server.

Oracle WSM is configured during domain creation or extension for Content Server to connect to the Policy Manager. You need to start either Oracle SOA Suite or Oracle BAM first so Content server can make these connections.

For more information, see Section 3.14, "Setting Up Oracle Web Services Manager Security."

F.2.6 Missing Files Error When Starting Records Server Connected to Microsoft SQL Server

If you are using a Microsoft SQL Server database with Oracle WebCenter Content: Records, you can safely ignore any errors with the following text that occur when the Records Managed Server is started:

Failed to find indexable webviewable for content item panel

This text refers to panels used by the Records dashboard for the user. By design, these panels do not have web-viewable interfaces that are indexable. Their content is derived when they are run at display time.

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.
 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 5.2.3.2, "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

http://support.microsoft.com

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

http://support.microsoft.com

F.3.3 RIDC Port Not Set on First Inbound Refinery Startup

The first time you start the Oracle WebCenter Content: Inbound Refinery Managed Server, Inbound Refinery generates an RIDC port not set exception.

The Remote Intradoc Client (RIDC) port is configured after you complete the initial configuration of Inbound Refinery and restart the Inbound Refinery Managed Server. Inbound Refinery should not generate this exception after it is configured and restarted.

For more information, see Section 5.1, "Completing the Initial Inbound Refinery Configuration."

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.