Monday, March 26, 2012
How to connect to remote MSDE database using VB.NET
I have a VB.NET application that works great with a local MSDE database. But, when I try to revise my connection string to point to a remote MSDE server and database, it fails. The MSDE Server Manager can pick up the remote server and tell me its runni
ng, but when I try to register it using SQL Server, or use a DSN to connect to it, I get a "SQL Server does not exist or access denied. ConnectionOpen(Connect())" My connection string is:
Provider=SQLOLEDB.1;Server=DSS\VSDOTNET;Database=d atabase;User ID=sa;Password = xxxxx;Integrated Security=SSPI
Any help will be appreciated. Thanks...
- Tim B.
hi Tim
"Tim Balderramos" <pacmantab@.hotmail.com> ha scritto nel messaggio
news:28F08CF8-86CF-4C04-9E5A-900296EC78A7@.microsoft.com...
> Greetings
> I have a VB.NET application that works great with a local MSDE database.
But, when I try
>to revise my connection string to point to a remote MSDE server and
database, it fails. The
>MSDE Server Manager can pick up the remote server and tell me its running,
but when I try
>to register it using SQL Server, or use a DSN to connect to it, I get a
"SQL Server does not
>exist or access denied. ConnectionOpen(Connect())" My connection string
is:
> Provider=SQLOLEDB.1;Server=DSS\VSDOTNET;Database=d atabase;User
>ID=sa;Password = xxxxx;Integrated Security=SSPI
the most frequent causes of that kind of error are reported in
http://support.microsoft.com/default...06&Product=sql
KB article...
please verify the remote MSDE instance has enabled networkprotocols too,
using the remote Server Network Utilityes (svrnecn.exe)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I think that does it. Here is what my co-worker did:
During MSDE setup, use SECURITYMODE=SQL
Then use SVRNETCN.exe and enable TCP/IP as a network library. I did this on
both machines, but you may not need to do it for both (wasn't sure, but didn't
think it mattered).
Here's the connection string that was working -
Provider=SQLOLEDB;Data Source=wrctest;user id=sa;password=wrctest;Initial
Catalog=winthrop;Net=dbmssocn;Auto Translate=True;Persist Security
Info=False;Use Encryption for Data=False
How to connect to my MSDE 2000 Rel A
I only have Framework installed on my machine, and I also installed MSDE 2000 Rel. A, using the following command:
C:\MSDERelA\setup.exe SAPWD="myPass" INSTANCENAME="myXP"
I can see that the service for this app is running. Though, I could not connect to it using oSql command like the following:
osql -S(local)\myXP -E
or
osql -S(local)\myXP -Usa, and supply the password "myPass".
The message was:
[DBMSLPCN]SQL Server does not exist or access denied.
[DBMSLPCN]ConnectionOpen (Connect()).
Any response would be appreciated.
Subi_IHave you tried
osql -Lto verify the instance name?
If that doesn't help you may also want to check out this link|||Hi McMurdo,
Thanks. The command did help to find my database (my initial post was wrong in specifying the instance name).
And the link really helps for managing MSDE without UI tools.
Thanks,
Subi_I
How to connect to msde on an other server?
This wasn't possible!
Unable to establish connection. Server unknown or access denied!
What can i do?
thx
Hi,
Can you enable the TCPIP protocol using the utility svrnetcn.exe from SQL
server machine. Run the
svrnetcn.exe from command prompt and after enabling the protocol stop and
start the MSSQL server Service .
After starting the service try connecting remotely
Thanks
Hari
SQL Server MVP
"Raupes" <Raupes@.discussions.microsoft.com> wrote in message
news:1055E5E7-0B98-4A3D-A303-8DA1C511FED4@.microsoft.com...
>I tried to connect to a msde on an other server via the enterprise manager.
> This wasn't possible!
> Unable to establish connection. Server unknown or access denied!
> What can i do?
> thx
|||Hi,
I have exactly the same problem. I have tried your
suggestion but without success.
Anyone have another suggestion?
Tks, Rui
>--Original Message--
>Hi,
>Can you enable the TCPIP protocol using the utility
svrnetcn.exe from SQL
>server machine. Run the
>svrnetcn.exe from command prompt and after enabling the
protocol stop and
>start the MSSQL server Service .
>After starting the service try connecting remotely
>
>--
>Thanks
>Hari
>SQL Server MVP
>
>"Raupes" <Raupes@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:1055E5E7-0B98-4A3D-A303-8DA1C511FED4@.microsoft.com...
enterprise manager.[vbcol=seagreen]
access denied!
>
>.
>
|||I had the same problem.
If you telnet to port 1433 on the machine running msde do you get a
connection failed message? If it fails it could be firewall settings.
I fixed the problem here by removing all protocols and then re-adding only
tcp/ip.
"Rui Oliveira" <anonymous@.discussions.microsoft.com> wrote in message
news:495b01c4c748$732788c0$a401280a@.phx.gbl...[vbcol=seagreen]
> Hi,
> I have exactly the same problem. I have tried your
> suggestion but without success.
> Anyone have another suggestion?
> Tks, Rui
> svrnetcn.exe from SQL
> protocol stop and
> message
> enterprise manager.
> access denied!
|||At first I had to configure the port at which the msde is listening.
After that I had to open the UDP 1434 port vor all wizzards of the
enterprise manager. Only god knows why the enterprise manager uses 1433 tcp
only and all other wizzards use 1434 udp.
hm.
hope that i could help you
cu
Raupes
"Rui Oliveira" wrote:
> Hi,
> I have exactly the same problem. I have tried your
> suggestion but without success.
> Anyone have another suggestion?
> Tks, Rui
> svrnetcn.exe from SQL
> protocol stop and
> message
> enterprise manager.
> access denied!
>
Friday, March 23, 2012
How to connect SQL-Server to MSDE using Linked Server?
See the subject sp_addlinkedserver in the Books Online.
Jim
"Geri Reshef" <GeriR@.Dubek.co.il> wrote in message
news:OTGIc%238%23EHA.3336@.TK2MSFTNGP11.phx.gbl...
>I s there a good explanation in the web for beginners like me?
>
sql
Wednesday, March 21, 2012
How to connect 2005 express
Now I cannot connect it on my SQL Server Group with Server Enterprise
Manager.
Thanks
Did you enable remote access?
"M" <mxchen@.hotvoice.com> wrote in message
news:Onz7tSJDGHA.2036@.TK2MSFTNGP14.phx.gbl...
> I installed SQL Server 2005 Express in a computer to replace MSDE.
> Now I cannot connect it on my SQL Server Group with Server Enterprise
> Manager.
> Thanks
>
>
|||Enterprise manager can't mange SQL Server 2005 instances correctly. The
reason EM doesn't see it is probably because you haven't enabled and started
the sqlbrowser and enabled networking for your Express instance but even
when you can see it, EM won't be able to manage Express because it is not
forward compatible.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"M" <mxchen@.hotvoice.com> wrote in message
news:Onz7tSJDGHA.2036@.TK2MSFTNGP14.phx.gbl...
> I installed SQL Server 2005 Express in a computer to replace MSDE.
> Now I cannot connect it on my SQL Server Group with Server Enterprise
> Manager.
> Thanks
>
>
|||Yes. but The Server Enterprise Manager is 2000 version
"Martin" <mpennings@.wanadoo.nl> wrote in message
news:43b42163$0$208$dbd41001@.news.wanadoo.nl...
> Did you enable remote access?
> "M" <mxchen@.hotvoice.com> wrote in message
> news:Onz7tSJDGHA.2036@.TK2MSFTNGP14.phx.gbl...
>
>
|||It won't work, I just tried myself. Enterprise manager is not compatible.
You'll need another tool.
"M" <mxchen@.hotvoice.com> wrote in message
news:%23W7jz6LDGHA.2700@.TK2MSFTNGP14.phx.gbl...
> Yes. but The Server Enterprise Manager is 2000 version
> "Martin" <mpennings@.wanadoo.nl> wrote in message
> news:43b42163$0$208$dbd41001@.news.wanadoo.nl...
>
>
|||It has been mentioned before, you can download it from:
http://www.microsoft.com/downloads/d...displaylang=en
"M" <mxchen@.hotvoice.com> wrote in message
news:%23W7jz6LDGHA.2700@.TK2MSFTNGP14.phx.gbl...
> Yes. but The Server Enterprise Manager is 2000 version
> "Martin" <mpennings@.wanadoo.nl> wrote in message
> news:43b42163$0$208$dbd41001@.news.wanadoo.nl...
>
>
sql
Monday, March 19, 2012
How to configure MSDE to listen on TCP/IP
I'm not able to connect to MSDE remotely. From the SQL Server logs, it
is listening on Shared Memory only. How do I configure it to listen on
TCP/IP ?
The MSDE is running on WinXP Pro SP2, and there is a instance of
SQL2005 Express installed side by side, the SQL2005 Express is
configure to listen on port 1618. The firewall already turned off.
Another problem is related to SQL2005 Express... I'm not able to
connect to the SQL2005 Express remotely when the firewall turned ON,
even port 1618 is already add into exception list.
Any idea ?
Thanks
JCVoon
Problem solved. I enable the Named Pipes protocol using SVRNETCN.exe
and restart the MSDE.
Why must enabled the Named Pipes when I only need TCP/IP protocol ?
JCVoon
On Jan 25, 12:45 pm, "jcvoon" <jiangchnan.v...@.maximas.com> wrote:
> Hi:
> I'm not able to connect to MSDE remotely. From the SQL Server logs, it
> is listening on Shared Memory only. How do I configure it to listen on
> TCP/IP ?
> The MSDE is running on WinXP Pro SP2, and there is a instance of
> SQL2005 Express installed side by side, the SQL2005 Express is
> configure to listen on port 1618. The firewall already turned off.
> Another problem is related to SQL2005 Express... I'm not able to
> connect to the SQL2005 Express remotely when the firewall turned ON,
> even port 1618 is already add into exception list.
> Any idea ?
> Thanks
> JCVoon
|||network communications are typically more interactive for named pipes whereas.
data transmissions are more streamlined and have less overhead in TCP/IP
You can have more in SQL BOL
"jcvoon" wrote:
> Problem solved. I enable the Named Pipes protocol using SVRNETCN.exe
> and restart the MSDE.
> Why must enabled the Named Pipes when I only need TCP/IP protocol ?
> JCVoon
>
> On Jan 25, 12:45 pm, "jcvoon" <jiangchnan.v...@.maximas.com> wrote:
>
|||> Another problem is related to SQL2005 Express... I'm not able to
> connect to the SQL2005 Express remotely when the firewall turned ON,
> even port 1618 is already add into exception list.
You have to add the C:\Program Files\Microsoft SQL
Server\90\Shared\sqlbrowser.exe into the exceptions list.
Monday, March 12, 2012
How to configure MSDE to listen on TCP/IP
I'm not able to connect to MSDE remotely. From the SQL Server logs, it
is listening on Shared Memory only. How do I configure it to listen on
TCP/IP ?
The MSDE is running on WinXP Pro SP2, and there is a instance of
SQL2005 Express installed side by side, the SQL2005 Express is
configure to listen on port 1618. The firewall already turned off.
Another problem is related to SQL2005 Express... I'm not able to
connect to the SQL2005 Express remotely when the firewall turned ON,
even port 1618 is already add into exception list.
Any idea ?
Thanks
JCVoonProblem solved. I enable the Named Pipes protocol using SVRNETCN.exe
and restart the MSDE.
Why must enabled the Named Pipes when I only need TCP/IP protocol '
JCVoon
On Jan 25, 12:45 pm, "jcvoon" <jiangchnan.v...@.maximas.com> wrote:
> Hi:
> I'm not able to connect to MSDE remotely. From the SQL Server logs, it
> is listening on Shared Memory only. How do I configure it to listen on
> TCP/IP ?
> The MSDE is running on WinXP Pro SP2, and there is a instance of
> SQL2005 Express installed side by side, the SQL2005 Express is
> configure to listen on port 1618. The firewall already turned off.
> Another problem is related to SQL2005 Express... I'm not able to
> connect to the SQL2005 Express remotely when the firewall turned ON,
> even port 1618 is already add into exception list.
> Any idea ?
> Thanks
> JCVoon|||network communications are typically more interactive for named pipes wherea
s.
data transmissions are more streamlined and have less overhead in TCP/IP
You can have more in SQL BOL
"jcvoon" wrote:
> Problem solved. I enable the Named Pipes protocol using SVRNETCN.exe
> and restart the MSDE.
> Why must enabled the Named Pipes when I only need TCP/IP protocol '
> JCVoon
>
> On Jan 25, 12:45 pm, "jcvoon" <jiangchnan.v...@.maximas.com> wrote:
>|||> Another problem is related to SQL2005 Express... I'm not able to
> connect to the SQL2005 Express remotely when the firewall turned ON,
> even port 1618 is already add into exception list.
You have to add the C:\Program Files\Microsoft SQL
Server\90\Shared\sqlbrowser.exe into the exceptions list.
How to configure MSDE to listen on TCP/IP
I'm not able to connect to MSDE remotely. From the SQL Server logs, it
is listening on Shared Memory only. How do I configure it to listen on
TCP/IP ?
The MSDE is running on WinXP Pro SP2, and there is a instance of
SQL2005 Express installed side by side, the SQL2005 Express is
configure to listen on port 1618. The firewall already turned off.
Another problem is related to SQL2005 Express... I'm not able to
connect to the SQL2005 Express remotely when the firewall turned ON,
even port 1618 is already add into exception list.
Any idea ?
Thanks
JCVoonProblem solved. I enable the Named Pipes protocol using SVRNETCN.exe
and restart the MSDE.
Why must enabled the Named Pipes when I only need TCP/IP protocol '
JCVoon
On Jan 25, 12:45 pm, "jcvoon" <jiangchnan.v...@.maximas.com> wrote:
> Hi:
> I'm not able to connect to MSDE remotely. From the SQL Server logs, it
> is listening on Shared Memory only. How do I configure it to listen on
> TCP/IP ?
> The MSDE is running on WinXP Pro SP2, and there is a instance of
> SQL2005 Express installed side by side, the SQL2005 Express is
> configure to listen on port 1618. The firewall already turned off.
> Another problem is related to SQL2005 Express... I'm not able to
> connect to the SQL2005 Express remotely when the firewall turned ON,
> even port 1618 is already add into exception list.
> Any idea ?
> Thanks
> JCVoon|||network communications are typically more interactive for named pipes whereas.
data transmissions are more streamlined and have less overhead in TCP/IP
You can have more in SQL BOL
"jcvoon" wrote:
> Problem solved. I enable the Named Pipes protocol using SVRNETCN.exe
> and restart the MSDE.
> Why must enabled the Named Pipes when I only need TCP/IP protocol '
> JCVoon
>
> On Jan 25, 12:45 pm, "jcvoon" <jiangchnan.v...@.maximas.com> wrote:
> > Hi:
> >
> > I'm not able to connect to MSDE remotely. From the SQL Server logs, it
> > is listening on Shared Memory only. How do I configure it to listen on
> > TCP/IP ?
> >
> > The MSDE is running on WinXP Pro SP2, and there is a instance of
> > SQL2005 Express installed side by side, the SQL2005 Express is
> > configure to listen on port 1618. The firewall already turned off.
> >
> > Another problem is related to SQL2005 Express... I'm not able to
> > connect to the SQL2005 Express remotely when the firewall turned ON,
> > even port 1618 is already add into exception list.
> >
> > Any idea ?
> >
> > Thanks
> > JCVoon
>|||> Another problem is related to SQL2005 Express... I'm not able to
> connect to the SQL2005 Express remotely when the firewall turned ON,
> even port 1618 is already add into exception list.
You have to add the C:\Program Files\Microsoft SQL
Server\90\Shared\sqlbrowser.exe into the exceptions list.
Friday, March 9, 2012
how to completly remove all sql instances!
I kinda play with MSDE / SQL Express and now I need to remove everything!
I did the manual remove (http://support.microsoft.com/kb/320873/EN-US/)
but I did copy the osql.exe file.
Now, when I do osql -L to list the instances, I got 4 of them!
all of which I have no idea how they got there.. and the names tell me nothing (nothing I ever typed during my test!)
- JUKELANSRV\SQLEXPRESS
- QUAD-1800
- SERVEURSQL (that's in French!)
- VIVENDI
the only thing that MIGHT have cause SOME of these (certainly not all), is ENSIM X PRO
Anyway.. I need to remove them all and everything related to SQL.
Thanks for any response!Any thoughts on this?|||Himartinbl, as I understand the osql -L command is used to list all servers detected on the network, including SQL aliases created on local client. If you want to check installed SQL instances on you local machine, you can check in registry or services.msc
How to completely remove MSDE
Thank you,If you can tell me what the error said, then I'll be in a position to help you. But If it said something about some file not be able to be deleted, make sure it (MSDE) isn't running.