Connecting to sql from Delphi 5

I try to connect (locally) to SQLServer Express from Delphi5. On my developer computer, which has Windows XP, SQLServer 2000, VisualStudio2005 (and with that, SQLExpress 2005), it is no problem. However, when I transfer my program and the database to other computers with Windows 2000/WindowsServer2003 and a more recent standalone-version of SQLExpress, I get error messages like:

'Db-Library error 10004: No connection possible: SQL Server not available or not existing'

It does not matter which protocols I activate at the Server or whether the Server Browser service is running or not.

Does anybody have an idea how this might be fixed? Or whether it is a problem of the operating system?

Didi you try making a connecting without any Delphi tools like sqlcmd.exe at the command prompt ?

HTH, Jens K. Suessemeyer.

http://www.sqlserver2005.de
|||

Yes, all MS SQL 2005 tools work.

Meanwhile I found a solution myself: Everything works fine, if I install SQL Server 2000 additionally -- the client suffices. I don't like talking to a new 2005 database via an old 2000 client library, but at least it works.

Thanks very much for helping.

Lucia Lehr

connecting to SQL express through VB

Hi all,

I have SQL server express edition 2005 installed on my computer and using VB in MS Access to run some queries. The VB function looks something like this..

Dim dataRS As New ADODB.Recordset
Dim cnnSQL As New ADODB.Connection

Set cnnSQL = New ADODB.Connection
cnnSQL.ConnectionString = "Provider=SQLNCLI;Server=.\SQLExpress;Database=TestDB;Trusted_Connection=yes;"

cnnSQL.Properties("Integrated Security").Value = "SSPI"
cnnSQL.Open

dataRS.Open "SELECT dbo_Table_1.* FROM dbo_Table_1", cnnSQL, adOpenStatic, adLockOptimistic

The code fails on the last line with message
"Invalid object name 'dbo_Table_1'"
(yes, I verified that the table actually does exist in the DB)

I must be doing something wrong with the connection string but all the things that I've tried so far haven't worked.. Can anyone offer any suggestions?

Thanks in advance,

Try providing the schema name for the table in your select statement, as in:

SELECT DBO.dbo_Table1.* FROM DBO.dbo_Table1

You schema may or may not be DBO, I just use that here as an example.

Mike

Connecting to remote SQL Server

I have SQL Server 2000 (Developer) on my computer. So I have SQL
Server Enterprise Manager + Tools (such as Query Analyzer).
I am doing some work on a remote server, mostly ASP pages (not
ASP.NET). There is a SQL Server database on that server. I would like
to use Enterprise Manager or Query Analyzer to access that database.
My main development environment is Dreamweaver MX2004. In Dreamweaver,
I was able to setup the database (on the databases tab) using a
"Custom Connection String", listed below (some info obfuscated for
security):
"Provider=SQLOLEDB.1;Persist Security Info=False;Initial
Catalog=funeral;Data Source=xx.xx.xx.xxx;Locale
Identifier=1033;Connect Timeout=15;Use Procedure for Prepare=1;Auto
Translate=True;Packet Size=4096;User Id=XXX;PASSWORD=XXXXXXXX;"
I don't know if it is possible to use the other tools to manage this
database. I've tried the following:
1. In Enterprise Manager, I've tried just putting the ip address as
the server, and "Use SQL Server authentication" from the user ID and
Password above, but I get the following error:
"SQL Server registration failed because of the connection failure
below... Cannot open user default database. Login failed"
2. Created a udl file. In the Provider, selected the "Microsoft OLE DB
Provider for SQL Server" Entered teh IP address and username/password
on the Connection Tab. I get the same error as #1 above.
Any insight would be greatly appreciated.
"Bryce Fischer" <spamtrap@.berzerker-soft.com> wrote in message
news:3btpo01us397pf1gmfl4bt9c8k9dcrv05e@.4ax.com...
> I have SQL Server 2000 (Developer) on my computer. So I have SQL
> Server Enterprise Manager + Tools (such as Query Analyzer).
> I am doing some work on a remote server, mostly ASP pages (not
> ASP.NET). There is a SQL Server database on that server. I would like
> to use Enterprise Manager or Query Analyzer to access that database.
> My main development environment is Dreamweaver MX2004. In Dreamweaver,
> I was able to setup the database (on the databases tab) using a
> "Custom Connection String", listed below (some info obfuscated for
> security):
> "Provider=SQLOLEDB.1;Persist Security Info=False;Initial
> Catalog=funeral;Data Source=xx.xx.xx.xxx;Locale
> Identifier=1033;Connect Timeout=15;Use Procedure for Prepare=1;Auto
> Translate=True;Packet Size=4096;User Id=XXX;PASSWORD=XXXXXXXX;"
> I don't know if it is possible to use the other tools to manage this
> database. I've tried the following:
> 1. In Enterprise Manager, I've tried just putting the ip address as
> the server, and "Use SQL Server authentication" from the user ID and
> Password above, but I get the following error:
> "SQL Server registration failed because of the connection failure
> below... Cannot open user default database. Login failed"
>
User XXX has a login on the remote server, but does not have a user in the
database he is configured to use. To administer the remote database, User
XXX must be a member of the sysadmin role on the remote server
http://snodland.blogspot.com
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.788 / Virus Database: 533 - Release Date: 01/11/2004
|||On Sat, 6 Nov 2004 22:04:54 -0000, "Bob Simms"
<bob_simms@.somewhere.com> wrote:

>User XXX has a login on the remote server, but does not have a user in the
>database he is configured to use. To administer the remote database, User
>XXX must be a member of the sysadmin role on the remote server
Thanks for the reply.
Is it possible to use Query Analyzer or Access to connect to the
server given the information in my original post? I don't need
administrator-like functionality. As I mentioned, in Dreamweaver, I'm
able to create a connection, and view the tables and data (not to be
confused with creating the connection on the ASP pages, but in
Dreamweaver itself.) Dreamweaver lets you browse the tables, and data,
it doesn't let you run SQL Statements, which is why I'd like to use
other tools I have.
TIA.
|||On Sat, 06 Nov 2004 20:21:58 -0500, Bryce Fischer
<spamtrap@.berzerker-soft.com> wrote:

>On Sat, 6 Nov 2004 22:04:54 -0000, "Bob Simms"
><bob_simms@.somewhere.com> wrote:
>
>Thanks for the reply.
>Is it possible to use Query Analyzer or Access to connect to the
>server given the information in my original post? I don't need
>administrator-like functionality. As I mentioned, in Dreamweaver, I'm
>able to create a connection, and view the tables and data (not to be
>confused with creating the connection on the ASP pages, but in
>Dreamweaver itself.) Dreamweaver lets you browse the tables, and data,
>it doesn't let you run SQL Statements, which is why I'd like to use
>other tools I have.
Well... After some persistence, I figured it out. In Access, and
Visual Studio, I was able to bring up the Data Link Properties dialog,
and enter the information, and the one step I was not doing, was
entering in the catalog in the "Select the database on the server:"
field.
I was able to accomplish the same thing in Visual Studio, Server
Explorer, Data Connections.

Connecting to remote SQL Server

I have SQL Server 2000 (Developer) on my computer. So I have SQL
Server Enterprise Manager + Tools (such as Query Analyzer).
I am doing some work on a remote server, mostly ASP pages (not
ASP.NET). There is a SQL Server database on that server. I would like
to use Enterprise Manager or Query Analyzer to access that database.
My main development environment is Dreamweaver MX2004. In Dreamweaver,
I was able to setup the database (on the databases tab) using a
"Custom Connection String", listed below (some info obfuscated for
security):
"Provider=SQLOLEDB.1;Persist Security Info=False;Initial
Catalog=funeral;Data Source=xx.xx.xx.xxx;Locale
Identifier=1033;Connect Timeout=15;Use Procedure for Prepare=1;Auto
Translate=True;Packet Size=4096;User Id=XXX;PASSWORD=XXXXXXXX;"
I don't know if it is possible to use the other tools to manage this
database. I've tried the following:
1. In Enterprise Manager, I've tried just putting the ip address as
the server, and "Use SQL Server authentication" from the user ID and
Password above, but I get the following error:
"SQL Server registration failed because of the connection failure
below... Cannot open user default database. Login failed"
2. Created a udl file. In the Provider, selected the "Microsoft OLE DB
Provider for SQL Server" Entered teh IP address and username/password
on the Connection Tab. I get the same error as #1 above.
Any insight would be greatly appreciated."Bryce Fischer" <spamtrap@.berzerker-soft.com> wrote in message
news:3btpo01us397pf1gmfl4bt9c8k9dcrv05e@.
4ax.com...
> I have SQL Server 2000 (Developer) on my computer. So I have SQL
> Server Enterprise Manager + Tools (such as Query Analyzer).
> I am doing some work on a remote server, mostly ASP pages (not
> ASP.NET). There is a SQL Server database on that server. I would like
> to use Enterprise Manager or Query Analyzer to access that database.
> My main development environment is Dreamweaver MX2004. In Dreamweaver,
> I was able to setup the database (on the databases tab) using a
> "Custom Connection String", listed below (some info obfuscated for
> security):
> "Provider=SQLOLEDB.1;Persist Security Info=False;Initial
> Catalog=funeral;Data Source=xx.xx.xx.xxx;Locale
> Identifier=1033;Connect Timeout=15;Use Procedure for Prepare=1;Auto
> Translate=True;Packet Size=4096;User Id=XXX;PASSWORD=XXXXXXXX;"
> I don't know if it is possible to use the other tools to manage this
> database. I've tried the following:
> 1. In Enterprise Manager, I've tried just putting the ip address as
> the server, and "Use SQL Server authentication" from the user ID and
> Password above, but I get the following error:
> "SQL Server registration failed because of the connection failure
> below... Cannot open user default database. Login failed"
>
User XXX has a login on the remote server, but does not have a user in the
database he is configured to use. To administer the remote database, User
XXX must be a member of the sysadmin role on the remote server
http://snodland.blogspot.com
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.788 / Virus Database: 533 - Release Date: 01/11/2004|||On Sat, 6 Nov 2004 22:04:54 -0000, "Bob Simms"
<bob_simms@.somewhere.com> wrote:

>User XXX has a login on the remote server, but does not have a user in the
>database he is configured to use. To administer the remote database, User
>XXX must be a member of the sysadmin role on the remote server
Thanks for the reply.
Is it possible to use Query Analyzer or Access to connect to the
server given the information in my original post? I don't need
administrator-like functionality. As I mentioned, in Dreamweaver, I'm
able to create a connection, and view the tables and data (not to be
confused with creating the connection on the ASP pages, but in
Dreamweaver itself.) Dreamweaver lets you browse the tables, and data,
it doesn't let you run SQL Statements, which is why I'd like to use
other tools I have.
TIA.|||On Sat, 06 Nov 2004 20:21:58 -0500, Bryce Fischer
<spamtrap@.berzerker-soft.com> wrote:

>On Sat, 6 Nov 2004 22:04:54 -0000, "Bob Simms"
><bob_simms@.somewhere.com> wrote:
>
>Thanks for the reply.
>Is it possible to use Query Analyzer or Access to connect to the
>server given the information in my original post? I don't need
>administrator-like functionality. As I mentioned, in Dreamweaver, I'm
>able to create a connection, and view the tables and data (not to be
>confused with creating the connection on the ASP pages, but in
>Dreamweaver itself.) Dreamweaver lets you browse the tables, and data,
>it doesn't let you run SQL Statements, which is why I'd like to use
>other tools I have.
Well... After some persistence, I figured it out. In Access, and
Visual Studio, I was able to bring up the Data Link Properties dialog,
and enter the information, and the one step I was not doing, was
entering in the catalog in the "Select the database on the server:"
field.
I was able to accomplish the same thing in Visual Studio, Server
Explorer, Data Connections.

Connecting to remote SQL Server

I have SQL Server 2000 (Developer) on my computer. So I have SQL
Server Enterprise Manager + Tools (such as Query Analyzer).
I am doing some work on a remote server, mostly ASP pages (not
ASP.NET). There is a SQL Server database on that server. I would like
to use Enterprise Manager or Query Analyzer to access that database.
My main development environment is Dreamweaver MX2004. In Dreamweaver,
I was able to setup the database (on the databases tab) using a
"Custom Connection String", listed below (some info obfuscated for
security):
"Provider=SQLOLEDB.1;Persist Security Info=False;Initial
Catalog=funeral;Data Source=xx.xx.xx.xxx;Locale
Identifier=1033;Connect Timeout=15;Use Procedure for Prepare=1;Auto
Translate=True;Packet Size=4096;User Id=XXX;PASSWORD=XXXXXXXX;"
I don't know if it is possible to use the other tools to manage this
database. I've tried the following:
1. In Enterprise Manager, I've tried just putting the ip address as
the server, and "Use SQL Server authentication" from the user ID and
Password above, but I get the following error:
"SQL Server registration failed because of the connection failure
below... Cannot open user default database. Login failed"
2. Created a udl file. In the Provider, selected the "Microsoft OLE DB
Provider for SQL Server" Entered teh IP address and username/password
on the Connection Tab. I get the same error as #1 above.
Any insight would be greatly appreciated."Bryce Fischer" <spamtrap@.berzerker-soft.com> wrote in message
news:3btpo01us397pf1gmfl4bt9c8k9dcrv05e@.4ax.com...
> I have SQL Server 2000 (Developer) on my computer. So I have SQL
> Server Enterprise Manager + Tools (such as Query Analyzer).
> I am doing some work on a remote server, mostly ASP pages (not
> ASP.NET). There is a SQL Server database on that server. I would like
> to use Enterprise Manager or Query Analyzer to access that database.
> My main development environment is Dreamweaver MX2004. In Dreamweaver,
> I was able to setup the database (on the databases tab) using a
> "Custom Connection String", listed below (some info obfuscated for
> security):
> "Provider=SQLOLEDB.1;Persist Security Info=False;Initial
> Catalog=funeral;Data Source=xx.xx.xx.xxx;Locale
> Identifier=1033;Connect Timeout=15;Use Procedure for Prepare=1;Auto
> Translate=True;Packet Size=4096;User Id=XXX;PASSWORD=XXXXXXXX;"
> I don't know if it is possible to use the other tools to manage this
> database. I've tried the following:
> 1. In Enterprise Manager, I've tried just putting the ip address as
> the server, and "Use SQL Server authentication" from the user ID and
> Password above, but I get the following error:
> "SQL Server registration failed because of the connection failure
> below... Cannot open user default database. Login failed"
>
User XXX has a login on the remote server, but does not have a user in the
database he is configured to use. To administer the remote database, User
XXX must be a member of the sysadmin role on the remote server
http://snodland.blogspot.com
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.788 / Virus Database: 533 - Release Date: 01/11/2004|||On Sat, 6 Nov 2004 22:04:54 -0000, "Bob Simms"
<bob_simms@.somewhere.com> wrote:
>> 1. In Enterprise Manager, I've tried just putting the ip address as
>> the server, and "Use SQL Server authentication" from the user ID and
>> Password above, but I get the following error:
>> "SQL Server registration failed because of the connection failure
>> below... Cannot open user default database. Login failed"
>User XXX has a login on the remote server, but does not have a user in the
>database he is configured to use. To administer the remote database, User
>XXX must be a member of the sysadmin role on the remote server
Thanks for the reply.
Is it possible to use Query Analyzer or Access to connect to the
server given the information in my original post? I don't need
administrator-like functionality. As I mentioned, in Dreamweaver, I'm
able to create a connection, and view the tables and data (not to be
confused with creating the connection on the ASP pages, but in
Dreamweaver itself.) Dreamweaver lets you browse the tables, and data,
it doesn't let you run SQL Statements, which is why I'd like to use
other tools I have.
TIA.|||On Sat, 06 Nov 2004 20:21:58 -0500, Bryce Fischer
<spamtrap@.berzerker-soft.com> wrote:
>On Sat, 6 Nov 2004 22:04:54 -0000, "Bob Simms"
><bob_simms@.somewhere.com> wrote:
>> 1. In Enterprise Manager, I've tried just putting the ip address as
>> the server, and "Use SQL Server authentication" from the user ID and
>> Password above, but I get the following error:
>> "SQL Server registration failed because of the connection failure
>> below... Cannot open user default database. Login failed"
>>User XXX has a login on the remote server, but does not have a user in the
>>database he is configured to use. To administer the remote database, User
>>XXX must be a member of the sysadmin role on the remote server
>Thanks for the reply.
>Is it possible to use Query Analyzer or Access to connect to the
>server given the information in my original post? I don't need
>administrator-like functionality. As I mentioned, in Dreamweaver, I'm
>able to create a connection, and view the tables and data (not to be
>confused with creating the connection on the ASP pages, but in
>Dreamweaver itself.) Dreamweaver lets you browse the tables, and data,
>it doesn't let you run SQL Statements, which is why I'd like to use
>other tools I have.
Well... After some persistence, I figured it out. In Access, and
Visual Studio, I was able to bring up the Data Link Properties dialog,
and enter the information, and the one step I was not doing, was
entering in the catalog in the "Select the database on the server:"
field.
I was able to accomplish the same thing in Visual Studio, Server
Explorer, Data Connections.

Connecting to Named Instance

Hi,

How can i connect to Named Instance of MSDE on remote server from Enterprice Manager in my local computer ?

Instance name is Helm

I can connect inside server like

osql -S -E .\Helm

But how i access from remote machine using Enterprice Manager ?

Regards,

Yujin Bobymachinename\Helm

Connecting to MSDE named instance

If we install MSDE 2000 SP3a with out a named instance we can connect to
through OSQL from a different computer on the network.
We used SVRNETCN.EXE to add TCP/IP to the protocol list.
We changed the port from 1059 or something like that to 1433.
We changed "LoginMode" to 2, but we also tried it with 0
But when we try to connect via OSQL
osql -S ROBXP\RR -U sa -P 11111
we get the following error.
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
the same OSQL command works OK from the local computer.
If we re-install with out a named instance we can connect fine with OSQL
Any ideas?
-Rob
PS. it was installed with the following:
setup SAPWD=11111 DISABLENETWORKPROTOCOLS=0 SECURITYMODE=SQL INSTANCENAME=RR
Check your MDAC version on the client you're trying to connect from. Upgrade
to the latest version and try it again.
MeanOldDBA
derrickleggett@.hotmail.com
http://weblogs.sqlteam.com/derrickl
When life gives you a lemon, fire the DBA.
"rob" wrote:

> If we install MSDE 2000 SP3a with out a named instance we can connect to
> through OSQL from a different computer on the network.
> We used SVRNETCN.EXE to add TCP/IP to the protocol list.
> We changed the port from 1059 or something like that to 1433.
> We changed "LoginMode" to 2, but we also tried it with 0
> But when we try to connect via OSQL
> osql -S ROBXP\RR -U sa -P 11111
> we get the following error.
>
> [DBNETLIB]SQL Server does not exist or access denied.
> [DBNETLIB]ConnectionOpen (Connect()).
> the same OSQL command works OK from the local computer.
>
> If we re-install with out a named instance we can connect fine with OSQL
> Any ideas?
> -Rob
> PS. it was installed with the following:
> setup SAPWD=11111 DISABLENETWORKPROTOCOLS=0 SECURITYMODE=SQL INSTANCENAME=RR
>
>
|||I ran Componet Checker 2.0 and it indidcates I have MDAC 2.8 SP1 which looks
to be the latest version.
"MeanOldDBA" <MeanOldDBA@.discussions.microsoft.com> wrote in message
news:86C87062-5A4C-4962-8FB3-99BA9CA2F375@.microsoft.com...
> Check your MDAC version on the client you're trying to connect from.
> Upgrade
> to the latest version and try it again.
|||hi,
rob wrote:

> We used SVRNETCN.EXE to add TCP/IP to the protocol list.
> We changed the port from 1059 or something like that to 1433.
usually 1433 is for default instances, where other port numbers indicates
named instances...
specifying a fixed port and not using the dynamic assigned port (wiche
requires on the server the UDP 1434 port to be available out of eventual
firewall) you have to specify an alias via Client Network Utility
(cliconfg.exe) on each remote client...
Andrea Montanari
http://www.asql.biz/DbaMgr.shtm
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||THANKS it works.
For anyone else reading this thread in the future.
You give it an alias name (RR for example) and and the servername is the
servername\instance
you can test the connection by using the alias name:
osql -S RR -U sa -Pxxxxx
thanks again.
.....
I have done some more testing. The only thing I am concerned about is:
After my program and MSDE is installed on someones computer, if they want to
access it from a different computer they will need to know how to create
exceptions in the WindowsXP firewall.
They will need to open up UPD 1434 and TCP port XXXX where XXXX is whatever
random port is used during installation of MSDE. I can find that port in
the registry and tell them at install time. But my users are not always
very proficient at using computers, and could have a hard time opening up
ports in the firewall.
If anyone has any suggestions about making this easier I would love to hear
about it.
-Rob
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3qfs6cFe280bU1@.individual.net...
> hi,
> rob wrote:
>
> usually 1433 is for default instances, where other port numbers indicates
> named instances...
> specifying a fixed port and not using the dynamic assigned port (wiche
> requires on the server the UDP 1434 port to be available out of eventual
> firewall) you have to specify an alias via Client Network Utility
> (cliconfg.exe) on each remote client...
> --
> Andrea Montanari
> http://www.asql.biz/DbaMgr.shtm
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Rob,
rob wrote:
> ....
> I have done some more testing. The only thing I am concerned about
> is: After my program and MSDE is installed on someones computer, if
> they want to access it from a different computer they will need to
> know how to create exceptions in the WindowsXP firewall.
> They will need to open up UPD 1434 and TCP port XXXX where XXXX is
> whatever random port is used during installation of MSDE. I can find
> that port in the registry and tell them at install time. But my
> users are not always very proficient at using computers, and could
> have a hard time opening up ports in the firewall.
> If anyone has any suggestions about making this easier I would love
> to hear about it.
>
actually you can provide the script available at
http://support.microsoft.com/kb/839980/en-us to provide an "automatic open
ports" :D
try having a look at it if can helps..
Andrea Montanari
http://www.asql.biz/DbaMgr.shtm
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Wow, that will make it easier. I was dreading having to give instructions to
open the firewall. ; )
I don't want to bother you, but I have one more question.
Your advice did work, and I can connect to the newly installed instance, -
IF I set up an alias.
BUT,
I have one computer that I installed with an instance that I do NOT have to
set up an alias for to connect remotely. I can not see what is different
for this computer. I even printed out the MSSQL registry settings for the
two computers and could not see a difference (besides uptime, etc.)
Even though your suggestion works, it would be much easier if I did not have
to set up an alias on the clients. Do you have any ideas what I did
differently with the one that works with out an alias?
Thanks,
Rob
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3qhp0hFem400U1@.individual.net...
> hi Rob,
> actually you can provide the script available at
> http://support.microsoft.com/kb/839980/en-us to provide an "automatic open
> ports" :D
> try having a look at it if can helps..
> --
> Andrea Montanari
> http://www.asql.biz/DbaMgr.shtm
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||I downloaded your program DBMgr2 and was able to connect to my DB without
using an alias. The difference was (from your help file) to use servername =
ROBXP\RR,1433
explicitly name the port number. This works via osql also.
The difference remains that I have one computer that I do not need to know
what the port number is, or set up an alias.
"rob" <ryost@..no.spam.rentright.com> wrote in message
news:OqGjGPbyFHA.2924@.TK2MSFTNGP15.phx.gbl...
> Wow, that will make it easier. I was dreading having to give instructions
> to open the firewall. ; )
> I don't want to bother you, but I have one more question.
> Your advice did work, and I can connect to the newly installed instance, -
> IF I set up an alias.
> BUT,
> I have one computer that I installed with an instance that I do NOT have
> to set up an alias for to connect remotely. I can not see what is
> different for this computer. I even printed out the MSSQL registry
> settings for the two computers and could not see a difference (besides
> uptime, etc.)
> Even though your suggestion works, it would be much easier if I did not
> have to set up an alias on the clients. Do you have any ideas what I did
> differently with the one that works with out an alias?
> Thanks,
> Rob
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
> news:3qhp0hFem400U1@.individual.net...
>
|||hi Rob,
rob wrote:
> I downloaded your program DBMgr2 and was able to connect to my DB
> without using an alias. The difference was (from your help file) to
> use servername = ROBXP\RR,1433
> explicitly name the port number. This works via osql also.
> The difference remains that I have one computer that I do not need to
> know what the port number is, or set up an alias.
probably it's not a named instance but a default one, that's to say ROBXP
and not ROBXP\RR..
default instances automatically listen on TCP 1433 as this port is the one
Microsoft reserved on IANA for SQL Server...
try having a look at it..
Andrea Montanari
http://www.asql.biz/DbaMgr.shtm
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I am pretty sure it is a named instance. I connected to it through your
Dbamgr2k by specifing
MICHELLEP\MICHELLE
I did not have to give it port 1433 (which is its port)
I did set this server up several months ago, and do not remember exactly how
I did it.
Also, when I go to add remove programs it is listed as:
Microsoft SQL Server Desktop Engine (MICHELLE)
and I think the instance name is listed in the paren's
From SQLPing:
C:\>sqlping 192.168.0.88
SQL-Pinging 192.168.0.88
Listening...
ServerName:MICHELLEP
InstanceName:MICHELLE
IsClustered:No
Version:8.00.194
tcp:1433
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3qieavFf286oU1@.individual.net...
> probably it's not a named instance but a default one, that's to say ROBXP
> and not ROBXP\RR..
> default instances automatically listen on TCP 1433 as this port is the one
> Microsoft reserved on IANA for SQL Server...
> try having a look at it..
> --
> Andrea Montanari
> http://www.asql.biz/DbaMgr.shtm
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>

Connecting to Local Database after Application Install

I have created an application which uses a SQL Express database. The program runs fine on the the computer where I built the app, however when I install the app on another computer I get an error telling me that under default SQL Express does not allow remote connections. The problem is that I dont want a remote connection I want a local connection, the database file is on the commputer. How can do get my application to look for the database on the local machine.

My connection string is:

Data Source=(local)\SQLEXPRESS;Initial Catalog="C:\DOCUMENTS AND SETTINGS\ADMINISTRATOR\PLDAQ.MDF";Integrated Security=True

I have made sure that the file is in the correct directory.

Any help would be greatly appretiated

hi,

the folder you are referencing is not a "standard" one in the "traditional" sense of SQL Server, and you can get problems if the account running the instance is not able to access that path... and anyway you should reference the intital catalog in the connection string via the "logical" name and not the physical primary data file name, thus
Data Source=(local)\SQLEXPRESS;Initial Catalog=dbLogicalFileName;Integrated Security=True
or use the AttachDBFilename feature of the User Instances mode..

try modifying the connection string to see if you are granted connection to the instance you are dealing with, as the exception you are reporting is quite a generic connection exception..

regards

|||

Andrea

I still have the same problem, I have updated my connection string to this:

Data Source = .\SQLEXPRESS;AttachDBFilename = [DataDirectory]\PLDaq.mdf;Integrated Security = True; UserInstance = False

I have managed to get arround the error by changeing the name of the non-design computer to mach the name of the design computer, this however, as I am sure you will agree, is only temporary as I don't want to have to change the name of every computer that I install this application on, what do I need to do to rectify this situation.

|||

hi,

as you are not using "User Instances", I'd not go for the AttachDBFileName property of the connection string.. I'd attach/create the database once and then I'd go for the "traditional" Database=yourDbName property of the connection string...

I have managed to get arround the error by changeing the name of the non-design computer to mach the name of the design computer

do you mean by that you "named" the destination computer the same as your dev pc? this is obviously not "mandatory"...

what is your |DataDirectory| value?

regards

|||

do you mean by that you "named" the destination computer the same as your dev pc? this is obviously not "mandatory"...

Unfortunatly this is the only way it will not generate the error posted above. Like I said the program is looking for a remote connection but I want a local one. So I tricked it into thinking that it was running on the dev computer by changeing the name. I will agree that this is obviously not convient, but that is why I am posting I just cant figure out how to fix it.

The |DataDirectory| tells the connection to look in the bin\debug folder during dev time, and also to look into the bin\data folder at run time, after installation obviously. So when the program is installed and all data files are stored in the (AppPath)\bin\data directory and that is where the program is supposed to look for the data files (e.g. Database and Log files), however, if the non dev computer has a different name it trys to find the dev computer to connect to the database, a remote connection, It cant do this as it is not connected to any network.

I have tryed the traditional Database = yourDbName and that causes the same problem

Also There may come a time when I want to use User Instances, but for the time being I just want the thing to work.

|||

PEng1 wrote:

Unfortunatly this is the only way it will not generate the error posted above. Like I said the program is looking for a remote connection but I want a local one. So I tricked it into thinking that it was running on the dev computer by changeing the name. I will agree that this is obviously not convient, but that is why I am posting I just cant figure out how to fix it.

the fix is using

Data Source = .\SQLEXPRESS or Data Source = (Local)\SQLEXPRESS property in the connection string...

here you have to specify the instance you have to connect to, and you can provide "." and/or "(Local)" for "local" connections"...

The |DataDirectory| tells the connection to look in the bin\debug folder during dev time, and also to look into the bin\data folder at run time, after installation obviously. So when the program is installed and all data files are stored in the (AppPath)\bin\data directory and that is where the program is supposed to look for the data files (e.g. Database and Log files), however, if the non dev computer has a different name it trys to find the dev computer to connect to the database, a remote connection, It cant do this as it is not connected to any network.

pay attention to your "custom data folder"... consider that the account running the SQLExpress intstance required adeguate NTFS permissions to that folder.. and consider Vista "headaches"/requirements with regard writing in Program Files folder...

regards

|||

Andrea,

I guess that I had the answer for a while and just didn't bother to check if it would work with a different name, or I changed something and just don't remeber what, probably the latter of the two, either way, the problem is resolved and I am greatly indebted for all of your help. Thanks a lot.

This program will be run on Windows 2000 for quite a while but it will eventually have to be moved to Vista or higher, what "headaches" are you refering to, I am not at all familiar with Vista since the company I work for still has some machines that are running 95 and One that is running DOS, yeah thats right I said DOS. I guess however that I should probably read up on the New OS any recomended reading?

|||

hi,

PEng1 wrote:

Andrea,

I guess that I had the answer for a while and just didn't bother to check if it would work with a different name, or I changed something and just don't remeber what, probably the latter of the two, either way, the problem is resolved and I am greatly indebted for all of your help. Thanks a lot.

This program will be run on Windows 2000 for quite a while but it will eventually have to be moved to Vista or higher, what "headaches" are you refering to, I am not at all familiar with Vista since the company I work for still has some machines that are running 95 and One that is running DOS, yeah thats right I said DOS. I guess however that I should probably read up on the New OS any recomended reading?

start reading at http://technet.microsoft.com/en-us/windowsvista/aa905108.aspx, http://technet.microsoft.com/en-us/windowsvista/aa906021.aspx, ....

and look in this forum for Vista troubles with UAC..

regards

Connecting to Local Database after Application Install

I have created an application which uses a SQL Express database. The program runs fine on the the computer where I built the app, however when I install the app on another computer I get an error telling me that under default SQL Express does not allow remote connections. The problem is that I dont want a remote connection I want a local connection, the database file is on the commputer. How can do get my application to look for the database on the local machine.

My connection string is:

Data Source=(local)\SQLEXPRESS;Initial Catalog="C:\DOCUMENTS AND SETTINGS\ADMINISTRATOR\PLDAQ.MDF";Integrated Security=True

I have made sure that the file is in the correct directory.

Any help would be greatly appretiated

hi,

the folder you are referencing is not a "standard" one in the "traditional" sense of SQL Server, and you can get problems if the account running the instance is not able to access that path... and anyway you should reference the intital catalog in the connection string via the "logical" name and not the physical primary data file name, thus
Data Source=(local)\SQLEXPRESS;Initial Catalog=dbLogicalFileName;Integrated Security=True
or use the AttachDBFilename feature of the User Instances mode..

try modifying the connection string to see if you are granted connection to the instance you are dealing with, as the exception you are reporting is quite a generic connection exception..

regards

|||

Andrea

I still have the same problem, I have updated my connection string to this:

Data Source = .\SQLEXPRESS;AttachDBFilename = [DataDirectory]\PLDaq.mdf;Integrated Security = True; UserInstance = False

I have managed to get arround the error by changeing the name of the non-design computer to mach the name of the design computer, this however, as I am sure you will agree, is only temporary as I don't want to have to change the name of every computer that I install this application on, what do I need to do to rectify this situation.

|||

hi,

as you are not using "User Instances", I'd not go for the AttachDBFileName property of the connection string.. I'd attach/create the database once and then I'd go for the "traditional" Database=yourDbName property of the connection string...

I have managed to get arround the error by changeing the name of the non-design computer to mach the name of the design computer

do you mean by that you "named" the destination computer the same as your dev pc? this is obviously not "mandatory"...

what is your |DataDirectory| value?

regards

|||

do you mean by that you "named" the destination computer the same as your dev pc? this is obviously not "mandatory"...

Unfortunatly this is the only way it will not generate the error posted above. Like I said the program is looking for a remote connection but I want a local one. So I tricked it into thinking that it was running on the dev computer by changeing the name. I will agree that this is obviously not convient, but that is why I am posting I just cant figure out how to fix it.

The |DataDirectory| tells the connection to look in the bin\debug folder during dev time, and also to look into the bin\data folder at run time, after installation obviously. So when the program is installed and all data files are stored in the (AppPath)\bin\data directory and that is where the program is supposed to look for the data files (e.g. Database and Log files), however, if the non dev computer has a different name it trys to find the dev computer to connect to the database, a remote connection, It cant do this as it is not connected to any network.

I have tryed the traditional Database = yourDbName and that causes the same problem

Also There may come a time when I want to use User Instances, but for the time being I just want the thing to work.

|||

PEng1 wrote:

Unfortunatly this is the only way it will not generate the error posted above. Like I said the program is looking for a remote connection but I want a local one. So I tricked it into thinking that it was running on the dev computer by changeing the name. I will agree that this is obviously not convient, but that is why I am posting I just cant figure out how to fix it.

the fix is using

Data Source = .\SQLEXPRESS or Data Source = (Local)\SQLEXPRESS property in the connection string...

here you have to specify the instance you have to connect to, and you can provide "." and/or "(Local)" for "local" connections"...

The |DataDirectory| tells the connection to look in the bin\debug folder during dev time, and also to look into the bin\data folder at run time, after installation obviously. So when the program is installed and all data files are stored in the (AppPath)\bin\data directory and that is where the program is supposed to look for the data files (e.g. Database and Log files), however, if the non dev computer has a different name it trys to find the dev computer to connect to the database, a remote connection, It cant do this as it is not connected to any network.

pay attention to your "custom data folder"... consider that the account running the SQLExpress intstance required adeguate NTFS permissions to that folder.. and consider Vista "headaches"/requirements with regard writing in Program Files folder...

regards

|||

Andrea,

I guess that I had the answer for a while and just didn't bother to check if it would work with a different name, or I changed something and just don't remeber what, probably the latter of the two, either way, the problem is resolved and I am greatly indebted for all of your help. Thanks a lot.

This program will be run on Windows 2000 for quite a while but it will eventually have to be moved to Vista or higher, what "headaches" are you refering to, I am not at all familiar with Vista since the company I work for still has some machines that are running 95 and One that is running DOS, yeah thats right I said DOS. I guess however that I should probably read up on the New OS any recomended reading?

|||

hi,

PEng1 wrote:

Andrea,

I guess that I had the answer for a while and just didn't bother to check if it would work with a different name, or I changed something and just don't remeber what, probably the latter of the two, either way, the problem is resolved and I am greatly indebted for all of your help. Thanks a lot.

This program will be run on Windows 2000 for quite a while but it will eventually have to be moved to Vista or higher, what "headaches" are you refering to, I am not at all familiar with Vista since the company I work for still has some machines that are running 95 and One that is running DOS, yeah thats right I said DOS. I guess however that I should probably read up on the New OS any recomended reading?

start reading at http://technet.microsoft.com/en-us/windowsvista/aa905108.aspx, http://technet.microsoft.com/en-us/windowsvista/aa906021.aspx, ....

and look in this forum for Vista troubles with UAC..

regards

Connecting to Local Database after Application Install

I have created an application which uses a SQL Express database. The program runs fine on the the computer where I built the app, however when I install the app on another computer I get an error telling me that under default SQL Express does not allow remote connections. The problem is that I dont want a remote connection I want a local connection, the database file is on the commputer. How can do get my application to look for the database on the local machine.

My connection string is:

Data Source=(local)\SQLEXPRESS;Initial Catalog="C:\DOCUMENTS AND SETTINGS\ADMINISTRATOR\PLDAQ.MDF";Integrated Security=True

I have made sure that the file is in the correct directory.

Any help would be greatly appretiated

hi,

the folder you are referencing is not a "standard" one in the "traditional" sense of SQL Server, and you can get problems if the account running the instance is not able to access that path... and anyway you should reference the intital catalog in the connection string via the "logical" name and not the physical primary data file name, thus
Data Source=(local)\SQLEXPRESS;Initial Catalog=dbLogicalFileName;Integrated Security=True
or use the AttachDBFilename feature of the User Instances mode..

try modifying the connection string to see if you are granted connection to the instance you are dealing with, as the exception you are reporting is quite a generic connection exception..

regards

|||

Andrea

I still have the same problem, I have updated my connection string to this:

Data Source = .\SQLEXPRESS;AttachDBFilename = [DataDirectory]\PLDaq.mdf;Integrated Security = True; UserInstance = False

I have managed to get arround the error by changeing the name of the non-design computer to mach the name of the design computer, this however, as I am sure you will agree, is only temporary as I don't want to have to change the name of every computer that I install this application on, what do I need to do to rectify this situation.

|||

hi,

as you are not using "User Instances", I'd not go for the AttachDBFileName property of the connection string.. I'd attach/create the database once and then I'd go for the "traditional" Database=yourDbName property of the connection string...

I have managed to get arround the error by changeing the name of the non-design computer to mach the name of the design computer

do you mean by that you "named" the destination computer the same as your dev pc? this is obviously not "mandatory"...

what is your |DataDirectory| value?

regards

|||

do you mean by that you "named" the destination computer the same as your dev pc? this is obviously not "mandatory"...

Unfortunatly this is the only way it will not generate the error posted above. Like I said the program is looking for a remote connection but I want a local one. So I tricked it into thinking that it was running on the dev computer by changeing the name. I will agree that this is obviously not convient, but that is why I am posting I just cant figure out how to fix it.

The |DataDirectory| tells the connection to look in the bin\debug folder during dev time, and also to look into the bin\data folder at run time, after installation obviously. So when the program is installed and all data files are stored in the (AppPath)\bin\data directory and that is where the program is supposed to look for the data files (e.g. Database and Log files), however, if the non dev computer has a different name it trys to find the dev computer to connect to the database, a remote connection, It cant do this as it is not connected to any network.

I have tryed the traditional Database = yourDbName and that causes the same problem

Also There may come a time when I want to use User Instances, but for the time being I just want the thing to work.

|||

PEng1 wrote:

Unfortunatly this is the only way it will not generate the error posted above. Like I said the program is looking for a remote connection but I want a local one. So I tricked it into thinking that it was running on the dev computer by changeing the name. I will agree that this is obviously not convient, but that is why I am posting I just cant figure out how to fix it.

the fix is using

Data Source = .\SQLEXPRESS or Data Source = (Local)\SQLEXPRESS property in the connection string...

here you have to specify the instance you have to connect to, and you can provide "." and/or "(Local)" for "local" connections"...

The |DataDirectory| tells the connection to look in the bin\debug folder during dev time, and also to look into the bin\data folder at run time, after installation obviously. So when the program is installed and all data files are stored in the (AppPath)\bin\data directory and that is where the program is supposed to look for the data files (e.g. Database and Log files), however, if the non dev computer has a different name it trys to find the dev computer to connect to the database, a remote connection, It cant do this as it is not connected to any network.

pay attention to your "custom data folder"... consider that the account running the SQLExpress intstance required adeguate NTFS permissions to that folder.. and consider Vista "headaches"/requirements with regard writing in Program Files folder...

regards

|||

Andrea,

I guess that I had the answer for a while and just didn't bother to check if it would work with a different name, or I changed something and just don't remeber what, probably the latter of the two, either way, the problem is resolved and I am greatly indebted for all of your help. Thanks a lot.

This program will be run on Windows 2000 for quite a while but it will eventually have to be moved to Vista or higher, what "headaches" are you refering to, I am not at all familiar with Vista since the company I work for still has some machines that are running 95 and One that is running DOS, yeah thats right I said DOS. I guess however that I should probably read up on the New OS any recomended reading?

|||

hi,

PEng1 wrote:

Andrea,

I guess that I had the answer for a while and just didn't bother to check if it would work with a different name, or I changed something and just don't remeber what, probably the latter of the two, either way, the problem is resolved and I am greatly indebted for all of your help. Thanks a lot.

This program will be run on Windows 2000 for quite a while but it will eventually have to be moved to Vista or higher, what "headaches" are you refering to, I am not at all familiar with Vista since the company I work for still has some machines that are running 95 and One that is running DOS, yeah thats right I said DOS. I guess however that I should probably read up on the New OS any recomended reading?

start reading at http://technet.microsoft.com/en-us/windowsvista/aa905108.aspx, http://technet.microsoft.com/en-us/windowsvista/aa906021.aspx, ....

and look in this forum for Vista troubles with UAC..

regards

Connecting to DB with Static IP over the internet

Hello Did anyone ever get the SQL2000 server or MSDE to work on an XP Pro
computer, with a static IP address? If so how is this done? Iâ've done the
following:
1) setup router to forward to a port 5000
2) I setup MS SQL server to listen to this port, I check error logs, and it
is listening, I do netstat â'a and it does list that it is being listened to.
3) I make sure the DMZ is clear for the computer that is being forward the
stuff from the internet.
4) I can use the Remote Desktop Connection to connect to that static IP
computer and it works just fine, â?¦
5) When I try to connect to the computer through a connection string I get
the oh so informative â'Invalid connection string attributeâ' even though I use
the same thing with another static ip, on a win2000 server, and it works the
connection string looks like this:
User ID=DAN;Password=DAN;Protocol=TCP/IP;Server=60.44.118.127;Port No=5000;
6) I did setup the server network utility with the port,
I am not sure what I missed, I know on the Server2000 operating system I
did go into the remote access routing utility, but I canâ't find that on
Windows XP Pro,
Can anyone help me out?Hi
Try including the port at the end of the IP address as shown in
http://www.connectionstrings.com/
John
"ARTMIC" wrote:
> Hello Did anyone ever get the SQL2000 server or MSDE to work on an XP Pro
> computer, with a static IP address? If so how is this done? Iâ've done the
> following:
> 1) setup router to forward to a port 5000
> 2) I setup MS SQL server to listen to this port, I check error logs, and it
> is listening, I do netstat â'a and it does list that it is being listened to.
> 3) I make sure the DMZ is clear for the computer that is being forward the
> stuff from the internet.
> 4) I can use the Remote Desktop Connection to connect to that static IP
> computer and it works just fine, â?¦
> 5) When I try to connect to the computer through a connection string I get
> the oh so informative â'Invalid connection string attributeâ' even though I use
> the same thing with another static ip, on a win2000 server, and it works the
> connection string looks like this:
> User ID=DAN;Password=DAN;Protocol=TCP/IP;Server=60.44.118.127;Port No=5000;
> 6) I did setup the server network utility with the port,
> I am not sure what I missed, I know on the Server2000 operating system I
> did go into the remote access routing utility, but I canâ't find that on
> Windows XP Pro,
> Can anyone help me out?
>|||Hi,
Have you checked WintowsXP firewall. If it turned on, you need to configure
the exception for this port.
Yuriy
"ARTMIC" wrote:
> Hello Did anyone ever get the SQL2000 server or MSDE to work on an XP Pro
> computer, with a static IP address? If so how is this done? Iâ've done the
> following:
> 1) setup router to forward to a port 5000
> 2) I setup MS SQL server to listen to this port, I check error logs, and it
> is listening, I do netstat â'a and it does list that it is being listened to.
> 3) I make sure the DMZ is clear for the computer that is being forward the
> stuff from the internet.
> 4) I can use the Remote Desktop Connection to connect to that static IP
> computer and it works just fine, â?¦
> 5) When I try to connect to the computer through a connection string I get
> the oh so informative â'Invalid connection string attributeâ' even though I use
> the same thing with another static ip, on a win2000 server, and it works the
> connection string looks like this:
> User ID=DAN;Password=DAN;Protocol=TCP/IP;Server=60.44.118.127;Port No=5000;
> 6) I did setup the server network utility with the port,
> I am not sure what I missed, I know on the Server2000 operating system I
> did go into the remote access routing utility, but I canâ't find that on
> Windows XP Pro,
> Can anyone help me out?
>|||Hi
Just to check that you have seen http://support.microsoft.com/kb/287932?
John
"John Bell" wrote:
> Hi
> Try including the port at the end of the IP address as shown in
> http://www.connectionstrings.com/
> John
> "ARTMIC" wrote:
> > Hello Did anyone ever get the SQL2000 server or MSDE to work on an XP Pro
> > computer, with a static IP address? If so how is this done? Iâ've done the
> > following:
> >
> > 1) setup router to forward to a port 5000
> > 2) I setup MS SQL server to listen to this port, I check error logs, and it
> > is listening, I do netstat â'a and it does list that it is being listened to.
> > 3) I make sure the DMZ is clear for the computer that is being forward the
> > stuff from the internet.
> > 4) I can use the Remote Desktop Connection to connect to that static IP
> > computer and it works just fine, â?¦
> > 5) When I try to connect to the computer through a connection string I get
> > the oh so informative â'Invalid connection string attributeâ' even though I use
> > the same thing with another static ip, on a win2000 server, and it works the
> > connection string looks like this:
> > User ID=DAN;Password=DAN;Protocol=TCP/IP;Server=60.44.118.127;Port No=5000;
> > 6) I did setup the server network utility with the port,
> >
> > I am not sure what I missed, I know on the Server2000 operating system I
> > did go into the remote access routing utility, but I canâ't find that on
> > Windows XP Pro,
> >
> > Can anyone help me out?
> >|||Thanks, i will try that, but i am pretty sure i tried all imaginable
connection strings, what gets to me is that it should work, i know the sql
server is listening to port 5000 ... i can remotely connect to that computer
over that static ip from my other computer with the Remote Desktop
Connection, so it looks ok, but why am i still having all these problems?
The funny thing is if i use the internal ip address of that computer that
connects to the router, then i can use the same connection string, (just
changing ip address) and the sql server responds, so internally it knows
about port 5000, as soon as i use the static ip, it complains about "Invalid
connection string attribute"
"John Bell" wrote:
> Hi
> Try including the port at the end of the IP address as shown in
> http://www.connectionstrings.com/
> John
> "ARTMIC" wrote:
> > Hello Did anyone ever get the SQL2000 server or MSDE to work on an XP Pro
> > computer, with a static IP address? If so how is this done? Iâ've done the
> > following:
> >
> > 1) setup router to forward to a port 5000
> > 2) I setup MS SQL server to listen to this port, I check error logs, and it
> > is listening, I do netstat â'a and it does list that it is being listened to.
> > 3) I make sure the DMZ is clear for the computer that is being forward the
> > stuff from the internet.
> > 4) I can use the Remote Desktop Connection to connect to that static IP
> > computer and it works just fine, â?¦
> > 5) When I try to connect to the computer through a connection string I get
> > the oh so informative â'Invalid connection string attributeâ' even though I use
> > the same thing with another static ip, on a win2000 server, and it works the
> > connection string looks like this:
> > User ID=DAN;Password=DAN;Protocol=TCP/IP;Server=60.44.118.127;Port No=5000;
> > 6) I did setup the server network utility with the port,
> >
> > I am not sure what I missed, I know on the Server2000 operating system I
> > did go into the remote access routing utility, but I canâ't find that on
> > Windows XP Pro,
> >
> > Can anyone help me out?
> >|||Thanks, i will read through that, maybe i missed something.
i'm so frustrated by this, i did this before with win2000 server a while
back and it worked ok, but with the Win XP Pro, it is sooooooooooooo hard to
do
"John Bell" wrote:
> Hi
> Just to check that you have seen http://support.microsoft.com/kb/287932?
> John
> "John Bell" wrote:
> > Hi
> >
> > Try including the port at the end of the IP address as shown in
> > http://www.connectionstrings.com/
> >
> > John
> >
> > "ARTMIC" wrote:
> >
> > > Hello Did anyone ever get the SQL2000 server or MSDE to work on an XP Pro
> > > computer, with a static IP address? If so how is this done? Iâ've done the
> > > following:
> > >
> > > 1) setup router to forward to a port 5000
> > > 2) I setup MS SQL server to listen to this port, I check error logs, and it
> > > is listening, I do netstat â'a and it does list that it is being listened to.
> > > 3) I make sure the DMZ is clear for the computer that is being forward the
> > > stuff from the internet.
> > > 4) I can use the Remote Desktop Connection to connect to that static IP
> > > computer and it works just fine, â?¦
> > > 5) When I try to connect to the computer through a connection string I get
> > > the oh so informative â'Invalid connection string attributeâ' even though I use
> > > the same thing with another static ip, on a win2000 server, and it works the
> > > connection string looks like this:
> > > User ID=DAN;Password=DAN;Protocol=TCP/IP;Server=60.44.118.127;Port No=5000;
> > > 6) I did setup the server network utility with the port,
> > >
> > > I am not sure what I missed, I know on the Server2000 operating system I
> > > did go into the remote access routing utility, but I canâ't find that on
> > > Windows XP Pro,
> > >
> > > Can anyone help me out?
> > >|||i Installed Win XP Pro on a test machine, and did not apply any updates to
that computer, as for the firewall, it is disabled when i'm in the netwrok
properties,
The only difference that i can recall from Windows server 2000 is that in
that operating system i modified the remote accesss routing settings. i can't
find that utility on Win XP Pro
Arghhhhh help
"Yuriy Al" wrote:
> Hi,
> Have you checked WintowsXP firewall. If it turned on, you need to configure
> the exception for this port.
> Yuriy
>
> "ARTMIC" wrote:
> > Hello Did anyone ever get the SQL2000 server or MSDE to work on an XP Pro
> > computer, with a static IP address? If so how is this done? Iâ've done the
> > following:
> >
> > 1) setup router to forward to a port 5000
> > 2) I setup MS SQL server to listen to this port, I check error logs, and it
> > is listening, I do netstat â'a and it does list that it is being listened to.
> > 3) I make sure the DMZ is clear for the computer that is being forward the
> > stuff from the internet.
> > 4) I can use the Remote Desktop Connection to connect to that static IP
> > computer and it works just fine, â?¦
> > 5) When I try to connect to the computer through a connection string I get
> > the oh so informative â'Invalid connection string attributeâ' even though I use
> > the same thing with another static ip, on a win2000 server, and it works the
> > connection string looks like this:
> > User ID=DAN;Password=DAN;Protocol=TCP/IP;Server=60.44.118.127;Port No=5000;
> > 6) I did setup the server network utility with the port,
> >
> > I am not sure what I missed, I know on the Server2000 operating system I
> > did go into the remote access routing utility, but I canâ't find that on
> > Windows XP Pro,
> >
> > Can anyone help me out?
> >|||Hi
Have you tried accessing this with osql or SQLPing?
http://www.sqlsecurity.com/Tools/FreeTools/tabid/65/Default.aspx
You may want to try telneting to the port.
John
"ARTMIC" wrote:
> Thanks, i will try that, but i am pretty sure i tried all imaginable
> connection strings, what gets to me is that it should work, i know the sql
> server is listening to port 5000 ... i can remotely connect to that computer
> over that static ip from my other computer with the Remote Desktop
> Connection, so it looks ok, but why am i still having all these problems?
> The funny thing is if i use the internal ip address of that computer that
> connects to the router, then i can use the same connection string, (just
> changing ip address) and the sql server responds, so internally it knows
> about port 5000, as soon as i use the static ip, it complains about "Invalid
> connection string attribute"
> "John Bell" wrote:
> > Hi
> >
> > Try including the port at the end of the IP address as shown in
> > http://www.connectionstrings.com/
> >
> > John
> >
> > "ARTMIC" wrote:
> >
> > > Hello Did anyone ever get the SQL2000 server or MSDE to work on an XP Pro
> > > computer, with a static IP address? If so how is this done? Iâ've done the
> > > following:
> > >
> > > 1) setup router to forward to a port 5000
> > > 2) I setup MS SQL server to listen to this port, I check error logs, and it
> > > is listening, I do netstat â'a and it does list that it is being listened to.
> > > 3) I make sure the DMZ is clear for the computer that is being forward the
> > > stuff from the internet.
> > > 4) I can use the Remote Desktop Connection to connect to that static IP
> > > computer and it works just fine, â?¦
> > > 5) When I try to connect to the computer through a connection string I get
> > > the oh so informative â'Invalid connection string attributeâ' even though I use
> > > the same thing with another static ip, on a win2000 server, and it works the
> > > connection string looks like this:
> > > User ID=DAN;Password=DAN;Protocol=TCP/IP;Server=60.44.118.127;Port No=5000;
> > > 6) I did setup the server network utility with the port,
> > >
> > > I am not sure what I missed, I know on the Server2000 operating system I
> > > did go into the remote access routing utility, but I canâ't find that on
> > > Windows XP Pro,
> > >
> > > Can anyone help me out?
> > >|||i figured it out, i was so into the sql part that i forgot to disable dhcp,
in other words the damn internal ip address changed on me every time i
rebooted and that is why i couldn't connect, i filled in the DSN, and
internal computer iP and made sure to forward port and dmz to it and it works
now,
the only thing i'm wondering is do i need DMZ enabled for that internal ip?
Thanks for the help though, those suggestions made me understand the SQL2000
software a lot more, and that sure is great, i love learning new things.
"John Bell" wrote:
> Hi
> Have you tried accessing this with osql or SQLPing?
> http://www.sqlsecurity.com/Tools/FreeTools/tabid/65/Default.aspx
> You may want to try telneting to the port.
> John
> "ARTMIC" wrote:
> > Thanks, i will try that, but i am pretty sure i tried all imaginable
> > connection strings, what gets to me is that it should work, i know the sql
> > server is listening to port 5000 ... i can remotely connect to that computer
> > over that static ip from my other computer with the Remote Desktop
> > Connection, so it looks ok, but why am i still having all these problems?
> > The funny thing is if i use the internal ip address of that computer that
> > connects to the router, then i can use the same connection string, (just
> > changing ip address) and the sql server responds, so internally it knows
> > about port 5000, as soon as i use the static ip, it complains about "Invalid
> > connection string attribute"
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > Try including the port at the end of the IP address as shown in
> > > http://www.connectionstrings.com/
> > >
> > > John
> > >
> > > "ARTMIC" wrote:
> > >
> > > > Hello Did anyone ever get the SQL2000 server or MSDE to work on an XP Pro
> > > > computer, with a static IP address? If so how is this done? Iâ've done the
> > > > following:
> > > >
> > > > 1) setup router to forward to a port 5000
> > > > 2) I setup MS SQL server to listen to this port, I check error logs, and it
> > > > is listening, I do netstat â'a and it does list that it is being listened to.
> > > > 3) I make sure the DMZ is clear for the computer that is being forward the
> > > > stuff from the internet.
> > > > 4) I can use the Remote Desktop Connection to connect to that static IP
> > > > computer and it works just fine, â?¦
> > > > 5) When I try to connect to the computer through a connection string I get
> > > > the oh so informative â'Invalid connection string attributeâ' even though I use
> > > > the same thing with another static ip, on a win2000 server, and it works the
> > > > connection string looks like this:
> > > > User ID=DAN;Password=DAN;Protocol=TCP/IP;Server=60.44.118.127;Port No=5000;
> > > > 6) I did setup the server network utility with the port,
> > > >
> > > > I am not sure what I missed, I know on the Server2000 operating system I
> > > > did go into the remote access routing utility, but I canâ't find that on
> > > > Windows XP Pro,
> > > >
> > > > Can anyone help me out?
> > > >|||Hi
To access the machine from the internal network without going out over the
internet your internal IP address will be needed. You should configure your
firewall/DMZ so that access to this IP address is only allowed internally.
HTH
John
"ARTMIC" wrote:
> i figured it out, i was so into the sql part that i forgot to disable dhcp,
> in other words the damn internal ip address changed on me every time i
> rebooted and that is why i couldn't connect, i filled in the DSN, and
> internal computer iP and made sure to forward port and dmz to it and it works
> now,
> the only thing i'm wondering is do i need DMZ enabled for that internal ip?
> Thanks for the help though, those suggestions made me understand the SQL2000
> software a lot more, and that sure is great, i love learning new things.
>
> "John Bell" wrote:
> > Hi
> >
> > Have you tried accessing this with osql or SQLPing?
> > http://www.sqlsecurity.com/Tools/FreeTools/tabid/65/Default.aspx
> >
> > You may want to try telneting to the port.
> >
> > John
> >
> > "ARTMIC" wrote:
> >
> > > Thanks, i will try that, but i am pretty sure i tried all imaginable
> > > connection strings, what gets to me is that it should work, i know the sql
> > > server is listening to port 5000 ... i can remotely connect to that computer
> > > over that static ip from my other computer with the Remote Desktop
> > > Connection, so it looks ok, but why am i still having all these problems?
> > > The funny thing is if i use the internal ip address of that computer that
> > > connects to the router, then i can use the same connection string, (just
> > > changing ip address) and the sql server responds, so internally it knows
> > > about port 5000, as soon as i use the static ip, it complains about "Invalid
> > > connection string attribute"
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi
> > > >
> > > > Try including the port at the end of the IP address as shown in
> > > > http://www.connectionstrings.com/
> > > >
> > > > John
> > > >
> > > > "ARTMIC" wrote:
> > > >
> > > > > Hello Did anyone ever get the SQL2000 server or MSDE to work on an XP Pro
> > > > > computer, with a static IP address? If so how is this done? Iâ've done the
> > > > > following:
> > > > >
> > > > > 1) setup router to forward to a port 5000
> > > > > 2) I setup MS SQL server to listen to this port, I check error logs, and it
> > > > > is listening, I do netstat â'a and it does list that it is being listened to.
> > > > > 3) I make sure the DMZ is clear for the computer that is being forward the
> > > > > stuff from the internet.
> > > > > 4) I can use the Remote Desktop Connection to connect to that static IP
> > > > > computer and it works just fine, â?¦
> > > > > 5) When I try to connect to the computer through a connection string I get
> > > > > the oh so informative â'Invalid connection string attributeâ' even though I use
> > > > > the same thing with another static ip, on a win2000 server, and it works the
> > > > > connection string looks like this:
> > > > > User ID=DAN;Password=DAN;Protocol=TCP/IP;Server=60.44.118.127;Port No=5000;
> > > > > 6) I did setup the server network utility with the port,
> > > > >
> > > > > I am not sure what I missed, I know on the Server2000 operating system I
> > > > > did go into the remote access routing utility, but I canâ't find that on
> > > > > Windows XP Pro,
> > > > >
> > > > > Can anyone help me out?
> > > > >

connecting to database

Hi everybody

I was trying to connect to datatbase on my computer, through java. I understand that I will need to download JDBC driver for that. But i am not sure which driver will I need, and where do i need to put it. Do I have to make some changes in CLASSPATH as well?

I am using SQL 2000. My jdk profile is j2sdk1.4.2.01. Also what is subname in

jdbc:<subprotocol>:<subname>

is it the name of database or what?

In need of help !!!!!!

thanks in advanceThe jdbc drive should be in the classpath and added to your project (depends on your environment).

I believe that the subname is the database (could be its ip), with subprotocol being the driver, for db2 its db2, not sure thought for sql 2000.

Are you creating a standalone java application and appled or jsp ?

connecting to data source issue

I'm having a problem connecting to an access database from
http://localhost/reports. I can connect from the computer I developed the
reports but when I goto another computer it gives me this error message
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'DataSource1'.
(rsErrorOpeningConnection)
I've created the same exact odbc connection in the systems tab as on the
computer I've created the project with. I've looked at there online help
but it didn't have any suggestions.
Is there anything else I need to do on the other computer in order for this
to work?
TIA,
JacksonHi Jackson
I am having the exact same problem. Did you find a solution? Should I find
one I will post it here.
Tina - MSFTE
"Jackson" wrote:
> I'm having a problem connecting to an access database from
> http://localhost/reports. I can connect from the computer I developed the
> reports but when I goto another computer it gives me this error message
> An error has occurred during report processing. (rsProcessingAborted)
> Cannot create a connection to data source 'DataSource1'.
> (rsErrorOpeningConnection)
> I've created the same exact odbc connection in the systems tab as on the
> computer I've created the project with. I've looked at there online help
> but it didn't have any suggestions.
> Is there anything else I need to do on the other computer in order for this
> to work?
>
> TIA,
> Jackson
>
>|||Jackson and Tina
I am having the same problem and have posted everywhere trying to find a
fix. This supposedly works. I have turned it over to the Network Mgr and he
is reviewing it. Hopefully, it will solve the problem. If it works, please
let me know or, if you find another solution I wuld really appreciate hearing
about it.
Roy
1. Kerberos is enabled
2. The servers are trusted for delegation
3. The SPN's are configured
"http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_security_2gmm.asp"
4. If you have several domain controllers wait for replication to complete.
If you don't wait you will pull your hair out because nothing you try will
works and all of sudden a few hours latter it starts working and you can't
figure out why.
5. Make sure all users have the option 'Enable Integrated Windows
Authentication' enabled in internet explorer, without it they will still get
the authentication error.
"Jackson" wrote:
> I'm having a problem connecting to an access database from
> http://localhost/reports. I can connect from the computer I developed the
> reports but when I goto another computer it gives me this error message
> An error has occurred during report processing. (rsProcessingAborted)
> Cannot create a connection to data source 'DataSource1'.
> (rsErrorOpeningConnection)
> I've created the same exact odbc connection in the systems tab as on the
> computer I've created the project with. I've looked at there online help
> but it didn't have any suggestions.
> Is there anything else I need to do on the other computer in order for this
> to work?
>
> TIA,
> Jackson
>
>|||It took a while but I finally got a work around.
I'm currently taking daily snapshots of the access reports. So now I don't
even need to create odbc connections on other user computers.
"Tina (MSFTE)" <Tina (MSFTE)@.discussions.microsoft.com> wrote in message
news:212D3E5F-C8D8-412F-9493-EBB9EACADA1A@.microsoft.com...
> Hi Jackson
> I am having the exact same problem. Did you find a solution? Should I find
> one I will post it here.
> Tina - MSFTE
> "Jackson" wrote:
>> I'm having a problem connecting to an access database from
>> http://localhost/reports. I can connect from the computer I developed
>> the
>> reports but when I goto another computer it gives me this error message
>> An error has occurred during report processing. (rsProcessingAborted)
>> Cannot create a connection to data source 'DataSource1'.
>> (rsErrorOpeningConnection)
>> I've created the same exact odbc connection in the systems tab as on the
>> computer I've created the project with. I've looked at there online help
>> but it didn't have any suggestions.
>> Is there anything else I need to do on the other computer in order for
>> this
>> to work?
>>
>> TIA,
>> Jackson
>>|||Roy,
Your post put me on the right track. The IIS server we deployed to is not in
a domain, neither was any of the users. I did not even think of looking for
this scenario, I assumed we were on the domain.
1) I requested a user to be created on the domain.
2) I gave this user Data reader rights on all the SQL and AS servers that
forms part of my solution
3) In RS I used the full username and password to be saved securely in RS
4) Selected "Use as WIS credentials to make the connection"
5) Selected "Impersonate user after connection created"
It works like a charm. Due to the client's unique network configuration -
servers on the network, but not in the domain - this is the only way the
solution will work.
"Roy" wrote:
> Jackson and Tina
> I am having the same problem and have posted everywhere trying to find a
> fix. This supposedly works. I have turned it over to the Network Mgr and he
> is reviewing it. Hopefully, it will solve the problem. If it works, please
> let me know or, if you find another solution I wuld really appreciate hearing
> about it.
> Roy
> 1. Kerberos is enabled
> 2. The servers are trusted for delegation
> 3. The SPN's are configured
> "http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_security_2gmm.asp"
> 4. If you have several domain controllers wait for replication to complete.
> If you don't wait you will pull your hair out because nothing you try will
> works and all of sudden a few hours latter it starts working and you can't
> figure out why.
> 5. Make sure all users have the option 'Enable Integrated Windows
> Authentication' enabled in internet explorer, without it they will still get
> the authentication error.
> "Jackson" wrote:
> > I'm having a problem connecting to an access database from
> > http://localhost/reports. I can connect from the computer I developed the
> > reports but when I goto another computer it gives me this error message
> >
> > An error has occurred during report processing. (rsProcessingAborted)
> >
> > Cannot create a connection to data source 'DataSource1'.
> > (rsErrorOpeningConnection)
> >
> > I've created the same exact odbc connection in the systems tab as on the
> > computer I've created the project with. I've looked at there online help
> > but it didn't have any suggestions.
> >
> > Is there anything else I need to do on the other computer in order for this
> > to work?
> >
> >
> > TIA,
> >
> > Jackson
> >
> >
> >|||I ran into the same issue. I have modified security to report howeve
I noticed that it is using the users credentials who is accessing th
report to initiate Oracle connection. It looks like the use
requires elevated permissions on C:\Program Files\Oracle and possibl
other directories
Still investigating...
Rya|||If you creaye a secure use in RSthat user can have the elevated priviledges
and not your real life users - better from a security point of view - that is
why I selected the options I did. See if that works to Oracle as well.
Cioa
Tina
"rjohnstone" wrote:
> I ran into the same issue. I have modified security to report however
> I noticed that it is using the users credentials who is accessing the
> report to initiate Oracle connection. It looks like the user
> requires elevated permissions on C:\Program Files\Oracle and possibly
> other directories.
> Still investigating...
> Ryan
>

Connecting to an SQL Server using a workgroup

I am trying to I am trying to connect to an SQL Server using a vb.net program. It works if
I put it on the SQL Server computer, but will not connect over my local
network that is set up as a workgroup. I get the following message:
Login failed for user 'DELL4100\Guest'

DELL4100 is the computer name where the sql server is on.

The connection string is:
Data Source=dell4100;Database=dbname;User ID=dbn;Password=password;
I have also tried Integrated Security=SSPI; instead of the User ID &
Password.

I do not know why it is using Guest instead of the User ID that I specified.
So, I created a Login name in the SQL Server called Guest with no password.
I also activated the Guest account in XP for both machines. Still the same
message.

I created accounts for dbn on both computers and gave them the same
password. I logged in under dsn and ran the program, but I still get the
same error.

I turned off the Windows firewall on both computers. I can share files and
printers between computers, just not access the SQL Server.

Can anyone help?

Thanks

Tim
using a vb.net program. It works if
I put it on the SQL Server computer, but will not connect over my local
network that is set up as a workgroup. I get the following message:
Login failed for user 'DELL4100\Guest'

DELL4100 is the computer name where the sql server is on.

The connection string is:
Data Source=dell4100;Database=dbname;User ID=dbn; Password=password;
I have also tried Integrated Security=SSPI; instead of the User ID &
Password.

I do not know why it is using Guest instead of the User ID that I specified.
So, I created a Login name in the SQL Server called Guest with no password.
I also activated the Guest account in XP for both machines. Still the same
message.

I created accounts for dbn on both computers and gave them the same
password. I logged in under dsn and ran the program, but I still get the
same error.

I turned off the Windows firewall on both computers. I can share files and
printers between computers, just not access the SQL Server.

Can anyone help?

Thanks

TimSomehow my message got mangled. I was editing the message and the time limit expired.

I wanted to add that the SQL Server is on an XP pro sp2 machine and that tcp/ip and Names Pipes are enabled and that it is listening on port 1433.|||I have the same issue, is there already an solution ?|||Try to create DSN to the server on your computer. If it doesn't work then it is not your code is a problem.
It is my only guess your SQL drivers are corrupt.|||I have the same question too. I just had to reinstall SQL server on a lab server that crashed, used to have a 'domain' windows 2003 setup but for some reason was set up as a peer-to-peer workgroup. Old way was to create sqlserver logins like: Workstation1\JoeDoe... now it says that is not a legal login, and I can;t 'find' anything but the server name? (I can otherwise access shared files between machines, etc.) . Is there some sql server issue with peer-to-peer networks?

Connecting to a second instance via VPN

Hi,

I have two SQL SERVER Instances on the computer I am trying to connect to via VPN:
1) TEST
2. TEST/INST2

I can connect to the first with no problems.

When I am trying to connect to the second (with the Enterprise Manager/Query Analyzer and even with isql) - I get the following message:
"SQL SERVER does not exists or access denied".

I use the SQL SERVER user and password to connect (as login sa).

How can I connect to the second instance?

Thanks in advance.you have to make sure that tcp/it is enabled on the server. can you use remote desktop or some other remote access tool to connect to the box? check to see if the service for the named instance is running (this should have been the first suggestion)|||Sorry, I had the instance name wrong...

Thanks for your answer anyway!

Connecting to a Remote Server with SQL Management Studio Express

I installed a copy of SQL 2005 Express on another computer here using the
automatic download and install from Microsoft supported by the setup
toolkit.
I can't access this server from another machine on the LAN using SQL
Management Studio Express. I can 'see' the server but cannot connect. Both
machines are running XP, mine is trying to log in as 'Guest'.
Do I need to configure SQL 2005 on the remote machine to use mixed-mode
authentication and try to log in using an SQL password, or is there a way to
make a remote user work with Windows Authentication?
How should I go about this?
Thanks.
You will have to disable the simple filesharhing in XP, otherweise the
client will try to logon using the guest account.
Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||If you haven't done so yet - enable TCP/IP via the SQL Server Surface Area
Configuration tool / Remote Connections on the destination SQL Server. SQL
Server 2005 Express doesn't enable this by default. Also turn on the SQL
Browser service.
M a M
"Jens" wrote:

> You will have to disable the simple filesharhing in XP, otherweise the
> client will try to logon using the guest account.
>
> Jens K. Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>
|||Thanks. I have done that but apparently have to enable mixed mode
authentication on the server in order to authenticate. How do I do this?
regards.
"M a M" <MaM@.discussions.microsoft.com> wrote in message
news:6045D19B-3B4F-4B27-B3CD-F82DD325E7DA@.microsoft.com...[vbcol=seagreen]
> If you haven't done so yet - enable TCP/IP via the SQL Server Surface Area
> Configuration tool / Remote Connections on the destination SQL Server. SQL
> Server 2005 Express doesn't enable this by default. Also turn on the SQL
> Browser service.
> M a M
> "Jens" wrote:
|||You could simply add the Windows NT account via the Security / Logins of the
Server in question. You have to log into the server locally obviously to make
this change. Either add the NT account or (your request) change the "Server
authentication" to SQL Server and Windows Authentication mode via the
Security tab of the SQL Server properties.
M a M
"Andrew Chalk" wrote:

> Thanks. I have done that but apparently have to enable mixed mode
> authentication on the server in order to authenticate. How do I do this?
> regards.
> "M a M" <MaM@.discussions.microsoft.com> wrote in message
> news:6045D19B-3B4F-4B27-B3CD-F82DD325E7DA@.microsoft.com...
>
>
|||> this change. Either add the NT account or (your request) change the
> "Server
> authentication" to SQL Server and Windows Authentication mode via the ...
How? This is XP with no SQL Management Studio Express. I have to connect
first before I can access the database with SQL MSE. That is the object of
this exercise.
Thanks.
"M a M" <MaM@.discussions.microsoft.com> wrote in message
news:96E18316-203F-46F1-A01D-FDEBE024CCBB@.microsoft.com...[vbcol=seagreen]
> You could simply add the Windows NT account via the Security / Logins of
> the
> Server in question. You have to log into the server locally obviously to
> make
> this change. Either add the NT account or (your request) change the
> "Server
> authentication" to SQL Server and Windows Authentication mode via the
> Security tab of the SQL Server properties.
> M a M
> "Andrew Chalk" wrote:
|||I loaded MSE on the remote machine and changed the logi mode to mixed. After
that, I was able to connect remotely with MSE.
So, my question boils down to this: How do I set the login mode of SQL
Server 2005 Express to mixed WITHOUT Manaagement Studio Express?
Thanks.
"M a M" <MaM@.discussions.microsoft.com> wrote in message
news:96E18316-203F-46F1-A01D-FDEBE024CCBB@.microsoft.com...[vbcol=seagreen]
> You could simply add the Windows NT account via the Security / Logins of
> the
> Server in question. You have to log into the server locally obviously to
> make
> this change. Either add the NT account or (your request) change the
> "Server
> authentication" to SQL Server and Windows Authentication mode via the
> Security tab of the SQL Server properties.
> M a M
> "Andrew Chalk" wrote:
|||HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.1\MSSQLServer change LoginMode from 1 to 2 and restart SQL
Server services.
"Andrew Chalk" wrote:

> I loaded MSE on the remote machine and changed the logi mode to mixed. After
> that, I was able to connect remotely with MSE.
> So, my question boils down to this: How do I set the login mode of SQL
> Server 2005 Express to mixed WITHOUT Manaagement Studio Express?
> Thanks.
> "M a M" <MaM@.discussions.microsoft.com> wrote in message
> news:96E18316-203F-46F1-A01D-FDEBE024CCBB@.microsoft.com...
>
>
|||Thanks!
"M a M" <MaM@.discussions.microsoft.com> wrote in message
news:6DBDB113-6DDE-4FAC-A09E-74FAAECAE75A@.microsoft.com...[vbcol=seagreen]
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
> Server\MSSQL.1\MSSQLServer change LoginMode from 1 to 2 and restart SQL
> Server services.
> "Andrew Chalk" wrote: