I have applied EBF 3581 for SQL Anywhere 9.02 and my Sybase based
application can no longer connect to the database. The problem is in the
connection API, which now passes the connection string back with the
password encrypted ("***").

The initial connection is made without problems, but after receiving the
connection string, it is stored and used in subsequent connection attempts,
hence the failure.

My main concern right now is how to remove the EBF to get the old behaviour
back. I have installed EBF3508 over the top, but the behaviour is still
there.

Any pointers?

Uninstall and reinstall is your most immediate and comprehensive
way of doing so. If you had made a copy of your original
%asany9% and %asanysh9% sub-trees you could replace
those with the original ones ... some gremlins are possible
but that has often worked for me.

But I am concerned about what you mean by and how you
are captering the connection string ... Are you using E/SQL
and the db_string_connect( ) function?

And do you know which change caused you these problems?
Would it be one of these:

================(Build #2529 - Engineering Case
#368825)================
If a datasource name was specified on the command line that contained an
encrypted password, dbisql would not have immediately connected to the
database,
but would have first displayed the "Connect" dialog. Now an attempt is
made
to connect immediately, without first displaying the "Connect" dialog.
================(Build #3266 - Engineering Case
#420588)================
The Data Source utility now supports encrypting the password when
creating
ODBC data sources. When the -pe command line option is specified, and a
PWD
entry is provided, the password in the PWD entry is encrypted and
replaced
by an ENP entry in the resulting data source.

or (as possibly due to dbdsn and #420588) you are using a DSN with
an encrypted password captured in the ODBC DSN (odbc.ini)?

It might help to include some details on platform and older ebf level
where this worked for you.

"Dominik" <lansasupport (AT) lansa (DOT) com.au> wrote

Thanks for your response. I have uninstalled and reinstalled Sybase, and
this has resolved my issue.
Prior to EBF 3581, I was using 3508 without any problems.
I am using Windows Vista business edition, and I have also tried this on
Windows 2003 Server with the same results.

As for how we are making the connection; we are using the ODBC API's
SQLDriverConnect and SQLConnect.

We are not using the -pe command line option, and I couldn't find anything
in the ODBC.Ini to indicate that the DSN is using an encrypted password

When I had EBF 3581 applied I did try turning the "Encrypt Password" setting
in the ODBC on/off but it made no difference.

One of the developers here has logged a support case with Sybase regarding
the change, since it has the potential to affect many of our customers.

Thanks again for your help
Dominik

"Nick Elson" <@@@nick@@@.@@@elson@sybase@@@.@@@com@@@> wrote