This appendix includes the following sections:
If you encounter an error during installation:
Read the Oracle Fusion Middleware Release Notes for Microsoft Windows (32-Bit) for the latest updates. The release notes are available with the platform-specific documentation. The most current version of the release notes is available from the Oracle Documentation page on Oracle Technology Network at
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:
Note the error and review the installation log files.
Remove the failed installation by following the steps in Chapter 10, "Deinstalling Oracle WebCenter Content."
Correct the issue that caused the error.
Restart the installation.
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."
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:
On a Windows operating system, the installer writes the following log files:
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.
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)
If the key store 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
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
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 184.108.40.206, "Configuring WebCenter Content 11g to Work with Imaging."
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."
Inbound Refinery will not run as either an application or a service. If you try to run Inbound Refinery from a command line, you receive the following error message:
Error: Cannot read the config.cfg.
|Sun Java is not installed on the Inbound Refinery machine. Sun Java must be installed on both the Content Server machine and the Inbound Refinery machine.||
Inbound Refinery will run as an application, but it will not run as a service. In some cases, you will receive the following error message when launching the service:
Error 1069: The service did not start due to a logon failure.
|If you receive Error 1069, the user linked to the Inbound Refinery service has not been given the right to log on as a service.||Make sure user linked to the Inbound Refinery service is valid and has the right to log on as a service.|
|There is a problem with the Inbound Refinery service.||
The Inbound Refinery service will run for a short period of time when started, but then the service fails and stops.
|Java options settings in the
||Change the Java options settings in the
intradoc.cfg file located in the
\bin directory in a text editor.
First, try the following setting:
Save your changes to the
intradoc.cfg file and restart the Inbound Refinery service.
If the first change is not successful, re-open the
intradoc.cfg file and try the following setting:
JvmCommandLine=$JAVA_EXE $JAVA_SERVICE_EXTRA_OPTIONS $APPEND_CLASSPATH $CLASSPATH $STARTUPCLASS
Save your changes to the
intradoc.cfg file and restart the Inbound Refinery service.
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."
|The refinery has been proxied to Content Server, but the
||Install and enable the
For more information, see Section 220.127.116.11, "Enabling Components for Inbound Refinery on Content Server."
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.
|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 web site 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.
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 web site at
You are running Inbound Refinery as a service, but it will not convert any documents, and the following error message is displayed in the Inbound Refinery log:
Unable to convert, native application reported: 'Permission denied'
This error will usually occur when Samba is used with Content Server on a UNIX operating system or with Inbound Refinery on a Windows operating system.
|You are using AutoExNT to map the UNIX volumes through a mapped network drive to Samba, and the DCOM permissions are not set properly for the user running the Inbound Refinery service.||Change the DCOM permissions for the user running the Inbound Refinery service. For details, see the following procedure for changing DCOM permissions.|
dcmocnfg.exe to check user permissions for the user running the Inbound Refinery service.
On the Default Security tab, make sure the domain user is added to Connect, Access, Launch, and Configuration.
Restart the Inbound Refinery service.
If this appendix does not solve the problem you encountered, try these other sources:
Oracle Fusion Middleware Release Notes for Microsoft Windows (32-Bit), available through the Oracle Documentation page on Oracle Technology Network at
My Oracle Support (formerly OracleMetaLink) web site at
If you do not find a solution for your problem, open a service request.