C Troubleshooting

This chapter describes errors you may receive and information about how to fix them.

This chapter includes the following topics:

Section C.1, "CLOB Conversion Error Opening Data Entry Window"
Section C.2, "Executable Creation Error Opening Data Entry Window"
Section C.3, "Data Entry Window Doesn't Open"
Section C.4, "RWServlet URL Connection Error"
Section C.5, "Dcapi error saying dll already loaded"
Section C.6, "Closing discrepancy of batch loaded CRF error"
Section C.7, "Application Hangs When User Tries to Open a New Window"

C.1 CLOB Conversion Error Opening Data Entry Window

If you receive an error when opening a data entry window that includes text about CLOB conversion, you may need to change the Wrap Data Types setting in the connection pool for the data source of the database.

During RDC Onsite installation, the Oracle Universal Installer creates one connection pool. If you set up additional connection pools manually, you must uncheck the Wrap Data Types setting for each one.

C.2 Executable Creation Error Opening Data Entry Window

If you open a Data Entry Window and get the error, oracle.pharma.oc.dcapi.DataCaptureEngineException: Failed all attempts to create executable, the problem is probably that the path variable on the application server is too long. This is because every software product installed on the computer adds one or more entries to this variable. Most of these entries are not required.

To fix the problem, clean up the path variable, getting rid of all unneeded entries to bring the total length down to 100 characters or the minimum possible.

On your Windows application server, go to the Control Panel, then System and Security, then System, then Advanced System Settings, then the Advanced tab, then Environment Variables.
In the System Variables pane, scroll down to the Path variable and select it.
Click Edit. In the Variable Value field, edit the value by removing all unneeded values until the total length is less than 100 characters, if possible. Also remove any spaces in the path.
Click OK to close each window.

C.3 Data Entry Window Doesn't Open

If you cannot open a Data Entry Window and find the error ORA-12154: TNS:could not resolve the connect identifier specified in the opaServer.out file in a location like: middleware_home\user_projects\domains\OPADomain\servers\Server_Name\logs\Server_Name.out, it is probably because you have not added the database where the CRF is stored to the tnsnames.ora file on the application server.

C.4 RWServlet URL Connection Error

If you are trying to connect to the Application Server using the rwservlet URL and see this error, "rep-52262 diagnostic output is disabled," Reports Server submissions fail.

To fix this:

Log on to the Application Server.
Go to DomainHome\config\fmwconfig\servers\WLS_REPORTS\applications\reports_11.1.2.1.0\configuration
Open rwservlet.properties in a text editor and add the following line below the <inprocess> parameter:

<webcommandaccess>L2</webcommandaccess>

C.5 Dcapi error saying dll already loaded

If you try to open the Data Entry window, after you deleted, and then redeployed the RDC Onsite, you see the Dcapi error saying dll already loaded.

When you redeploy the .ear file, for example, after applying a patch, you must restart the WebLogicServer or the Data Entry Window does not open.

To fix this, you need to restart WebLogicServer.

Note:

In general, you don't need to delete and redeploy RDC Onsite. However, if you have to do that for any reason, follow the instructions as provided in Appendix D.

C.6 Closing discrepancy of batch loaded CRF error

If you get the following message upon saving a change to a discrepancy or blanking outone or more sections of the CRF: All responses in one or more sections have been deleted. If this is the desired action, please delete the entire document, or contact your help desk to change the status of the document, the problem is that the Save logic detected that the CRF was either batch loaded or in status Pass 2 Started, Complete, or Pending and all responses have been deleted in one or more sections. This is not allowed for CRFs that are either batch loaded or in status Pass 2 Started, Complete, or Pending.

Click OK in response to the message. The system displays the document with your changes to the discrepancy status or blanked fields. You can either delete the CRF or close it, using the option to discard changes -- and then contact your help desk to change the status of the document.

To fix this:

For new documents that have status PASS 2 and need to have their Blank flag set to Y, you need to do the following:
1. Update the blank flag via RDCI key changes in Oracle Clinical.
2. Migrate the documents so they can be opened again in RDC Onsite.
For documents that already have the problem, you need to do the following:
1. Create a RDCI Key change in Oracle Clinical to change the Blank flag from N to Y for the documents affected.
2. Create a second RDCI Key change to change the Blank flag from N to Y N for the documents affected (the same ones updated in the first key change).
3. Migrate the documents changed. After that it will be possible to open the blank documents in RDC Onsite.

C.7 Application Hangs When User Tries to Open a New Window

If a user connecting to RDC Onsite using Internet Explorer tries to open a new window and nothing happens, the user may need to increase the number of connections allowed in IE. For instructions from Microsoft, see http://support.microsoft.com/kb/282402#fixit4me. The problem description is about being unable to download only two files at a time, but the fixes described work for the RDC Onsite problem.

C.8 Cannot Log In to Application

If a user cannot log in to RDC Onsite, he or she may have entered the application's URL twice in the same browser window.

Close all browser windows and try the URL again.