Troubleshooting Graphic Layout Problems

Note:

Check My Oracle Support for troubleshooting tips.

Here are problems you may encounter when working with Graphic Layouts, and possible solutions to each one:

• FRM 41213 Followed by a 771000 Error Message
  
• FRM-41214 Followed by a 777100 Error Message
  
• Nothing Happens When You Try to Generate a Provisional DCI Form
  

FRM 41213 Followed by a 771000 Error Message

If generating a Provisional DCI Form fails with the error "FRM-41213: Unable to connect to the report server", it indicates that the Maintain DCIs Form cannot communicate with the Report Server to process a PDF generation request.

This can be caused if a previous job failed in such a way to cause the current connection from your session to the Reports Server to be disconnected. Try logging out and then logging back in. If this does not work, have an Administrator check if the Reports Server is running.

If you have Administrator privileges, log on to the Reports Server Computer. From the Start menu, select Control Panel, choose Services, check that the Reports Server has a status of STARTED. If not, start it. If you cannot start it, make sure Oracle Discover 4i Service is stopped.

FRM-41214 Followed by a 777100 Error Message

If you navigate to the Special menu, select DCI Layout, then choose Generate Provisional DCI Form, you may get the message:

FRM-41214: Unable to run the report

and followed by error message 777100: Either the PDF for the DCI Form failed to be generated, or the URL of its location is incorrect.

In that case, check these details:

• Is the DCI Form Layout valid? To check, open the Provisional DCI Form Layout in the editor, and run File, and then Validate. Fix any errors, and then try again to generate the DCI Form.

• Was the Reports job successful? The job may have run on the Reports Server instance, but failed because Reports thought that its input was invalid. If the job failed, ask the Queue Manager for details. Typical failure messages contain comments like these:

  • Object 'Rectangle_3751' is not fully enclosed by its enclosing object 'Body'.This occurs when the Form Layout Generator places an object too close to a boundary. Go back to the DCM Graphic Layout, and move objects in from the boundaries of the DCM Layout Region.

  • Body area is beyond print area. This occurs when the page selected for generating the DCI Form is not enough to hold the DCI Layouts. Choose a larger Page Definition.

  • BLOCK#_1_ is empty. This occurs when there are empty blocks in DCM and DCI Layouts. Remove the empty blocks through layout editor and retry DCI Form generation. Usually you will get this if the DCM Graphic Layouts are generated with small first block heights.

  • Image is not found. This occurs when Reports Server cannot find the image that was added to the DCI Layout. Check that the \Software\Oracle\9iDS_HOME\RDC_DCIF_IMAGES registry value is set on Web Server and Reports Server. This is the UNC path specification of the directory where you store DCI Layout images.

• Does the Form Layout have any empty pages? To check, open the Provisional DCI Form Layout in the editor. If there are any empty pages, the system returns this error.

• Is the output more than 20 pages? Due to technical limitations, the DCI Form may not generate. Try reducing the number of pages to less than 20.

• Try running a reference codelist report to a file. Navigate to Admin, then Reports, and Reference Codelists. Select a reference codelist to print, click Job Details, and change destination to FILE. If this does not work, see the Reports Server troubleshooting guide on Metalink.

If you have Administrator privileges, you can try these possibilities:

• Open Windows Explorer to the XMLTEMP directory. Generate the Provisional DCI Form and watch for the creation of the file PDFGENDCIIDVERSIONS_SN First 10 characters of OC ACCOUNT timestamp MI:SStemp.xml. If xml exists, save the file to a different folder before exiting the Maintain DCIs window. If it does not exist, check registry setting OPA_XMLTEMP_UNC, described below.

• Are the required registry values set? The report that generates the PDF reads these registry values on the Reports Server:

  • \Software\Oracle\9iDS_HOME\OPA_XMLTEMP_HTTP

    This is the URL of the directory into which XML is downloaded, and PDF is written to be uploaded.

  • \Software\Oracle\9iDS_HOME\OPA_XMLTEMP_UNC

    This is the UNC pathspec of the directory into which XML is downloaded, and PDF is written to be uploaded.

  • \Software\Oracle\9iDS_HOME\RDC_DCIF_IMAGES

    This is the UNC pathspec of the directory in which image GIF files are to be found, for incorporation into the generated PDF.

• Is the directory pointed to by OPA_XMLTEMP_UNC shared, with read and write permissions, to the account used to set up the Report Server? Log on to the Reports Server computer as domain\opareps. Check that the path specified by the value of registry setting OPA_XMLTEMP_UNC exists. Copy the registry value to the clipboard, then look for the value using Window Explorer. If not, correct the value.

• Is the directory pointed to by RDC_DCIF_IMAGES shared, with read permissions to the account used to set up the Report Server? Log on to the Reports Server computer as domain\account_used_to_set_up_the_Report_Server. Check that the path specified by the value of registry setting RDC_DCIF_IMAGES exists. Copy the value to the clipboard, then look for the value using Window Explorer. If not, correct the value.

• Was the generated PDF document placed into the XMLTEMP directory? You must perform this test before exiting the DCI Form. Look in the directory of the registry setting OPA_XMLTEMP_UNC value. PDFGENDCIIDVERSIONS_SN First 10 characters of OC ACCOUNT timestamp MI:SStemp.xml.

• Is the Reports Server started as the account used to set up the Reports Server initially? Log on to the Reports Server, from Control Panel, then Services, and check the property of the Oracle Reports Server to see if it is started as domain\account_used_to_set_up_the_Report_Server.

Nothing Happens When You Try to Generate a Provisional DCI Form

If you try to generate a Provisional DCI Form through the Special menu in the Maintain DCIs window, and the system returns control to you without returning either an error message or a DCI Form, check the init.ora file for the database.

If the init.ora file contains one or more utl_file_dir parameter definitions, but does not contain a utl_file_dir parameter definition for the directory <opahome>/oc/xmltemp (which is the directory that Oracle Clinical uses during DCI Form generation), you need to add that parameter to the init.ora file.

During Oracle Clinical installation, the directory <opahome>/oc/xmltemp is created. For example, if your opa home directory is usr/opapps, then the directory usr/opapps/oc/xmltemp is created. Add a utl_file_dir parameter definition for this directory as follows:

1. Add the following two lines to the init.ora file, immediately before or after the other utl_file_dir parameter definitions:

   UTL_FILE_DIR = /usr/opapps/oc/xmltemp

   UTL_FILE_DIR = /usr/opapps/oc/xmltemp/

   The second line is the same as the first except for the slash at the end. This line is necessary because of a bug: Oracle Clinical currently includes an extra slash in its references to files in the XMLTEMP directory.

2. Stop and restart the database.