ASA 9.0.2.3228 Server on Windows XP SP2
ASA 9.0.2.3228 Client on Virtual PC also with Windows XP SP2

I am trying to re-install an old webshop application where the vendor no
longer exists. This application is still running in production on a
Windows 2000 Server (DB Server & application both on the same machine).
To do further tests, I've installed a copy of the application on a
virtual PC but can't get it to connect to the database.

I can connect without a problem with dbisqlc from the virtual pc to the
DB server, user IDs & password are known. But when the application tries
to connect to the DB server, I get the error message
"[Sybase][ODBC Driver][Adaptive Serber Anywhere]Connection error: Trying
to add unknown port". Unfortunatly no error number is given. I can't
find anything in the docs & Mr. Google shows also only one unswered
question.

When I delete or change the ODBC data source, I get a different error
message, so that lets me assume that this entry is correct. TCPIP
network connection is enabled.

I have even tried to trace the network activity. With dbisql, I get lots
of TCP packages but when the webshop application starts, there is no
network activity whatsoever.

Any ideas where to look?

Thanks

Klaus

--
reply pub . pieper ibeq
to kp3 . at . com

What are the contents of the DSN?

Was the "old" application also using v902.3228? The term "old" and
"v902.3228" don't typically appear in the same sentence, since build 3228
was posted in December, 2005.

--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup

iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swd/base.do
-> Choose SQL Anywhere Studio
-> Set filter to "Display ALL platforms IN ALL MONTHS"


"Klaus P. Pieper" <me (AT) private (DOT) net> wrote

Klaus P. Pieper wrote:
Can you show us the DSN settings (use the command "dbdsn -gu YOUR_DSN"
for a user DSN or -gs for a system DSN) ?

Consider adding connection logging to your DSN. Edit the DSN and:

1. select the Advanced tab
2. check the "Display debugging information in a log file" checkbox
3. enter the full path for a log file to be created (e.g.
c:/asa_connection.txt)

After a failed connection attempt, look at the log file to see what it
displays. Feel free to post it here if you are unsure.

greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/

Reg,

Reg Domaratzki (iAnywhere Solutions) schrieb:
no, it was designed with ASA 7.02 and later upgraded to 7.04. However,
on the production system it is also working with v902.3228.

Thanks

Klaus

--
reply pub . pieper ibeq
to kp3 . at . com

Greg Fenton schrieb:
wow, that did it!

Appearently, the virtual PC with Windows XP had no NETBIOS installed and
the application provided NETBIOS as a protocol in the link option of the
connection string. I removed NETBIOS completely from the connection
string and it works!

As a side note, on one of my attempts to fix the test installation, I
had deleted the NETBIOS section but left two commas between TCPIP and
SHAREDMEMEORY (LINKS="TCPIP, ,SHAREDMEMORY"). That caused the same
error message even when given as a link parameter to dbping.

Thanks!

Klaus

--
reply pub . pieper ibeq
to kp3 . at . com