This appendix describes common problems that you might encounter when using the WebCenter Content Storage Connector for Microsoft SharePoint 2010 and explains how to solve them.
This appendix includes the following sections:
In addition to this appendix, review the Oracle Fusion Middleware Error Messages Reference for information about the error messages you may encounter.
This section provides guidelines and a process for using the information in this chapter. Using the following guidelines and process will focus and minimize the time you spend resolving problems.
When using the information in this chapter, Oracle recommends:
After performing any of the solution procedures in this chapter, immediately retrying the failed task that led you to this troubleshooting information. If the task still fails when you retry it, perform a different solution procedure in this chapter and then try the failed task again. Repeat this process until you resolve the problem.
Making notes about the solution procedures you perform, symptoms you see, and data you collect while troubleshooting. If you cannot resolve the problem using the information in this chapter and you must log a service request, the notes you make will expedite the process of solving the problem.
Follow the process outlined in Table A-1 when using the information in this chapter. If the information in a particular section does not resolve your problem, proceed to the next step in this process.
Table A-1 Process for Using the Information in this Chapter
| Step | Section to Use | Purpose |
|---|---|---|
|
1 |
Perform problem-specific troubleshooting procedures for WebCenter Content Storage Connector for Microsoft SharePoint 2010. This section describes:
|
|
|
2 |
Use this section to view frequently asked questions and their answers. |
|
|
3 |
Use My Oracle Support to get additional troubleshooting information about Oracle Fusion Applications or Oracle BI. My Oracle Support provides access to several useful troubleshooting resources, including Knowledge Base articles and Community Forums and Discussions. |
|
|
4 |
Log a service request if the information in this chapter and My Oracle Support does not resolve your problem. You can log a service request using My Oracle Support at |
This section describes common problems and solutions. It contains the following topics:
Section A.2.1, "No Execution Notifications while Installing RBS"
Section A.2.6, "On WebCenter Content, the Connection Configuration Page Displays an Error"
Note:
The solutions provided in this section are based on general observations. The solutions may vary depending on your environment. You might also find other solutions to these issues.
While installing RBS, you do not see any execution notifications.
The RBS installation command runs the installation in the background.
The RBS installation command creates a log file, named rbs_install_log.txt, in the same folder that contains the RBS.msi file. You can view notifications in this log file.
Invalid installation command.
Verify the command that you used to install RBS. For information about how to install RBS, see
http://technet.microsoft.com/en-us/library/ff629463(v=office.14).aspx#Section3
You must also ensure that you replace the following variables of the RBS installation command with valid values:
RBS
If the current path of the command prompt is the same as the path of the RBS installation file, you must replace the RBS variable with the name of the MSI file. If the current path of the command prompt is not the same as the path of the RBS installation file, you must provide the complete path for the file.
DBInstanceName
You must replace the DBInstanceName variable with the SQL server instance name where the database, for which you want to install RBS, exists. You must also verify that this SQL server instance is accessible by using the server instance name.
WSS_Content
You must replace this variable with the database name for which you want to install RBS. You must also verify that this database exists on the SQL server instance that is provided as the DBInstanceName.
Master key does not exist in the database.
The database for which you want to install RBS must contain the DatabaseMasterKey. To create the DatabaseMasterKey:
Replace the variable WSS_Content with the name of the database for which you want to install RBS.
Use the following command:
use [WSS_Content] if not exists (select * from sys.symmetric_keys where name = N'##MS_DatabaseMasterKey##') create master key encryption by password = N'Admin Key Password !2#4'
Authentication issue.
This error occurs when you try to install RBS without appropriate permissions. You must install RBS as a user with sufficient permissions or as a user SharePoint Farm account for this installation.
WCCConnector solution package is already added or deployed.
When deploying the ABC package, the error WCCConnector solution is already added/deployed might appear.This means that the connector is already present in the SharePoint environment. If you are reinstalling the solution, validate that you uninstalled and retracted the connector properly.
The DeploySolution.ps1 file is not digitally signed.
If the environment supports only digitally-signed scripts, follow the standard mechanism to deploy the WSP solution on the SharePoint environment. You must add or deploy WCCConnector.wsp on the SharePoint farm.
Invalid SQL Credentials provided during Connector Installation
Enter valid user credentials for the SQL user.
Invalid or outdated SQL credentials
To update the SQL credentials:
Run the command prompt as an administrator.
Change the path to the folder that contains the WCCConnectorInstaller.exe file.
Use the following command:
WCCConnectorInstaller.exe UpdateSQLCred
Provide the SQL credentials that the connector must use.
The WebLogic Server authenticator was not configured to use the default Java authenticator (-DUseSunHttpHandler).
The following error appears:
http://{doamin}:{port}/_vti_adm/WCCConnector/ConfigurationService.svc with the supplied Domain/Username/Password. Runtime error: com.sun.xml.ws.wsdl.parser.InaccessibleWSDLException: 2 counts of InaccessibleWSDLException.
To ensure that WebCenter Content uses the Java authenticator:
Navigate to the following path:
$domain_home\bin
$domain_home is the domain home directory where WebCenter Content is installed.
Open the startManagedWebLogic.cmd file in edit mode.
Search for JAVA_OPTIONS.
Append the following line to JAVA_OPTIONS:
-DUseSunHttpHandler=true
The system user of the WebCenter Content Server has permissions on the SharePoint Server.
The following error appears:
Getting Runtime error: com.sun.xml.ws.protocol.soap.MessageCreationException: Couldn't create SOAP message due to exception: XML reader error: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '4' (code 52) in prolog; expected '<' ?
You must ensure that the system user of the WebCenter Content server does not have the permission to access the SharePoint server. If the system user has the permission, remove the permission, restart the WebLogic server, and then try again.
Invalid or outdated SQL credentials
To update the SQL credentials:
Run the command prompt as an administrator.
Change the path to the folder that contains the WCCConnectorInstaller.exe file.
Use the following command:
WCCConnectorInstaller.exe UpdateSQLCred
Provide the SQL credentials that the connector must use.
On which database do I need to install and enable RBS?
To find the database where you must install and enable RBS:
Identify the site collection on which you want to enable the connector.
Open SharePoint 2010 Central Administration.
Click Application Management. The Application Management page appears.
In the Site Collection region, click View All Site Collections. The Site Collection List page appears.
Select the web application where the site collection exists. The list of site collections for the web application that you selected appears.
Select the site collection for which you want to enable the connector. The site collection details appear on the right region. These details contain the name of the database in which the site collection exists. You must install RBS on this database
How do I verify whether the RBS installation is successful?
RBS installation has two types of installation, one of the first Web server and the other on all additional Web and Application servers. The validation for both the scenarios is different.To verify whether RBS is successfully installed on the First Web server:
Verify the RBS Installation Logs.
The RBS installation command creates a log file, named rbs_install_log.txt, in the same folder that contains the RBS.msi file. Open the log file by using a text editor and scroll down to the bottom of the file. You must see the following notification in the last few lines of the log file:
Product: SQL Remote Blob Storage - Installation completed successfully.
Note:
This notification does not indicate that the installation is successful. If you see this notification, you must proceed with the database verification task.
Database Verification.
On the SQL Server, verify that the RBS tables exist in the SharePoint content database. You must see several tables under the SharePoint content database. These tables have names that are preceded by the letters mssqlrbs.
To verify whether RBS is successfully installed on all additional Web and Application servers:
Verify the RBS Installation Logs.
The RBS installation command creates a log file, named rbs_install_log.txt, in the same folder that contains the RBS.msi file. Open the log file by using a text editor and scroll down to the bottom of the file. You must see the following notification in the last few lines of the log file:
Product: SQL Remote Blob Storage - Installation completed successfully.
Note:
This notification does not indicate that the installation is successful. If you see this notification, you must proceed with the database verification task.
Verify the RBS folder content.
Verify whether the path C:\Program Files\Microsoft SQL Remote Blob Storage 10.50 contains the following directories:
1033
Client Library
Documentation
Maintainer
Provider Libraries
Server
You can use My Oracle Support (formerly MetaLink) to help resolve Oracle Fusion Middleware problems. My Oracle Support contains several useful troubleshooting resources, such as:
Knowledge base articles
Community forums and discussions
Patches and upgrades
Certification information
Note:
You can also use My Oracle Support to log a service request.
You can access My Oracle Support at https://support.oracle.com.