Showing posts with label program. Show all posts
Showing posts with label program. Show all posts

Tuesday, February 14, 2012

Cannot connect to MSDE on SBS 2003

My client has installed e scanner program wich is suposed til run on a MSDE
database. The program has to run on a reasently installed SBS 2003 server.
The server is installed with only standard features, the isa server is not
installed. Clients are running in a standard 2003 domain.
The program is working fine on the server but clients cannot connect. I test
from Excel to make the test as basic as possible. The primary client is a
terminal server 2000 but trying from XP machines do not make any difference.
I get the following error fra Excel:
Connection failed:
SQLState: '01000'
SQL Server Error: 2
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL server does not exist or
acces is denied.
To your infomation, the msde is the latest build and updates. The MDAC is
updatet on the terminalserver.
I suspect the SBS 2003 has shut down something somewhere but I have no clue
where to look. I am a total norvice in SQL.
I have checked the port 1433 an it is not "LISTENING" (nor 1434 if thats the
port) Shall it be Listening and if so, how do I get it to listen?
Michael,
I had this exact problem on one of my SBS 2003 machines running MSDE.
Often 3rd party backup software like Veritas Backup Exec, attaches to
SQL/MSDE and modifies settings. Sometimes all communication protocols
are disabled.
To fix this, on the server run 'svrnetcn' and make sure that at least
one protocol is enabled. As you checked port 1433 I assume you want to
use TCP/IP, so ensure that at least TCP is in the 'Enabled Protocols'
section.
You also need to confirm that SQL is configured to communicate via this
protocol on the client machines. To do this, run 'cliconfg' on the
client machines. You will see a similar configuration tool to the
server. Make sure the 'Enabled Protocols' match the server, ie
confirm/add TCP.
Good luck, Al.
*** Sent via Developersdex http://www.codecomments.com ***

Cannot connect to MSDE on SBS 2003

My client has installed e scanner program wich is suposed til run on a MSDE
database. The program has to run on a reasently installed SBS 2003 server.
The server is installed with only standard features, the ISA server is not
installed. Clients are running in a standard 2003 domain.
The program is working fine on the server but clients cannot connect. I test
from Excel to make the test as basic as possible. The primary client is a
terminal server 2000 but trying from XP machines do not make any difference.
I get the following error fra Excel:
Connection failed:
SQLState: '01000'
SQL Server Error: 2
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Con
nect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL server does not
exist or
acces is denied.
To your infomation, the msde is the latest build and updates. The MDAC is
updatet on the terminalserver.
I suspect the SBS 2003 has shut down something somewhere but I have no clue
where to look. I am a total norvice in SQL.
I have checked the port 1433 an it is not "LISTENING" (nor 1434 if thats the
port) Shall it be Listening and if so, how do I get it to listen?Michael,
I had this exact problem on one of my SBS 2003 machines running MSDE.
Often 3rd party backup software like Veritas Backup Exec, attaches to
SQL/MSDE and modifies settings. Sometimes all communication protocols
are disabled.
To fix this, on the server run 'svrnetcn' and make sure that at least
one protocol is enabled. As you checked port 1433 I assume you want to
use TCP/IP, so ensure that at least TCP is in the 'Enabled Protocols'
section.
You also need to confirm that SQL is configured to communicate via this
protocol on the client machines. To do this, run 'cliconfg' on the
client machines. You will see a similar configuration tool to the
server. Make sure the 'Enabled Protocols' match the server, ie
confirm/add TCP.
Good luck, Al.
*** Sent via Developersdex http://www.codecomments.com ***

Sunday, February 12, 2012

Cannot Connect to an MS SQL Server

Hi,

I've developed an application that connects to an MS SQL server to read and write from a database. I have tested the program on about 6 computers (all on different networks and internet connections, etc...) and they can all access the database remotely just fine.

However, today I tried it on another PC (i.e. the 7th computer) and for some reason it won't connect. This computer is definitely on the internet as I can surf the web with it just fine, but every time I try to run the program it comes up and says that it cannot connect to the database. I can't remember the exact error message, but it was behaving as if the computer wasn't on the internet. What might cause a problem like this?

I did notice that this PC is running Norton Antivirus. All the other computers I tested on were not using Norton. Could Norton be the possible cause (i.e. might it be blocking a port or something like that). I will test it without Norton running, but I just thought I'd ask here too to see if anyone knows other possible reasons why this would be happening.

Thanks.

Have you tried to ping the IP/DNS name of the SQL Server machine?|||moving to SQL Server Data Access forum.|||

Yes. Norton Antivirus could be the cause of the issue. Try run your app with Norton disabled. I assume all your 7 machines are clients and the SQL Server is always the one.

One more thing you can check is to see if you have outdated alias defined on the 7-th machine. Use c:\windows\system32\cliconfg.exe or SQL Server Configuration Manager (if you app use sqlncli.dll) to check it.