We have a little glitch in moving from XP to Windows 7. Our practice when a user needs a new password is to give them a password over the phone and immediately expire it.

The problem is that using the DOA dialog results in an ORA-01017 error in Windows 7 after the user enters and verifies their new Oracle password. On XP it works fine.

Delphi XE, DOA 4.1 from 2011, no handling of the password or DOA dialog other than calling Execute. I couldn't find any relevant posts on the forum other than possibly changing fonts from MS Sans Serif, which looks nicer, but didn't solve the problem.

Can you let me know the Oracle Client version on Windows 7?

The client and OCI.dll are 11.2.0.1

Any luck on identifying the problem? We have the source, but I haven't found anything yet that solves the problem.

If it makes a difference, we've been customers the past ten years, serial number 01.94043.

We have not yet been able to determine what might cause this. If you have the source, can you add the {$D+} directive to the Oracle.inc file, add the source directory to the Delphi search path, and trace the issue? You should be able to see how the expiration is detected, which function is called to set the expired password, and how the ORA-001017 exception is eventually raised.

Okay, thanks, it isn't a DOA problem. It's an Oracle client problem.

Our network admin installed the client from 11.2.0.3 onto Windows 7 when he built the installation image. Although the OCI.dll properties read 11.2.0.1, it isn't backwards compatible when reading from an 11.2 database version before 11.2.0.3.

The search that I ran to eventually find this out was:
problems with Oracle client 11.2.0.1 and Windows 7 and expired password
which includes gems such as;
http://feed.askmaclean.com/archives/11-2-0-3-client-password-expiry-and-ora-1017.html