CONNECT TO SERVER PROBLEM

I am getting this message when trying to connect to SQL SERVER 2005;
An error has occurred while establishing connection to the server.When connecting to SQL Server 2005, this failure may be caused by the fact that under default settings SQL Server does not allow remote connections(provider:shared memory provider , error 40-could not open a connection to SQL Server)(MicrosoftSQL SERVER, Error: 2)
Can anyone help to fix this problem please

Are you using SQL Express? If so, you need to enable remote connections. They are disabled by default.

Thanks,
Sam Lester (MSFT)

|||SQL SERVER 2005, STANDART
|||

On the server execute these statements:

sp_configure 'remote admin connections', 1

go

reconfigure

go

Then you should be able to connect from a client workstation.

Connect to named instance on different domain

I am having trouble connecting to a named instance on a different domain. For example, I am in the domain mydomain.com, the machine is in ops.mydomain.com.

In Query Analyzer I have tried to connect (without success) to:

machinename\instance

machinename

i.p. address

i.p. address\instance

Within the same domain I can successfully connect to

machinename\instance

Any ideas? Also, this machine is part of a cluster...not sure if that matters. I have full permissions to connect to this machine.

ThanksNever mind...the instance was setup to a port different than 1433. We changed it to 1433, rebooted the server, and now I can connect.

One issue though: I can only connect by specifying the i.p. address, i.e.

255.255.255.0\instancename

Using the server name or setting up an alias doesn't seem to work.

Originally posted by banderson
I am having trouble connecting to a named instance on a different domain. For example, I am in the domain mydomain.com, the machine is in ops.mydomain.com.

In Query Analyzer I have tried to connect (without success) to:

machinename\instance

machinename

i.p. address

i.p. address\instance

Within the same domain I can successfully connect to

machinename\instance

Any ideas? Also, this machine is part of a cluster...not sure if that matters. I have full permissions to connect to this machine.

Thanks

Connect to MySQL in SQL Server 2005

I am having trouble connecting to a MySQL database in SQL Server 2005. How can this be done in the easiest fashion?

Dear MattD,

Are you trying to import data from MySql to Sql server 2005?

HTH,

Suprotim Agarwal

|||Moved to SQL Server Data Access.|||

With which functionality are you trying to connect to SQL Server ? DTS / SSIS / Linked Server / Adhoc remote access ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

sqlsql

Connect to MySQL in SQL Server 2005

I am having trouble connecting to a MySQL database in SQL Server 2005. How can this be done in the easiest fashion?

Dear MattD,

Are you trying to import data from MySql to Sql server 2005?

HTH,

Suprotim Agarwal

|||Moved to SQL Server Data Access.|||

With which functionality are you trying to connect to SQL Server ? DTS / SSIS / Linked Server / Adhoc remote access ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

Connect to MSDE file on ISP Server

Are there any articles about connecting a MDB or ADP front-end to a MSDE
database that is located on our ISP's server? When I try to Google the
subject, I get a bazillion hits but non really apply to WAN connections.
Any help or pointers would be appreciated
Paul P
There is nothing special to do when connecting to MSDE over the WAN, all you
have to do is to use the connection parameters given to you by your ISP; the
only condition being that the port 1433 has not been blocked. (Because of
security concerns, more and more ISP are blocking the port 1433 at the
firewall level.)
If you want to have more details for the connection string:
http://www.able-consulting.com/ADO_Conn.htm
http://www.connectionstrings.com/
I suggest that you ask your ISP about this.
S. L.
"Paul Proefrock" <proefrock@.sbcglobal.net> wrote in message
news:OXISVonAFHA.904@.TK2MSFTNGP12.phx.gbl...
> Are there any articles about connecting a MDB or ADP front-end to a MSDE
> database that is located on our ISP's server? When I try to Google the
> subject, I get a bazillion hits but non really apply to WAN connections.
> Any help or pointers would be appreciated
> Paul P
>
|||Hi Sylvain,
I can't connect to MSDE on my ISP also. I just called them (my ISP) and
they informed me that port 1433 was not blocked. I know that the TCP/IP is
enabled on the MSDE and sql server logins are allowed. When I try to
register the msde from my local enterprise manager I can't. Is there
anything else that may cause it to fail that you are aware of? Oh - is there
a way to remotely check to see if 1433 is blocked just in case I was given
bad info?
Thanks in advance, Mike
"Sylvain Lafontaine" wrote:

> There is nothing special to do when connecting to MSDE over the WAN, all you
> have to do is to use the connection parameters given to you by your ISP; the
> only condition being that the port 1433 has not been blocked. (Because of
> security concerns, more and more ISP are blocking the port 1433 at the
> firewall level.)
> If you want to have more details for the connection string:
> http://www.able-consulting.com/ADO_Conn.htm
> http://www.connectionstrings.com/
> I suggest that you ask your ISP about this.
> S. L.
> "Paul Proefrock" <proefrock@.sbcglobal.net> wrote in message
> news:OXISVonAFHA.904@.TK2MSFTNGP12.phx.gbl...
>
>
|||You may try to add the port 1433 after the TCP/IP address (separated by a
comma) and also specify that you want to use the TCP/IP protocol by
explicitely mentionning the DBMSSOCN network library; something like:
Provider=sqloledb;Data Source=190.190.200.100,1433;Network
Library=DBMSSOCN;Initial Catalog=pubs;User ID=sa;Password=asdasd
The Network library was mandatory on Win98, if I remember correctly, but
shouldn't be necessary with WinXP. Also, make sure that you have the latest
service pack applied, as well as MDAC 2.8 (won't hurt). Don't forget to
check for a firewall on your own side.
You can try to ping the remote address on the port 1433. Often, the address
of the SQL-Server is not the same as the address of the web site; because it
is located on another machine than the web server.
Beside that, I don't know.
S. L.
"Michael McTaggart" <Michael McTaggart@.discussions.microsoft.com> wrote in
message news:BC06CED5-780A-4B21-8D40-1C2332D796F6@.microsoft.com...[vbcol=seagreen]
> Hi Sylvain,
> I can't connect to MSDE on my ISP also. I just called them (my ISP) and
> they informed me that port 1433 was not blocked. I know that the TCP/IP
> is
> enabled on the MSDE and sql server logins are allowed. When I try to
> register the msde from my local enterprise manager I can't. Is there
> anything else that may cause it to fail that you are aware of? Oh - is
> there
> a way to remotely check to see if 1433 is blocked just in case I was given
> bad info?
> Thanks in advance, Mike
>
> "Sylvain Lafontaine" wrote:

Connect to enterprise manager

WIthin out network were all having issues connecting to SQL server, e.g. it
would allows connection when we can intermitadley connect.
Are the any know firewall issues or other known bugs?Hi,
Might be because of slow network, Try executing the below command from your
cleint PC
Ping <SQL Server IP Address> -t
If you get contineous "Request time out", then inform ur system / network
admin.
Thanks
Hari
MCDBA
"Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
> WIthin out network were all having issues connecting to SQL server, e.g.
> it
> would allows connection when we can intermitadley connect.
> Are the any know firewall issues or other known bugs?|||Hari,
Seems as if it could be that. DB on on internal netowrk are fine. But the
problem db is with our hositng compnay: we have a 2 Meg brodband line
(operating a 1.6mbit/sec).
Any suggest of what I can say to our hositng company? I know our IP are in
there firewall, and thus sometimes we can connect; would a firewall with an
ISP tend to stop ping's?
Other options could be our router or our ISP.
THanks for you help on this!
regards
MAtthew.
"Hari Prasad" wrote:
> Hi,
> Might be because of slow network, Try executing the below command from your
> cleint PC
> Ping <SQL Server IP Address> -t
> If you get contineous "Request time out", then inform ur system / network
> admin.
> Thanks
> Hari
> MCDBA
> "Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
> message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
> > WIthin out network were all having issues connecting to SQL server, e.g.
> > it
> > would allows connection when we can intermitadley connect.
> >
> > Are the any know firewall issues or other known bugs?
>
>|||Hi Matthew
If you're trying to ping a server at your ISP, it can very well be that they
don't allow pinging. In most cases pinging is blocked from outside a
firewall - not only on ISP's but also on most other companies.
I'd suggest that you call your ISP and talk to them about this issue because
you'd need to have the proper ports open to get into your SQL server. I
don't know if they will allow this or not, but if not you might be able to
do it via a VPN connection.
Regards
Steen
Matthew Burgess wrote:
> Hari,
> Seems as if it could be that. DB on on internal netowrk are fine. But
> the problem db is with our hositng compnay: we have a 2 Meg brodband
> line (operating a 1.6mbit/sec).
> Any suggest of what I can say to our hositng company? I know our IP
> are in there firewall, and thus sometimes we can connect; would a
> firewall with an ISP tend to stop ping's?
> Other options could be our router or our ISP.
> THanks for you help on this!
> regards
> MAtthew.
> "Hari Prasad" wrote:
>> Hi,
>> Might be because of slow network, Try executing the below command
>> from your cleint PC
>> Ping <SQL Server IP Address> -t
>> If you get contineous "Request time out", then inform ur system /
>> network admin.
>> Thanks
>> Hari
>> MCDBA
>> "Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
>> message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
>> WIthin out network were all having issues connecting to SQL server,
>> e.g. it
>> would allows connection when we can intermitadley connect.
>> Are the any know firewall issues or other known bugs?|||I got a similar problem in my network but in my case the network connection
goes well until the user opens Enterprise Manager and start working. In some
moment the network connection is lost, PINGing the server will not respond.
My network is not a slow one. This problems occurs for more than one user.
Will you please indicate me how you resolved the problem or any workaround
for this? I am almost decided to format that server with all the work that it
implies and its impact on my users
Thanks
César
> Hi Matthew
> If you're trying to ping a server at your ISP, it can very well be that they
> don't allow pinging. In most cases pinging is blocked from outside a
> firewall - not only on ISP's but also on most other companies.
> I'd suggest that you call your ISP and talk to them about this issue because
> you'd need to have the proper ports open to get into your SQL server. I
> don't know if they will allow this or not, but if not you might be able to
> do it via a VPN connection.
> Regards
> Steen
>
> Matthew Burgess wrote:
> > Hari,
> >
> > Seems as if it could be that. DB on on internal netowrk are fine. But
> > the problem db is with our hositng compnay: we have a 2 Meg brodband
> > line (operating a 1.6mbit/sec).
> >
> > Any suggest of what I can say to our hositng company? I know our IP
> > are in there firewall, and thus sometimes we can connect; would a
> > firewall with an ISP tend to stop ping's?
> >
> > Other options could be our router or our ISP.
> >
> > THanks for you help on this!
> >
> > regards
> >
> > MAtthew.
> >
> > "Hari Prasad" wrote:
> >
> >> Hi,
> >>
> >> Might be because of slow network, Try executing the below command
> >> from your cleint PC
> >>
> >> Ping <SQL Server IP Address> -t
> >>
> >> If you get contineous "Request time out", then inform ur system /
> >> network admin.
> >>
> >> Thanks
> >> Hari
> >> MCDBA
> >>
> >> "Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
> >> message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
> >> WIthin out network were all having issues connecting to SQL server,
> >> e.g. it
> >> would allows connection when we can intermitadley connect.
> >>
> >> Are the any know firewall issues or other known bugs?
>
>|||I have a similar problem. The network connection is OK but when the user
enters Enterprise manager and starts working with some DTS, the connection
with the server is lost. PINGing the server do not respond. It happens in
more than one user. I have changed the redundant NIC but it remains the same.
Will you please give me a hint how did you manage to solve it or if you
tried any workaround for this?
"Steen Persson" wrote:
> Hi Matthew
> If you're trying to ping a server at your ISP, it can very well be that they
> don't allow pinging. In most cases pinging is blocked from outside a
> firewall - not only on ISP's but also on most other companies.
> I'd suggest that you call your ISP and talk to them about this issue because
> you'd need to have the proper ports open to get into your SQL server. I
> don't know if they will allow this or not, but if not you might be able to
> do it via a VPN connection.
> Regards
> Steen
>
> Matthew Burgess wrote:
> > Hari,
> >
> > Seems as if it could be that. DB on on internal netowrk are fine. But
> > the problem db is with our hositng compnay: we have a 2 Meg brodband
> > line (operating a 1.6mbit/sec).
> >
> > Any suggest of what I can say to our hositng company? I know our IP
> > are in there firewall, and thus sometimes we can connect; would a
> > firewall with an ISP tend to stop ping's?
> >
> > Other options could be our router or our ISP.
> >
> > THanks for you help on this!
> >
> > regards
> >
> > MAtthew.
> >
> > "Hari Prasad" wrote:
> >
> >> Hi,
> >>
> >> Might be because of slow network, Try executing the below command
> >> from your cleint PC
> >>
> >> Ping <SQL Server IP Address> -t
> >>
> >> If you get contineous "Request time out", then inform ur system /
> >> network admin.
> >>
> >> Thanks
> >> Hari
> >> MCDBA
> >>
> >> "Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
> >> message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
> >> WIthin out network were all having issues connecting to SQL server,
> >> e.g. it
> >> would allows connection when we can intermitadley connect.
> >>
> >> Are the any know firewall issues or other known bugs?
>
>

Connect to enterprise manager

WIthin out network were all having issues connecting to SQL server, e.g. it
would allows connection when we can intermitadley connect.
Are the any know firewall issues or other known bugs?
Hi,
Might be because of slow network, Try executing the below command from your
cleint PC
Ping <SQL Server IP Address> -t
If you get contineous "Request time out", then inform ur system / network
admin.
Thanks
Hari
MCDBA
"Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
> WIthin out network were all having issues connecting to SQL server, e.g.
> it
> would allows connection when we can intermitadley connect.
> Are the any know firewall issues or other known bugs?
|||Hari,
Seems as if it could be that. DB on on internal netowrk are fine. But the
problem db is with our hositng compnay: we have a 2 Meg brodband line
(operating a 1.6mbit/sec).
Any suggest of what I can say to our hositng company? I know our IP are in
there firewall, and thus sometimes we can connect; would a firewall with an
ISP tend to stop ping's?
Other options could be our router or our ISP.
THanks for you help on this!
regards
MAtthew.
"Hari Prasad" wrote:

> Hi,
> Might be because of slow network, Try executing the below command from your
> cleint PC
> Ping <SQL Server IP Address> -t
> If you get contineous "Request time out", then inform ur system / network
> admin.
> Thanks
> Hari
> MCDBA
> "Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
> message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
>
>
|||Hi Matthew
If you're trying to ping a server at your ISP, it can very well be that they
don't allow pinging. In most cases pinging is blocked from outside a
firewall - not only on ISP's but also on most other companies.
I'd suggest that you call your ISP and talk to them about this issue because
you'd need to have the proper ports open to get into your SQL server. I
don't know if they will allow this or not, but if not you might be able to
do it via a VPN connection.
Regards
Steen
Matthew Burgess wrote:[vbcol=seagreen]
> Hari,
> Seems as if it could be that. DB on on internal netowrk are fine. But
> the problem db is with our hositng compnay: we have a 2 Meg brodband
> line (operating a 1.6mbit/sec).
> Any suggest of what I can say to our hositng company? I know our IP
> are in there firewall, and thus sometimes we can connect; would a
> firewall with an ISP tend to stop ping's?
> Other options could be our router or our ISP.
> THanks for you help on this!
> regards
> MAtthew.
> "Hari Prasad" wrote:
|||I got a similar problem in my network but in my case the network connection
goes well until the user opens Enterprise Manager and start working. In some
moment the network connection is lost, PINGing the server will not respond.
My network is not a slow one. This problems occurs for more than one user.
Will you please indicate me how you resolved the problem or any workaround
for this? I am almost decided to format that server with all the work that it
implies and its impact on my users
Thanks
César
> Hi Matthew
> If you're trying to ping a server at your ISP, it can very well be that they
> don't allow pinging. In most cases pinging is blocked from outside a
> firewall - not only on ISP's but also on most other companies.
> I'd suggest that you call your ISP and talk to them about this issue because
> you'd need to have the proper ports open to get into your SQL server. I
> don't know if they will allow this or not, but if not you might be able to
> do it via a VPN connection.
> Regards
> Steen
>
> Matthew Burgess wrote:
>
>
|||I have a similar problem. The network connection is OK but when the user
enters Enterprise manager and starts working with some DTS, the connection
with the server is lost. PINGing the server do not respond. It happens in
more than one user. I have changed the redundant NIC but it remains the same.
Will you please give me a hint how did you manage to solve it or if you
tried any workaround for this?
"Steen Persson" wrote:

> Hi Matthew
> If you're trying to ping a server at your ISP, it can very well be that they
> don't allow pinging. In most cases pinging is blocked from outside a
> firewall - not only on ISP's but also on most other companies.
> I'd suggest that you call your ISP and talk to them about this issue because
> you'd need to have the proper ports open to get into your SQL server. I
> don't know if they will allow this or not, but if not you might be able to
> do it via a VPN connection.
> Regards
> Steen
>
> Matthew Burgess wrote:
>
>

Connect to a remote database using QA or EM *WITHOUT* ever creating CNU aliases first? (MS

Accessing a hosting company's MS SQL 2000 server.
I don't have any problems connecting to a remote database with Query
Analyzer (QA) or Enterprise Manager (EM)... as
long as I first create "aliases" using the "client network utility" (CNU).
How would I connect to a remote database using QA or EM *WITHOUT* ever
creating any CNU aliases first?
QA and EM never seem to have a place to enter in the remote SQL machine's IP
address, port number, user name, password, database, etc.
(All the stuff that is needed to connect... that CNU allows me to enter.)
Thanks.
In the server name drop down for connecting with Query
Analyzer, you can type the IP address followed by a comma
and then the listening port. If you select SQL Server
Authentication, you can type a User and Password.
-Sue
On Tue, 27 Mar 2007 00:26:59 -0400, "\"A_Michigan_User\""
<Michigan_RE_M0VE@.ameritech.net> wrote:

>Accessing a hosting company's MS SQL 2000 server.
>I don't have any problems connecting to a remote database with Query
>Analyzer (QA) or Enterprise Manager (EM)... as
>long as I first create "aliases" using the "client network utility" (CNU).
>How would I connect to a remote database using QA or EM *WITHOUT* ever
>creating any CNU aliases first?
>QA and EM never seem to have a place to enter in the remote SQL machine's IP
>address, port number, user name, password, database, etc.
>(All the stuff that is needed to connect... that CNU allows me to enter.)
>Thanks.
>
|||Wow... thanks.
I was thinking that is a drop-down list-box... and that I could NOT type
directly into it... but I can.
I got things working with QA... now I'll have to try EM also.
Thanks again.
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:rm0i039em6h6gtm73mh6qeqij54qpncb52@.4ax.com...
> In the server name drop down for connecting with Query
> Analyzer, you can type the IP address followed by a comma
> and then the listening port. If you select SQL Server
> Authentication, you can type a User and Password.
> -Sue
> On Tue, 27 Mar 2007 00:26:59 -0400, "\"A_Michigan_User\""
> <Michigan_RE_M0VE@.ameritech.net> wrote:
>

Connect SQLRPS2005 to SQL2k DB?

How do I go about connecting SQLRPS2005 in SPS3.0 integration mode to
a SQL2k DB?
(Actually I want to report from a Project server 2003 instance, which
is based on sql2k.
I have SQLRPS2k5 installed on the sharepoint server and have lots of
green ticks for the installation. I have also installed the SPS3.0
plug-in and cofigured its paramters through SPS central.
Then I create a data source within my SPS report libary with:
Data source type: Microsoft SQL Server
connection string: data source=act01projsvr01;initial
catalog=ProjectServer
Credentials: windows integrated
However, when I try to create a report builder model using this data
source I get:
Cannot create a connection to data source 'EPM Pilot.rsds'.
(rsErrorOpeningConnection)
Login failed for user '(null)'. Reason: Not associated with a trusted
SQL Server connection.
So obviously the current users windows credentials are not getting
passed through to the remote SQL server correctly?
Any ideas?It looks like double hop issue. Real (and hard) solution is to use Kerberos.
As workaround, you can try to use stored credentials instead of Windows
Integrated.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"scubaal" <al@.blakes.net> wrote in message
news:1173848679.463141.29360@.n59g2000hsh.googlegroups.com...
> How do I go about connecting SQLRPS2005 in SPS3.0 integration mode to
> a SQL2k DB?
> (Actually I want to report from a Project server 2003 instance, which
> is based on sql2k.
> I have SQLRPS2k5 installed on the sharepoint server and have lots of
> green ticks for the installation. I have also installed the SPS3.0
> plug-in and cofigured its paramters through SPS central.
> Then I create a data source within my SPS report libary with:
> Data source type: Microsoft SQL Server
> connection string: data source=act01projsvr01;initial
> catalog=ProjectServer
> Credentials: windows integrated
> However, when I try to create a report builder model using this data
> source I get:
> Cannot create a connection to data source 'EPM Pilot.rsds'.
> (rsErrorOpeningConnection)
> Login failed for user '(null)'. Reason: Not associated with a trusted
> SQL Server connection.
> So obviously the current users windows credentials are not getting
> passed through to the remote SQL server correctly?
> Any ideas?
>

Connect SQL Server

I have troubles connecting to database now. Anyone please help me!

I connect to SQL Server but I'm not sure I'm doing the right way or not...
I have a table named "t_user" in SQL Server and the fields are
usrid varchar 5
usrpwd varbinary 256

Here is my code :
=================
Dimmyconn As SqlConnection
Dimmycmd As SqlCommand
Dimreader As SqlDataReader
DimstrUsr, strPwd As String

strUsr = txtUsr.Text

myconn = New SqlConnection("server=(local); database=test; user id=myuser; password=mypassword")
mycmd = myconn.CreateCommand()
mycmd.CommandText = "SELECT * FROM t_user WHERE usrid=@.username AND pwdcompare(UPPER(@.password) , usrpwd)=1 "

mycmd.Parameters.Add("@.username", SqlDbType.VarChar, 5).Value = txtUsr.Text
mycmd.Parameters.Add("@.password", SqlDbType.VarChar, 50).Value = txtPwd.Text

myconn.Open()
reader = mycmd.ExecuteReader()

If Not reader.Read() Then
lblMessage.Text = "<font color=red>Invalid username/password (" & strUsr & ")</font>"
Else
Session("invsystem_usr") = reader.GetString(0)
Response.Redirect("../main/main.aspx")

End If

reader.Close()
myconn.Close()
=================Hi,
if i recall clearly it's supposed to be in this format
myconn = New SqlConnection("server=localhost;database=mydatabasename;user id=myuser;password=mypassword")

note that there is no spaces in the string
btw database name is not the name of your table but the name of the database your table in in.
example Northwind|||Thank you :)|||server=(local) works fine. localhost is refered mainly by webserver in my mind so it always looks weird to see it in a connection string. :)

Connect Excel Pivot Table to SQL Server Stored Procedure

Friends,
Hi ...
I have been connecting Excel pivot tables to SQL server tables and views
through an ODBC DSN connection.
I know there is a way to connect a pivot table to a SQL Server stored
procedure, but can't figure it out. The Excel pivot table connection wizard
doesn't seem to offer stored procedures as one of the connection choices.
Anyone out there know how to do this?
Thanks, Bill Morgan
Thanks ...
Hi, again ...
Got answer from SQL Server programmer, and was able to connect Excel pivot
table to SQL Server stored procedure:
In Excel, go to Data \ Get External Data \ New Database Query. Choose SQL
Server connection and then select the appropriate DSN connection to your SQL
Server (and in the DSN options, be sure to set the DSN default to the right
database).
Follow the dialog box prompts. You may not see the right tables/views to
choose from, but select any table in order to keep going through the
successive dialog boxes. When given the choice, you want to "View Data or
Edit Query in Microsoft Query" (dialog box with 3 radio buttons - you want
the middle button in Excel 2000)
When you get to the end of the dialog boxes, go into View/SQL (or click on
SQL icon on the toolbar) and delete the SQL code that is in the SQL box. In
it's place, type EXEC your_database_name.Owner.your_stored_procedure_nam e.
Click OK when the dialog box says you cannot view your query graphically.
Once you see the query result (rows and columns of data) go to File \ Export
results to Excel. Then be sure to check the Pivot Table radio button on the
dialog box that comes up.
The pivot table is refreshable, and as long as the UserName in the DSN has
ReadOnly priveledges (and as long as you have granted EXEC permission on the
stored procedure) you can share the pivot table with other users.
"bill_morgan_3333" wrote:

> Friends,
> Hi ...
> I have been connecting Excel pivot tables to SQL server tables and views
> through an ODBC DSN connection.
> I know there is a way to connect a pivot table to a SQL Server stored
> procedure, but can't figure it out. The Excel pivot table connection wizard
> doesn't seem to offer stored procedures as one of the connection choices.
> Anyone out there know how to do this?
> Thanks, Bill Morgan
> Thanks ...
>

Connect Excel Pivot Table to SQL Server Stored Procedure

Friends,
Hi ...
I have been connecting Excel pivot tables to SQL server tables and views
through an ODBC DSN connection.
I know there is a way to connect a pivot table to a SQL Server stored
procedure, but can't figure it out. The Excel pivot table connection wizard
doesn't seem to offer stored procedures as one of the connection choices.
Anyone out there know how to do this?
Thanks, Bill Morgan
Thanks ...Hi, again ...
Got answer from SQL Server programmer, and was able to connect Excel pivot
table to SQL Server stored procedure:
In Excel, go to Data \ Get External Data \ New Database Query. Choose SQL
Server connection and then select the appropriate DSN connection to your SQL
Server (and in the DSN options, be sure to set the DSN default to the right
database).
Follow the dialog box prompts. You may not see the right tables/views to
choose from, but select any table in order to keep going through the
successive dialog boxes. When given the choice, you want to "View Data or
Edit Query in Microsoft Query" (dialog box with 3 radio buttons - you want
the middle button in Excel 2000)
When you get to the end of the dialog boxes, go into View/SQL (or click on
SQL icon on the toolbar) and delete the SQL code that is in the SQL box. In
it's place, type EXEC your_database_name.Owner.your_stored_procedure_name.
Click OK when the dialog box says you cannot view your query graphically.
Once you see the query result (rows and columns of data) go to File \ Export
results to Excel. Then be sure to check the Pivot Table radio button on the
dialog box that comes up.
The pivot table is refreshable, and as long as the UserName in the DSN has
ReadOnly priveledges (and as long as you have granted EXEC permission on the
stored procedure) you can share the pivot table with other users.
"bill_morgan_3333" wrote:

> Friends,
> Hi ...
> I have been connecting Excel pivot tables to SQL server tables and views
> through an ODBC DSN connection.
> I know there is a way to connect a pivot table to a SQL Server stored
> procedure, but can't figure it out. The Excel pivot table connection wizar
d
> doesn't seem to offer stored procedures as one of the connection choices.
> Anyone out there know how to do this?
> Thanks, Bill Morgan
> Thanks ...
>

Connect Errors

I've seen a similar post here, however my situation is different.

While I am connecting to SQL server 2000 EE from a different client machine using Query Analyzer it gives me the following error message .

Unable to connect to server >
Server : MSG 18452 Level 16 state 1

[Microsoft ODBC ][SQL Server Driver][SQL server]
Login failed for user '(null)' Reason , not associated with a trusted SQL
server connection.

I can connect to two other SQL servers in the same domain just fine with QueryAnalyzer. The machine that I cannot connect to is also my PDC. It is running Win2KSP4, the client is WinXPSP1. I've added and removed the machine from the domain (at my wits end) just to make sure the accounts are not cached. This is the only computer I'm having these client problems with, no matter who logs in.

Any suggestions would be greatly appreciated.Let me add more information.

SQL Server I cannot connect to using Windows Login is also my PDC

I can connect to two other SQL servers that are member servers on the same domain. All servers are running SQL2000EE/SP3a MDAC 2.7SP1 on Win2K, including domain controller.

I can log into the SQL server in question using sa account from the client (which is running XPSP1/SQL2000Tools/MDAC2.7FOR XP.

If I try to add databases using Enterprise Manager from the client, I can add the other two DB servers, however I get the same error when trying to add the SQL server in question.

I'm stumped as the Windows Domain account has to be working as I can authenticate to connect to the domain as well as the other two SQL servers. (I've tried this with a regular user account with SQL rights as well as my domain admin account which has SQL rights.

I can connect to the server in question from any other client in the office using the two windows domain accounts that do not work on the client.

I'd rather not reformat te client and start over as there are other tools (Rational) installed whose license is a real pain to get redone. BTW, all other clients have identical configurations (Rational, etc) which work.

Like I said previously, ANY HELP WOULD BE GREATLY APPRECIATED!
I've tried uninstalling/resinstalling the SQL tools/SP3a, reset the computer domain account (doesn't matter as I can connect to the other two servers), something in the registry etc must have got trashed is all I can figure.|||Go to Client Network Configuration on the client where you can't connect to the server from, remove and then re-add TCP/IP protocol. See if this helps, else - try to use the IP of the server while trying to connect, or, try to create an alias using the same utility.|||OK, tried removing/adding TCP/IP. Same Result.

Tried connecting to the IP address, same result.

Tried Adding alias with auto and manual port 1433, same result.

I can connect with sa however in each of the above instances.

I'm totally stumped, it almost acts like it is not using a domain account, except that it authenticates to the other servers ok.

Thanks for the suggestions, they are appreciated!|||UPDATE:

If I remove all protocols and then go back and re-add NamedPipes, I can login to the problem server from the problem client. Once we go back to TCP/IP, we are back to nothing. I run a trace on the server and it doesn't even show me hitting the server attempting a login until I revert to Named Pipes.

I have no filters or security on the IP settings on the client so it should connect just fine (connects to other two servers using TCP/IP just fine).

Any ideas? I'd like to get back to TCP for the client machine to connect to all three servers.

Thanks again!|||...and of course, if I ask you "Is TCP/IP protocol enabled on the server?" you'll say: "Yes", right?|||TCP is enabled on the server. I've also removed Named Pipes from other clients just to make sure. My other clients can connect to that and all other servers using TCP. The bad client can connect to the other servers using TCP, just not this one.

It has to be the client machine, I just don't know what it is.

Tried reinstalling TCP on client as well, no change.

Personal firewall was deinstalled on client as well.

Thanks,

Phil|||The only other thing I'd suggest (it's kind of primitive) would be to search your client's registry for 1433. Maybe there are some remnants of your "personal firewall" in there that prevent communication with the server...And while you're at it, look for server's name and IP as well. Something has to be burried in there...|||Thanks, I'll double check it.

Get this though, I can telnet to 1433 from the client and connect to the server, however anytime I use TCP on that client, nothing gets through to the SQL trace I'm running on the server.|||That's really odd. Also, see if there is anything going on in Data Sources. Could it be that you have an ODBC data source that has the same server name, but points to something else?|||Checked the ODBC data sources, nothing in there.

Also checked the security options on the client machine, however they are in order as I have group policy on the domain so all computers have same policy.

Thanks again for the suggestions.|||Go to the server. Register it in EM. Right click. Properties. Security Tab. Authentication. Choose SQL Server and Windows. OK.
Go to client. Test it out.|||Already set to both Windows and SQl auth. Double checked it anyway and restarted server. tested with client. Same response.

Like I said before, other clients can connect using TCP and Windows or SQL auth. This client can only connect with TCP using SQL auth. To use Windows auth, I have to use Named Pipes.

Very perplexing. I've enev uininstalled and reinstalled all of the XP network updates as well as the regular networking on the client.

Thanks again,

connect dbase II in ssis

I am having trouble connecting dbf of version dbase II. I can connect dbase III and dbase IV in ssis package,but can't connect dbase II.hope your help!who can help me|||

MS does not support DBBase II with their solution (JET). See the supported versions listed here-

How to use dBASE data with Access and Jet
(http://support.microsoft.com/kb/230125/en-us)

You will need to find a third-party driver, for ODBD, OLE-DB or ADO.Net. Saying that, it is rather old now, and I have never seen one. If you can understand the file format, then you could write your own source and/or connection manager.

|||

liguancong wrote:

I am having trouble connecting dbf of version dbase II. I can connect dbase III and dbase IV in ssis package,but can't connect dbase II.hope your help!

have you tried saving the dbf as a version III or IV file?

Connect at only One port

When connecting to sql 2000 Enterprise manager opens multiple ports.
For example
Proto Local Address Foreign Address State
TCP 192.168.7.12:1433 192.168.7.12:3275 ESTABLISHED
TCP 192.168.7.12:1433 192.168.7.12:3634 ESTABLISHED
TCP 192.168.7.12:3634 192.168.7.12:1433 ESTABLISHED
How can I force sql to connect only at 1433 or other single port. I facts
is there such posibility?
Hi -
If you analyze the entries in the SQL Server error log file, you can verify
that the instance of SQL Server is listening on the correct IP address and on
the correct port. By default, a default instance of SQL Server listens on the
port 1433. You can also use Server Network Utility to verify the protocol
settings for SQL Server and to change the properties in SQL Server, including
the protocols that can connect to SQL Server and the ports that can be used.
For more information about using Server Network Utility, see the "SQL Server
Network Utility" topic in SQL Server Books Online.
Sometimes, SQL Server 2000 may not bind to port 1433 or any other specified
port. This problem may occur if the port is being used by another application
or if you are trying to connect by using an IP address that is not correct.
Therefore, the TCP/IP connections to SQL Server may not be successful and you
may receive the following error message in the SQL Server error log file:
2001-11-14 15:49:14.12 server SuperSocket Info: Bind failed on TCP port 1433.
Please check the below link :
http://support.microsoft.com/default.aspx?kbid=307197
Let me know if it helps you.
"Radin" wrote:

> When connecting to sql 2000 Enterprise manager opens multiple ports.
> For example
> Proto Local Address Foreign Address State
> TCP 192.168.7.12:1433 192.168.7.12:3275 ESTABLISHED
> TCP 192.168.7.12:1433 192.168.7.12:3634 ESTABLISHED
> TCP 192.168.7.12:3634 192.168.7.12:1433 ESTABLISHED
> How can I force sql to connect only at 1433 or other single port. I facts
> is there such posibility?
>

Connect at only One port

When connecting to sql 2000 Enterprise manager opens multiple ports.
For example
Proto Local Address Foreign Address State
TCP 192.168.7.12:1433 192.168.7.12:3275 ESTABLISHED
TCP 192.168.7.12:1433 192.168.7.12:3634 ESTABLISHED
TCP 192.168.7.12:3634 192.168.7.12:1433 ESTABLISHED
How can I force sql to connect only at 1433 or other single port. I facts
is there such posibility?Hi -
If you analyze the entries in the SQL Server error log file, you can verify
that the instance of SQL Server is listening on the correct IP address and o
n
the correct port. By default, a default instance of SQL Server listens on th
e
port 1433. You can also use Server Network Utility to verify the protocol
settings for SQL Server and to change the properties in SQL Server, includin
g
the protocols that can connect to SQL Server and the ports that can be used.
For more information about using Server Network Utility, see the "SQL Server
Network Utility" topic in SQL Server Books Online.
Sometimes, SQL Server 2000 may not bind to port 1433 or any other specified
port. This problem may occur if the port is being used by another applicatio
n
or if you are trying to connect by using an IP address that is not correct.
Therefore, the TCP/IP connections to SQL Server may not be successful and yo
u
may receive the following error message in the SQL Server error log file:
2001-11-14 15:49:14.12 server SuperSocket Info: Bind failed on TCP port 1433
.
Please check the below link :
http://support.microsoft.com/default.aspx?kbid=307197
Let me know if it helps you.
"Radin" wrote:

> When connecting to sql 2000 Enterprise manager opens multiple ports.
> For example
> Proto Local Address Foreign Address State
> TCP 192.168.7.12:1433 192.168.7.12:3275 ESTABLISHED
> TCP 192.168.7.12:1433 192.168.7.12:3634 ESTABLISHED
> TCP 192.168.7.12:3634 192.168.7.12:1433 ESTABLISHED
> How can I force sql to connect only at 1433 or other single port. I facts
> is there such posibility?
>

Configuring users

Hi,
I am connecting to sql server 2000 from an Access 2000 project. I want to
have certain users edit a stored procedure. I can give them execute
permission but this doesn't allow them edit. I don't want to give them owner
permissions on the sp.
How do I allow them edit this sp only?
Thanks
Tom
Currently only the owner, the DB owner or someone with system administration
permissions can alter an sp...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Tom Swanick" <tom.swanick@.activant.com> wrote in message
news:OFRuinn5EHA.2876@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I am connecting to sql server 2000 from an Access 2000 project. I want to
> have certain users edit a stored procedure. I can give them execute
> permission but this doesn't allow them edit. I don't want to give them
owner
> permissions on the sp.
> How do I allow them edit this sp only?
> Thanks
> Tom
>
|||Or db_ddladmin; however, this will also give them edit permissions on all
objects in the database.
Sincerely,
Anthony Thomas

"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:eIaw0Jp5EHA.1408@.TK2MSFTNGP10.phx.gbl...
Currently only the owner, the DB owner or someone with system administration
permissions can alter an sp...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Tom Swanick" <tom.swanick@.activant.com> wrote in message
news:OFRuinn5EHA.2876@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I am connecting to sql server 2000 from an Access 2000 project. I want to
> have certain users edit a stored procedure. I can give them execute
> permission but this doesn't allow them edit. I don't want to give them
owner
> permissions on the sp.
> How do I allow them edit this sp only?
> Thanks
> Tom
>

Configuring users

Hi,
I am connecting to sql server 2000 from an Access 2000 project. I want to
have certain users edit a stored procedure. I can give them execute
permission but this doesn't allow them edit. I don't want to give them owner
permissions on the sp.
How do I allow them edit this sp only?
Thanks
TomCurrently only the owner, the DB owner or someone with system administration
permissions can alter an sp...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Tom Swanick" <tom.swanick@.activant.com> wrote in message
news:OFRuinn5EHA.2876@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I am connecting to sql server 2000 from an Access 2000 project. I want to
> have certain users edit a stored procedure. I can give them execute
> permission but this doesn't allow them edit. I don't want to give them
owner
> permissions on the sp.
> How do I allow them edit this sp only?
> Thanks
> Tom
>|||Or db_ddladmin; however, this will also give them edit permissions on all
objects in the database.
Sincerely,
Anthony Thomas
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:eIaw0Jp5EHA.1408@.TK2MSFTNGP10.phx.gbl...
Currently only the owner, the DB owner or someone with system administration
permissions can alter an sp...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Tom Swanick" <tom.swanick@.activant.com> wrote in message
news:OFRuinn5EHA.2876@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I am connecting to sql server 2000 from an Access 2000 project. I want to
> have certain users edit a stored procedure. I can give them execute
> permission but this doesn't allow them edit. I don't want to give them
owner
> permissions on the sp.
> How do I allow them edit this sp only?
> Thanks
> Tom
>

Configuring SQL Server Express 2005 for Remote Access

Hello All
In the course of another thread I posted a question regarding problems
connecting to SQL Server Express 2005. The fundamental issue is that
SQL Server Express does not have remote access enabled by default.
Enabling it is a multi-step process.
I expect this will be a common problem given the popularity of the
(free) SQL Server Express so as a thank you for the help I have
received in resolving the issue, I have built a web page documenting
the steps involved.
http://www.datamasker.com/SSE2005_NetworkCfg.htm
Cheers
Dale
#####
The connectivity problems manifest themselves as the following error
messages (I list them here so online searches might pick up this
thread).
SQL Network Interfaces, error: 26 - Error Locating Server/Instance
Specified
An error has occured while establishing a
connection to the server. When connecting to SQL Server 2005,this
failure may be caused by the fact that under the default settings SQL
Server does not allow remote connections.(provider:Named Pipes
Provider,error:40-Could not open connection to SQL Server))
Server does not exist or access deniedPerfect timing.. This is great.. it helped me out big-time.. thanksa again..
"NoSpam@.NoSpam.com" wrote:
> Hello All
> In the course of another thread I posted a question regarding problems
> connecting to SQL Server Express 2005. The fundamental issue is that
> SQL Server Express does not have remote access enabled by default.
> Enabling it is a multi-step process.
> I expect this will be a common problem given the popularity of the
> (free) SQL Server Express so as a thank you for the help I have
> received in resolving the issue, I have built a web page documenting
> the steps involved.
> http://www.datamasker.com/SSE2005_NetworkCfg.htm
> Cheers
> Dale
> #####
> The connectivity problems manifest themselves as the following error
> messages (I list them here so online searches might pick up this
> thread).
> SQL Network Interfaces, error: 26 - Error Locating Server/Instance
> Specified
> An error has occured while establishing a
> connection to the server. When connecting to SQL Server 2005,this
> failure may be caused by the fact that under the default settings SQL
> Server does not allow remote connections.(provider:Named Pipes
> Provider,error:40-Could not open connection to SQL Server))
> Server does not exist or access denied
>|||Hi, how do I make sure everything sql server needs to have installed is
installed when I sign into suface area configuration and click add services
and connections I get a message that says no sql server components are
install or not under admin acssess. I am prety sure they are installed and
also that I am admin but for some strange reaosn I get this silly message.
*sigh* I would like to simply switch to express version of vs2005 hoping that
its easyer for newbies.