Tag Archives: Troubleshooting - Page 4

Excel Not Launching Properly from Web ADI

Posted by on December 1, 2006 No comments

Problem: When Web ADI launches Microsoft Excel, the output Excel spreadsheet does not run.

Solution: This problem seems to be occurring only in Microsoft Excel 2003. In Excel 2003, Enable Trust VB Projects.

Step 1:        After launching Excel 2003, navigate to Tools > Options.

Step 2:        Click the Security tab.

Step 3:        Click the Macro Security button.

Step 4:        Click the Trusted Publishers tab.

Step 5:        Ensure that Trust access to Visual Basic project is checked.

Step 6:        Click OK to exit the option. Click OK again.

Refer to Metalink Doc ID:  Note: 106528.1 (Subject:  Application Desktop Integrator – Product Documentation)

Refer to Metalink Doc ID:  Note: 376976.1 (Subject:  WEB ADI “Run-Time Error ‘50290’ Method ‘Run’ Of Object ‘_application Failed”)

Refer to Metalink Doc ID:  Note: 295901.1 (Subject:  No Excel File Created When Using Excel 2002; Excel 2002 Does Not Appear In Viewers LOV)

See also http://support.microsoft.com/default.aspx?scid=kb;en-us;282033

Recreating DBC file

Posted by on November 22, 2006 No comments

Problem: While installing vision instance, the post-install check “JSP Check” fails with the message “DBC file may be invalid”.

Solution: Recreate DBC file.

Note: Run these commands from $FND_TOP/secure. Also, source environment file first.

To create a DBC file and server ID:
java oracle.apps.fnd.security.AdminAppServer apps/apps@vis ADD FNDNAM=apps GWYUID=applsyspub/pub TWO_TASK=vis SECURE_PATH=%FND_TOP%secure GUEST_USER_PWD=guest/guest APPS_JDBC_DRIVER_TYPE=THIN DB_HOST=eam.clientnetwork.com DB_PORT=1522

To check status:
java oracle.apps.fnd.security.AdminAppServer apps/apps@vis STATUS DB_HOST=eam.clientnetwork.com DB_PORT=1522

To delete DBC file:
java oracle.apps.fnd.security.AdminAppServer apps/apps@vis DELETE DB_HOST=eam.clientnetwork.com DB_PORT=1522

Also, you can run adgendbc.sh, located in $COMMON_TOP/admin/install/

For Database Connectivity problems, ensure that the hosts file is set up properly:

127.0.0.1 localhost.localdomain localhost
hostname.domainname hostname

On Windows, use java. On Linux/Unix, use JRE.

Reference:
Metalink Doc ID: 108865.1 (How To Create a Database Connection(DBC) File and Troubleshooting Common Problems)

Configurating Oracle Diagnostics Tool Responsibility

Posted by on September 22, 2006 No comments

This documentation shows how to set up the Oracle Diagnostics Tool responsibility after installing it.

The following tasks should be completed using a responsibility that can assign responsibilities (e.g. “System Administrator”).

Step 1:        To assign the “Oracle Diagnostics Tool” responsibility to eBusiness Suite users.

If “User Management” responsibility is available:

  1. Select the “User Management” responsibility
  2. Click on “Users”
  3. Query the user to which the “Oracle Diagnostics Tool” responsibility should be assigned
  4. Select the “Update” icon
  5. Click the “Assign Roles” button
  6. Search for “Oracle Diagnostics Tool”
  7. Tick the “Select” check box and then click the “Select” button
  8. Fill in the “Justification” text field and then click the “Apply” button
  9. Click the “Home” hyperlink to return to the eBusiness Suite home page

If “User Management” responsibility is not available:

  1. Open the “Users” form (Security > User > Define)
  2. Query an existing user
  3. Add a row in the Responsibilities sub-tab region
  4. Select “Oracle Diagnostics Tool” responsibility (Application: “CRM Foundation”) from the responsibility LoV
  5. Click “OK” and save the record

See Metalink Document Subject:  Diagnostics Responsibility Configuration

Doc ID:  Note:358831.1

Troubleshooting Launching Oracle Applications

Posted by on August 10, 2006 No comments

Problem: Unable to get application to launch.

Solution: Try the following:

Step 1:        Check the hosts file (either /etc/hosts or C:WINDOWSSYSTEM32 DRIVERSETCHOSTS) and ensure that the IP address and host is in the file.

Step 2:        Ensure that the local addresses are bypassed in the browser.

Step 3:        Ensure that the instance is started on the server.