Forum Stats

  • 3,815,637 Users
  • 2,259,064 Discussions
  • 7,893,194 Comments

Discussions

ORA-01017 with Managed Provider 4.112.3.60. Bug with ODP on Win 2008 R2?

124»

Answers

  • Alex Keh-Oracle
    Alex Keh-Oracle Posts: 3,057 Employee

    With FIPS turned on, do you mind sending me a client side ODP.NET trace at level 7 and server side Net trace at level 16, plus any errors in the RDBMS or alert logs? You can email it to me alex.keh [at] oracle.com.

    My team can take a look and see why this may be striking Windows 2008 R2 specifically, but not any other Windows OS.

  • Lannie Liberty
    Lannie Liberty Member Posts: 224 Blue Ribbon

    On Win 7 Dev
    I enabled FIPS compliance in Local Policy > Security

    .NET 4.0 Test APP with ODP.NET Managed driver fails with LOGIN FAIL oracle error.

    This is not the same error we get on Windows 2008 platform (connection lost error),
    but it is a managed driver failure that should be dealt with
    since the unmanaged driver may not be affected by FIPS compliance enabled.
    (have to test that too)

    Disable FIPS compliance and .NET 4.0 Test APP works again.

    Repeat twice and it is reproducible.

    I add this to app config:

    <configuration>
      <runtime>   
        <enforceFIPSPolicy enabled="false"/>   
      </runtime>
    </configuration>

    Setting is described to IGNORE operating system FIPS policy

    I enabled FIPS compliance in Local Policy > Security

    .NET 4.0 Test APP with ODP.NET Managed driver works

    So this on Local Machine Security, Windows 7 over comes the FIPS problem.

    Now, will have to try this on our Windows 2008 platform where managed driver is failing

    user2284427
  • Lannie Liberty
    Lannie Liberty Member Posts: 224 Blue Ribbon

    Applied this config change in Windows 2008, and not change in errors reported above

This discussion has been closed.