Forms customization error

Dear all,
Enabled action menu using form personalization for launching reports , when user clicks on Actions-->ReportName it is throwing error --> "Function not available to this responsibility, change the responsibility or contact the system administrator." Kindly help.
Regards,
Charan

Hi;
Please see:
R12 Error 'Function not available to this responsibility' When Trying to Access Custom Form. [ID 553014.1]
The Function Is Not Available Under The Responsibility [ID 454285.1]
R12: Function not available to this responsibility. Change responsibilities or contact System Administrator [ID 1167627.1]
Regard
Helios

Similar Messages

OAM customization error

I wanted to change the font colour of user manager application to red.To get this done i followed the instructions given in the document.the steps have been done in the process are as below.
2.5.1 Prerequisites to Customizing Styles
Be sure to complete the following prerequisites before you start to customize a style. This enables you to keep the original Classic Style (\style0) intact for reference and in case you need to return to it as a last resort.
To prepare to customize styles
As an Identity Administrator, add your own named style as described in the Oracle Access Manager Identity and Common Administration Guide.
The original style stays in effect until an Identity Administrator makes your style the new system default.
As an Identity Administrator, select the new style as the default style so that you can see the effect of any changes you make.
2.5.2 Customization Facts
Style Updates and Maintenance: Default wrapper files in \style0 and default global stylesheets in \shared are periodically updated to instantiate improvements through patches and product upgrades.
The Release Notes notify you when such updates occur so you can propagate the changes to your custom styles. Oracle recommends that you compare the new file with your custom file and propagate any changes to your custom styles. It is risky to overwrite a default style with a customized style that bears the same name.
Be sure to record the changes you make and the files that are involved so you can more quickly update custom stylesheets when you update default styles.
Custom Directory: Stylesheet customization should occur only within your custom directory. Customized stylesheets must reside in your custom directory and relative pointers in all files must point to the files in your custom directory, not to files in \shared.
Registration Files: As discussed in "General Content of Registration Files", a common registration file and each application's registration file contain the names of the stylesheets and schema files needed to present pages for the application. For example, when you look at the User Manager registration file in identity\oblix\apps\userservcenter\userservcenterreg.xml, you can see the application name and the names of the stylesheets the application calls during the completion of various functions.
Also, given the application and the program name, you can locate the corresponding schema file name in the application's registration file.
Oracle recommends that only experienced developers using extreme care consider editing a registration file. Registration files are covered in more detail at "Registration Files".
Pointers: All wrapper files and stylesheets contain pointers as include statements that call another file. Most of these pointers are relative pointers that indicate where within the directory structure the file is without providing an absolute path name.
For example, when you look at the usc_profile.xsl stylesheet called by User Manager functions, you can see that it contains include statements with relative pointers that call the following files:
./basic.xsl
./selectorinfo.xsl
./usc_searchform.xsl
./usc_navbar.xsl
When you change the location of a file (place a copy of a stylesheet in your custom directory for customization), pointers to this file (whether relative or absolute) must be changed to reflect the new location in every file that calls it. All relative pointers in a stylesheet should point to files in your custom directory.
In addition, many stylesheets contain relative pointers to object files. If Oracle Access Manager cannot instantiate an object when the page is loaded, unexpected behavior may result. All relative pointers to object files should be absolute pointers, as discussed in "Editing Stylesheets".
Wrapper Files: Wrapper files include pointers to actual stylesheets in \shared. However, you cannot be assured that a wrapper file is called before the stylesheet because both the common registration file and the application's own registration file call stylesheets according to an internal ordering. For this reason, all wrapper files in your custom directory must be overwritten by a copy of the corresponding default stylesheet from the \shared directory.
Important:
Customizing stylesheets is an iterative process. Attempting to copy the entire contents of \shared into your custom directory at one time produce an error.
Rather than copying all stylesheets at once, you start by investigating registration files to learn which functions (programs) call which stylesheets. You then selectively copy base stylesheets and a function-related stylesheet into your custom directory to overwrite their wrapper files, as discussed in "Copying Stylesheets to Your Custom Directory". You then customize and test the style for that function. When this returns satisfactory results you repeat the process to customize another function.
2.5.3 Customization Guidelines
The following guidelines should help ensure a successful customization.
Retain all original files in the \style0 and \shared directories in pristine condition and store them safely for future use. Also, make a backup copy of your customized style files so that patches won't disrupt your customization.
Record all changes you make and the files that are affected.
Customize and test your new styles in a non-production environment before migrating them to your production environment.
Important:
Oracle recommends that you do not modify original style files in the \shared or \style0 directories. These may be overwritten by patch updates and product upgrades or you may want to refer to them later.
When you use only one style, consider breaking the dependence on stylesheets in the \shared directory (again, to prevent patch\release updates to \style0 and \shared from disrupting customizations). This means that no stylesheet in your custom directory should inherit from or reference a stylesheet in \shared or \style0.
When you use multiple custom styles, consider the pros and cons of sharing customizations between multiple custom styles with implementing individual customizations for each custom style. For example:
Two styles that share the same stylesheet: When two custom styles (custom_style1 and custom_style2) can share the same stylesheet you may be tempted to customize the stylesheet in the \shared directory despite the risk of having your custom style overwritten by an updated stylesheet in a product patch or upgrade.
Two individual styles: When two custom styles (custom_style1 and custom_style2) require their individually customized stylesheets you use the standard methodology and overwrite the wrapper files in your custom directory with the corresponding stylesheets in \shared.
Consider using parameter stylesheet files for a custom style collection, rather than using hard-coded values (tab id's, attribute names, table/link properties, and so on); this is similar to how program code is written using header files.
2.5.4 Customization Methodology Checklist
As mentioned earlier, customization is an iterative process and more of an art than a science. This Guide does not attempt to give precise instructions for getting the presentation you want. Instead, this section outlines the recommended approach for a minor change.
Important:
Oracle recommends that you focus on stylesheets for one function at a time. Attempting to copy all stylesheets from \shared into your custom style directory results in an error.
Table 2-28 Customization Methodology Checklist
Check Action Description
Add a New Style
See the Oracle Access Manager Identity and Common Administration Guide for details about adding a style and selecting your new style as the default.
Choose a Function to Customize
Decide which function to customize first. Oracle recommends that you customize stylesheets related to one function at a time.
Copy Selected Stylesheets into Your Custom Directory
Copy selected stylesheets from \shared to your custom directory to overwrite corresponding wrapper stylesheets:
Base stylesheets
Stylesheets included in base stylesheets
A function-related stylesheet identified in application registration file
Function-related stylesheets identified in oblixbasereg.xml
Customize Stylesheets in Your Custom Directory
Change relative pointers in copied stylesheets to point to files in your custom directory.
Change relative pointers to objects to absolute pointers.
Complete other changes to implement the function's customization.
Record Your Work
Keep a record of the files you change and the changes you make.
Copy Your Custom Directory Structure to WebPass
Build a custom directory structure on WebPass and copy customized styles and images into it.
Note: On WebPass, stylesheets are used only for client-side processing and are not required for server-side processing.
Test Your Customized Style
Test the customized style and make any alterations you need to the stylesheets in your custom directory.
Record the changes.
Customize Another Function
Repeat this process on a function by function basis:
Choose a function.
Copy related stylesheets from \shared to your custom directory.
Customize pointers and styles.
Record and test your work.
Propagate the Customized Style
When you have copied and customized all stylesheets for the application, copy the custom style directory to all Identity Servers and WebPass hosts in your environment.
2.6 Customizing the Identity System Pages
This example shows a method for changing the way a page looks, without changing what it does. The change is a simple font color alteration for a specific page in one application. After making the change you must verify that the change is successful. When you finish this functional customization, you must create the same custom style directory structure on WebPass and copy all image files into it so WebPass can display the appropriate images in response to queries. You then test the implementation.
The following topics demonstrate one sequence in the "Customization Methodology Checklist". You can complete the following procedures to gain first-hand experience:
Task overview: Customizing Identity System pages includes
Completing Prerequisites
Choosing a Function to Customize
Copying Stylesheets to Your Custom Directory
Editing Stylesheets
Copying Images and Styles to WebPass
Testing Your Customized Style
Propagating Styles
See also:
For details about localizing messages, see "Localizing XSL Files".
2.6.1 Completing Prerequisites
A prerequisite to customizing a style is to add a style and select the new style as the default, as described in the Oracle Access Manager Identity and Common Administration Guide. The resulting files and file structure provide the foundation for your customization.
Suppose you added a new style named Pastel in a directory named Pastel and requested files be copied from Classic Style (in directory \style0).
To confirm the results of adding a new style
Add a style and select it as the default, as described in the Oracle Access Manager Identity and Common Administration Guide.
New Custom Directory: Oracle Access Manager creates a directory that duplicates \style0 for the default language, English. If you have installed a Language Pack for French, Oracle Access Manager also creates a directory that duplicates \style0 in the French language directory.
Locate your new custom directory.
For example:
Identity_install_dir \identity\oblix\lang\en-us\Pastel
Identity_install_dir \identity\oblix\lang\fr-fr\Pastel
Wrapper Stylesheets: Your custom directory contains wrapper stylesheets that point to actual stylesheets in another directory. If you selected the Classic Style to copy from, your custom directory duplicates the content of the \style0 directory.
Open a wrapper stylesheet in your new custom directory, basic.xsl, and review the files that it includes.
For this example:
Identity_install_dir\identity\oblix\lang\en-us\Pastel\basic.xsl
<?xml version="1.0" ?>
- 
- <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:oblix="http://www.oblix.com/">
<xsl:include href="./style.xsl" />
<xsl:include href="../msgctlg.xsl" />
<xsl:include href="../../shared/basic.xsl" />
</xsl:stylesheet>
The basic.xsl wrapper stylesheet includes the following three files:
style.xsl file in your custom directory
msgctlg.xsl, one directory up from your custom directory (in identity\oblix\lang\en-us)
basic.xsl in identity\oblix\lang\shared
Locate and review the content of the basic.xsl stylesheet in \shared.
For example:
Identity_install_dir\identity\oblix\lang\shared\basic.xsl
<?xml version="1.0" ?>
- 
- <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:oblix="http://www.oblix.com/">
<xsl:include href="obstringutil.xsl" />
- 
<xsl:include href="font.xsl" />
<xsl:include href="title.xsl" />
The basic.xsl stylesheet in the \shared directory includes additional files (font.xsl, title.xsl, obstringutil.xsl) and provides templates to define attributes and status and control display information. See "basic.xsl" for more information.
During your customization process, you copy selected stylesheets from the \shared directory into your custom directory. This overwrites wrapper files with corresponding stylesheets you can then edit in your custom directory.
New Custom XML Document: In addition to the custom directory structure, when you select the new custom style as the default style, Oracle Access Manager creates an XML document (a duplicate of style0.xml) named after the directory you created.
Locate and open the custom xml document that was created when you added the new style.
For this example:
Identity_install_dir\identity\oblix\config\style\Pastel.xml
<?xml version="1.0" ?>
- <ParamsCtlg xmlns="http://www.oblix.com" CtlgName="style0">
- <ValNameList ListName="">
<NameValPair ParamName="styleReady" Value="TRUE" />
</ValNameList>
</ParamsCtlg>
This new file, stored with style0.xml, provides the status of your custom style and the location of the original style directory from which wrapper files were copied. For example, if your custom style directory is named Pastel and you copied from Classic Style, the Pastel.xml file is created when you select Pastel as the default style.
You do not need to edit this file. The original style0.xml remains unchanged. Also, there is a .lck version, Pastel.xml.lck, which is a lock file. No other new files are created when you add a new style.
Updated styles.xml: The styles.xml file is updated to include a new NameValPair that provides both the directory and style names you supplied when creating the style.
Locate and open the styles.xml file to confirm it was updated with your new style information.
For example:
Identity_install_dir\identity\oblix\config\style\styles.xml
<?xml version="1.0" encoding="ISO-8859-1" ?>
- <ValNameList xmlns="http://www.oblix.com" ListName="styles.xml">
<NameValPair ParamName="style0" Value="Classic Style" />
<NameValPair ParamName="Pastel" Value="Pastel" />
</ValNameList>
In this example, both the default Classic Style and new custom Pastel style are identified. You do not need to edit this file.
After confirming your custom directory structure, new and updated files, you are ready to choose a function and begin your customization.
2.6.2 Choosing a Function to Customize
The first step in the customization process is to choose a function to customize. For this example, suppose you want to change the font color to red on a specific page of the User Manager without changing anything else.
To identify the function and source information
Log in to the Identity System, as usual.
Navigate to the desired page.
For this example, click:
Identity System Console, User Manager, and then click My Identity
The page appears, as shown in Figure 2-6.
Figure 2-6 Customization Example: A User Manager Page Displays Red Text
The following information on each Identity System application page is useful for customizing styles:
Application Name: The application name, User Manager, appears on a highlighted tab in the top left area of the screen.
Each application's \bin directory contains the registration file that you need to identify functions. See "Registration Files".
Page Name: The page name, in this example it is My Profile, is the first page that you want to customize so you can see text in a red font color.
Registration File Path: The URL for each page includes a path to the application page, for example, identity\oblix\apps\userservcenter\bin\userservcenter.cgi. You can use this to locate the relevant registration file on the Identity Server.
Function Name: The URL for each page also includes a segment, program=view in this case, that you can use to locate the relevant stylesheet name for the function in the registration file.
Record the required information to assist you during the customization.
For this example:
Application: User Manager
Page: User Profile
Registration File Path: Identity_install_dir\identity\oblix\apps\userservcenter\bin\
Function: program=view
2.6.3 Copying Stylesheets to Your Custom Directory
Once you have identified the function you want to customize, your next task in any customization is to copy relevant stylesheets into your custom directory from the \shared directory. This activity overwrites wrapper files in your custom directory with copies of stylesheets you can customize. This also retains the original stylesheets in \shared as well as the original default wrappers in \style0.
Locating and copying relevant stylesheets is an iterative process in itself. In the following procedure you must locate and copy:
Base stylesheets
Stylesheets included in base stylesheets
The specific function-related stylesheet identified for the program in the application's registration file, in this case the stylesheet associated with program=view
Stylesheets included in the function-related stylesheet
Eventually your custom directory must contain all stylesheets, including those identified in the application's registration file and in oblixbasereg.xml. Even if you do not need to edit a stylesheet, it must be copied to your custom directory.
Important:
Copying stylesheets is an iterative process that must be done in a selective manner. Attempting to copy all stylesheets from \shared to you custom directory at one time results in an error.
To locate and copy relevant stylesheets
Copy the base stylesheets to your custom style directory from \shared to overwrite the default wrappers with stylesheets you can customize.
For example:
Copy from: Identity_install_dir\identity\oblix\lang\en-us\shared\ basic.xsl, font.xsl, searchform.xsl, navbar.xsl, title.xsl
Copy to: Identity_install_dir\identity\oblix\lang\en-us\Pastel\
This retains the original base stylesheets in \shared as well as the original default wrappers in \style0.
Open each base stylesheet in your custom style directory and locate include statements that point to other stylesheets you must copy, as well as any style information you need to customize.
For this example, see Table 2-29:
Table 2-29 Base Stylesheet Pointers and Items to Customize
Base Stylesheets in Custom Directory Pointers to Related Stylesheets and Items to Customize
basic.xsl
Contains implied relative include pointers to other stylesheets you need in your local custom directory:
<xsl:include href="obstringutil.xsl" />
<xsl:include href="font.xsl" />
<xsl:include href="title.xsl" />
Record the names of additional stylesheets you must copy into your custom directory from \shared. In this case, obstringutil.xsl.
font.xsl
Does not contain include pointers to other files.
Does contain color information you can customize:
<xsl:variable name="subHeadingColor">#006699...
<xsl:variable name="contentTitleColor">#000000...
<xsl:variable name="contentTextColor">#000000...
searchform.xsl
Does not contain include pointers to other files.
Does not contain color information to customize. No changes needed to this stylesheet in your custom directory.
navbar.xsl
Does not contain include pointers to other files.
Does contain color information you may customize later.
title.xsl
Does not contain include pointers to other files.
Does contain color information you may customize later. No changes needed to this stylesheet in your custom directory.
Copy stylesheets included in base stylesheets to your custom directory from \shared.
For this example, obstringutil.xsl:
Copy from: Identity_install_dir\identity\oblix\lang\en-us\shared\ obstringutil.xsl
Copy to: Identity_install_dir\identity\oblix\lang\en-us\Pastel\obstringutil.xsl
Record the stylesheets you have copied from \shared to your custom directory so you can track your work.
Locate the required registration files.
For this example, oblixbasereg.xml and userservcenterreg.xml:
Identity_install_dir\identity\oblix\apps\common\bin\oblixbasereg.xml Identity_install_dir\identity\oblix\apps\userservcenter\bin\ userservcenterreg.xml
At some point, you typically need stylesheets included in the common registration file oblixbasereg.xml. However, stylesheets included in oblixbasereg.xml are not needed for this example.
For this example, you must locate only the function-related stylesheet in the userservcenterreg.xml file.
Open the application's registration file and locate the function-related stylesheet you need.
For this example, locate ObProgram name="view":
<?xml version="1.0" ?>
- <ObProgramRegistry>
- <ObApplication name="userservcenter">
- <ObProgram name="front">
<ObStyleSheet name="usc_profile.xsl" />
<ObSchema name="usc_front.xsd" />
</ObProgram>
- <ObProgram name="commonNavbar">
<ObStyleSheet name="usc_profile.xsl" />
<ObSchema name="usc_front.xsd" />
</ObProgram>
- <ObProgram name="view">
<ObStyleSheet name="usc_profile.xsl" />
<ObButton name="initiateDeactivateUser" />
- 
<ObButton name="userreactivate" />
<ObButton name="wfTicketDelete" />
<ObButton name="userModify" />
<ObSchema name="usc_profile.xsd" />
</ObProgram>
You can see in the registration file that the usc_profile.xsl stylesheet is associated with the function you want to customize (ObProgram name="view"). The usc_profile.xsl stylesheet is also associated with a number of other functions.
Copy the function-related stylesheet, usc_profile.xsl, to your custom style directory from \shared and record the stylesheet name.
For this example:
Copy From: Identity_install_dir\identity\oblix\lang\en-us\shared\ usc_profile.xsl
Copy To: Identity_install_dir\identity\oblix\lang\en-us\Pastel\ usc_profile.xsl
Open the function-related stylesheet and locate include statements that point to other stylesheets you must copy, record any information you plan to customize.
For this example, usc_profile.xsl:
Table 2-30 usc_profile.xsl Pointers and Items to Customize
usc_profile.xsl in Custom Directory Pointers to Related Stylesheets and Items to Customize
usc_profile.xsl
This main stylesheet for the User Manager includes stylesheets that must be copied to your custom directory:
<xsl:include href="./basic.xsl" />
<xsl:include href="./selectorinfo.xsl" />
<xsl:include href="./usc_searchform.xsl" />
<xsl:include href="./usc_navbar.xsl" />
Note: selectorinfo.xsl, usc_searchform.xsl and usc_navbar.xsl should be copied.
Also record pointers to objects that should be customized:
<object id="cenroll" classid= ...
codebase="../../common/bin/xenroll.cab" />
and
<script src="../../common/bin/installCert.vbx" ...
Repeat steps to copy relevant stylesheets, then record their names and details you plan to change.
For this example:
Copy From:
Identity_install_dir\identity\oblix\lang\en-us\shared\selectorinfo.xsl
Identity_install_dir\identity\oblix\lang\en-us\shared\usc_searchform.xsl
Identity_install_dir\identity\oblix\lang\en-us\shared\usc_navbar.xsl
Copy To:
Identity_install_dir\identity\oblix\lang\en-us\Pastel\selectorinfo.xsl Identity_install_dir\identity\oblix\lang\en-us\Pastel\usc_searchform.xsl Identity_install_dir\identity\oblix\lang\en-us\Pastel\usc_navbar.xsl
These stylesheets do not contain include statements, other stylesheet names, nor parameters you need to change.
You have collected, copied, and recorded relevant stylesheets for this example.
2.6.4 Editing Stylesheets
After copying relevant stylesheets, you may need to edit them. As described in Table 2-29 the information that needs to be customized for this example includes:
Font colors defined in the base stylesheet font.xsl should be changed to red.
Pointers to objects defined in usc_profile.xsl should change from a relative path to an absolute path.
Note:
To help streamline development and testing, consider implementing XSL stylesheet control parameters. See "Caching Considerations".
To edit stylesheets for a simple font color change
Open the font.xsl stylesheet in your custom directory in a text editor.
For example,
Identity_install_dir\identity\oblix\lang\en-us\Pastel\ font.xsl
Edit the stylesheet to change all colors from the default color to red (FF0000), then save the change.
For example,
Change all Default Font Colors From:
... <xsl:variable name="pageHeaderColor">#006699</xsl:variable>
<xsl:variable name="subHeadingColor">#006699</xsl:variable>
<xsl:variable name="contentTitleColor">#000000</xsl:variable>
<xsl:variable name="contentTextColor">#000000</xsl:variable>
and others ...
To Red (#FF0000):
... <xsl:variable name="pageHeaderColor">#FF0000</xsl:variable>
<xsl:variable name="subHeadingColor">#FF0000</xsl:variable>
<xsl:variable name="contentTitleColor">#FF0000</xsl:variable>
<xsl:variable name="contentTextColor">#FF0000</xsl:variable>
and others ...
Record your changes to this file.
If you restarted the Identity Server now you would not yet see your changes. This is because you have not yet customized the function-related stylesheet that identifies where to apply the changes.
Edit the basic.xsl stylesheet in your custom directory as follows to add required include statements that were in the original basic.xml (but were lost when you copied over the basic.xsl from the shared folder).
Locate the line containing the following:
<xsl:include href="obstringutil.xsl"/>
Add the following information so that it precedes the line identified in a):
<xsl:include href="./style.xsl" />
<xsl:include href="../msgctlg.xsl" />
Edit the usc_profile.xsl stylesheet in your custom directory to change the relative path to objects, as shown in the following, then save the changes.
For example:
Change From a Relative Path:
- <head>
...<object id="cenroll" classid="clsid:43F8F289-7A20-11D0-8F06-00C04FC295E1" codebase="../../common/bin/xenroll.cab" />
... <script src="../../common/bin/installCert.vbx" language="VBScript" />
</head>
Change To an Absolute Path:
- <head>
... <object id="cenroll" classid="clsid:43F8F289-7A20-11D0-8F06-00C04FC295E1" codebase="/identity/oblix/apps/common/bin/xenroll.cab" />
... <script src="/identity/oblix/apps/common/bin/installCert.vbx" language="VBScript" />
</head>
This concludes the specific function-related change for this example.
Ensure that file system access control for new custom style directories and files is set to match the ownership and permissions of \style0.
Restart the Identity Server.
If you log in to the Identity System now and view the My Identity page, you see the red font color. However, the images supplied by WebPass won't appear until they are included in a corresponding custom style directory structure on the WebPass host.
After doing this i checked user manager application then iam being displayed the following error page.
style shhet error report form.
an error has occured while executing the application.
your browser does not support sending email automatically.
please send email to <a=" "><\a> with the following information.
you name
email adress
make sure to append the trace back in the mail
in the log file errors have been given as below
Error: ExXSLTProcessingGeneric: Exception processing stylesheet. Root stylesheet ID: ../../../lang/en-us/pastel2/usc_profile.xsl
"Failed to compile XSL file."     XSL file:^../../../lang/en-us/pastel2/usc_profile.xsl
Error: ExXSLTProcessingGeneric: Exception processing stylesheet. Root stylesheet ID: ../../../lang/en-us/pastel2/usc_profile.xsl
"OIS_LOG_PASSED_ERROR"     Error^writer\obhtmlpage.cpp:276: Error: ExXSLTProcessingGeneric: Exception processing stylesheet. Root stylesheet ID: ../../../lang/en-us/pastel2/usc_profile.xsl

Hi Matt,
I think the page you are being redirected to is servererror.jsp, which is deployed within oam-server.ear, within its own ngsso-web.war application. You could deploy your own version of this. I assume you could also modify the ErrorPage setting in oam-config.xml to define your own page, though I have not tested this. This would be a customisation, so you would be responsible for the system behaviour when doing this.
Regards,
Colin

Customize error-page

Hi all,
May I customize error page for HTTP Status 401 (http authentication error)? I am using <auth-method>BASIC</auth-method> , therefore
<form-error-page>/xxx.jsp</form-error-page> is not working, please advise.
Thx.
Jacky

Use <error-page>/error.html</error-page> element

Crystal Report Windows Forms Viewer Error in 1 Workstation after upgrade of PL

Hi all,
We just upgraded SAP from 8.82 PL02 to 8.82 PL15.
Afterwards, in just 1 workstation, Crystal Reports layouts have Crystal Report Windows Forms Viewer error I attach.
Before the upgrade this error did not happen.
No permissions or authorizations were changed in the workstation.
The Crystal Reports layouts remain working fine in server and in the other workstations.
In the workstation following are installed:
- Operating System Windows 7;
- Microsoft .NET Framework 4.5;
- SAP Crystal Reports runtime engine for. NET Framework;
- Crystal Report 2008 Runtime SP6;
- Microsoft SQL Server 2008 R2 Native Client.
All, but the operating system, are equal to the other workstations.
User has edit access to SAP folders, temp and access to the attach path.
We already uninstalled SAP client and client agent and re-installed it but with no avail.
Can anyone help me?
Thanks in advance.
Best regards,
Pedro Mariano

Hi San Xu,
Thank you for your input.
However I'm facing problem with each software is suitable.
I installed SAP Crystal Reports for SAP Business One (CR 2011 V14.0.4.738), but with no avail.
Thanks in advance.
Best regards,
Pedro Mariano

How to Customize Error message in JXL

Hi All,
I want to customize error message in JXL. I.e. When we apply number validation to a cell and if you enter invalid data MS-Excel shows error message saying that "The value you entered is not valid". But I want to customize this message to "Data should be a decimal number". Can anyone help me how to acheive it. Thanks in Advance.
Thanks
Venkat.

Thx alot...!! for all your valuable replies.
And, I found a way to achieve my requirement in a declarative way.
I just created an entity validator on EmployeeEO.
- Rule_Type: Key Exists
- Rule Definition:
- Validation Target Type: Entity Object
- Association Name : <Select Assiociation created > "EmpDeptFK"
- Failure Handling:
- Error Message: "Invalid Deparment ID {0} Entered. Please enter a valid Department ID."
- Message Token for "0": Department ID
And It fulfilled my requirement.

InfoPath form, rich text fields, "There was a form postback error" InvalidOperationException, There has been an error while processing the form

Using InfoPath 2013 browser enabled form.
I am getting the above error on ALL Infopath Designed Rich Text fields, where the "Cannot be blank" attribute is set.
To reproduce it, I create a custom list and custom list form with InfoPath 2013. I add 2 Rich Text fields and enable "cannot be blank". To raise the error, I put some data in the RT field. Skip to another field (so focus is changed and a postback
occurs), then back to original field to delete the contents (to raise the validation).
I originally thought it was associated with the HTMLCHKR.DLL not being registered (and I have re-registered it just in case), but the exception I get from the ULS logs reads (it is from a list AFTER I have re-registered the DLL):
There was a form postback error. (User: 0#.w|myDomain\jc, Form Name: Template, IP: , Request: h t t p ://MyWebApp/MySite/Lists/rtAfterHtmlCHkrReg/Item/newifs.aspx?List=2212ff41-77b4-445b-931b-d7e538c9da91&Source=h t t p://MyWebApp/MySite/Lists/rtAfterHtmlCHkrReg/AllItems.aspx&RootFolder=&Web=3db49106-bdca-47bb-b4cd-a549d2d86aa7,
Form ID: urn:schemas-microsoft-com:office:infopath:list:-AutoGen-2015-01-16T21:51:48:853Z, Type: InvalidOperationException, Exception Message: No content generated as the result of the operation.) 8cc5e09c-3665-903b-575a-faaac506c40a
I noticed that errors associated with the HTMLCHKR.DLL not being registered would have some sort of COM exception (example: TYPE_E_LIBNOTREGISTERED or REGDB_E_CLASSNOTREG)
I also should mention that this problem started happening about 3 weeks ago. We have extended the web application to handle HTTPS on the intranet zone (we had a reverse proxy project that did not eventuate) - would that cause something? How can I do further
checking?

Hi,
I have done a test in my SharePoint, and I met the same issue with you.
I created a custom list and custom list form with InfoPath 2013. I added 2 Rich Text fields and enabled "cannot be blank". I put some content in the RT field, then delete the contents, I got the error message:"there has been an
error while processing the form."
Here is a similar post said that executing the command: regsvr32 "C:\Program Files\Common Files\Microsoft Shared\
OFFICE14\htmlchkr.dll" will solve the issue.
https://social.msdn.microsoft.com/Forums/en-US/eb2e0f6e-c8e4-4e92-ac5e-a09d72759eda/rich-text-field-error-in-webform?forum=sharepointcustomizationprevious
But I just disabled "cannot be blank", and it solved the issue.
Best Regards,
Lisa Chen
Lisa Chen
TechNet Community Support

I have a problem in this that i want to paas a form in a case that when user pres n then it must go to a form but error arises and not working good and threading is not responding

made in cosmos help please need it
using System;
using Cosmos.Compiler.Builder;
using System.Threading;
using System.Windows.Forms;
namespace IUOS
    class Program
        #region Cosmos Builder logic
        // Most users wont touch this. This will call the Cosmos Build tool
        [STAThread]
        static void Main(string[] args)
            BuildUI.Run();
        #endregion
        // Main entry point of the kernel
        public static void Init()
            var xBoot = new Cosmos.Sys.Boot();
            xBoot.Execute();
            Console.ForegroundColor = ConsoleColor.DarkBlue;
            a:
            Console.WriteLine("------------------------------");
            Console.WriteLine("WELCOME TO THE NEWLY OS MADE BY THE STUDENTS OF IQRA UNIVERSITY!");
            Console.WriteLine("------------------------------");
            Console.WriteLine();
            Console.WriteLine();
            Console.WriteLine();
            Console.WriteLine("\t _____
            Console.WriteLine("\t|   |       |            |
|          |      |");
            Console.WriteLine("\t|   |       |            |
|          |      |");
            Console.WriteLine("\t|   |       |            |
|          |      |");
            Console.WriteLine("\t|   |       |            |
|          |      |___________");
            Console.WriteLine("\t|   |       |            |
|          |                  |");
            Console.WriteLine("\t|   |       |            |
|          |                  |");
            Console.WriteLine("\t|   |       |            |
|          |                  |");
            Console.WriteLine("\t|   |       |            |
|          |                  |");
            Console.WriteLine("\t|   |       |            |
|          |                  |");
            Console.WriteLine("\t|_____|       |____________|         |____________|      ____________");
            string input;
            Console.WriteLine();
            Console.Write("\nAbout OS     : a");
            Console.Write("\nTo Shutdown : s");
            Console.Write("\nTo Reboot    : r");
            Console.Write("\nStart Windows Normaly : n");
            Console.WriteLine();
            input = Console.ReadLine();
            if (input == "s" || input == "S"){
                Cosmos.Sys.Deboot.ShutDown();
            else
            if (input == "r" || input == "R"){
                Cosmos.Sys.Deboot.Reboot();
            else
            if (input == "a" || input == "A"){
                Console.ForegroundColor = ConsoleColor.DarkBlue;
                Console.Clear();
                Console.WriteLine("\n\n\n-------------------------------------");
                Console.WriteLine("version: DISPLAYS OS VERSION");
                Console.WriteLine("about: DISPLAYS INFO ABOUT ANGRY OS");
                Console.WriteLine("hello or hi: DISPLAYS A HELLO WORLD");
                Console.WriteLine("MESSAGE THAT WAS USED TO TEST THIS OS!!");
                Console.WriteLine("-----------------------------------");
                Console.Write("You Want to know : ");
                input = Console.ReadLine();
                if (input == "version"){
                    Console.WriteLine("--------------------");
                    Console.WriteLine("OS VERSION 0.1");
                    Console.WriteLine("--------------------");
                else
                if (input == "about"){
                    Console.WriteLine("--------------------------------------------");
                    Console.WriteLine("OS IS DEVELOPED BY Qazi Jalil-ur-Rahman & Syed Akber Abbas Jafri");
                    Console.WriteLine("--------------------------------------------");
                Console.Write("Want to go back to the main window");
                Console.Write("\nYes : ");
                string ans = Console.ReadLine();
                if (ans == "y" || ans == "Y")
                    goto a;
                    Thread.Sleep(10000);
                else
                if (input == "n" || input == "N")
                    Thread.Sleep(5000);
                    Console.Clear();
                    for (int i = 0; i <= 0; i++){
                        Console.Write("\n\n\n\n\t\t\t\t\t ____        ____   ___
                        Console.Write("\n\t\t|\t\t | |      |    |
|   | | | | |");
                        Console.Write("\n\t\t|\t|    | |---- |    |
|   | | | | |---");
                        Console.Write("\n\t\t|____|____| |____ |___ |____ |___| |    | |___");
                        Thread.Sleep(500);
                    Thread.Sleep(5000);
                    Console.Clear();
                    BootUserInterface();
                    Console.ReadLine();
//                    Form1 fo = new Form1();
                else{
                    for (int i = 0; i <= 5; i++){
                        Console.Beep();
                        Thread.Sleep(1000);
                        goto a;
            while (true);
        private static void BootUserInterface() {
            Thread t = new Thread(UserInterfaceThread);
            t.IsBackground = true;
            t.SetApartmentState(ApartmentState.STA);
            t.Start();
        private static void UserInterfaceThread(object arg) {
            Form1 frm = new Form1(); // use your own
            Application.Run(frm);

Hi
Jalil Cracker,
>>when user pres n then it must go to a form but error arises and not working good and threading is not respondin
Could you post the error information? And which line caused this error？
If you want to show Form1, you can use form.show() method
Form1 frm = new Form1();
frm.Show();
In addition, Cosmos is an acronym for C# Open Source Managed Operating System. This is not Microsoft product.If the issue is related to Cosmos, it would be out of our support. Thanks for your understanding. And you need raise an issue at Cosmos site.
Best regards,
kristin
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

First ever Web Form - URL error

Hi. I'm attempting to call my first Web form, but I'm getting this error:
URL:
http://springfield01:7777/forms/frmservlet?config=ttmsmenu
ERROR:
500 Internal Server Error
Forms Servlet Error.
Missing or invalid value for baseHTML parameter.
Please check the servlet configuration to make sure this value specifies a valid file.
My FormsWeb.Cfg file is posted below. Any help would be greatly appreciated!
FORMSWEB.CFG:
# $Id: formsweb.cfg 15-apr-2005.13:17:30 pkuhn Exp $
# formsweb.cfg defines parameter values used by the FormsServlet (frmservlet)
# This section defines the Default settings. Any of them may be overridden in the
# following Named Configuration sections. If they are not overridden, then the
# values here will be used.
# The default settings comprise two types of parameters: System parameters,
# which cannot be overridden in the URL, and User Parameters, which can.
# Parameters which are not marked as System parameters are User parameters.
# SYSTEM PARAMETERS
# These have fixed names and give information required by the Forms
# Servlet in order to function. They cannot be specified in the URL query
# string. But they can be overridden in a named configuration (see below).
# Some parameters specify file names: if the full path is not given,
# they are assumed to be in the same directory as this file. If a path
# is given, then it should be a physical path, not a URL.
# USER PARAMETERS
# These match variables (e.g. %form%) in the baseHTML file. Their values
# may be overridden by specifying them in the URL query string
# (e.g. "http://myhost.mydomain.com/forms/frmservlet?form=myform&width=700")
# or by overriding them in a specific, named configuration (see below)
[default]
# System parameter: default base HTML file
baseHTML=base.htm
# System parameter: base HTML file for use with JInitiator client
baseHTMLjinitiator=basejini.htm
# System parameter: base HTML file for use with Sun's Java Plug-In
baseHTMLjpi=basejpi.htm
# System parameter: delimiter for parameters in the base HTML files
HTMLdelimiter=%
# System parameter: working directory for Forms runtime processes
# WorkingDirectory defaults to <oracle_home>/forms if unset.
workingDirectory=
# System parameter: file setting environment variables for the Forms runtime processes
envFile=default.env
# Forms runtime argument: whether to escape certain special characters
# in values extracted from the URL for other runtime arguments
escapeparams=true
# Forms runtime argument: which form module to run
form=test.fmx
# Forms runtime argument: database connection details
userid=
# Forms runtime argument: whether to run in debug mode
debug=no
# Forms runtime argument: host for debugging
host=
# Forms runtime argument: port for debugging
port=
# Other Forms runtime arguments: grouped together as one parameter.
# These settings support running and debugging a form from the Builder:
otherparams=buffer_records=%buffer% debug_messages=%debug_messages% array=%array% obr=%obr% query_only=%query_only% quiet=%quiet% render=%render% record=%record% tracegroup=%tracegroup% log=%log% term=%term%
# Sub argument for otherparams
buffer=no
# Sub argument for otherparams
debug_messages=no
# Sub argument for otherparams
array=no
# Sub argument for otherparams
obr=no
# Sub argument for otherparams
query_only=no
# Sub argument for otherparams
quiet=yes
# Sub argument for otherparams
render=no
# Sub argument for otherparams
record=
# Sub argument for otherparams
tracegroup=
# Sub argument for otherparams
log=
# Sub argument for otherparams
term=
# HTML page title
pageTitle=Oracle Application Server Forms Services
# HTML attributes for the BODY tag
# HTMLbodyAttrs=
# immediately hide the applet parent window
HTMLbodyAttrs=onLoad='javascript:self.moveTo(1601,1201)'
# HTML to add before the form
# HTMLbeforeForm=
HTMLbeforeForm=<SCRIPT LANGUAGE="JavaScript">window.opener = top;</SCRIPT>
# HTML to add after the form
HTMLafterForm=
# Forms applet parameter: URL path to Forms ListenerServlet
serverURL=/forms/lservlet
# Forms applet parameter
codebase=/forms/java
# Forms applet parameter
# imageBase=DocumentBase
imageBase=/forms/java
# Forms applet parameter
#width=1000
#width=100%
width=500
# Forms applet parameter
#height=700
#height=100%
height=500
# Forms applet parameter
separateFrame=true
# separateFrame=
# Forms applet parameter
splashScreen=no
#splashScreen=ttmslogo_new.gif
# Forms applet parameter
background=no
# background=
# background=ttmslogo_new.gif
# Forms applet parameter
logo=ttms_banner.gif
# Forms applet parameter
lookAndFeel=Oracle
# Forms applet parameter
colorScheme=teal
# Forms applet parameter
restrictedURLparams=HTMLbodyAttrs,HTMLbeforeForm,pageTitle,HTMLafterForm,log,allow_debug,allowNewConnections
# Forms applet parameter
formsMessageListener=
# Forms applet parameter
recordFileName=
# Forms applet parameter
serverApp=default
# Forms applet archive setting for JInitiator
archive_jini=frmall_jinit.jar
# Forms applet archive setting for other clients (Sun Java Plugin, Appletviewer, etc)
archive=frmall.jar
# Number of times client should retry if a network failure occurs. You should
# only change this after reading the documentation.
networkRetries=0
# Page displayed to Netscape users to allow them to download Oracle JInitiator.
# Oracle JInitiator is used with Windows clients.
# If you create your own page, you should set this parameter to point to it.
jinit_download_page=/forms/jinitiator/us/jinit_download.htm
# Parameter related to the version of JInitiator
jinit_classid=clsid:CAFECAFE-0013-0001-0022-ABCDEFABCDEF
# Parameter related to the version of JInitiator
jinit_exename=jinit.exe#Version=1,3,1,22
# Parameter related to the version of JInitiator
jinit_mimetype=application/x-jinit-applet;version=1.3.1.22
# Page displayed to users to allow them to download Sun's Java Plugin.
# Sun's Java Plugin is typically used for non-Windows clients.
# (NOTE: you should check this page and possibly change the settings)
jpi_download_page=http://java.sun.com/products/archive/j2se/1.4.2_06/index.html
# Parameter related to the version of the Java Plugin
jpi_classid=clsid:CAFEEFAC-0014-0002-0006-ABCDEFFEDCBA
# Parameter related to the version of the Java Plugin
jpi_codebase=http://java.sun.com/products/plugin/autodl/jinstall-1_4_2-windows-i586.cab#Version=1,4,2,06
# Parameter related to the version of the Java Plugin
jpi_mimetype=application/x-java-applet;jpi-version=1.4.2_06
# EM config parameter
# Set this to "1" to enable Enterprise Manager to track Forms processes
em_mode=0
# Single Sign-On OID configuration parameter
oid_formsid=%OID_FORMSID%
# Single Sign-On OID configuration parameter
oracle_home=/apps/oracle9i/product/oracleforms
# Single Sign-On OID configuration parameter
formsid_group_dn=%GROUP_DN%
# Single Sign-On OID configuration parameter: indicates whether we allow
# dynamic resource creation if the resource is not yet created in the OID.
ssoDynamicResourceCreate=true
# Single Sign-On parameter: URL to redirect to if ssoDynamicResourceCreate=false
ssoErrorUrl=
# Single Sign-On parameter: Cancel URL for the dynamic resource creation DAS page.
ssoCancelUrl=
# Single Sign-On parameter: indicates whether the url is protected in which
# case mod_osso will be given control for authentication or continue in
# the FormsServlet if not. It is false by default. Set it to true in an
# application-specific section to enable Single Sign-On for that application.
ssoMode=false
# The parameter allow_debug determines whether debugging is permitted.
# Administrators should set allow_debug to "true" if servlet
# debugging is required, or to provide access to the Forms Trace Xlate utility.
# Otherwise these activities will not be allowed (for security reasons).
allow_debug=false
# Parameter which determines whether new Forms sessions are allowed.
# This is also read by the Forms EM Overview page to show the
# current Forms status.
allowNewConnections=true
# EndUserMonitoring
# EndUserMonitoringEnabled parameter
# Indicates whether EUM/Chronos integration is enabled
EndUserMonitoringEnabled=
# EndUserMonitoringURL
# indicates where to record EUM/Chronos data
EndUserMonitoringURL=
# Example Named Configuration Section
# Example 1: configuration to run forms in a separate browser window with
# "generic" look and feel (include "config=sepwin" in the URL)
# You may define your own specific, named configurations (sets of parameters)
# by adding special sections as illustrated in the following examples.
# Note that you need only specify the parameters you want to change. The
# default values (defined above) will be used for all other parameters.
# Use of a specific configuration can be requested by including the text
# "config=<your_config_name>" in the query string of the URL used to run
# a form. For example, to use the sepwin configuration, your could issue
# a URL like "http://myhost.mydomain.com/forms/frmservlet?config=sepwin".
[sepwin]
separateFrame=True
lookandfeel=Generic
# Example Named Configuration Section
# Example 2: configuration forcing use of the Java Plugin in all cases (even if
# the client browser is on Windows)
[jpi]
baseHTMLJInitiator=basejpi.htm
# Example Named Configuration Section
# Example 3: configuration running the Forms ListenerServlet in debug mode
# (debug messages will be written to the servlet engine's log file).
[debug]
serverURL=/forms/lservlet/debug
# Sample configuration for deploying WebUtil. Note that WebUtil is shipped with
# DS but not AS and is also available for download from OTN.
[webutil]
WebUtilArchive=frmwebutil.jar,jacob.jar
WebUtilLogging=off
WebUtilLoggingDetail=normal
WebUtilErrorMode=Alert
WebUtilDispatchMonitorInterval=5
WebUtilTrustInternal=true
WebUtilMaxTransferSize=16384
baseHTMLjinitiator=webutiljini.htm
baseHTMLjpi=webutiljpi.htm
archive_jini=frmall_jinit.jar
archive=frmall.jar
lookAndFeel=oracle
[ttmsmenu]
WebUtilArchive=frmwebutil.jar,jacob.jar
WebUtilLogging=off
WebUtilLoggingDetail=normal
WebUtilErrorMode=Alert
WebUtilDispatchMonitorInterval=5
WebUtilTrustInternal=true
WebUtilMaxTransferSize=16384
baseHTMLjinitiator=webutiljini.htm
baseHTMLjpi=webutiljpi.htm
baseHTML=webutilbase.htm
archive_jini=frmall_jinit.jar
archive=frmall.jar
lookAndFeel=oracle
width=500
height=500
background=no
form=ttmsmenu.fmx

# or by overriding them in a specific, named configuration (see below)
[default]
this line seems to start a named section that finishes nowhere.
comment this line (put a # in front of it)
FRancois

OIM Form Customization

Hi,
My customer is having following requirements related to OIM Form Customization.
1.In createuser form,UserID ,Password and Confirm Password Should not be displayed.We are generating userid and password automatically and we should not allow the admin to enter userid and password while creating user.
2.Is it possible to make a form field mandatory only to specific usertype ? . For contractors,we need to make "Deprovisoning Date" as mandatory field but for employees,it should be a non-mandatory field.
3.Is it possible to have different form fields in Create user Form and Manager User Form.Since Create user form will be used to create contracors,we we don’t need to specify user defined fields related to employees ( JobName,PoitionName,EmployeeType etc) in create user form.
I am facing problems in implementing above requirements.Can somebody suggest,how I can implement these?.
Thanks.

Please check this Note 468779.1 from metalink.
Goal
How To Disable Password And Confirm Password or How to set the password fields as optional?
Solution
You can't set password field optional,this is mandatory field and hard coded in action class but you can set default value from jsp(tjspGenerateCreateUserForm.jsp) page. You can't be remove completely password section from User Creation Page as this is hard coded in the source code. Password is mandatory field for User creation API .
You can provide default password value from the JSP file. After modifying the JSP page as below,while creating OIM user both fields(Password and Confirm password) will not be editable.
Please try to modify tjspGenerateCreateUserForm.jsp
*(<BEA-Home>\user_projects\domains\proquire901\XLApplications\WLXellerateFull.ear\xlWebApp.war\tiles\util).
Add < value="123" readonly="true> these two attribute in password section and
ChangePassword section.
===
##Password section######
<td>
<html:password name="manageUserForm" property="password"
value="123" redisplay="true" readonly="true" styleClass="Fields" tabindex="1"/>
</td>
###confirmPassword section######
<td>
<html:password name="manageUserForm" property="confirmPassword"
value="123" readonly="true" redisplay="true" styleClass="Fields" tabindex="2"/>
</td>
==

BPEL with human using task forms (customization in task display).

All,
I have deployed a BPEL with human task with task forms (customization in task display).
For above customization Jdev automatically generates set of jsp files like Header1.jsp,Footer1.jsp,payload-body.jsp and <task name .jsp> and build an ear which includes war file.
I have deployed ear as j2ee app using em console.
It got deployed but when I check em console I could not see any active jsps listed.
due to this task customizations are not displayed properly.
but for same app in production instance, it is listing all jsp files in EM console
Any idea where I am missing
Thanks,
Praveen

I got it.
If there are no active jsp/servlets listed means they are never invoked.
I invoked them explicitly then they started coming in the list
Regards,
Praveen

Parameter form format error

I have just deployed my first report to our 9iAS app server. I can successfully run the report in my browser if I pass ALL parameters in the URL. When I attempt to use paramForm=YES in my URL, the parameter form appears like it should, but when I selected values (LOV) on the parameter form and click "Submit Query", I get the following error.
REP-52007: Parameter form format error.
java.lang.IllegalStateException: Response is already committed!
     at com.evermind[Oracle9iAS (9.0.2.0.0) Containers for J2EE].server.http.EvermindHttpServletResponse.setContentType(EvermindHttpServletResponse.java:973)
     at javax.servlet.ServletResponseWrapper.setContentType(ServletResponseWrapper.java:27)
     at oracle.reports.rwclient.RWReportRunner.setContentType(RWReportRunner.java:261)
     at oracle.reports.rwclient.RWReportRunner.getMainFile(RWReportRunner.java:135)
     at oracle.reports.rwclient.RWReportRunner.getMainFile(RWReportRunner.java:95)
     at oracle.reports.rwclient.RWClient.runReport(RWClient.java:1322)
     at oracle.reports.rwclient.RWClient.processRequest(RWClient.java:1139)
     at oracle.reports.rwclient.RWClient.doPost(RWClient.java:328)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:283)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:336)
     at com.evermind[Oracle9iAS (9.0.2.0.0) Containers for J2EE].server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:59)
     at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:283)
     at com.evermind[Oracle9iAS (9.0.2.0.0) Containers for J2EE].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:523)
     at com.evermind[Oracle9iAS (9.0.2.0.0) Containers for J2EE].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:269)
     at com.evermind[Oracle9iAS (9.0.2.0.0) Containers for J2EE].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:735)
     at com.evermind[Oracle9iAS (9.0.2.0.0) Containers for J2EE].server.http.AJPRequestHandler.run(AJPRequestHandler.java:151)
     at com.evermind[Oracle9iAS (9.0.2.0.0) Containers for J2EE].util.ThreadPoolThread.run(ThreadPoolThread.java:64)
Can anyone tell me what is wrong? This report run fine, including the parameter selection, in the Report Builder. I simply saved the report out to a JSP and copied it to the report server.
Thanks,
Kevin

You may have hit a bug when passing parameter paramform as "PARAMFORM=yes" or "Paramform=yes", you will get the REP-52007 error. The fix will be available in Reports 9.0.2.1.
As a work around, please submit the request with all lower case "paramform=yes" and try again.
Hope this helps,
-Jeff Tang

Forms login error for first 2-3 time

Hello,
we have a strange issue , users from Europe region are getting Form connection error(FRM 92050) while they login for the first time of the day,self service page is coming fine then while opening any form it's giving error. after they close the session and try for another 2/3 times they are able to open the forms.
Jinitiator console is not showing any error.
Also FRD trace is not getting generated for the above case of issue.
we have shared appltop architecture with 4 apps tier loadbalanced. if setting 'ICX Forms Launcher' to direct hostname instead of loadbalancer url issue is not coming.but it doesn't prove load balancer has issue as self service pages are coming properly through LB
Any idea how to trouleshoot?
Thanks,
Rishi

Hi,
Please see (Note: 420021.1 - FRM-92050: FAILED TO CONNECT TO THE SERVER /FORMS/FORMSERVLET:-1 WHEN USING LOAD BALANCE) and (Note: 601694.1 - How To Check Session Persistence On BigIP F5 And Cisco Ace Load Balancer Appliances).
Regards,
Hussein

Submitting a PDF form and Error Message

One of my users received the following error message when submitting a PDF form: "An error occurred during the submit process. The server has an invalid SSL certificate." Can anyone tell me what this error is and how do I prevent it?

I have had the same error - we are behind a webfilter which is very tight
can you please advise the domains i need to whitelist?
many thanks
Bruce

11.5.10 forms server error

hi all
i have installed EBS 11i on windows xp
it worked fine for last few months.now i am getting forms server error.
i can login as user and when i try to go to applications like AR transactions,
jinitiator is also geting intiated.it stops at this stage and i can see the oracle logo in the back ground .but the forms do not open.
i can see the forms generic error like 'forms 90500:cannot connect to the forms server'.
i tried to start the forms server using adfrmsctl cmd from envshell.it says forms server already started.
can anyone help me regarding this.
Thanks in advance

HI
I can find the jinitiator.trace but cant find the jinitiator.log
this is standalone installationn on my laptop(windows XP)
this is what i found in the trace file
Loading http://oracle.mydomain.com:8000/OA_JAVA/oracle/apps/fnd/jar/fndforms.jar from JAR cache
Loading http://oracle.mydomain.com:8000/OA_JAVA/oracle/apps/fnd/jar/fndformsi18n.jar from JAR cache
Loading http://oracle.mydomain.com:8000/OA_JAVA/oracle/apps/fnd/jar/fndewt.jar from JAR cache
Loading http://oracle.mydomain.com:8000/OA_JAVA/oracle/apps/fnd/jar/fndswing.jar from JAR cache
Loading http://oracle.mydomain.com:8000/OA_JAVA/oracle/apps/fnd/jar/fndbalishare.jar from JAR cache
Loading http://oracle.mydomain.com:8000/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar from JAR cache
Loading http://oracle.mydomain.com:8000/OA_JAVA/oracle/apps/fnd/jar/fndctx.jar from JAR cache
Loading http://oracle.mydomain.com:8000/OA_JAVA/oracle/apps/fnd/jar/fndlist.jar from JAR cache
connectMode=Socket
serverHost=oracle.mydomain.com
serverPort=9000
.

Oracle forms server error

hi all
i have installed EBS 11i on windows xp
it worked fine for last few months.now i am getting forms server error.
i can login as user and when i try to go to applications like AR transactions
jinitiator is also geting intiated.it stops at this stage and i can see the oracle logo in the back ground .but the forms do not open.
i can see the error cannot connect to the forms server.
i tried to start the frms server using adfrmsctl cmd from envshell.it says forms server already started.
can anyone help me regarding this.
thanks in advance.

yes its related to some forms generic error
it can be seen in the popup and the loading of forms stops there
i cant access the applications because it stucks there.
i can open forms like xml publisher administrator etc.but not the module based liek AR etc.
my data base works fine.

Forms customization error

Similar Messages

Maybe you are looking for