MSDE Access via the Network

I'm having a terrible time accessing an MSDE instance over the network.
sqlDMO's listAvailableSQLServers doesn't see the installed instance. I
installed the MSDE instance using setup.exe with the following command:
setup.exe disablenetworkprotocols=0 sapwd="<pwd>" securityMode=SQL
instanceName="<my instance name>"
No luck. So I thought I'd use the svrnetcn.exe utility to enable network
protocols since MSDE seems to be ignoring the command line. When I try to run
svrnetcn.exe, the screen flickers but the program never opens.
This *was* working several weeks ago. It quit working about the time I
installed Service Pack 2 for Windows XP on the box that was hosting this
server. Does anyone have any idea why this is happening to me? Any help
would be GREATLY appreciated.
Rob Reagan
rob@.digitallabsinc.com
hi Rob,
"Rob Reagan" <RobReagan@.discussions.microsoft.com> ha scritto nel messaggio
news:5B63E3CB-8307-49C8-ABC4-56B114893B1D@.microsoft.com...
> I'm having a terrible time accessing an MSDE instance over the network.
> sqlDMO's listAvailableSQLServers doesn't see the installed instance. I
> installed the MSDE instance using setup.exe with the following command:
> setup.exe disablenetworkprotocols=0 sapwd="<pwd>" securityMode=SQL
> instanceName="<my instance name>"
> No luck. So I thought I'd use the svrnetcn.exe utility to enable network
> protocols since MSDE seems to be ignoring the command line. When I try to
run
> svrnetcn.exe, the screen flickers but the program never opens.
> This *was* working several weeks ago. It quit working about the time I
> installed Service Pack 2 for Windows XP on the box that was hosting this
> server. Does anyone have any idea why this is happening to me? Any help
> would be GREATLY appreciated.
> Rob Reagan
> rob@.digitallabsinc.com
>
SP service pack 2 changed a lot of things regarding SQL Server connections
too..
I've not installed sp2 yet, but it's worth reading
http://support.microsoft.com/default.aspx?kbid=841249 and related links...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thank you so much! That's just the information I needed.
SP2 makes my PC so secure, not even my own applications can get through...
"Andrea Montanari" wrote:

> hi Rob,
> "Rob Reagan" <RobReagan@.discussions.microsoft.com> ha scritto nel messaggio
> news:5B63E3CB-8307-49C8-ABC4-56B114893B1D@.microsoft.com...
> run
> SP service pack 2 changed a lot of things regarding SQL Server connections
> too..
> I've not installed sp2 yet, but it's worth reading
> http://support.microsoft.com/default.aspx?kbid=841249 and related links...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>

MSDE 2000 and ODBC (Connection failed)

Hi
I Installed MSDE 2000 and try to connect with it via ODBC.
I want the connection with SQL Server authentication using a login ID "sa" and blank password
But it is dispaly this message:
====================
Connection failed:
SQLState:'28000'
SQL Server Error:18456
[Microsoft][ODBC Sql Server Driver][SQL Server]Login failed for user 'sa'
====================check what authentication method your msde is using and make sure that standard security is available.|||Thanks ms_sql_dba

My MSDE use both WINDOWS/SQL Server authentication
I check "LoginMode" value in REGISTRY it's = Zero which mean both|||Thanks ms_sql_dba

My MSDE use both WINDOWS/SQL Server authentication
I check "LoginMode" value in REGISTRY it's = Zero which mean both|||Up 4 Help|||I found the Solution in Archive which guide me to this link:
http://www.dbforums.com/showthread.php?threadid=711306

The Solution is very simple:
Change "SA" password

use this command line in DOS:
osql -Q"exec sp_password null,'newpassword','sa'" -E

MSDE / ODBC install problem...please help...

I have installed MSDE (and ODBC) at my client site on their 2003 server. I
have attached my SQL database via Teratrax Database Manager to the MSDE
server however when I try to setup the ODBC connection it doesn't list the
database in the drop-down. I cannot attach to the database from my notebook
either because I am not authenticated onto their domain.
I have also applied the regedit on the LoginMode key setting it to 2 and
rebooted but I still cannot connect to the database via the ODBC manager.
What am I doing wrong? I am NOT good with the scripts for configuring things
- generally I use the Enterprise Manager.
Try running the client config (cliconfig.exe) and create an alias for the
server. Specify the protocol to talk to it - (probably TCP/IP vs. named
pipes). On my system its in \windows\system32.
Brian
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:46518420-EF43-475F-BECA-9E5A7E6A21D2@.microsoft.com...
>I have installed MSDE (and ODBC) at my client site on their 2003 server. I
> have attached my SQL database via Teratrax Database Manager to the MSDE
> server however when I try to setup the ODBC connection it doesn't list the
> database in the drop-down. I cannot attach to the database from my
> notebook
> either because I am not authenticated onto their domain.
> I have also applied the regedit on the LoginMode key setting it to 2 and
> rebooted but I still cannot connect to the database via the ODBC manager.
> What am I doing wrong? I am NOT good with the scripts for configuring
> things
> - generally I use the Enterprise Manager.

MSDE - Problems connecting using SQL Authentication

I'm trying to use the import/export part of MSDE. When I choose to connect to the server via Windows NT Authentication, everything works fine, assuming I have a connection to the server open (ie VPN connection).

When I chooose SQL Server Authentication, I get the following error:

Client unable to establish connection [CBNMPNTW] ConnectionOpen(CreateFile()).

I need to be able to connect using sql server authentication. Can anyone help me?

Thanks,
StephanieRE:
I'm trying to use the import/export part of MSDE. When I choose to connect to the server via Windows NT Authentication, everything works fine, assuming I have a connection to the server open (ie VPN connection). When I chooose SQL Server Authentication, I get the following error: Client unable to establish connection [CBNMPNTW] ConnectionOpen(CreateFile()). I need to be able to connect using sql server authentication. Can anyone help me?
Thanks,
Stephanie

Q1 Can anyone help me?
A1 Possibly, more information would be helpful and is probably quite necessary. You may well have more than one issue, i.e.(Are you using DSNs, do you have a local DSN(s) configured to use TCP/IP instead of Named Pipes, are you able to tracert / ping your MSDE server with and / or without Windows NT Authentication via your VPN, is your VPN Win NT authentication based, etc., etc.,?).

Msde

When setting up the MSDE should you be able to connect to it ... from another machine using Sql client tools via enterprise manager...like you would connecting to machines that have sql standard editionyou have to have a port open in your windows firewall if you are doing this one a workstation. MSDE also shuts down after the last connection closes and you have to change that.|||MSDE can also be set up to not listen on any network protocol. Check the errorlog of MSDE to make sure it is listening on the network.|||By default network connections to MSDE are disabled. However, you can change that in the instance settings.

Also, as far as I know, all versions of SQL Server 2005 don't allow network connections by default as well. But yet again, that can all be changed in the configuration manager.|||we are mainly connection to sql 2000 machines...
I can connect to instantly from visual studio .net 2003 through the server explorer... but through client tools via enterprise manager its a no go...
I set up the instance with the parameter setting DISABLENETWORKPROTOCOLS=0 so that the instance can accept connections....