![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
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? |
#3
| |||
| |||
|
|
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? |
#4
| |||
| |||
|
|
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? |
#5
| |||
| |||
|
|
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. |
#6
| |||
| |||
|
|
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? |
![]() |
| Thread Tools | |
| Display Modes | |
| |