dbTalk Databases Forums  

Problems connecting to Sybase SQL server

sybase.public.sqlanywhere.general sybase.public.sqlanywhere.general


Discuss Problems connecting to Sybase SQL server in the sybase.public.sqlanywhere.general forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Ken Shibata
 
Posts: n/a

Default Problems connecting to Sybase SQL server - 10-06-2009 , 10:21 AM






We have a Multi-User Windows application which uses
Microsoft Visual Studio 2005 and Sybase SQL Anywhere v8.02
(Embedded SQL). We use installation disks to install our
application and Sybase SQL Anywhere v8.0.2 onto client’s
server machine. In most cases, we have no problem to start
our application after they are installed.

A Few days ago, we did a new installation on a server which
runs Windows 2008. The workstation user, which is on Windows
XP, was unable to connect to the Sybase SQL server which is
started on this server machine. We tried “dblocate”
utility and Sybase Central. Both failed to find the SQL
server on the network. There is no problem to locate this
server machine from the workstation.

The Sybase SQL server is started with these parameters:

-x TCPIP{DOBROADCAST=NO;HOST=SERVERNAME} -ti 0 -c 25P
-gd ALL -gk ALL -gp 4096 -n ENGINE8

What could be the primary reasons that prevent a workstation
to locate a Sybase SQL server?

What are the settings or setup should we check on the
client’s server or network environment?

Reply With Quote
  #2  
Old   
Graeme Perrow [Sybase iAnywhere]
 
Posts: n/a

Default Re: Problems connecting to Sybase SQL server - 10-06-2009 , 10:37 AM






Are the client and server machines on the same subnet? If not, UDP
broadcasts from the client will not reach the server. On the client, you
can try this:

dbping -d -c uid=XXX;pwd=XXX;eng=ENGINE8;links=tcpip(host=<SERV ERNAME>)

Where <SERVERNAME> is the name of the machine running dbsrv8. If that
works, you now have a connection string that you can use in your
application. If not, add -z to the dbping command (dbping -z -d -c...)
and the output may help you. If not, post it here.

BTW, the HOST parameter on the server is not useful; you can remove it.

Graeme Perrow
Senior Software Developer
gperrow _at_ ianywhere _dot_ com
Sybase iAnywhere Engineering

SQL Anywhere Developer Community
http://www.sybase.com/developer/libr...ere-techcorner
SQL Anywhere Blog Center
http://www.sybase.com/sqlanyblogs


Ken Shibata wrote:


Graeme Perrow
Senior Software Developer
gperrow _at_ ianywhere _dot_ com
Sybase iAnywhere Engineering

SQL Anywhere Developer Community
http://www.sybase.com/developer/libr...ere-techcorner
SQL Anywhere Blog Center
http://www.sybase.com/sqlanyblogs


Ken Shibata wrote:
Quote:
We have a Multi-User Windows application which uses
Microsoft Visual Studio 2005 and Sybase SQL Anywhere v8.02
(Embedded SQL). We use installation disks to install our
application and Sybase SQL Anywhere v8.0.2 onto client’s
server machine. In most cases, we have no problem to start
our application after they are installed.

A Few days ago, we did a new installation on a server which
runs Windows 2008. The workstation user, which is on Windows
XP, was unable to connect to the Sybase SQL server which is
started on this server machine. We tried “dblocate”
utility and Sybase Central. Both failed to find the SQL
server on the network. There is no problem to locate this
server machine from the workstation.

The Sybase SQL server is started with these parameters:

-x TCPIP{DOBROADCAST=NO;HOST=SERVERNAME} -ti 0 -c 25P
-gd ALL -gk ALL -gp 4096 -n ENGINE8

What could be the primary reasons that prevent a workstation
to locate a Sybase SQL server?

What are the settings or setup should we check on the
client’s server or network environment?
We have a Multi-User Windows application which uses
Microsoft Visual Studio 2005 and Sybase SQL Anywhere v8.02
(Embedded SQL). We use installation disks to install our
application and Sybase SQL Anywhere v8.0.2 onto client’s
server machine. In most cases, we have no problem to start
our application after they are installed.

A Few days ago, we did a new installation on a server which
runs Windows 2008. The workstation user, which is on Windows
XP, was unable to connect to the Sybase SQL server which is
started on this server machine. We tried “dblocate”
utility and Sybase Central. Both failed to find the SQL
server on the network. There is no problem to locate this
server machine from the workstation.

The Sybase SQL server is started with these parameters:

-x TCPIP{DOBROADCAST=NO;HOST=SERVERNAME} -ti 0 -c 25P
-gd ALL -gk ALL -gp 4096 -n ENGINE8

What could be the primary reasons that prevent a workstation
to locate a Sybase SQL server?

What are the settings or setup should we check on the
client’s server or network environment?

Reply With Quote
  #3  
Old   
Ken Shibata
 
Posts: n/a

Default Re: Problems connecting to Sybase SQL server - 10-06-2009 , 04:10 PM



Graeme, the client and server machines are not on the same
subnet. On the client I tried this:

dbping -d -c
uid=XXX;pwd=XXX;eng=engine8;links=tcpip(host=serve rname);
dbf=d:\cms\benet\be_user.db

I then get the error message:

Ping database failed -- Database server not found.

Please advise. Thanks.

Quote:
Are the client and server machines on the same subnet? If
not, UDP broadcasts from the client will not reach the
server. On the client, you can try this:

dbping -d -c uid=XXX;pwd=XXX;eng=ENGINE8
;links=tcpip(host=<SERVERNAME>)

Where <SERVERNAME> is the name of the machine running
dbsrv8. If that works, you now have a connection string
that you can use in your application. If not, add -z to
the dbping command (dbping -z -d -c...) and the output
may help you. If not, post it here.

BTW, the HOST parameter on the server is not useful; you
can remove it.

Graeme Perrow
Senior Software Developer
gperrow _at_ ianywhere _dot_ com
Sybase iAnywhere Engineering

SQL Anywhere Developer Community


http://www.sybase.com/developer/libr...ere-techcorner
SQL Anywhere Blog Center
http://www.sybase.com/sqlanyblogs


Ken Shibata wrote:


Graeme Perrow
Senior Software Developer
gperrow _at_ ianywhere _dot_ com
Sybase iAnywhere Engineering

SQL Anywhere Developer Community


http://www.sybase.com/developer/libr...ere-techcorner
SQL Anywhere Blog Center
http://www.sybase.com/sqlanyblogs


Ken Shibata wrote:
We have a Multi-User Windows application which uses
Microsoft Visual Studio 2005 and Sybase SQL Anywhere
v8.02 (Embedded SQL). We use installation disks to
install our application and Sybase SQL Anywhere v8.0.2
onto client’s server machine. In most cases, we have
no
problem to start our application after they are
installed.
A Few days ago, we did a new installation on a server
which runs Windows 2008. The workstation user, which is
on Windows XP, was unable to connect to the Sybase SQL
server which is started on this server machine. We tried
“dblocate” utility and Sybase Central. Both failed
to
find the SQL server on the network. There is no problem
to locate this server machine from the workstation.

The Sybase SQL server is started with these parameters:

-x TCPIP{DOBROADCAST=NO;HOST=SERVERNAME} -ti 0 -c
25P
-gd ALL -gk ALL -gp 4096 -n ENGINE8

What could be the primary reasons that prevent a
workstation to locate a Sybase SQL server?

What are the settings or setup should we check on the
client’s server or network environment?
We have a Multi-User Windows application which uses
Microsoft Visual Studio 2005 and Sybase SQL Anywhere
v8.02 (Embedded SQL). We use installation disks to
install our application and Sybase SQL Anywhere v8.0.2
onto client’s server machine. In most cases, we have
no
problem to start our application after they are
installed.
A Few days ago, we did a new installation on a server
which runs Windows 2008. The workstation user, which is
on Windows XP, was unable to connect to the Sybase SQL
server which is started on this server machine. We tried
“dblocate” utility and Sybase Central. Both failed
to
find the SQL server on the network. There is no problem
to locate this server machine from the workstation.

The Sybase SQL server is started with these parameters:

-x TCPIP{DOBROADCAST=NO;HOST=SERVERNAME} -ti 0 -c
25P
-gd ALL -gk ALL -gp 4096 -n ENGINE8

What could be the primary reasons that prevent a
workstation to locate a Sybase SQL server?

What are the settings or setup should we check on the
client’s server or network environment?

Reply With Quote
  #4  
Old   
Graeme Perrow [Sybase iAnywhere]
 
Posts: n/a

Default Re: Problems connecting to Sybase SQL server - 10-07-2009 , 10:25 AM



Sorry, I missed something else as well - you need the DoBroadcast=None
parameter.

I am assuming you are replacing "servername" with the actual name of the
machine that is running the server? Also, I am assuming that
D:\cmd\benet\be_user.db is a file located on the *server* machine, not
on the local client machine?

So try this (you can leave off the -d switch and the UID and PWD for now):

dbping -c
eng=engine8;links=tcpip(host=<servername>;DoBroadc ast=none);dbf=d:\cms\benet\be_user.db


Graeme Perrow
Senior Software Developer
gperrow _at_ ianywhere _dot_ com
Sybase iAnywhere Engineering

SQL Anywhere Developer Community
http://www.sybase.com/developer/libr...ere-techcorner
SQL Anywhere Blog Center
http://www.sybase.com/sqlanyblogs


Ken Shibata wrote:
Quote:
Graeme, the client and server machines are not on the same
subnet. On the client I tried this:

dbping -d -c
uid=XXX;pwd=XXX;eng=engine8;links=tcpip(host=serve rname);
dbf=d:\cms\benet\be_user.db

I then get the error message:

Ping database failed -- Database server not found.

Please advise. Thanks.

Are the client and server machines on the same subnet? If
not, UDP broadcasts from the client will not reach the
server. On the client, you can try this:

dbping -d -c uid=XXX;pwd=XXX;eng=ENGINE8
;links=tcpip(host=<SERVERNAME>)

Where <SERVERNAME> is the name of the machine running
dbsrv8. If that works, you now have a connection string
that you can use in your application. If not, add -z to
the dbping command (dbping -z -d -c...) and the output
may help you. If not, post it here.

BTW, the HOST parameter on the server is not useful; you
can remove it.

Graeme Perrow
Senior Software Developer
gperrow _at_ ianywhere _dot_ com
Sybase iAnywhere Engineering

SQL Anywhere Developer Community


http://www.sybase.com/developer/libr...ere-techcorner
SQL Anywhere Blog Center
http://www.sybase.com/sqlanyblogs


Ken Shibata wrote:


Graeme Perrow
Senior Software Developer
gperrow _at_ ianywhere _dot_ com
Sybase iAnywhere Engineering

SQL Anywhere Developer Community


http://www.sybase.com/developer/libr...ere-techcorner
SQL Anywhere Blog Center
http://www.sybase.com/sqlanyblogs


Ken Shibata wrote:
We have a Multi-User Windows application which uses
Microsoft Visual Studio 2005 and Sybase SQL Anywhere
v8.02 (Embedded SQL). We use installation disks to
install our application and Sybase SQL Anywhere v8.0.2
onto client’s server machine. In most cases, we have
no
problem to start our application after they are
installed.
A Few days ago, we did a new installation on a server
which runs Windows 2008. The workstation user, which is
on Windows XP, was unable to connect to the Sybase SQL
server which is started on this server machine. We tried
“dblocate” utility and Sybase Central. Both failed
to
find the SQL server on the network. There is no problem
to locate this server machine from the workstation.

The Sybase SQL server is started with these parameters:

-x TCPIP{DOBROADCAST=NO;HOST=SERVERNAME} -ti 0 -c
25P
-gd ALL -gk ALL -gp 4096 -n ENGINE8

What could be the primary reasons that prevent a
workstation to locate a Sybase SQL server?

What are the settings or setup should we check on the
client’s server or network environment?
We have a Multi-User Windows application which uses
Microsoft Visual Studio 2005 and Sybase SQL Anywhere
v8.02 (Embedded SQL). We use installation disks to
install our application and Sybase SQL Anywhere v8.0.2
onto client’s server machine. In most cases, we have
no
problem to start our application after they are
installed.
A Few days ago, we did a new installation on a server
which runs Windows 2008. The workstation user, which is
on Windows XP, was unable to connect to the Sybase SQL
server which is started on this server machine. We tried
“dblocate” utility and Sybase Central. Both failed
to
find the SQL server on the network. There is no problem
to locate this server machine from the workstation.

The Sybase SQL server is started with these parameters:

-x TCPIP{DOBROADCAST=NO;HOST=SERVERNAME} -ti 0 -c
25P
-gd ALL -gk ALL -gp 4096 -n ENGINE8

What could be the primary reasons that prevent a
workstation to locate a Sybase SQL server?

What are the settings or setup should we check on the
client’s server or network environment?

Reply With Quote
  #5  
Old   
Jeff Albion [Sybase iAnywhere]
 
Posts: n/a

Default Re: Problems connecting to Sybase SQL server - 10-07-2009 , 02:48 PM



Hi Ken,

Ken Shibata wrote:
Quote:
A Few days ago, we did a new installation on a server which
runs Windows 2008. The workstation user, which is on Windows
XP, was unable to connect to the Sybase SQL server which is
started on this server machine. We tried “dblocate”
utility and Sybase Central. Both failed to find the SQL
server on the network. There is no problem to locate this
server machine from the workstation.
Windows Server 2008 runs "Windows Firewall with Advanced Security" by
default, and does not have the nice "auto-configure" window that pops up
in other versions of Windows. You'll need to add "dbsrv8" as an
exception to the firewall rules, or (if the server is already on a
secured internal network and your IT department is okay with it) just
disable the firewall.

See: http://technet.microsoft.com/en-us/n.../bb545423.aspx for more
details.

Regards,

--
Jeff Albion, Sybase iAnywhere

iAnywhere Developer Community :
http://www.sybase.com/developer/libr...ere-techcorner
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
SQL Anywhere Patches and EBFs :
http://downloads.sybase.com/swd/summ...&timeframe =0
Report a Bug/Open a Case : http://case-express.sybase.com/cx/

Reply With Quote
  #6  
Old   
Ken Shibata
 
Posts: n/a

Default Re: Problems connecting to Sybase SQL server - 10-08-2009 , 11:08 AM



I am taking vacation for one week and did not get the chance
to try your suggestion on client’s server. I will re-post
the result and question after I come back to work. Thanks.


Quote:
Sorry, I missed something else as well - you need the
DoBroadcast=None parameter.

I am assuming you are replacing "servername" with the
actual name of the machine that is running the server?
Also, I am assuming that D:\cmd\benet\be_user.db is a
file located on the *server* machine, not on the local
client machine?

So try this (you can leave off the -d switch and the UID
and PWD for now):

dbping -c
eng=engine8;links=tcpip(host=<servername
;DoBroadcast=none);dbf=d:\cms\benet\be_user.db


Graeme Perrow
Senior Software Developer
gperrow _at_ ianywhere _dot_ com
Sybase iAnywhere Engineering

SQL Anywhere Developer Community


http://www.sybase.com/developer/libr...ere-techcorner
SQL Anywhere Blog Center
http://www.sybase.com/sqlanyblogs


Ken Shibata wrote:
Graeme, the client and server machines are not on the
same subnet. On the client I tried this:

dbping -d -c

uid=XXX;pwd=XXX;eng=engine8;links=tcpip(host=serve rname)
; dbf=d:\cms\benet\be_user.db

I then get the error message:

Ping database failed -- Database server not found.

Please advise. Thanks.

Are the client and server machines on the same subnet?
If >> not, UDP broadcasts from the client will not reach
the >> server. On the client, you can try this:

dbping -d -c uid=XXX;pwd=XXX;eng=ENGINE8
;links=tcpip(host=<SERVERNAME>)

Where <SERVERNAME> is the name of the machine running
dbsrv8. If that works, you now have a connection
string >> that you can use in your application. If not,
add -z to >> the dbping command (dbping -z -d -c...) and
the output >> may help you. If not, post it here.

BTW, the HOST parameter on the server is not useful;
you >> can remove it.

Graeme Perrow
Senior Software Developer
gperrow _at_ ianywhere _dot_ com
Sybase iAnywhere Engineering

SQL Anywhere Developer Community




http://www.sybase.com/developer/libr...ere-techcorner
SQL Anywhere Blog Center
http://www.sybase.com/sqlanyblogs


Ken Shibata wrote:


Graeme Perrow
Senior Software Developer
gperrow _at_ ianywhere _dot_ com
Sybase iAnywhere Engineering

SQL Anywhere Developer Community




http://www.sybase.com/developer/libr...ere-techcorner
SQL Anywhere Blog Center
http://www.sybase.com/sqlanyblogs


Ken Shibata wrote:
We have a Multi-User Windows application which uses
Microsoft Visual Studio 2005 and Sybase SQL Anywhere
v8.02 (Embedded SQL). We use installation disks to
install our application and Sybase SQL Anywhere v8.0.2
onto client’s server machine. In most cases, we have
no
problem to start our application after they are
installed.
A Few days ago, we did a new installation on a server
which runs Windows 2008. The workstation user, which
is >>> on Windows XP, was unable to connect to the Sybase
SQL >>> server which is started on this server machine. We
tried >>> “dblocate” utility and Sybase Central. Both
failed to
find the SQL server on the network. There is no
problem >>> to locate this server machine from the
workstation.
The Sybase SQL server is started with these
parameters:
-x TCPIP{DOBROADCAST=NO;HOST=SERVERNAME} -ti 0 -c
25P
-gd ALL -gk ALL -gp 4096 -n ENGINE8

What could be the primary reasons that prevent a
workstation to locate a Sybase SQL server?

What are the settings or setup should we check on the
client’s server or network environment?
We have a Multi-User Windows application which uses
Microsoft Visual Studio 2005 and Sybase SQL Anywhere
v8.02 (Embedded SQL). We use installation disks to
install our application and Sybase SQL Anywhere v8.0.2
onto client’s server machine. In most cases, we have
no
problem to start our application after they are
installed.
A Few days ago, we did a new installation on a server
which runs Windows 2008. The workstation user, which
is >>> on Windows XP, was unable to connect to the Sybase
SQL >>> server which is started on this server machine. We
tried >>> “dblocate” utility and Sybase Central. Both
failed to
find the SQL server on the network. There is no
problem >>> to locate this server machine from the
workstation.
The Sybase SQL server is started with these
parameters:
-x TCPIP{DOBROADCAST=NO;HOST=SERVERNAME} -ti 0 -c
25P
-gd ALL -gk ALL -gp 4096 -n ENGINE8

What could be the primary reasons that prevent a
workstation to locate a Sybase SQL server?

What are the settings or setup should we check on the
client’s server or network environment?

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.