Showing posts with label odbc. Show all posts
Showing posts with label odbc. Show all posts

Friday, March 30, 2012

MSDE timeout with wireless network enabled

Hi,
I have local MSDE installed on my laptop. When I am physically
connected to our network I can connect through my ODBC application
without issue.
However, when I have wireless networking enabled the first time I try to
connect I get a timeout. But, I'm able to immediately connect after
that initial timeout without a problem. This only occurs when wireless
networking is enabled, as the timeout does not occur with a physical LAN
connection.
I have the following installation:
MDAC SDK 2.8
MSDE 8.00.761
XP SP2
VS.NET 7.1
Any help would be greatly appreciated.
Thanks,
John
I am having a similar issue using SQL querries over a wireless connection.
Is there a technology that is better suited for wireless? Say .net?
Thanks in advance...
"JohnD" wrote:

> Hi,
> I have local MSDE installed on my laptop. When I am physically
> connected to our network I can connect through my ODBC application
> without issue.
> However, when I have wireless networking enabled the first time I try to
> connect I get a timeout. But, I'm able to immediately connect after
> that initial timeout without a problem. This only occurs when wireless
> networking is enabled, as the timeout does not occur with a physical LAN
> connection.
> I have the following installation:
> MDAC SDK 2.8
> MSDE 8.00.761
> XP SP2
> VS.NET 7.1
> Any help would be greatly appreciated.
> Thanks,
> John
>
|||Do you have the same problem if you use an IP address instead of the MSDE
instance name? Perhaps you're having a name resolution problem?
Jim
"Chris James" <Chris James@.discussions.microsoft.com> wrote in message
news:B19527EB-85E1-4DBC-9E51-A8CD463C1A89@.microsoft.com...[vbcol=seagreen]
>I am having a similar issue using SQL querries over a wireless connection.
> Is there a technology that is better suited for wireless? Say .net?
> Thanks in advance...
> "JohnD" wrote:
|||Thanks for the post Jim, Ive tried it using IP and Instance name... The
funny thing is that not all wireless installations have this issue, I have
two sites across the street and down about 1/4 mile. One site with approx
250' between wireless access point and client work fairly reliably, the other
is only 50' apart and they fail all the time. I wonder if its the
application making too many querries and boging down the wireless. Both
sites are using identical equipment as well.
"Jim Young" wrote:

> Do you have the same problem if you use an IP address instead of the MSDE
> instance name? Perhaps you're having a name resolution problem?
> Jim
> "Chris James" <Chris James@.discussions.microsoft.com> wrote in message
> news:B19527EB-85E1-4DBC-9E51-A8CD463C1A89@.microsoft.com...
>
>

MSDE SQL Connection error

I am trying to connect to a remote MSDE SQL database. When I set up the odbc connection I get a connection denied error. The SQL server is on a windows 2003 server. Any ideas are greatly appreciated.
Thanks, LinsLoMSDE won't allow remote connections on Windows 2003 unless you apply MSDE sp3a.

-PatP|||This is currently on the server, but it is still not connecting...|||what are you using to connect? a programming language (c, c++, c#) and are they .net? If you are using .net then i would suggest trying to use the sql connection library instead of the odbc. are you on the same network as the db server? please provide more info on your situation. I can not give an accurate answer with out more information

Wednesday, March 21, 2012

MSDE on XP running, but not recognized in ODBC

I installed an MSDE instance for a user running XP with an
admin Windows account. The MSDE Server icon appears in
the notification area, but without the green arrow. Task
manager shows that it is running. Trying to start it up
manually doesn't do anything. When I go to add the Data
Source in ODBC, System DSN (MDAC 2.8 is installed), when
we go to pick the MSDE Server, it doesn't appear in the
drop down when picking a server. Any thoughts or ideas
would be great. Thanks, JRaub.
hi JRaub,
JRaub wrote:
> I installed an MSDE instance for a user running XP with an
> admin Windows account. The MSDE Server icon appears in
> the notification area, but without the green arrow. Task
> manager shows that it is running. Trying to start it up
> manually doesn't do anything. When I go to add the Data
> Source in ODBC, System DSN (MDAC 2.8 is installed), when
> we go to pick the MSDE Server, it doesn't appear in the
> drop down when picking a server. Any thoughts or ideas
> would be great. Thanks, JRaub.
please have a look at
http://support.microsoft.com/default...b;EN-US;814132
if you want to modify the networkprotocols setting, please run the Server
Network Utility (svrnetcn.exe) and enable the desired protocol
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks. I'll give this a shot. Nothing else has worked.[vbcol=seagreen]
>--Original Message--
>hi JRaub,
>JRaub wrote:
an[vbcol=seagreen]
Task
>please have a look at
>http://support.microsoft.com/default.aspx?scid=kb;EN-
US;814132
>if you want to modify the networkprotocols setting,
please run the Server
>Network Utility (svrnetcn.exe) and enable the desired
protocol
>--
>Andrea Montanari (Microsoft MVP - SQL Server)
>http://www.asql.biz/DbaMgr.shtm
http://italy.mvps.org
>DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
>(my vb6+sql-dmo little try to provide MS MSDE 1.0 and
MSDE 2000 a visual
>interface)
>-- remove DMO to reply
>
>.
>

MSDE on a local computer (not into a LAN)

I try to develop an installer that should install MSDE and an app that needs an MSDE database. But the problem is, that the ODBC (and my installer too) see no MSDE installation if the computer is no part of a network. If i plug the network cable, i can find the MSDE (SQL Server) without a problem. If i unplug it, my installer (and ODBC too) find no MSDE/SQL installation.

Can anyone help me? Maybe should i set another option when i install MSDE to make it work on a local computer that is no part of a network? Any advice would be a bid help.

Thank you,
IulianI don't know why i cannot work with MSDE when my computer is no more in network.. pls ..some help would be so needed|||So? Anyone any idea?|||I've got a .CAB and Setup.exe that installs for clients :

- MSDE
- Minimum SQL Server with the db Master, tempdb,... (free part)

Plus a little free Entreprise-Manager-Look-A-Like program

does this interast you ?|||and functions and when the client have a local computer (that isn't in a network)?

Many thanks for your time and help!!!|||the file .Cab is too big to be sent by here
email me your e-mail so that i can send you the package|||i have send u my email adress.

I wait your file.

Tnks again|||i didn't receive your email

MSDE ODBC connection fails

I have 3 PCs on a LAN.
PC 1 has MSDE installed
PC 2 has MSDE installed
PC 3 doesn't have MSDE installed
I can set-up an ODBC connection through TCP/IP port and named pipes from PC
1 to PC 2 and vice versa.
The same TCP/IP ODBC details are used on PC 3 to connect to MSDE on PC 1 and
2 but the connection always fails. The named pipe connection works.
Originally PC 2 did not have MSDE installed and a TCP/IP ODBC connection
could not be made to PC 1 either. Once MSDE was installed the TCP/IP ODBC
connection worked.
Any ideas what the problem is here?
I know that by default MSDE is not set-up to allow access from a client
across the network but when I installed MSDE I used these switch commands to
allow it:
cd c:\MSDERelA
setup SAPWD="whatever" INSTANCENAME="PC1MSDE" TARGETDIR="C:\MSDE"
SECURITYMODE=SQL DISABLENETWORKPROTOCOLS=0 /L*v C:/MSDELog.log
At first I thought perhaps MSDE was listening on a different port to what it
was reporting but the MSDE log that is generated when the service starts and
svrnetcn.exe both indicate the same socket is being used. I have tried using
a different port.
I notice that when MSDE is installed, there is an extra option in the ODBC
TCP/IP dialog window 'dynamically determine port' and wondered if this had
anything to do with the problem? However, it doesn't seem to make a
difference because PC 1 and PC 2 can connect to each other with or without
this option enabled.
I found this article http://support.microsoft.com/kb/306865 which explains
how SQL Server 2000 may not be listening on TCP/IP sockets but the registry
keys again indicate that the correct port is being used.
FYI, I am using MSDE 2000. PC2 has been upgraded to MSDE2000 SP4 but that
hasn't resolved the issue. All 3 PCs are W2K Pro so no firewall issues.
I'm a bit stuck as to what else to try.
Ha, ha, ha - sorted it!
I installed the latest MDAC from
http://www.microsoft.com/downloads/d...DisplayLang=en
on PC 3 which didn't have MSDE installed and I can now make an ODBC
connection to any MSDE on the network.
The Microsoft Access Data Components include an updated SQL Server ODBC
driver.
Good way to end a Friday afternoon.
"Swaffs" wrote:

> I have 3 PCs on a LAN.
> PC 1 has MSDE installed
> PC 2 has MSDE installed
> PC 3 doesn't have MSDE installed
> I can set-up an ODBC connection through TCP/IP port and named pipes from PC
> 1 to PC 2 and vice versa.
> The same TCP/IP ODBC details are used on PC 3 to connect to MSDE on PC 1 and
> 2 but the connection always fails. The named pipe connection works.
> Originally PC 2 did not have MSDE installed and a TCP/IP ODBC connection
> could not be made to PC 1 either. Once MSDE was installed the TCP/IP ODBC
> connection worked.
> Any ideas what the problem is here?
> I know that by default MSDE is not set-up to allow access from a client
> across the network but when I installed MSDE I used these switch commands to
> allow it:
> cd c:\MSDERelA
> setup SAPWD="whatever" INSTANCENAME="PC1MSDE" TARGETDIR="C:\MSDE"
> SECURITYMODE=SQL DISABLENETWORKPROTOCOLS=0 /L*v C:/MSDELog.log
>
> At first I thought perhaps MSDE was listening on a different port to what it
> was reporting but the MSDE log that is generated when the service starts and
> svrnetcn.exe both indicate the same socket is being used. I have tried using
> a different port.
> I notice that when MSDE is installed, there is an extra option in the ODBC
> TCP/IP dialog window 'dynamically determine port' and wondered if this had
> anything to do with the problem? However, it doesn't seem to make a
> difference because PC 1 and PC 2 can connect to each other with or without
> this option enabled.
> I found this article http://support.microsoft.com/kb/306865 which explains
> how SQL Server 2000 may not be listening on TCP/IP sockets but the registry
> keys again indicate that the correct port is being used.
> FYI, I am using MSDE 2000. PC2 has been upgraded to MSDE2000 SP4 but that
> hasn't resolved the issue. All 3 PCs are W2K Pro so no firewall issues.
> I'm a bit stuck as to what else to try.
>

MSDE not working

I have installed MSDE on a computer but when I try to create an odbc
connection to it, I can't find the server in the list.
It seems that it isn't running, but I have checked the service to see if it
is running, and it is.
I am trying this on a system that has SQL Server for developers on it.
Could this be causing the problem?
Can someone point me in the right direction on this?How are you tring to connect. I take it this is a named instance so what
error do you get if you try and connect with osql e.g.
osql -E -S.\INSTANCENAME
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Lance Geeck" <lgeeck@.cox.net> wrote in message
news:_RzIc.19690$yc.8850@.fed1read06...
> I have installed MSDE on a computer but when I try to create an odbc
> connection to it, I can't find the server in the list.
> It seems that it isn't running, but I have checked the service to see if
it
> is running, and it is.
> I am trying this on a system that has SQL Server for developers on it.
> Could this be causing the problem?
> Can someone point me in the right direction on this?
>
>|||Jasper,
Thanks for responding.
The error message says:
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect() ).
Thanks
Lance
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:uS%23G5vEaEHA.3420@.TK2MSFTNGP12.phx.gbl...
> How are you tring to connect. I take it this is a named instance so what
> error do you get if you try and connect with osql e.g.
> osql -E -S.\INSTANCENAME
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Lance Geeck" <lgeeck@.cox.net> wrote in message
> news:_RzIc.19690$yc.8850@.fed1read06...
> > I have installed MSDE on a computer but when I try to create an odbc
> > connection to it, I can't find the server in the list.
> >
> > It seems that it isn't running, but I have checked the service to see if
> it
> > is running, and it is.
> >
> > I am trying this on a system that has SQL Server for developers on it.
> > Could this be causing the problem?
> >
> > Can someone point me in the right direction on this?
> >
> >
> >
>sql

Monday, March 12, 2012

MSDE Link Server

Is it possible to link MSDE to another server through ODBC? I want to do this like you can in Access, where you get external data by linking tables. Any ideas? Thanks!You should be able to usesp_addlinkedserver to accomplish this.

Terri

Friday, March 9, 2012

MSDE Installation Problem

I have installed MSDE on a computer but when I try to create an ODBC
connection to it, I can't find the server in the ODBC list of servers
available.
I am trying this on a system that has SQL Server 2000 for Developers on it
What does appear in the list are the following:
(local)
CRA-SERVER-2
Cra-Server-2
I don't know why there are two servers listed plus local, but all three
point to
the database setup under SQL Server 2000 for Developers.
It appears that MSDE installed properly. When I look in Component Services,
it is listed as MSSQL$CDC2, status = Started, Startup type = Automatic,
Logon as Local System. CDC2 is the instance name that I specified in the
Setup portion of the MSDE install package.
The directories specified all seem to have the files and data structures.
When I run the OSQL -E -S \CDC2 I get an error. The error message says:
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect() ).
When I look at the Task Manager, I have 2 copies of sqlservr.exe running. I
Assume one is for SQL Server 2000 Developer and the other is MSDE. (?)
I am a developer and need an ODBC connection to the database in the MSDE
installed CDC2 server. Can someone point me in the right direction for
resolving
this ODBC/SQL Server problem?
Thanks for your help.
LanceDoes this work with SQL authentication?
Meaning,
Osql -Usa -Ppassword sqlserver\instancename?
If it does, then you might want to check
325022 INFO: MSDE Security and Authentication
http://support.microsoft.com/?id=325022
Cheers,
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

MSDE Installation Problem

I have installed MSDE on a computer but when I try to create an ODBC
connection to it, I can't find the server in the ODBC list of servers
available.
I am trying this on a system that has SQL Server 2000 for Developers on it
What does appear in the list are the following:
(local)
CRA-SERVER-2
Cra-Server-2
I don't know why there are two servers listed plus local, but all three
point to
the database setup under SQL Server 2000 for Developers.
It appears that MSDE installed properly. When I look in Component Services,
it is listed as MSSQL$CDC2, status = Started, Startup type = Automatic,
Logon as Local System. CDC2 is the instance name that I specified in the
Setup portion of the MSDE install package.
The directories specified all seem to have the files and data structures.
When I run the OSQL -E -S \CDC2 I get an error. The error message says:
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect() ).
When I look at the Task Manager, I have 2 copies of sqlservr.exe running. I
Assume one is for SQL Server 2000 Developer and the other is MSDE. (?)
I am a developer and need an ODBC connection to the database in the MSDE
installed CDC2 server. Can someone point me in the right direction for
resolving
this ODBC/SQL Server problem?
Thanks for your help.
Lance
Does this work with SQL authentication?
Meaning,
Osql -Usa -Ppassword sqlserver\instancename?
If it does, then you might want to check
325022 INFO: MSDE Security and Authentication
http://support.microsoft.com/?id=325022
Cheers,
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

MSDE Installation Problem

I have installed MSDE on a computer but when I try to create an ODBC
connection to it, I can't find the server in the ODBC list of servers
available.
I am trying this on a system that has SQL Server 2000 for Developers on it
What does appear in the list are the following:
(local)
CRA-SERVER-2
Cra-Server-2
I don't know why there are two servers listed plus local, but all three
point to
the database setup under SQL Server 2000 for Developers.
It appears that MSDE installed properly. When I look in Component Services,
it is listed as MSSQL$CDC2, status = Started, Startup type = Automatic,
Logon as Local System. CDC2 is the instance name that I specified in the
Setup portion of the MSDE install package.
The directories specified all seem to have the files and data structures.
When I run the OSQL -E -S \CDC2 I get an error. The error message says:
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect() ).
When I look at the Task Manager, I have 2 copies of sqlservr.exe running. I
Assume one is for SQL Server 2000 Developer and the other is MSDE. (?)
I am a developer and need an ODBC connection to the database in the MSDE
installed CDC2 server. Can someone point me in the right direction for
resolving
this ODBC/SQL Server problem?
Thanks for your help.
LanceDoes this work with SQL authentication?
Meaning,
Osql -Usa -Ppassword sqlserver\instancename?
If it does, then you might want to check
325022 INFO: MSDE Security and Authentication
http://support.microsoft.com/?id=325022
Cheers,
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.