I have successfully installed SQL Server 2005 on a server that also has SQL
Server 2000. Using SQL Server 2005 interface, how could I connect to a
named instance of a SQL Server 2005 database? As I try, it keeps connecting
me to the SQL Server 2000 db. Is this something you set up in CLient tools?
Please let me know, I connect to the SQL Server using a temp dns name.
Thanks,
Here is what I what to achieve:
category1
content2
content3
content4
content5
content6Please disregard this text. Came from an old message.
"Here is what I what to achieve:
category1
content2
content3
content4
content5
content6"
<programmingcodeATjards.com> wrote in message
news:e83mL7OrGHA.4864@.TK2MSFTNGP03.phx.gbl...
>I have successfully installed SQL Server 2005 on a server that also has SQL
>Server 2000. Using SQL Server 2005 interface, how could I connect to a
>named instance of a SQL Server 2005 database? As I try, it keeps
>connecting me to the SQL Server 2000 db. Is this something you set up in
>CLient tools? Please let me know, I connect to the SQL Server using a temp
>dns name.
> Thanks,
>
> Here is what I what to achieve:
> category1
> content2
> content3
> content4
> content5
> content6
>
>|||<programmingcodeATjards.com> wrote in message
news:e83mL7OrGHA.4864@.TK2MSFTNGP03.phx.gbl...
> I have successfully installed SQL Server 2005 on a server that also has
SQL
> Server 2000. Using SQL Server 2005 interface, how could I connect to a
> named instance of a SQL Server 2005 database? As I try, it keeps
connecting
> me to the SQL Server 2000 db. Is this something you set up in CLient
tools?
> Please let me know, I connect to the SQL Server using a temp dns name.
> Thanks,
>
Not sure what you're trying, but generally it's servername\instancename. If
not instance name is provided it deafults to the default instance.
>
> Here is what I what to achieve:
> category1
> content2
> content3
> content4
> content5
> content6
>
>
Showing posts with label installed. Show all posts
Showing posts with label installed. Show all posts
Tuesday, March 27, 2012
Connecting to SQL Server 2005
Hi all,
I have Windows XP SP2 and SQL Server 2005 CTP installed on my machine.
I am trying to connect to the database in a ASP.net application but no matter how much i try i get the following error message : System.Data.SqlClient.SQLException:SQL Server does not exist or Access denied
I have Windows XP SP2 and SQL Server 2005 CTP installed on my machine.
I am trying to connect to the database in a ASP.net application but no matter how much i try i get the following error message : System.Data.SqlClient.SQLException:SQL Server does not exist or Access denied
I have tried to fix the problmm by checking in all the online blogs and trying out whatever is being suggested , still no luck!!!
Would appreciate if anybody could help me
Thanks.
sshettyThe folks on the SQL Server Data Access forum (http://forums.microsoft.com/msdn/ShowForum.aspx?ForumID=87) should be able to help you out with this one.
Raman Iyer
SQL Server Data Mining
Connecting to SQL Server 2005
I installed the SQL Server 2005 Trial and am now having trouble connecting. When I bring up the ASP.NET Configuration tool and Go to "Provider configuration" "Select a single provider for all site management data" AspNetSqlProvider Test I get the following message.
"Could not establish a connection to the database.
If you have not yet created the SQL Server database, exit the Web Site Administration tool, use the aspnet_regsql command-line utility to create and configure the database, and then return to this tool to set the provider. "
I have already run the aspnet_regsql command-line utility.
Can anybody give me some information on how to set this up.
I am currently working with the club web site starter kit.
I first recommend you go grab this awesome management tool for the express edts :
http://www.microsoft.com/downloads/details.aspx?familyid=82afbd59-57a4-455e-a2d6-1d4c98d40f6e&displaylang=en
I would then first check to see if your connections to the DB work with this tool and copy the connection strings it gives you and use them in your app. Also, you can configure ASPNETDB from the web.config level and dont have to use the web tool. This way you can test directoly to ASPNETDB. I havent used the club starter kit but im sure it either uses app_data or aspnetdb in the db. All you have to do is point to the right one. I wrote a couple blogs on this :
http://eramseur.blogspot.com/2005/12/aspnet-20-create-custom-provider-for_10.html
I would also check out scotts entry :
http://weblogs.asp.net/scottgu/archive/2006/02/24/438953.aspx
He has another article about how to get membershp up in 15 minutes and you should look at that too.
Connecting to SQL Server 2005
I have successfully installed SQL Server 2005 on a server that also has SQL
Server 2000. Using SQL Server 2005 interface, how could I connect to a
named instance of a SQL Server 2005 database? As I try, it keeps connecting
me to the SQL Server 2000 db. Is this something you set up in CLient tools?
Please let me know, I connect to the SQL Server using a temp dns name.
Thanks,
Here is what I what to achieve:
category1
content2
content3
content4
content5
content6Please disregard this text. Came from an old message.
"Here is what I what to achieve:
category1
content2
content3
content4
content5
content6"
<programmingcodeATjards.com> wrote in message
news:e83mL7OrGHA.4864@.TK2MSFTNGP03.phx.gbl...
>I have successfully installed SQL Server 2005 on a server that also has SQL
>Server 2000. Using SQL Server 2005 interface, how could I connect to a
>named instance of a SQL Server 2005 database? As I try, it keeps
>connecting me to the SQL Server 2000 db. Is this something you set up in
>CLient tools? Please let me know, I connect to the SQL Server using a temp
>dns name.
> Thanks,
>
> Here is what I what to achieve:
> category1
> content2
> content3
> content4
> content5
> content6
>
>|||<programmingcodeATjards.com> wrote in message
news:e83mL7OrGHA.4864@.TK2MSFTNGP03.phx.gbl...
> I have successfully installed SQL Server 2005 on a server that also has
SQL
> Server 2000. Using SQL Server 2005 interface, how could I connect to a
> named instance of a SQL Server 2005 database? As I try, it keeps
connecting
> me to the SQL Server 2000 db. Is this something you set up in CLient
tools?
> Please let me know, I connect to the SQL Server using a temp dns name.
> Thanks,
>
Not sure what you're trying, but generally it's servername\instancename. If
not instance name is provided it deafults to the default instance.
>
> Here is what I what to achieve:
> category1
> content2
> content3
> content4
> content5
> content6
>
>sqlsql
Server 2000. Using SQL Server 2005 interface, how could I connect to a
named instance of a SQL Server 2005 database? As I try, it keeps connecting
me to the SQL Server 2000 db. Is this something you set up in CLient tools?
Please let me know, I connect to the SQL Server using a temp dns name.
Thanks,
Here is what I what to achieve:
category1
content2
content3
content4
content5
content6Please disregard this text. Came from an old message.
"Here is what I what to achieve:
category1
content2
content3
content4
content5
content6"
<programmingcodeATjards.com> wrote in message
news:e83mL7OrGHA.4864@.TK2MSFTNGP03.phx.gbl...
>I have successfully installed SQL Server 2005 on a server that also has SQL
>Server 2000. Using SQL Server 2005 interface, how could I connect to a
>named instance of a SQL Server 2005 database? As I try, it keeps
>connecting me to the SQL Server 2000 db. Is this something you set up in
>CLient tools? Please let me know, I connect to the SQL Server using a temp
>dns name.
> Thanks,
>
> Here is what I what to achieve:
> category1
> content2
> content3
> content4
> content5
> content6
>
>|||<programmingcodeATjards.com> wrote in message
news:e83mL7OrGHA.4864@.TK2MSFTNGP03.phx.gbl...
> I have successfully installed SQL Server 2005 on a server that also has
SQL
> Server 2000. Using SQL Server 2005 interface, how could I connect to a
> named instance of a SQL Server 2005 database? As I try, it keeps
connecting
> me to the SQL Server 2000 db. Is this something you set up in CLient
tools?
> Please let me know, I connect to the SQL Server using a temp dns name.
> Thanks,
>
Not sure what you're trying, but generally it's servername\instancename. If
not instance name is provided it deafults to the default instance.
>
> Here is what I what to achieve:
> category1
> content2
> content3
> content4
> content5
> content6
>
>sqlsql
connecting to SQL Server 2000 using JDBC
I've download Microsoft SQL Server 2000 JDBC Driver. All these files are being installed and saved in a folder called sql. For example, the IP adress is 255.255.255.255 , I updated the code and saved it as test1.java in this manner:
import java.sql.*;
/**
* Microsoft SQL Server JDBC test program
*/
public class test1 {
public test1() throws Exception {
// Get connection
DriverManager.registerDriver(new
com.microsoft.jdbc.sqlserver.SQLServerDriver());
Connection connection = DriverManager.getConnection(
"jdbc:microsoft:sqlserver:@.255.255.255","abc","abc");
if (connection != null) {
System.out.println();
System.out.println("Successfully connected");
System.out.println();
// Meta data
DatabaseMetaData meta = connection.getMetaData();
System.out.println("\nDriver Information");
System.out.println("Driver Name: "
+ meta.getDriverName());
System.out.println("Driver Version: "
+ meta.getDriverVersion());
System.out.println("\nDatabase Information ");
System.out.println("Database Name: "
+ meta.getDatabaseProductName());
System.out.println("Database Version: "+
meta.getDatabaseProductVersion());
}
} // Test
public static void main (String args[]) throws Exception {
test1 test = new test1();
}
}
I'm able to compile but when I run the program, the given error is:
Exception in thread "main" java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Unable to connect. Invalid URL.
at com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown Source
)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager .java:512)
at java.sql.DriverManager.getConnection(DriverManager .java:171)
at test1.<init>(test1.java:10)
at test1.main(test1.java:31)
I have checked that the given IP address is correct, so please can anyone enlighten me about the problem.
Thanks.You must set your database name and port number such as following
Connection connection = DriverManager.getConnection(
"jdbc:microsoft:sqlserver:@.255.255.255:1433;Databas eName=MyDB","abc","abc");
You can also use your computer name in url
"jdbc:microsoft:sqlserver://MYSERVER:1433;DatabaseName=MYDB","USERID","PASSWORD"
Originally posted by diablos00
I've download Microsoft SQL Server 2000 JDBC Driver. All these files are being installed and saved in a folder called sql. For example, the IP adress is 255.255.255.255 , I updated the code and saved it as test1.java in this manner:
import java.sql.*;
/**
* Microsoft SQL Server JDBC test program
*/
public class test1 {
public test1() throws Exception {
// Get connection
DriverManager.registerDriver(new
com.microsoft.jdbc.sqlserver.SQLServerDriver());
Connection connection = DriverManager.getConnection(
"jdbc:microsoft:sqlserver:@.255.255.255","abc","abc");
if (connection != null) {
System.out.println();
System.out.println("Successfully connected");
System.out.println();
// Meta data
DatabaseMetaData meta = connection.getMetaData();
System.out.println("\nDriver Information");
System.out.println("Driver Name: "
+ meta.getDriverName());
System.out.println("Driver Version: "
+ meta.getDriverVersion());
System.out.println("\nDatabase Information ");
System.out.println("Database Name: "
+ meta.getDatabaseProductName());
System.out.println("Database Version: "+
meta.getDatabaseProductVersion());
}
} // Test
public static void main (String args[]) throws Exception {
test1 test = new test1();
}
}
I'm able to compile but when I run the program, the given error is:
Exception in thread "main" java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Unable to connect. Invalid URL.
at com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown Source
)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager .java:512)
at java.sql.DriverManager.getConnection(DriverManager .java:171)
at test1.<init>(test1.java:10)
at test1.main(test1.java:31)
I have checked that the given IP address is correct, so please can anyone enlighten me about the problem.
Thanks.|||I had the same problem,
The problem is that the Microsoft jdbc driver used unicode and Ianywhere can't handle it.
Use an other jdbc driver from a 3de party will solve this problem.
I used the jdbc driver from datadirect (Type 4 jdbc driver) and this one
was working perfectly. Only thing is you have to pay for it.
I hope i could help you with this.
Greetz|||Microsofts JDBC driver works just fine. In fact it's an old data direct Type 4 driver. Make sure you have the service pack 1 jdbc driver. Here's the exact connection url I use with no problems.
jdbc:jtds:sqlserver://tlmssql3:1388/db1;USER=appsrv1;PASSWORD=password;TDS=8.0
import java.sql.*;
/**
* Microsoft SQL Server JDBC test program
*/
public class test1 {
public test1() throws Exception {
// Get connection
DriverManager.registerDriver(new
com.microsoft.jdbc.sqlserver.SQLServerDriver());
Connection connection = DriverManager.getConnection(
"jdbc:microsoft:sqlserver:@.255.255.255","abc","abc");
if (connection != null) {
System.out.println();
System.out.println("Successfully connected");
System.out.println();
// Meta data
DatabaseMetaData meta = connection.getMetaData();
System.out.println("\nDriver Information");
System.out.println("Driver Name: "
+ meta.getDriverName());
System.out.println("Driver Version: "
+ meta.getDriverVersion());
System.out.println("\nDatabase Information ");
System.out.println("Database Name: "
+ meta.getDatabaseProductName());
System.out.println("Database Version: "+
meta.getDatabaseProductVersion());
}
} // Test
public static void main (String args[]) throws Exception {
test1 test = new test1();
}
}
I'm able to compile but when I run the program, the given error is:
Exception in thread "main" java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Unable to connect. Invalid URL.
at com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown Source
)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager .java:512)
at java.sql.DriverManager.getConnection(DriverManager .java:171)
at test1.<init>(test1.java:10)
at test1.main(test1.java:31)
I have checked that the given IP address is correct, so please can anyone enlighten me about the problem.
Thanks.You must set your database name and port number such as following
Connection connection = DriverManager.getConnection(
"jdbc:microsoft:sqlserver:@.255.255.255:1433;Databas eName=MyDB","abc","abc");
You can also use your computer name in url
"jdbc:microsoft:sqlserver://MYSERVER:1433;DatabaseName=MYDB","USERID","PASSWORD"
Originally posted by diablos00
I've download Microsoft SQL Server 2000 JDBC Driver. All these files are being installed and saved in a folder called sql. For example, the IP adress is 255.255.255.255 , I updated the code and saved it as test1.java in this manner:
import java.sql.*;
/**
* Microsoft SQL Server JDBC test program
*/
public class test1 {
public test1() throws Exception {
// Get connection
DriverManager.registerDriver(new
com.microsoft.jdbc.sqlserver.SQLServerDriver());
Connection connection = DriverManager.getConnection(
"jdbc:microsoft:sqlserver:@.255.255.255","abc","abc");
if (connection != null) {
System.out.println();
System.out.println("Successfully connected");
System.out.println();
// Meta data
DatabaseMetaData meta = connection.getMetaData();
System.out.println("\nDriver Information");
System.out.println("Driver Name: "
+ meta.getDriverName());
System.out.println("Driver Version: "
+ meta.getDriverVersion());
System.out.println("\nDatabase Information ");
System.out.println("Database Name: "
+ meta.getDatabaseProductName());
System.out.println("Database Version: "+
meta.getDatabaseProductVersion());
}
} // Test
public static void main (String args[]) throws Exception {
test1 test = new test1();
}
}
I'm able to compile but when I run the program, the given error is:
Exception in thread "main" java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Unable to connect. Invalid URL.
at com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown Source
)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager .java:512)
at java.sql.DriverManager.getConnection(DriverManager .java:171)
at test1.<init>(test1.java:10)
at test1.main(test1.java:31)
I have checked that the given IP address is correct, so please can anyone enlighten me about the problem.
Thanks.|||I had the same problem,
The problem is that the Microsoft jdbc driver used unicode and Ianywhere can't handle it.
Use an other jdbc driver from a 3de party will solve this problem.
I used the jdbc driver from datadirect (Type 4 jdbc driver) and this one
was working perfectly. Only thing is you have to pay for it.
I hope i could help you with this.
Greetz|||Microsofts JDBC driver works just fine. In fact it's an old data direct Type 4 driver. Make sure you have the service pack 1 jdbc driver. Here's the exact connection url I use with no problems.
jdbc:jtds:sqlserver://tlmssql3:1388/db1;USER=appsrv1;PASSWORD=password;TDS=8.0
connecting to SQL Server 2000
hi all;
I have a SQL server ent. edition installed on windows 2003, I want to
register another SQL server instance installed on windows xp, in my
enterprise manager. When I try to do that i get the following error message.
"SQL server does not exists or access denied."
note that no domain controller is installed on the network.
What is reason, and how can i resolve it?
all ideas would be highly appreciated...
AnsariYou have to verify that :
1. you have nioo network problems , you can test sharing a folder on the XP
machine and access this share from Win2003
2. Verifiy that you have no accounts problems and permissions
3.verify thant services are really started on the xp machine
4. try to register xp server from Win2003 using the IP adresss first second
try with the netbios name .
5. activate the mixed security on the xp machine and try to register with SA
login .
I think that with these 5 tests you should fix the poblem
hch
"Ansari" a écrit :
> hi all;
> I have a SQL server ent. edition installed on windows 2003, I want to
> register another SQL server instance installed on windows xp, in my
> enterprise manager. When I try to do that i get the following error messag
e.
> "SQL server does not exists or access denied."
> note that no domain controller is installed on the network.
> What is reason, and how can i resolve it?
> all ideas would be highly appreciated...
> Ansari
>
>
I have a SQL server ent. edition installed on windows 2003, I want to
register another SQL server instance installed on windows xp, in my
enterprise manager. When I try to do that i get the following error message.
"SQL server does not exists or access denied."
note that no domain controller is installed on the network.
What is reason, and how can i resolve it?
all ideas would be highly appreciated...
AnsariYou have to verify that :
1. you have nioo network problems , you can test sharing a folder on the XP
machine and access this share from Win2003
2. Verifiy that you have no accounts problems and permissions
3.verify thant services are really started on the xp machine
4. try to register xp server from Win2003 using the IP adresss first second
try with the netbios name .
5. activate the mixed security on the xp machine and try to register with SA
login .
I think that with these 5 tests you should fix the poblem
hch
"Ansari" a écrit :
> hi all;
> I have a SQL server ent. edition installed on windows 2003, I want to
> register another SQL server instance installed on windows xp, in my
> enterprise manager. When I try to do that i get the following error messag
e.
> "SQL server does not exists or access denied."
> note that no domain controller is installed on the network.
> What is reason, and how can i resolve it?
> all ideas would be highly appreciated...
> Ansari
>
>
connecting to SQL Server 2000
hi all;
I have a SQL server ent. edition installed on windows 2003, I want to
register another SQL server instance installed on windows xp, in my
enterprise manager. When I try to do that i get the following error message.
"SQL server does not exists or access denied."
note that no domain controller is installed on the network.
What is reason, and how can i resolve it?
all ideas would be highly appreciated...
Ansari
You have to verify that :
1. you have nioo network problems , you can test sharing a folder on the XP
machine and access this share from Win2003
2. Verifiy that you have no accounts problems and permissions
3.verify thant services are really started on the xp machine
4. try to register xp server from Win2003 using the IP adresss first second
try with the netbios name .
5. activate the mixed security on the xp machine and try to register with SA
login .
I think that with these 5 tests you should fix the poblem
hch
"Ansari" a écrit :
> hi all;
> I have a SQL server ent. edition installed on windows 2003, I want to
> register another SQL server instance installed on windows xp, in my
> enterprise manager. When I try to do that i get the following error message.
> "SQL server does not exists or access denied."
> note that no domain controller is installed on the network.
> What is reason, and how can i resolve it?
> all ideas would be highly appreciated...
> Ansari
>
>
sqlsql
I have a SQL server ent. edition installed on windows 2003, I want to
register another SQL server instance installed on windows xp, in my
enterprise manager. When I try to do that i get the following error message.
"SQL server does not exists or access denied."
note that no domain controller is installed on the network.
What is reason, and how can i resolve it?
all ideas would be highly appreciated...
Ansari
You have to verify that :
1. you have nioo network problems , you can test sharing a folder on the XP
machine and access this share from Win2003
2. Verifiy that you have no accounts problems and permissions
3.verify thant services are really started on the xp machine
4. try to register xp server from Win2003 using the IP adresss first second
try with the netbios name .
5. activate the mixed security on the xp machine and try to register with SA
login .
I think that with these 5 tests you should fix the poblem
hch
"Ansari" a écrit :
> hi all;
> I have a SQL server ent. edition installed on windows 2003, I want to
> register another SQL server instance installed on windows xp, in my
> enterprise manager. When I try to do that i get the following error message.
> "SQL server does not exists or access denied."
> note that no domain controller is installed on the network.
> What is reason, and how can i resolve it?
> all ideas would be highly appreciated...
> Ansari
>
>
sqlsql
connecting to SQL Server 2000
hi all;
I have a SQL server ent. edition installed on windows 2003, I want to
register another SQL server instance installed on windows xp, in my
enterprise manager. When I try to do that i get the following error message.
"SQL server does not exists or access denied."
note that no domain controller is installed on the network.
What is reason, and how can i resolve it?
all ideas would be highly appreciated...
AnsariYou have to verify that :
1. you have nioo network problems , you can test sharing a folder on the XP
machine and access this share from Win2003
2. Verifiy that you have no accounts problems and permissions
3.verify thant services are really started on the xp machine
4. try to register xp server from Win2003 using the IP adresss first second
try with the netbios name .
5. activate the mixed security on the xp machine and try to register with SA
login .
I think that with these 5 tests you should fix the poblem
hch
"Ansari" a écrit :
> hi all;
> I have a SQL server ent. edition installed on windows 2003, I want to
> register another SQL server instance installed on windows xp, in my
> enterprise manager. When I try to do that i get the following error message.
> "SQL server does not exists or access denied."
> note that no domain controller is installed on the network.
> What is reason, and how can i resolve it?
> all ideas would be highly appreciated...
> Ansari
>
>
I have a SQL server ent. edition installed on windows 2003, I want to
register another SQL server instance installed on windows xp, in my
enterprise manager. When I try to do that i get the following error message.
"SQL server does not exists or access denied."
note that no domain controller is installed on the network.
What is reason, and how can i resolve it?
all ideas would be highly appreciated...
AnsariYou have to verify that :
1. you have nioo network problems , you can test sharing a folder on the XP
machine and access this share from Win2003
2. Verifiy that you have no accounts problems and permissions
3.verify thant services are really started on the xp machine
4. try to register xp server from Win2003 using the IP adresss first second
try with the netbios name .
5. activate the mixed security on the xp machine and try to register with SA
login .
I think that with these 5 tests you should fix the poblem
hch
"Ansari" a écrit :
> hi all;
> I have a SQL server ent. edition installed on windows 2003, I want to
> register another SQL server instance installed on windows xp, in my
> enterprise manager. When I try to do that i get the following error message.
> "SQL server does not exists or access denied."
> note that no domain controller is installed on the network.
> What is reason, and how can i resolve it?
> all ideas would be highly appreciated...
> Ansari
>
>
Connecting to SQL Server & XP Service Pack 2
I installed XP Service Pack 2 on my desktop machine which had SQL Server 2000
running on it prior to the install. I have a C# web application that runs
against a local SQL Server database which I cannot get to work now that I
have installed the XP service pack. I have read all of the Microsoft "HOW To"
documents about configuring SQL Server for the Service Pack but I still
cannot get the Web Appliation to communicate with the database. I always get
the "SQL Server does not exist or access denied." error message. I have tried
the following:
1. Added Port 1433 (TCP/IP) to the Firewall Exception List (1433 is the
static port SQL Server is using)
2. Added Port 445 (TCP/IP) to the Firewall Exception List
3. Added the sqlserver.exe file to the Firewall Exception List
The database connection string I am using in the web application is:
server=local;uid=sa;pwd=<password>;database=Resear ch
At this point I am not sure what else to try. I cannot connect to the
database if the Firewall is turned off. Should this be the case? Any
assistance is much appreciated.
Sincerely,
Tom Hessen
Hi Tom,
I had the same problem and decided to look at the other end of the
connection. I was running SQL Server ( Service Pack 2 ). When I upgraded
to SQL Server ( Service Pack 3a ) everything started working again.
"Tom Hessen" <Tom Hessen@.discussions.microsoft.com> wrote in message news:<645A76F5-D701-4411-9720-1C6AC67A7ED5@.microsoft.com>...
> I installed XP Service Pack 2 on my desktop machine which had SQL Server 2000
> running on it prior to the install. I have a C# web application that runs
> against a local SQL Server database which I cannot get to work now that I
> have installed the XP service pack. I have read all of the Microsoft "HOW To"
> documents about configuring SQL Server for the Service Pack but I still
> cannot get the Web Appliation to communicate with the database. I always get
> the "SQL Server does not exist or access denied." error message. I have tried
> the following:
> 1. Added Port 1433 (TCP/IP) to the Firewall Exception List (1433 is the
> static port SQL Server is using)
> 2. Added Port 445 (TCP/IP) to the Firewall Exception List
> 3. Added the sqlserver.exe file to the Firewall Exception List
> The database connection string I am using in the web application is:
> server=local;uid=sa;pwd=<password>;database=Resear ch
> At this point I am not sure what else to try. I cannot connect to the
> database if the Firewall is turned off. Should this be the case? Any
> assistance is much appreciated.
> Sincerely,
> Tom Hessen
|||Hi Tom,
I've had a little trouble posting, but hopefully this will get through.
I also did everything you listed below. It did not work for me
either ( for a java client ).
I then decided to look at the other end of the connection. I was running
SQLServer ( Service Pack 2 ). When I upgraded to SQLServer ( Service Pack
3a ) everything started working again.
Hope this helps,
Mike S.
"Tom Hessen" <Tom Hessen@.discussions.microsoft.com> wrote in message news:<645A76F5-D701-4411-9720-1C6AC67A7ED5@.microsoft.com>...
> I installed XP Service Pack 2 on my desktop machine which had SQL Server 2000
> running on it prior to the install. I have a C# web application that runs
> against a local SQL Server database which I cannot get to work now that I
> have installed the XP service pack. I have read all of the Microsoft "HOW To"
> documents about configuring SQL Server for the Service Pack but I still
> cannot get the Web Appliation to communicate with the database. I always get
> the "SQL Server does not exist or access denied." error message. I have tried
> the following:
> 1. Added Port 1433 (TCP/IP) to the Firewall Exception List (1433 is the
> static port SQL Server is using)
> 2. Added Port 445 (TCP/IP) to the Firewall Exception List
> 3. Added the sqlserver.exe file to the Firewall Exception List
> The database connection string I am using in the web application is:
> server=local;uid=sa;pwd=<password>;database=Resear ch
> At this point I am not sure what else to try. I cannot connect to the
> database if the Firewall is turned off. Should this be the case? Any
> assistance is much appreciated.
> Sincerely,
> Tom Hessen
sqlsql
running on it prior to the install. I have a C# web application that runs
against a local SQL Server database which I cannot get to work now that I
have installed the XP service pack. I have read all of the Microsoft "HOW To"
documents about configuring SQL Server for the Service Pack but I still
cannot get the Web Appliation to communicate with the database. I always get
the "SQL Server does not exist or access denied." error message. I have tried
the following:
1. Added Port 1433 (TCP/IP) to the Firewall Exception List (1433 is the
static port SQL Server is using)
2. Added Port 445 (TCP/IP) to the Firewall Exception List
3. Added the sqlserver.exe file to the Firewall Exception List
The database connection string I am using in the web application is:
server=local;uid=sa;pwd=<password>;database=Resear ch
At this point I am not sure what else to try. I cannot connect to the
database if the Firewall is turned off. Should this be the case? Any
assistance is much appreciated.
Sincerely,
Tom Hessen
Hi Tom,
I had the same problem and decided to look at the other end of the
connection. I was running SQL Server ( Service Pack 2 ). When I upgraded
to SQL Server ( Service Pack 3a ) everything started working again.
"Tom Hessen" <Tom Hessen@.discussions.microsoft.com> wrote in message news:<645A76F5-D701-4411-9720-1C6AC67A7ED5@.microsoft.com>...
> I installed XP Service Pack 2 on my desktop machine which had SQL Server 2000
> running on it prior to the install. I have a C# web application that runs
> against a local SQL Server database which I cannot get to work now that I
> have installed the XP service pack. I have read all of the Microsoft "HOW To"
> documents about configuring SQL Server for the Service Pack but I still
> cannot get the Web Appliation to communicate with the database. I always get
> the "SQL Server does not exist or access denied." error message. I have tried
> the following:
> 1. Added Port 1433 (TCP/IP) to the Firewall Exception List (1433 is the
> static port SQL Server is using)
> 2. Added Port 445 (TCP/IP) to the Firewall Exception List
> 3. Added the sqlserver.exe file to the Firewall Exception List
> The database connection string I am using in the web application is:
> server=local;uid=sa;pwd=<password>;database=Resear ch
> At this point I am not sure what else to try. I cannot connect to the
> database if the Firewall is turned off. Should this be the case? Any
> assistance is much appreciated.
> Sincerely,
> Tom Hessen
|||Hi Tom,
I've had a little trouble posting, but hopefully this will get through.
I also did everything you listed below. It did not work for me
either ( for a java client ).
I then decided to look at the other end of the connection. I was running
SQLServer ( Service Pack 2 ). When I upgraded to SQLServer ( Service Pack
3a ) everything started working again.
Hope this helps,
Mike S.
"Tom Hessen" <Tom Hessen@.discussions.microsoft.com> wrote in message news:<645A76F5-D701-4411-9720-1C6AC67A7ED5@.microsoft.com>...
> I installed XP Service Pack 2 on my desktop machine which had SQL Server 2000
> running on it prior to the install. I have a C# web application that runs
> against a local SQL Server database which I cannot get to work now that I
> have installed the XP service pack. I have read all of the Microsoft "HOW To"
> documents about configuring SQL Server for the Service Pack but I still
> cannot get the Web Appliation to communicate with the database. I always get
> the "SQL Server does not exist or access denied." error message. I have tried
> the following:
> 1. Added Port 1433 (TCP/IP) to the Firewall Exception List (1433 is the
> static port SQL Server is using)
> 2. Added Port 445 (TCP/IP) to the Firewall Exception List
> 3. Added the sqlserver.exe file to the Firewall Exception List
> The database connection string I am using in the web application is:
> server=local;uid=sa;pwd=<password>;database=Resear ch
> At this point I am not sure what else to try. I cannot connect to the
> database if the Firewall is turned off. Should this be the case? Any
> assistance is much appreciated.
> Sincerely,
> Tom Hessen
sqlsql
Connecting to SQL Server & XP Service Pack 2
I installed XP Service Pack 2 on my desktop machine which had SQL Server 2000
running on it prior to the install. I have a C# web application that runs
against a local SQL Server database which I cannot get to work now that I
have installed the XP service pack. I have read all of the Microsoft "HOW To"
documents about configuring SQL Server for the Service Pack but I still
cannot get the Web Appliation to communicate with the database. I always get
the "SQL Server does not exist or access denied." error message. I have tried
the following:
1. Added Port 1433 (TCP/IP) to the Firewall Exception List (1433 is the
static port SQL Server is using)
2. Added Port 445 (TCP/IP) to the Firewall Exception List
3. Added the sqlserver.exe file to the Firewall Exception List
The database connection string I am using in the web application is:
server=local;uid=sa;pwd=<password>;database=Research
At this point I am not sure what else to try. I cannot connect to the
database if the Firewall is turned off. Should this be the case? Any
assistance is much appreciated.
Sincerely,
Tom HessenHi Tom,
I had the same problem and decided to look at the other end of the
connection. I was running SQL Server ( Service Pack 2 ). When I upgraded
to SQL Server ( Service Pack 3a ) everything started working again.
"Tom Hessen" <Tom Hessen@.discussions.microsoft.com> wrote in message news:<645A76F5-D701-4411-9720-1C6AC67A7ED5@.microsoft.com>...
> I installed XP Service Pack 2 on my desktop machine which had SQL Server 2000
> running on it prior to the install. I have a C# web application that runs
> against a local SQL Server database which I cannot get to work now that I
> have installed the XP service pack. I have read all of the Microsoft "HOW To"
> documents about configuring SQL Server for the Service Pack but I still
> cannot get the Web Appliation to communicate with the database. I always get
> the "SQL Server does not exist or access denied." error message. I have tried
> the following:
> 1. Added Port 1433 (TCP/IP) to the Firewall Exception List (1433 is the
> static port SQL Server is using)
> 2. Added Port 445 (TCP/IP) to the Firewall Exception List
> 3. Added the sqlserver.exe file to the Firewall Exception List
> The database connection string I am using in the web application is:
> server=local;uid=sa;pwd=<password>;database=Research
> At this point I am not sure what else to try. I cannot connect to the
> database if the Firewall is turned off. Should this be the case? Any
> assistance is much appreciated.
> Sincerely,
> Tom Hessen|||Hi Tom,
I've had a little trouble posting, but hopefully this will get through.
I also did everything you listed below. It did not work for me
either ( for a java client ).
I then decided to look at the other end of the connection. I was running
SQLServer ( Service Pack 2 ). When I upgraded to SQLServer ( Service Pack
3a ) everything started working again.
Hope this helps,
Mike S.
"Tom Hessen" <Tom Hessen@.discussions.microsoft.com> wrote in message news:<645A76F5-D701-4411-9720-1C6AC67A7ED5@.microsoft.com>...
> I installed XP Service Pack 2 on my desktop machine which had SQL Server 2000
> running on it prior to the install. I have a C# web application that runs
> against a local SQL Server database which I cannot get to work now that I
> have installed the XP service pack. I have read all of the Microsoft "HOW To"
> documents about configuring SQL Server for the Service Pack but I still
> cannot get the Web Appliation to communicate with the database. I always get
> the "SQL Server does not exist or access denied." error message. I have tried
> the following:
> 1. Added Port 1433 (TCP/IP) to the Firewall Exception List (1433 is the
> static port SQL Server is using)
> 2. Added Port 445 (TCP/IP) to the Firewall Exception List
> 3. Added the sqlserver.exe file to the Firewall Exception List
> The database connection string I am using in the web application is:
> server=local;uid=sa;pwd=<password>;database=Research
> At this point I am not sure what else to try. I cannot connect to the
> database if the Firewall is turned off. Should this be the case? Any
> assistance is much appreciated.
> Sincerely,
> Tom Hessen
running on it prior to the install. I have a C# web application that runs
against a local SQL Server database which I cannot get to work now that I
have installed the XP service pack. I have read all of the Microsoft "HOW To"
documents about configuring SQL Server for the Service Pack but I still
cannot get the Web Appliation to communicate with the database. I always get
the "SQL Server does not exist or access denied." error message. I have tried
the following:
1. Added Port 1433 (TCP/IP) to the Firewall Exception List (1433 is the
static port SQL Server is using)
2. Added Port 445 (TCP/IP) to the Firewall Exception List
3. Added the sqlserver.exe file to the Firewall Exception List
The database connection string I am using in the web application is:
server=local;uid=sa;pwd=<password>;database=Research
At this point I am not sure what else to try. I cannot connect to the
database if the Firewall is turned off. Should this be the case? Any
assistance is much appreciated.
Sincerely,
Tom HessenHi Tom,
I had the same problem and decided to look at the other end of the
connection. I was running SQL Server ( Service Pack 2 ). When I upgraded
to SQL Server ( Service Pack 3a ) everything started working again.
"Tom Hessen" <Tom Hessen@.discussions.microsoft.com> wrote in message news:<645A76F5-D701-4411-9720-1C6AC67A7ED5@.microsoft.com>...
> I installed XP Service Pack 2 on my desktop machine which had SQL Server 2000
> running on it prior to the install. I have a C# web application that runs
> against a local SQL Server database which I cannot get to work now that I
> have installed the XP service pack. I have read all of the Microsoft "HOW To"
> documents about configuring SQL Server for the Service Pack but I still
> cannot get the Web Appliation to communicate with the database. I always get
> the "SQL Server does not exist or access denied." error message. I have tried
> the following:
> 1. Added Port 1433 (TCP/IP) to the Firewall Exception List (1433 is the
> static port SQL Server is using)
> 2. Added Port 445 (TCP/IP) to the Firewall Exception List
> 3. Added the sqlserver.exe file to the Firewall Exception List
> The database connection string I am using in the web application is:
> server=local;uid=sa;pwd=<password>;database=Research
> At this point I am not sure what else to try. I cannot connect to the
> database if the Firewall is turned off. Should this be the case? Any
> assistance is much appreciated.
> Sincerely,
> Tom Hessen|||Hi Tom,
I've had a little trouble posting, but hopefully this will get through.
I also did everything you listed below. It did not work for me
either ( for a java client ).
I then decided to look at the other end of the connection. I was running
SQLServer ( Service Pack 2 ). When I upgraded to SQLServer ( Service Pack
3a ) everything started working again.
Hope this helps,
Mike S.
"Tom Hessen" <Tom Hessen@.discussions.microsoft.com> wrote in message news:<645A76F5-D701-4411-9720-1C6AC67A7ED5@.microsoft.com>...
> I installed XP Service Pack 2 on my desktop machine which had SQL Server 2000
> running on it prior to the install. I have a C# web application that runs
> against a local SQL Server database which I cannot get to work now that I
> have installed the XP service pack. I have read all of the Microsoft "HOW To"
> documents about configuring SQL Server for the Service Pack but I still
> cannot get the Web Appliation to communicate with the database. I always get
> the "SQL Server does not exist or access denied." error message. I have tried
> the following:
> 1. Added Port 1433 (TCP/IP) to the Firewall Exception List (1433 is the
> static port SQL Server is using)
> 2. Added Port 445 (TCP/IP) to the Firewall Exception List
> 3. Added the sqlserver.exe file to the Firewall Exception List
> The database connection string I am using in the web application is:
> server=local;uid=sa;pwd=<password>;database=Research
> At this point I am not sure what else to try. I cannot connect to the
> database if the Firewall is turned off. Should this be the case? Any
> assistance is much appreciated.
> Sincerely,
> Tom Hessen
Connecting to SQL Server
Hi:
I installed SQL Express in one of my Notebook A (XP Pro SP2), I could start writing code with VB6 as it is in local machine (.\Sqlexpress)
At later stage, I used another Notebook B (XP pro SP1). I changed the notebook workgroup with the same name and try to connect to Notebook A with Ethernet Cable using SQLOLEDB to make connection, I had this Error Message
"Test Connection Failed because of an error initialising the provider.[DBNETLIB][Connection Open(Connect()).]SQL Server Does not Exist or Access Denied"
I look thru this forum, I quoted Jens K. Suessmeyer comment
This simply mean that in a network you either will need all users to have their own database OR dedicate a "server" (which can also be a workstation) to host the database as a server attached instance.
So I Presume I could used a PC/Notebook (not a Server) as Database Server?
If I used Windows NT Integrated Security, then I should create user accounts at Notebook A? Or Create User Accounts at SQL Server If i used "Used Specific User Name and Password" to Log in ?
My Intention is If I have 5 PC to log in to Server Automatically whenever they switch on the PC with the VB6 Program executing during start up. It make login to User as transparent as possible.
Thanks
"So I Presume I could used a PC/Notebook (not a Server) as Database Server?"
Yes, indeed you can.
If I used Windows NT Integrated Security, then I should create user accounts at Notebook A? Or Create User Accounts at SQL Server If i used "Used Specific User Name and Password" to Log in ?
If you are in a workgroup the (SQL Server) computers cannot verify the user of another computer as no trust exists between the computers (having the same workgroup name is not a trust). There is a workaround (I would name it hack), to use the same useraccount names and passwords on all computers to logon with Windows Authentication. I would suggest in that case to use SQL Server authentication instead.
"My Intention is If I have 5 PC to log in to Server Automatically whenever they switch on the PC with the VB6 Program executing during start up. It make login to User as transparent as possible."
Use SQL Server logins instead, if you don′t want any user interaction you should use a fixed user name to logon.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.d
Connecting to SQL Server
I installed MSDE today using the setup.exe file, so the syntax was
setup SAPWD=mypassword securitymode=SQL
it worked, I reboot and I see the SQL Server running...
I opened my web matrix, went into the data section and tried to make a new connection to then create databases etc, and it bombs...
I click on SQL Authentication
username sa
password mypassword
and I tried to create a new database
it says either SQL doesn't exsist, or access denied...
any idea's what I did wrong?
Thanks
CadenUPDATE:
I downloaded the new web matrix and everything works just peachy now
Sunday, March 25, 2012
Connecting to SQL or MSDE difficulty !
Hey guys,
I am a newbie here, so please bear with me. I have installed SQL Server 2005 CTP on Machine A and MSDE on Machine B. Both these contain the PUBS database beside others. On Machine C, I have installed "ASP.Net Web Matrix" and I want to be able to connect to either Machine A or B to access the PUBS database. It connects to Machine B, when I put in the Servers IP address. But everytime I try to connect to Machine A, it gives me an error saying, "Unable to connect to the database. To connect to this server you must use SQL Server Management Studio or SQL Server Management objects(SMO) ".
I heard that connection strings are needed to access the SQL Server 2005 but I have no idea where to begin. Do I need to create special users to access the Server or will Windows authentication work ? Could anyone help me out in connecting to the SQL Server 2005 CTP?
|||Try the link below for a walk through tutorial and related link and I would not use SMO (SQL Server Management Object) it is Microsoft property and experience have thought me not to use Microsoft property in my code when using SQL Server. Hope this helps.
http://weblogs.asp.net/scottgu/archive/2005/08/25/423703.aspx|||I tried all that but nothing seems to work. Could the firewall cause a problem ? If yes, then what can I do to rectify it ?|||Yes the firewall usually removes either TCP/IP or Named Pipes from your protocol stack in SQL Server, right click in Management studio and go to properties then Network Configuration and make sure both TCP/IP and Named Pipes is enabled. Hope this helps.|||I get connected to the SQL Server 2000 from a client machine using Web Matrix. I do this by entering the Server name of the SQL Server, say X250-122 and then connecting to a database on that Server. It gives me no problem at all.
When I try the same but in this case trying to connect to an instance of MSDE instead, named NetSDK, i.e. X250-122\NetSDK, on the same Server where SQL Server 2k is installed, then it gives me the following error :
" Unable to connect to the database. SQL Server does not exist or access denied. ConnectionOpen(Connect())".
I tried everything in my capacity that I could but there doesn't seem to be any solution. The protocols ( TCP/IP, Named Pipes) are enabled too. Could you please tell me how to go about this dilemma I am in. Is there a specific way of connecting to an MSDE instance from a client machine ? Please help !!|||The problem was Asp.net account permissions on the MSDE, register it in the full version and go to the security section in Enterprise Manager and configure the server permissions and then to the database and configure the database permissions for Asp.net in the MSDE instance. Another option is to run sp_grantlogin and sp_grantdbaccess in Query Analyzer against the database in the MSDE instance. Hope this helps.
|||I tried doing what you asked and it was already set by default. Ok, let me give you some more details...
I have a local account on each of these machines A, B, C, named say ROOT. SQL Server 2000 and an instance of MSDE named NetSDK is installed on Machine A. All 3 machines have Windows XP Professional with SP 2. Now if I try connecting M/c B or M/c C to the SQL Server on M/c A through the ROOT logins on each of those machines and using ASP.Net Web Matrix, it connects without any problems. But if I do the same trying to connect to NetSDK, it gives me the error I told you about.
I have given ROOT permissions on the SQL Server and the MSDE instance too. But only SQL Server goes through. Thanks for the help, by the way. I appreciate it !!
P.S. By registering the MSDE instance, what did you mean ? I have to register it under Enterprise Manager right ? Because I did that and under Security, there are logins for Machine A\ASPNET, Machine A\ROOT, etc. These are exactly the same as the ones on the SQL Server.
|||Another Problem has just cropped up !! I tried connecting from Machine A to SQL Server 2005 installed on Machine B using the same ROOT login and it didn't work giving me the following error - Unable to connect to the Database. To connect to this Server you must use SQL Server Management Studio or SQL SMO.
But when I tried connecting to Machine B from Query Analyzer i.e. FILE > Connect > Machine B...it works fine. Could you resolve this problem too besides the MSDE one. Thanks !!|||
I am a newbie here, so please bear with me. I have installed SQL Server 2005 CTP on Machine A and MSDE on Machine B. Both these contain the PUBS database beside others. On Machine C, I have installed "ASP.Net Web Matrix" and I want to be able to connect to either Machine A or B to access the PUBS database. It connects to Machine B, when I put in the Servers IP address. But everytime I try to connect to Machine A, it gives me an error saying, "Unable to connect to the database. To connect to this server you must use SQL Server Management Studio or SQL Server Management objects(SMO) ".
I heard that connection strings are needed to access the SQL Server 2005 but I have no idea where to begin. Do I need to create special users to access the Server or will Windows authentication work ? Could anyone help me out in connecting to the SQL Server 2005 CTP?
Management studio is a separate install under management tools, within SQL Server you don't need permissions if you use integrated. When you install the management studio you can register the MSDE. Hope this helps.
|||I had no problems connecting to the MSDE-based server. It's the SQL Server 2005 that's the problem. Could you tell me what I have to do in Management Studio to get the ASP.Net Application that is running on a client machine to connect to it ? Is there some connection string I have to use ? What about this SMO thing ?|||Try the link below for a walk through tutorial and related link and I would not use SMO (SQL Server Management Object) it is Microsoft property and experience have thought me not to use Microsoft property in my code when using SQL Server. Hope this helps.
http://weblogs.asp.net/scottgu/archive/2005/08/25/423703.aspx|||I tried all that but nothing seems to work. Could the firewall cause a problem ? If yes, then what can I do to rectify it ?|||Yes the firewall usually removes either TCP/IP or Named Pipes from your protocol stack in SQL Server, right click in Management studio and go to properties then Network Configuration and make sure both TCP/IP and Named Pipes is enabled. Hope this helps.|||I get connected to the SQL Server 2000 from a client machine using Web Matrix. I do this by entering the Server name of the SQL Server, say X250-122 and then connecting to a database on that Server. It gives me no problem at all.
When I try the same but in this case trying to connect to an instance of MSDE instead, named NetSDK, i.e. X250-122\NetSDK, on the same Server where SQL Server 2k is installed, then it gives me the following error :
" Unable to connect to the database. SQL Server does not exist or access denied. ConnectionOpen(Connect())".
I tried everything in my capacity that I could but there doesn't seem to be any solution. The protocols ( TCP/IP, Named Pipes) are enabled too. Could you please tell me how to go about this dilemma I am in. Is there a specific way of connecting to an MSDE instance from a client machine ? Please help !!|||The problem was Asp.net account permissions on the MSDE, register it in the full version and go to the security section in Enterprise Manager and configure the server permissions and then to the database and configure the database permissions for Asp.net in the MSDE instance. Another option is to run sp_grantlogin and sp_grantdbaccess in Query Analyzer against the database in the MSDE instance. Hope this helps.
|||I tried doing what you asked and it was already set by default. Ok, let me give you some more details...
I have a local account on each of these machines A, B, C, named say ROOT. SQL Server 2000 and an instance of MSDE named NetSDK is installed on Machine A. All 3 machines have Windows XP Professional with SP 2. Now if I try connecting M/c B or M/c C to the SQL Server on M/c A through the ROOT logins on each of those machines and using ASP.Net Web Matrix, it connects without any problems. But if I do the same trying to connect to NetSDK, it gives me the error I told you about.
I have given ROOT permissions on the SQL Server and the MSDE instance too. But only SQL Server goes through. Thanks for the help, by the way. I appreciate it !!
P.S. By registering the MSDE instance, what did you mean ? I have to register it under Enterprise Manager right ? Because I did that and under Security, there are logins for Machine A\ASPNET, Machine A\ROOT, etc. These are exactly the same as the ones on the SQL Server.
|||Another Problem has just cropped up !! I tried connecting from Machine A to SQL Server 2005 installed on Machine B using the same ROOT login and it didn't work giving me the following error - Unable to connect to the Database. To connect to this Server you must use SQL Server Management Studio or SQL SMO.
But when I tried connecting to Machine B from Query Analyzer i.e. FILE > Connect > Machine B...it works fine. Could you resolve this problem too besides the MSDE one. Thanks !!|||
By registering a server you can access all SQL Server in your network as local access and you do that at the very top of Enterprise Manager. What you do under security is creating a user access to the server not server registration. I have registered 68 SQL Servers in one XP pro box so you will not run into problem with the few instances you have. hope this helps.
|||I did register both the SQL Server and the MSDE instance named NetSDK, but just the SQL Server is granting access to users over the network and it's giving the same error as before. Is my way of accessing correct...i.e. say X250-122\NetSDK ?|||I tried this too... I created a user named ASPNET on the SQL Server machine and I granted the user access under EM for the MSDE instance NetSDK on the same machine. Then I tried logging in from another machine through WebMatrix and it logged in only to the SQL Server and not the NetSDK instance, giving me this error...Unable to connect to the database, Login Failed. Not associated with a trusted SQL Server connection. What could be the reason for that. I am getting access through all the accounts to the SQL Server but not the MSDE instance !!|||Create a new database in the MSDE do an INSERT INTO from the old database then create permissions for the Server under the security section for Asp.net and for the database in the database. Then you may have to delete the old database, I think you have run into orphaned permissions that are created in the Master but not usable in the database. Run a search for orphaned permissions in the BOL (books online). Hope this helps.|||Thanks...it works fine now. I appreciate your help !!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
Thursday, March 22, 2012
Connecting to SharePoint MSDE Database
I have a SharePoint server that I want to be able to connect to its database
and pull info off. When I installed the Sharepoint server it installed an
instance of msde. For the life of me I cannot remotely connect to this MSDE
instance. I am able to remotely connect to the backup exec instance on the
same server and I am able to connect to it when logged in locally. I read
somewhere that you can only connect to the default instance of msde, is this
true? If so is there a way to change the sharepoint instance to the default
instance? any suggestions to this would be greatly appreciated.
OK, the error I get when attempting to connect to the sharepoint instance
from computer on LAN on port 1433 is:
SQL server does not exist or access denied
I can connect to Backup Exec instance from same computer on LAN. This
instance uses port 1207
I can connect to Sharepoint instance when logged on locally to the
sharepoint server.
I have port scanned the server and it is listening on port 1207 but not on
port 1433. I can telnet to port 1207 but not to 1433.
I have attempted to change the port # for the sharepoint instance and still
no success. There are no firewalls inbetween the connection.
I am running MSDE for 2000 with sp4 on it
TCP/IP and Named Pipes are enabled on both instances of MSDE.
We are discussing connecting to backupexec instance and linking servers to
sharepoint instance and then pull data off but this is kind of backwards way
of doing this...
"JPD" wrote:
> Hi,
> You should be able to connect to any instance of MSDE, whether or not it
> is a default or named instance. In fact you are already connecting to a
> named instance (the BACKUPEXEC one). Named instances are identified as
> follows:
> server_name\instance_name
> Default instances are identified just by the server (host) name.
> Furthermore you cannot change which instance is the default instance on
> your server. There is no such thing as a DEFAULT property associated
> with an instance. A default instance is one that uses the name of the
> host server. Named instances are a development over SQL Server 7.0 in
> which only one instance could be installed per Windows server. To get
> around this in SQL Server 2000 and later you can install multiple
> instances. You can choose to give them all a unique name or you could
> give up to one instance no name. It assumes the name of the host and is
> called the default instance.
> As far as your problem is concerned, in order to help further you need
> to tell us what error message you are getting when you attempting a
> connection.
> Jonathan
>
> APT SA wrote:
>
sqlsql
and pull info off. When I installed the Sharepoint server it installed an
instance of msde. For the life of me I cannot remotely connect to this MSDE
instance. I am able to remotely connect to the backup exec instance on the
same server and I am able to connect to it when logged in locally. I read
somewhere that you can only connect to the default instance of msde, is this
true? If so is there a way to change the sharepoint instance to the default
instance? any suggestions to this would be greatly appreciated.
OK, the error I get when attempting to connect to the sharepoint instance
from computer on LAN on port 1433 is:
SQL server does not exist or access denied
I can connect to Backup Exec instance from same computer on LAN. This
instance uses port 1207
I can connect to Sharepoint instance when logged on locally to the
sharepoint server.
I have port scanned the server and it is listening on port 1207 but not on
port 1433. I can telnet to port 1207 but not to 1433.
I have attempted to change the port # for the sharepoint instance and still
no success. There are no firewalls inbetween the connection.
I am running MSDE for 2000 with sp4 on it
TCP/IP and Named Pipes are enabled on both instances of MSDE.
We are discussing connecting to backupexec instance and linking servers to
sharepoint instance and then pull data off but this is kind of backwards way
of doing this...
"JPD" wrote:
> Hi,
> You should be able to connect to any instance of MSDE, whether or not it
> is a default or named instance. In fact you are already connecting to a
> named instance (the BACKUPEXEC one). Named instances are identified as
> follows:
> server_name\instance_name
> Default instances are identified just by the server (host) name.
> Furthermore you cannot change which instance is the default instance on
> your server. There is no such thing as a DEFAULT property associated
> with an instance. A default instance is one that uses the name of the
> host server. Named instances are a development over SQL Server 7.0 in
> which only one instance could be installed per Windows server. To get
> around this in SQL Server 2000 and later you can install multiple
> instances. You can choose to give them all a unique name or you could
> give up to one instance no name. It assumes the name of the host and is
> called the default instance.
> As far as your problem is concerned, in order to help further you need
> to tell us what error message you are getting when you attempting a
> connection.
> Jonathan
>
> APT SA wrote:
>
sqlsql
Connecting to SharePoint MSDE Database
I have a SharePoint server that I want to be able to connect to its database
and pull info off. When I installed the Sharepoint server it installed an
instance of msde. For the life of me I cannot remotely connect to this MSDE
instance. I am able to remotely connect to the backup exec instance on the
same server and I am able to connect to it when logged in locally. I read
somewhere that you can only connect to the default instance of msde, is this
true? If so is there a way to change the sharepoint instance to the default
instance? any suggestions to this would be greatly appreciated.Hi,
You should be able to connect to any instance of MSDE, whether or not it
is a default or named instance. In fact you are already connecting to a
named instance (the BACKUPEXEC one). Named instances are identified as
follows:
server_name\instance_name
Default instances are identified just by the server (host) name.
Furthermore you cannot change which instance is the default instance on
your server. There is no such thing as a DEFAULT property associated
with an instance. A default instance is one that uses the name of the
host server. Named instances are a development over SQL Server 7.0 in
which only one instance could be installed per Windows server. To get
around this in SQL Server 2000 and later you can install multiple
instances. You can choose to give them all a unique name or you could
give up to one instance no name. It assumes the name of the host and is
called the default instance.
As far as your problem is concerned, in order to help further you need
to tell us what error message you are getting when you attempting a
connection.
Jonathan
APT SA wrote:
> I have a SharePoint server that I want to be able to connect to its databa
se
> and pull info off. When I installed the Sharepoint server it installed an
> instance of msde. For the life of me I cannot remotely connect to this MS
DE
> instance. I am able to remotely connect to the backup exec instance on th
e
> same server and I am able to connect to it when logged in locally. I read
> somewhere that you can only connect to the default instance of msde, is th
is
> true? If so is there a way to change the sharepoint instance to the defau
lt
> instance? any suggestions to this would be greatly appreciated.|||OK, the error I get when attempting to connect to the sharepoint instance
from computer on LAN on port 1433 is:
SQL server does not exist or access denied
I can connect to Backup Exec instance from same computer on LAN. This
instance uses port 1207
I can connect to Sharepoint instance when logged on locally to the
sharepoint server.
I have port scanned the server and it is listening on port 1207 but not on
port 1433. I can telnet to port 1207 but not to 1433.
I have attempted to change the port # for the sharepoint instance and still
no success. There are no firewalls inbetween the connection.
I am running MSDE for 2000 with sp4 on it
TCP/IP and Named Pipes are enabled on both instances of MSDE.
We are discussing connecting to backupexec instance and linking servers to
sharepoint instance and then pull data off but this is kind of backwards way
of doing this...
"JPD" wrote:
> Hi,
> You should be able to connect to any instance of MSDE, whether or not it
> is a default or named instance. In fact you are already connecting to a
> named instance (the BACKUPEXEC one). Named instances are identified as
> follows:
> server_name\instance_name
> Default instances are identified just by the server (host) name.
> Furthermore you cannot change which instance is the default instance on
> your server. There is no such thing as a DEFAULT property associated
> with an instance. A default instance is one that uses the name of the
> host server. Named instances are a development over SQL Server 7.0 in
> which only one instance could be installed per Windows server. To get
> around this in SQL Server 2000 and later you can install multiple
> instances. You can choose to give them all a unique name or you could
> give up to one instance no name. It assumes the name of the host and is
> called the default instance.
> As far as your problem is concerned, in order to help further you need
> to tell us what error message you are getting when you attempting a
> connection.
> Jonathan
>
> APT SA wrote:
>|||Hi,
Look at the SQL Server error log under c:\program files\microsoft sql
server\mssql\log. The file ERRORLOG should tell you what ip address(es)
and port number(s) the service is listening on. Maybe you could get
more info on what's going wrong in there.
Jonathan
APT SA wrote:[vbcol=seagreen]
> OK, the error I get when attempting to connect to the sharepoint instance
> from computer on LAN on port 1433 is:
> SQL server does not exist or access denied
> I can connect to Backup Exec instance from same computer on LAN. This
> instance uses port 1207
> I can connect to Sharepoint instance when logged on locally to the
> sharepoint server.
> I have port scanned the server and it is listening on port 1207 but not on
> port 1433. I can telnet to port 1207 but not to 1433.
> I have attempted to change the port # for the sharepoint instance and stil
l
> no success. There are no firewalls inbetween the connection.
> I am running MSDE for 2000 with sp4 on it
> TCP/IP and Named Pipes are enabled on both instances of MSDE.
> We are discussing connecting to backupexec instance and linking servers to
> sharepoint instance and then pull data off but this is kind of backwards w
ay
> of doing this...
>
>
> "JPD" wrote:
>
and pull info off. When I installed the Sharepoint server it installed an
instance of msde. For the life of me I cannot remotely connect to this MSDE
instance. I am able to remotely connect to the backup exec instance on the
same server and I am able to connect to it when logged in locally. I read
somewhere that you can only connect to the default instance of msde, is this
true? If so is there a way to change the sharepoint instance to the default
instance? any suggestions to this would be greatly appreciated.Hi,
You should be able to connect to any instance of MSDE, whether or not it
is a default or named instance. In fact you are already connecting to a
named instance (the BACKUPEXEC one). Named instances are identified as
follows:
server_name\instance_name
Default instances are identified just by the server (host) name.
Furthermore you cannot change which instance is the default instance on
your server. There is no such thing as a DEFAULT property associated
with an instance. A default instance is one that uses the name of the
host server. Named instances are a development over SQL Server 7.0 in
which only one instance could be installed per Windows server. To get
around this in SQL Server 2000 and later you can install multiple
instances. You can choose to give them all a unique name or you could
give up to one instance no name. It assumes the name of the host and is
called the default instance.
As far as your problem is concerned, in order to help further you need
to tell us what error message you are getting when you attempting a
connection.
Jonathan
APT SA wrote:
> I have a SharePoint server that I want to be able to connect to its databa
se
> and pull info off. When I installed the Sharepoint server it installed an
> instance of msde. For the life of me I cannot remotely connect to this MS
DE
> instance. I am able to remotely connect to the backup exec instance on th
e
> same server and I am able to connect to it when logged in locally. I read
> somewhere that you can only connect to the default instance of msde, is th
is
> true? If so is there a way to change the sharepoint instance to the defau
lt
> instance? any suggestions to this would be greatly appreciated.|||OK, the error I get when attempting to connect to the sharepoint instance
from computer on LAN on port 1433 is:
SQL server does not exist or access denied
I can connect to Backup Exec instance from same computer on LAN. This
instance uses port 1207
I can connect to Sharepoint instance when logged on locally to the
sharepoint server.
I have port scanned the server and it is listening on port 1207 but not on
port 1433. I can telnet to port 1207 but not to 1433.
I have attempted to change the port # for the sharepoint instance and still
no success. There are no firewalls inbetween the connection.
I am running MSDE for 2000 with sp4 on it
TCP/IP and Named Pipes are enabled on both instances of MSDE.
We are discussing connecting to backupexec instance and linking servers to
sharepoint instance and then pull data off but this is kind of backwards way
of doing this...
"JPD" wrote:
> Hi,
> You should be able to connect to any instance of MSDE, whether or not it
> is a default or named instance. In fact you are already connecting to a
> named instance (the BACKUPEXEC one). Named instances are identified as
> follows:
> server_name\instance_name
> Default instances are identified just by the server (host) name.
> Furthermore you cannot change which instance is the default instance on
> your server. There is no such thing as a DEFAULT property associated
> with an instance. A default instance is one that uses the name of the
> host server. Named instances are a development over SQL Server 7.0 in
> which only one instance could be installed per Windows server. To get
> around this in SQL Server 2000 and later you can install multiple
> instances. You can choose to give them all a unique name or you could
> give up to one instance no name. It assumes the name of the host and is
> called the default instance.
> As far as your problem is concerned, in order to help further you need
> to tell us what error message you are getting when you attempting a
> connection.
> Jonathan
>
> APT SA wrote:
>|||Hi,
Look at the SQL Server error log under c:\program files\microsoft sql
server\mssql\log. The file ERRORLOG should tell you what ip address(es)
and port number(s) the service is listening on. Maybe you could get
more info on what's going wrong in there.
Jonathan
APT SA wrote:[vbcol=seagreen]
> OK, the error I get when attempting to connect to the sharepoint instance
> from computer on LAN on port 1433 is:
> SQL server does not exist or access denied
> I can connect to Backup Exec instance from same computer on LAN. This
> instance uses port 1207
> I can connect to Sharepoint instance when logged on locally to the
> sharepoint server.
> I have port scanned the server and it is listening on port 1207 but not on
> port 1433. I can telnet to port 1207 but not to 1433.
> I have attempted to change the port # for the sharepoint instance and stil
l
> no success. There are no firewalls inbetween the connection.
> I am running MSDE for 2000 with sp4 on it
> TCP/IP and Named Pipes are enabled on both instances of MSDE.
> We are discussing connecting to backupexec instance and linking servers to
> sharepoint instance and then pull data off but this is kind of backwards w
ay
> of doing this...
>
>
> "JPD" wrote:
>
Connecting to Reporting Services Server failed!!!
SQL Server 2005 and SSRS 2005 is curently installed on the same box. The OS is Windows 2003 (S) enterprise edition.
When I connect to the Reporting Services Server using the Sql Server Management studio I get the following error message
The request failed with HTTP status 407: Proxy Authentication Required.
(Microsoft.sqlserver.Management.UI.RSClient)
rsAccessDenied
I am tring to connect using the Windows Admin id. I would like to get an answer from this form.
-Aza
Any body to help here
-Nitu
Connecting to Remote SQL Server
Hi all,
I have been encountering problems in connectiing to an sql server remotely. I have a SQL Server installed on a machine with a public IP. I am, running an application on one of my other Servers having a Public IP as well. Now i want to access the SQL Server Database of my first machine from my second machine, but i cannot get connected to it. I give the IP address of the machine in the connection string but it fails. I have also tried it with the port number. What could possibly be the solution for a problem like this ?
Regards.
Hi there,
Maybe It caused by your windows firewall ! the initial status of Windows Firewall is on.
Check the status by turning off your windows firewall on SQL Server machine.
Babak Izadi
LotraSoft Ltd.
By default, SQL Server 2005 does not allows remote connections. To configure SQL Server 2005 to allow remote connections, complete all the following steps:
1.Select the SQL Server Surface Area Configuration tool from the Configuration Tools and then click Surface Area Configuration for Services and Connections option. expand Database Engine, click Remote Connections, click Local and remote connections, click the appropriate protocol to enable for your environment, and then click Apply and Ok for restarting the Database engine service.
2. Try adding sqlservr.exe (present in MSSQL.1\MSSQL\Binn directory for the default instance and \MSSQL$instance_name\Binn directory for the named instance) in the list of allowed firewall exceptions on the Windows 2003 box.
Regards,
Rajesh
|||Can the two servers ping each other?
from serverA run in a command prompt: "ping serverB"
from serverB run in a command prompt: "ping serverA"
If one of the two fails, you probably have a network problem
Else look at the above post's (Rajesh) instructions
|||Can you check whether there are any issues with WINS issue on the network, ifyou are not able to register with name as explained you might try PING between the boxes and also check the firewall exception in this case to avoid any other barrier.Connecting to remote named instance
Hi,
I need some help connecting to a remote named instance of SQL Server 2000
Lets say the server has fqdn: "sqlsrv1.dk.mydomain.com" and is installed as
a named instance with name: "COPENHAGEN"
Trying to connect from another location using
"sqlsrv1.dk.mydomain.com\COPENHAGEN" will fail, but connecting from the
location in question using "sqlsrv1\COPENHAGEN" will succceed.
How do I do this ?
In advance, thanks...
Soren
Soren,
If the servers are on the same domain, you should be able to connect to the
remote server using
sqlsrv1\COPENHAGEN
Benny
P.S. Where in Denmark
"Soren Staun Jorgensen" <no@.spam.com> skrev i en meddelelse
news:O8BBndMOEHA.1456@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I need some help connecting to a remote named instance of SQL Server 2000
> Lets say the server has fqdn: "sqlsrv1.dk.mydomain.com" and is installed
as
> a named instance with name: "COPENHAGEN"
> Trying to connect from another location using
> "sqlsrv1.dk.mydomain.com\COPENHAGEN" will fail, but connecting from the
> location in question using "sqlsrv1\COPENHAGEN" will succceed.
> How do I do this ?
> In advance, thanks...
> Soren
>
>
|||It might be name resolution problem.
Ping sqlsrv1.dk.mydomain.com\COPENHAGEN
and
Ping sqlsrv1
is it returning the same ip address.
And also check your MDAC version.
Regards.
I need some help connecting to a remote named instance of SQL Server 2000
Lets say the server has fqdn: "sqlsrv1.dk.mydomain.com" and is installed as
a named instance with name: "COPENHAGEN"
Trying to connect from another location using
"sqlsrv1.dk.mydomain.com\COPENHAGEN" will fail, but connecting from the
location in question using "sqlsrv1\COPENHAGEN" will succceed.
How do I do this ?
In advance, thanks...
Soren
Soren,
If the servers are on the same domain, you should be able to connect to the
remote server using
sqlsrv1\COPENHAGEN
Benny
P.S. Where in Denmark
"Soren Staun Jorgensen" <no@.spam.com> skrev i en meddelelse
news:O8BBndMOEHA.1456@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I need some help connecting to a remote named instance of SQL Server 2000
> Lets say the server has fqdn: "sqlsrv1.dk.mydomain.com" and is installed
as
> a named instance with name: "COPENHAGEN"
> Trying to connect from another location using
> "sqlsrv1.dk.mydomain.com\COPENHAGEN" will fail, but connecting from the
> location in question using "sqlsrv1\COPENHAGEN" will succceed.
> How do I do this ?
> In advance, thanks...
> Soren
>
>
|||It might be name resolution problem.
Ping sqlsrv1.dk.mydomain.com\COPENHAGEN
and
Ping sqlsrv1
is it returning the same ip address.
And also check your MDAC version.
Regards.
Connecting to remote named instance
Hi,
I need some help connecting to a remote named instance of SQL Server 2000
Lets say the server has fqdn: "sqlsrv1.dk.mydomain.com" and is installed as
a named instance with name: "COPENHAGEN"
Trying to connect from another location using
"sqlsrv1.dk.mydomain.com\COPENHAGEN" will fail, but connecting from the
location in question using "sqlsrv1\COPENHAGEN" will succceed.
How do I do this '
In advance, thanks...
SorenSoren,
If the servers are on the same domain, you should be able to connect to the
remote server using
sqlsrv1\COPENHAGEN
Benny
P.S. Where in Denmark
"Soren Staun Jorgensen" <no@.spam.com> skrev i en meddelelse
news:O8BBndMOEHA.1456@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I need some help connecting to a remote named instance of SQL Server 2000
> Lets say the server has fqdn: "sqlsrv1.dk.mydomain.com" and is installed
as
> a named instance with name: "COPENHAGEN"
> Trying to connect from another location using
> "sqlsrv1.dk.mydomain.com\COPENHAGEN" will fail, but connecting from the
> location in question using "sqlsrv1\COPENHAGEN" will succceed.
> How do I do this '
> In advance, thanks...
> Soren
>
>|||It might be name resolution problem.
Ping sqlsrv1.dk.mydomain.com\COPENHAGEN
and
Ping sqlsrv1
is it returning the same ip address.
And also check your MDAC version.
Regards.
I need some help connecting to a remote named instance of SQL Server 2000
Lets say the server has fqdn: "sqlsrv1.dk.mydomain.com" and is installed as
a named instance with name: "COPENHAGEN"
Trying to connect from another location using
"sqlsrv1.dk.mydomain.com\COPENHAGEN" will fail, but connecting from the
location in question using "sqlsrv1\COPENHAGEN" will succceed.
How do I do this '
In advance, thanks...
SorenSoren,
If the servers are on the same domain, you should be able to connect to the
remote server using
sqlsrv1\COPENHAGEN
Benny
P.S. Where in Denmark
"Soren Staun Jorgensen" <no@.spam.com> skrev i en meddelelse
news:O8BBndMOEHA.1456@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I need some help connecting to a remote named instance of SQL Server 2000
> Lets say the server has fqdn: "sqlsrv1.dk.mydomain.com" and is installed
as
> a named instance with name: "COPENHAGEN"
> Trying to connect from another location using
> "sqlsrv1.dk.mydomain.com\COPENHAGEN" will fail, but connecting from the
> location in question using "sqlsrv1\COPENHAGEN" will succceed.
> How do I do this '
> In advance, thanks...
> Soren
>
>|||It might be name resolution problem.
Ping sqlsrv1.dk.mydomain.com\COPENHAGEN
and
Ping sqlsrv1
is it returning the same ip address.
And also check your MDAC version.
Regards.
Subscribe to:
Posts (Atom)