Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Connection Error ORA-01019

352081Apr 4 2005 — edited Apr 5 2005
I'm Getting this error when I try to connect using the Microsoft OLE driver (MSDAORA) full text of the error is:

Error Type:
Microsoft OLE DB Provider for Oracle (0x80004005)
Error while trying to retrieve text for error ORA-01019
/OpenIncOra/GetRole.asp, line 15

When I change the drive to ORAOLEDB I get the following error:
Error Type:
OraOLEDB (0x80004005)
?GÔ
/OpenIncOra/GetRole.asp, line 18

I'm using IIS 6 on a Windows XP Pro machine, to which I've added the IUSR and IWAM accounts with Full Control to the ora92\bin directory.

Any ideas of what the problem is?

Comments

unknown-7404

2781564 wrote:

Oracle CRM is blocked by Java 8 due to "medium" security being removed.  Possibly this is because the application requests all permissions.  Is there a reconfiguring that can be done to allow it to run/launch in Java "high" security mode.  The desktop administrators just upgraded all call center desktops to Java 8 (1.8_20) and Contact Center and other "Java forms" based application components are failing to launch.

We are working with the Admin/Security teams to see if our site can be added to the site Exceptions list but this is a lengthy process and hope we can configure CRM to work with the higher "Java" security requirement.

This is not really a Java 8 question. You need to post in a CRM forum or open an SR with Oracle support via your MOS account.

As you already noted Java 8 "medium" security was removed.

https://www.java.com/en/download/help/jcp_security.xml

Starting with Java 8 Update 20, the Medium security level has been removed from the Java Control Panel. Only High and Very High levels are available.

The exception site list provides users with the option of allowing the same applets that would have been allowed by selecting the Medium option but on a site-by-site basis therefore minimizing the risk of using more permissive settings.

Seems like someone in your org approved the Java update without properly testing ALL of the possible affected apps.

1 - 1
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on May 3 2005
Added on Apr 4 2005
1 comment
2,346 views