At long last we have decided to upgrade our product database and
distributed runtimes to SA11. We have been using the authenticated
version of ASA 9 for years without a problem, but we have not been
able to get 11 to accept authentication. Do we have to get a new
authentication string perhaps for 11?

We have the SET OPTION PUBLIC.database_authentication... , including
the "go" in an authenticate.sql file in the Scripts directory. When I
create a new database, even if using Central, the authentication
information does not appear in the server message window. After the db
comes up, I have run the authenticate.sql in dbisql, without error,
but it doesn't seem to make any difference.

Anyone know what I might be doing wrong. The more I think about it,
the more I suspect that the authentication keys are version-specific.
If so, do I call support or my account rep or ...?

Seth Krieger
Synergistic Office Solutions, Inc.
www.sosoft.com

Can you post the first few characters of the signature for the
database_authentication and connection_authentication?

There was a problem with some older signatures that may require you to
obtain new strings but I want to verify that your signatures are impacted.


Seth wrote:

Chris, here are the first 15 of the signature: 000fa55157edb8e
- Seth


On Dec 15, 1:09*pm, "Chris Keating (Sybase iAnywhere)"
<keating_nos... (AT) sybase (DOT) com> wrote:


-

Chris -
Your response provided the hint I needed. I did not realize that the
signatures were different for the two authentication strings, so I was
trying to authenticate the db using the connection signature. I dug up
the original database_authentication signature, created the script and
ran it. No surprise to you, I am sure, but it now works just as it
should!

Thanks much!

- Seth


On Dec 15, 1:09*pm, "Chris Keating (Sybase iAnywhere)"
<keating_nos... (AT) sybase (DOT) com> wrote: