I have had a very odd problem, and thus far have found two solutions. The
problem is, I don't really understand either solution, other than "it
probably has to do with security".

Problem: NT 4, SP 6, IE 6. SQL Anyhwere 5.5.05 Build 2817 and ASA 8.0.2
Build 4308. Also using Mobilink. So far, the problem is on only one specific
configuration -- it works under other configurations.

Description: An older application is using the SQL 5.5.05 database, and that
database has data in it that we want to sync to a database on a hand held.
Since Mobilink won't talk to SQL 5.5.05, we used ASA 8.0.2 for the database,
with some of our data actually in the ASA 8 database, and the bulk of the
data in the SQL 5.5.05 database via proxy tables.

Issue: Only the "first" application can connect to the 5.5.05 database
(e.g., our older application, or ASA 8 via proxy tables.). The second fails
to connect, with very odd DBCLIENT behavior, including a DRWatson.

So far, I have found two work arounds: 1) Run DBCLIENT as a service. 2) Run
ASA8 under the Administrator account (was running it under the Local System
account).

#1 is not allowed, because "it might break something else" in our
configuration. I'm now going to propose #2, to see what interesting
rejection I can get...

So the question is, what is common between these two solutions? I used the
local system account when running DBCLIENT as a service. Our application
runs under some other user account. Could this have been caused by one of
the many microsoft Security Updates to windows? On other machines, we have
not had this problem.

More info: (please snip when replying!)

Here is the output from the first DBCLIENT connection that works:

-------------------------------------
1: -x
2: tcpip
3: -z
4: -o
5: c:\userdsn.txt
6: -ga
7: -n
8: STORE351
9: -N2359438,297:236

Sybase SQL Anywhere Network Requestor Version 5.5.05 Build #2817
Copyright by Sybase, Inc., and its subsidiaries, 1988, 1999.
All rights reserved. Sybase is a trademark of Sybase, Inc.

Trying to start TCPIP link ...
Loading WSOCK32.DLL
My IP-address is: 192.168.193.154
Listener threads to start: 2
Threads started: 2
TCPIP link started successfully
Starting with 200 buffers of size 512 bytes
Looking for STORE351
Sending broadcast
I am in a class C network
Using broadcast address of: 192.168.193.255
Using broadcast address of: 255.255.255.255
Found server:
192.168.193.154
Found server STORE351 on TCPIP link
Liveness timeout 120, liveness retransmit period 30
started
start req pid:20 port:51 'DB_GET_ENVIRONMENT' sqlcode:0
done req pid:20 port:51 'DB_GET_ENVIRONMENT' sqlcode:0
start req pid:20 port:52 'DB_CONNECT: SQL_DBC_1830868' sqlcode:0
done req pid:20 port:52 'DB_CONNECT: SQL_DBC_1830868' sqlcode:0
-------------------------------------

Here is the output from the second, when it fails (if it succeeds, no log is
created, since DBCLIENT was detected as running):
-------------------------------------
1: -x
2: tcpip
3: -Z
4: -o
5: c:\sysdns.txt
6: -ga
7: -n
8: STORE351
9: -N8716742,225:396

Sybase SQL Anywhere Network Requestor Version 5.5.05 Build #2817
Copyright by Sybase, Inc., and its subsidiaries, 1988, 1999.
All rights reserved. Sybase is a trademark of Sybase, Inc.

Trying to start TCPIP link ...
Loading WSOCK32.DLL
My IP-address is: 192.168.193.154
Listener threads to start: 2
Threads started: 2
TCPIP link started successfully
Starting with 200 buffers of size 512 bytes
Looking for STORE351
Sending broadcast
I am in a class C network
Using broadcast address of: 192.168.193.255
Using broadcast address of: 255.255.255.255
Found server:
192.168.193.154
Found server STORE351 on TCPIP link
Liveness timeout 120, liveness retransmit period 30
started
An engine with that name has already started
Shutting down listener thread: 0
-------------------------------------


The unchangables: Even though the server is local, all connections must be
via DBCLIENT, because of some other nebulous reason, probably on the same
level as no allowing DBCLIENT to run as a service...

Oooops!!!!

Scratch that!

I left the setting for the account to be local system on the ASA 8 database
server. However, what I *did* change was the "Interact with desktop"
setting -- it must be checked!

This was also the same on the DBClient as a service -- it too must have the
interact with desktop checked, or it would not work (e.g., work just like
before, by failing and starting a new DBCLIENT).

This is very incomprehensible to me... Nick Elson, any ideas?

"Mark Hampton" <mhampton.removeme (AT) datavantagecorp (DOT) com> wrote