cant connect xp pro sp2 to database on ntserver 4

We have a program using sqlserver7, bde 5.01, msde, which works fine on the
98se machines we have connecting to ntserver4, however we got a new xp pro
machine with sp2, I have mapped the exe to the network and it goes to a login
screen, where it then fails to connect to the database with a generic cannot
connect to database error. I have turned the firewall in xp off to see if
that helps, I have also included the exe and the instance of sql server on
the list of exceptions
in the firewall
any ideas what I'm missing?
managed to fix the problem ourselves, looked in the registry settings for
borland, turns out the config file was looking at the server but the dll was
looking locally, so we repointed the dll to the server borland folder and hey
presto program connects and works fine
another side point, I was able to export the borland registry key from a
98se machine into the xp pro machine to enable quick setup of borland on xp
"seatzie" wrote:

> We have a program using sqlserver7, bde 5.01, msde, which works fine on the
> 98se machines we have connecting to ntserver4, however we got a new xp pro
> machine with sp2, I have mapped the exe to the network and it goes to a login
> screen, where it then fails to connect to the database with a generic cannot
> connect to database error. I have turned the firewall in xp off to see if
> that helps, I have also included the exe and the instance of sql server on
> the list of exceptions
> in the firewall
> any ideas what I'm missing?

cant connect xp pro sp2 to database on ntserver 4

We have a program using sqlserver7, bde 5.01, msde, which works fine on the
98se machines we have connecting to ntserver4, however we got a new xp pro
machine with sp2, I have mapped the exe to the network and it goes to a logi
n
screen, where it then fails to connect to the database with a generic cannot
connect to database error. I have turned the firewall in xp off to see if
that helps, I have also included the exe and the instance of sql server on
the list of exceptions
in the firewall
any ideas what I'm missing?managed to fix the problem ourselves, looked in the registry settings for
borland, turns out the config file was looking at the server but the dll was
looking locally, so we repointed the dll to the server borland folder and he
y
presto program connects and works fine
another side point, I was able to export the borland registry key from a
98se machine into the xp pro machine to enable quick setup of borland on xp
"seatzie" wrote:

> We have a program using sqlserver7, bde 5.01, msde, which works fine on th
e
> 98se machines we have connecting to ntserver4, however we got a new xp pro
> machine with sp2, I have mapped the exe to the network and it goes to a lo
gin
> screen, where it then fails to connect to the database with a generic cann
ot
> connect to database error. I have turned the firewall in xp off to see if
> that helps, I have also included the exe and the instance of sql server on
> the list of exceptions
> in the firewall
> any ideas what I'm missing?

Can't connect with Upgrade Advisor

I'm having trouble connecting the Upgrade Advisor to a SQL 2000 box at a client. Here's the setup:

1> I'm running UA on a Virtual PC image

2> I can run UA against other SQL machines on the same domain

3> I can register and administer the SQL server I'm having trouble with in Enterprise Manager

4> I have SA rights on the SQL box I'm having trouble with.

5> The problem is when entering the server name and clicking "detect," it errors out with "The network path not found (mscorlib)."

6> I've tried server name, FQDN and IP address.

This is a fairly convoluted layout, so there could be a firewall issue that I'm not aware of (but I don't think so).

Any help would be appreciated!

Bob

Bob, have you tried running UA directly on the target server? It shouldn't be a problem unless the OS level on the server doesn't support UA.|||

Hey, Allen. Thanks for the feedback...as we discussed Thursday (but I mention here in case anyone else is interested), I don't want to add the .Net Framework to the server at this point.

Bob

Can't connect using management studio while using remote desktop connection on lan.

I get the error message:

An error has occurred 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.

I am not able to find this setting. Could someone please inform me of where to look and maybe what to do?

Thanks in advance.

Start/Programs/Microsoft SQL Server 2005/Configuration Tools/SQL Server Surface Area Configuration Manager/
Click Surface Area Configuration for Services and Connections
Click Database Engines / Remote connections
Select Local and Remote connections and one of the 3 choices below

also make sure the Allow Remote Connection to This Server option is checked on the
Server Properties/Connections page

|||

lkh wrote:

Start/Programs/Microsoft SQL Server 2005/Configuration Tools/SQL Server Surface Area Configuration Manager/
Click Surface Area Configuration for Services and Connections
Click Database Engines / Remote connections
Select Local and Remote connections and one of the 3 choices below

also make sure the Allow Remote Connection to This Server option is checked on the
Server Properties/Connections page

I have found the settings within the configuration tools up to the part where you mention the 3 choices below with success.

The part:
also make sure the Allow Remote Connection to This Server option is checked on the
Server Properties/Connections page

Is that from within the same configuration area or elsewhere?
Thanks so much.|||In Object Explorer in SQL Server Management Studio (SSMS) right click the server, click properties.|||

lkh wrote:

In Object Explorer in SQL Server Management Studio (SSMS) right click the server, click properties.

I'm sorry, there is nothing listed under object explorer pane. I see a default server under database engine in the registered servers pane.

Maybe because I haven't been able to connect yet? I'm not sure where else to look. I'm prolly goofed atm.

Maybe I'll have to do this the normal way and actually connect locally on that computer, then set that setting you mention.

I was hoping I could avoid having to do that, but I will if I have to.|||

right-click the default server, then click Connect/Object Explorer

SQL Server service also has to be started

|||Thanks so much for the help, the second part is already set to allow remote connections.
Turns out the problem I was having was due to my logging in as the second admin account on that pc. I could swear I installed it from that user account but it's acting like I can only connect to SQL via the original account on the pc.
Can't put my finger on it as it's been too long since the install.

Thanks for the help, all's good for now.|||Are you connecting with server\instance?

cant connect to sql server 2005,v9.001314

Hi all,
i have the same problem with connecting to the sql server 2005 version
9.00.1314 ....i m trying from past two days now...i have installed
sql management studio...but everytime i try to connect with it...using
the server name as SHUCHI...it gives me error as:
cannot connect to SHUCHI
additional information: 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)(Microsoft
SQL Server,Error:2)
n in the surface area configuration for services and
connection-localhost wheneva i m clicking on Surface area configuration
it gives me error as:
No sql server 2005 components were found on the specified computer.
either no components are installed,or you are not an administrator on
this computer(SQLSAC)
n i m there in the administrator's group...n i found that in services
for the sql server ...
inside SQL SERVER 2005 SERVICE and SQL SERVER 2005 Network...
there is nothing i mean it says NO ITEMS TO SHOW IN THIS VIEW.....
i really cant understand wats wrong'?CAN YOU PLEASEEEEEEEEEEEEE HELP
MEEEEEEEEEEEEEEEEEE...PLEASEEEEEEEEEEEEEEEEEEEEEEE...i already
installed it thrice....
I will b waiting for your reply...please try to reply ASAP...
shuchi.Are you able to run SQL Server Configuration Manager?
If so, try enabling named pipes.
If that doesn't work, look in Start | Administrative Tools | Services.
Please list all items there that begin with "SQL Server" - that will
let me know which services you have installed.
Andrew Watt
MVP - InfoPath
On 10 Oct 2005 01:27:23 -0700, "Shuch" <ShuchiTandon@.gmail.com> wrote:

>Hi all,
>i have the same problem with connecting to the sql server 2005 version
>9.00.1314 ....i m trying from past two days now...i have installed
>sql management studio...but everytime i try to connect with it...using
>the server name as SHUCHI...it gives me error as:
>cannot connect to SHUCHI
>additional information: 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)(Microsoft
>SQL Server,Error:2)
>n in the surface area configuration for services and
>connection-localhost wheneva i m clicking on Surface area configuration
>it gives me error as:
>No sql server 2005 components were found on the specified computer.
>either no components are installed,or you are not an administrator on
>this computer(SQLSAC)
>n i m there in the administrator's group...n i found that in services
>for the sql server ...
>inside SQL SERVER 2005 SERVICE and SQL SERVER 2005 Network...
>there is nothing i mean it says NO ITEMS TO SHOW IN THIS VIEW.....
>i really cant understand wats wrong'?CAN YOU PLEASEEEEEEEEEEEEE HELP
>MEEEEEEEEEEEEEEEEEE...PLEASEEEEEEEEEEEEEEEEEEEEEEE...i already
>installed it thrice....
>I will b waiting for your reply...please try to reply ASAP...
>shuchi.|||Was this ever resolved. I'm having the same connection issues. Running all
services with all defaults. Named Pipes and TCP/IP both enable on Client an
d
Server.
"Shuch" wrote:

> Hi all,
> i have the same problem with connecting to the sql server 2005 version
> 9.00.1314 ....i m trying from past two days now...i have installed
> sql management studio...but everytime i try to connect with it...using
> the server name as SHUCHI...it gives me error as:
> cannot connect to SHUCHI
> additional information: 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)(Microsoft
> SQL Server,Error:2)
> n in the surface area configuration for services and
> connection-localhost wheneva i m clicking on Surface area configuration
> it gives me error as:
> No sql server 2005 components were found on the specified computer.
> either no components are installed,or you are not an administrator on
> this computer(SQLSAC)
> n i m there in the administrator's group...n i found that in services
> for the sql server ...
> inside SQL SERVER 2005 SERVICE and SQL SERVER 2005 Network...
> there is nothing i mean it says NO ITEMS TO SHOW IN THIS VIEW.....
> i really cant understand wats wrong'?CAN YOU PLEASEEEEEEEEEEEEE HELP
> MEEEEEEEEEEEEEEEEEE...PLEASEEEEEEEEEEEEEEEEEEEEEEE...i already
> installed it thrice....
> I will b waiting for your reply...please try to reply ASAP...
> shuchi.
>

cant connect to sql server 2005,v9.001314

Hi all,
i have the same problem with connecting to the sql server 2005 version
9.00.1314 ....i m trying from past two days now...i have installed
sql management studio...but everytime i try to connect with it...using
the server name as SHUCHI...it gives me error as:
cannot connect to SHUCHI
additional information: 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)(Microsoft
SQL Server,Error:2)
n in the surface area configuration for services and
connection-localhost wheneva i m clicking on Surface area configuration
it gives me error as:
No sql server 2005 components were found on the specified computer.
either no components are installed,or you are not an administrator on
this computer(SQLSAC)
n i m there in the administrator's group...n i found that in services
for the sql server ...
inside SQL SERVER 2005 SERVICE and SQL SERVER 2005 Network...
there is nothing i mean it says NO ITEMS TO SHOW IN THIS VIEW.....
i really cant understand wats wrong??CAN YOU PLEASEEEEEEEEEEEEE HELP
MEEEEEEEEEEEEEEEEEE...PLEASEEEEEEEEEEEEEEEEEEEEEE E...i already
installed it thrice....
I will b waiting for your reply...please try to reply ASAP...
shuchi.
Are you able to run SQL Server Configuration Manager?
If so, try enabling named pipes.
If that doesn't work, look in Start | Administrative Tools | Services.
Please list all items there that begin with "SQL Server" - that will
let me know which services you have installed.
Andrew Watt
MVP - InfoPath
On 10 Oct 2005 01:27:23 -0700, "Shuch" <ShuchiTandon@.gmail.com> wrote:

>Hi all,
>i have the same problem with connecting to the sql server 2005 version
>9.00.1314 ....i m trying from past two days now...i have installed
>sql management studio...but everytime i try to connect with it...using
>the server name as SHUCHI...it gives me error as:
>cannot connect to SHUCHI
>additional information: 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)(Microsoft
>SQL Server,Error:2)
>n in the surface area configuration for services and
>connection-localhost wheneva i m clicking on Surface area configuration
>it gives me error as:
>No sql server 2005 components were found on the specified computer.
>either no components are installed,or you are not an administrator on
>this computer(SQLSAC)
>n i m there in the administrator's group...n i found that in services
>for the sql server ...
>inside SQL SERVER 2005 SERVICE and SQL SERVER 2005 Network...
>there is nothing i mean it says NO ITEMS TO SHOW IN THIS VIEW.....
>i really cant understand wats wrong??CAN YOU PLEASEEEEEEEEEEEEE HELP
>MEEEEEEEEEEEEEEEEEE...PLEASEEEEEEEEEEEEEEEEEEEEE EE...i already
>installed it thrice....
>I will b waiting for your reply...please try to reply ASAP...
>shuchi.
|||Was this ever resolved. I'm having the same connection issues. Running all
services with all defaults. Named Pipes and TCP/IP both enable on Client and
Server.
"Shuch" wrote:

> Hi all,
> i have the same problem with connecting to the sql server 2005 version
> 9.00.1314 ....i m trying from past two days now...i have installed
> sql management studio...but everytime i try to connect with it...using
> the server name as SHUCHI...it gives me error as:
> cannot connect to SHUCHI
> additional information: 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)(Microsoft
> SQL Server,Error:2)
> n in the surface area configuration for services and
> connection-localhost wheneva i m clicking on Surface area configuration
> it gives me error as:
> No sql server 2005 components were found on the specified computer.
> either no components are installed,or you are not an administrator on
> this computer(SQLSAC)
> n i m there in the administrator's group...n i found that in services
> for the sql server ...
> inside SQL SERVER 2005 SERVICE and SQL SERVER 2005 Network...
> there is nothing i mean it says NO ITEMS TO SHOW IN THIS VIEW.....
> i really cant understand wats wrong??CAN YOU PLEASEEEEEEEEEEEEE HELP
> MEEEEEEEEEEEEEEEEEE...PLEASEEEEEEEEEEEEEEEEEEEEEE E...i already
> installed it thrice....
> I will b waiting for your reply...please try to reply ASAP...
> shuchi.
>

Can't connect to SQL Server 2000 with Visual Studio 2005

I've been using Delphi for years (Win 32) and connecting to my SQL Server
databases with no problem.
I am now trying to learn both VB and C#. (Visual studio 2005)
From the Data menu, I select Add New Data Source
I then choose Database
I select Microsoft SQL Server as the Data Source
The Add Connection Dialog appears
It populates the Server name dropdown with both of my SQL servers.
However, when I try to select a database name, the dropdown is never
populated.
If I manually enter a known database name and try to connect, I get a
TimeOut Expired (or server not responding) error.
This happens whether I use windows authentication or SQL server
authentication.
This drill works fine with Delphi (Win 32) and connects without a hitch.
Any help would be appreciated.
Regards,
Dave
Take a look at my connecting whitepaper on my blog. It lays down the basics.
I expect the rights are not setup correctly or you've chosen a server
instance that's not visible on the network.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Dave Davis" <online@.blindsided.org> wrote in message
news:uvZV0Qt3HHA.4400@.TK2MSFTNGP06.phx.gbl...
> I've been using Delphi for years (Win 32) and connecting to my SQL Server
> databases with no problem.
> I am now trying to learn both VB and C#. (Visual studio 2005)
> From the Data menu, I select Add New Data Source
> I then choose Database
> I select Microsoft SQL Server as the Data Source
> The Add Connection Dialog appears
> It populates the Server name dropdown with both of my SQL servers.
> However, when I try to select a database name, the dropdown is never
> populated.
> If I manually enter a known database name and try to connect, I get a
> TimeOut Expired (or server not responding) error.
> This happens whether I use windows authentication or SQL server
> authentication.
> This drill works fine with Delphi (Win 32) and connects without a hitch.
> Any help would be appreciated.
> Regards,
> Dave
>
|||Bill,
Remember, I connect without any problems using Borland's Delphi. I have for
years.
I also connect with no problems using ASP.
If the rights aren't setup properly or the instance wasn't visible on the
network it seems to me that I couldn't connect with anything.
Or, does .net require different rights or something else different in the
SQL server setup?
Thanks,
Dave
"William Vaughn" <billvaNoSPAM@.betav.com> wrote in message
news:elZYHTv3HHA.1484@.TK2MSFTNGP06.phx.gbl...
> Take a look at my connecting whitepaper on my blog. It lays down the
> basics. I expect the rights are not setup correctly or you've chosen a
> server instance that's not visible on the network.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant, Dad, Grandpa
> Microsoft MVP
> INETA Speaker
> www.betav.com
> www.betav.com/blog/billva
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Dave Davis" <online@.blindsided.org> wrote in message
> news:uvZV0Qt3HHA.4400@.TK2MSFTNGP06.phx.gbl...
>

Can't connect to SQL Server 2000 with Visual Studio 2005

I've been using Delphi for years (Win 32) and connecting to my SQL Server
databases with no problem.
I am now trying to learn both VB and C#. (Visual studio 2005)
From the Data menu, I select Add New Data Source
I then choose Database
I select Microsoft SQL Server as the Data Source
The Add Connection Dialog appears
It populates the Server name dropdown with both of my SQL servers.
However, when I try to select a database name, the dropdown is never
populated.
If I manually enter a known database name and try to connect, I get a
TimeOut Expired (or server not responding) error.
This happens whether I use windows authentication or SQL server
authentication.
This drill works fine with Delphi (Win 32) and connects without a hitch.
Any help would be appreciated.
Regards,
DaveTake a look at my connecting whitepaper on my blog. It lays down the basics.
I expect the rights are not setup correctly or you've chosen a server
instance that's not visible on the network.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Dave Davis" <online@.blindsided.org> wrote in message
news:uvZV0Qt3HHA.4400@.TK2MSFTNGP06.phx.gbl...
> I've been using Delphi for years (Win 32) and connecting to my SQL Server
> databases with no problem.
> I am now trying to learn both VB and C#. (Visual studio 2005)
> From the Data menu, I select Add New Data Source
> I then choose Database
> I select Microsoft SQL Server as the Data Source
> The Add Connection Dialog appears
> It populates the Server name dropdown with both of my SQL servers.
> However, when I try to select a database name, the dropdown is never
> populated.
> If I manually enter a known database name and try to connect, I get a
> TimeOut Expired (or server not responding) error.
> This happens whether I use windows authentication or SQL server
> authentication.
> This drill works fine with Delphi (Win 32) and connects without a hitch.
> Any help would be appreciated.
> Regards,
> Dave
>|||Bill,
Remember, I connect without any problems using Borland's Delphi. I have for
years.
I also connect with no problems using ASP.
If the rights aren't setup properly or the instance wasn't visible on the
network it seems to me that I couldn't connect with anything.
Or, does .net require different rights or something else different in the
SQL server setup?
Thanks,
Dave
"William Vaughn" <billvaNoSPAM@.betav.com> wrote in message
news:elZYHTv3HHA.1484@.TK2MSFTNGP06.phx.gbl...
> Take a look at my connecting whitepaper on my blog. It lays down the
> basics. I expect the rights are not setup correctly or you've chosen a
> server instance that's not visible on the network.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant, Dad, Grandpa
> Microsoft MVP
> INETA Speaker
> www.betav.com
> www.betav.com/blog/billva
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "Dave Davis" <online@.blindsided.org> wrote in message
> news:uvZV0Qt3HHA.4400@.TK2MSFTNGP06.phx.gbl...
>

Can't connect to SQL server

Hi,
I'm having trouble connecting to the SQL server in a LAN. I can't even
telnet to the port 1433 of the server. Does anyone have any idea how to fix
this problem?
Shafiee.
Are you able to ping the SQL Server? What error are you getting when you try
connecting to the server using Query Analyzer?
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"shafiee" <mohamed.shafee@.gmail.com> wrote in message
news:Ov0k0dSrFHA.304@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I'm having trouble connecting to the SQL server in a LAN. I can't even
> telnet to the port 1433 of the server. Does anyone have any idea how to
fix
> this problem?
> Shafiee.
>
|||Hi Narayana,
Yes I am able to ping to the server. The server isn't listening to client
requests. The version of SQL server installed is SQL 2000. Any ideas?
Shafiee.
"Narayana Vyas Kondreddi" wrote:

> Are you able to ping the SQL Server? What error are you getting when you try
> connecting to the server using Query Analyzer?
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "shafiee" <mohamed.shafee@.gmail.com> wrote in message
> news:Ov0k0dSrFHA.304@.TK2MSFTNGP11.phx.gbl...
> fix
>
>
|||If SQL Server is running and you can ping the server, one
possibility is that the server is listening on shared memory
only which means only local connections will be allowed. Use
the server network utility on the SQL Server box to make
sure you have protocols enabled. You can also check the SQL
Server error log from when the instance started to see what
protocols, ports SQL Server is listening on. If it's only
Shared Memory, enable TCP/IP on the server using the server
network utility.
-Sue
On Tue, 30 Aug 2005 19:59:04 -0700, "Shafiee"
<Shafiee@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hi Narayana,
>Yes I am able to ping to the server. The server isn't listening to client
>requests. The version of SQL server installed is SQL 2000. Any ideas?
>Shafiee.
>"Narayana Vyas Kondreddi" wrote:

Can't connect to SQL server

Hi,
I'm having trouble connecting to the SQL server in a LAN. I can't even
telnet to the port 1433 of the server. Does anyone have any idea how to fix
this problem?
Shafiee.Are you able to ping the SQL Server? What error are you getting when you try
connecting to the server using Query Analyzer?
--
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"shafiee" <mohamed.shafee@.gmail.com> wrote in message
news:Ov0k0dSrFHA.304@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I'm having trouble connecting to the SQL server in a LAN. I can't even
> telnet to the port 1433 of the server. Does anyone have any idea how to
fix
> this problem?
> Shafiee.
>|||Hi Narayana,
Yes I am able to ping to the server. The server isn't listening to client
requests. The version of SQL server installed is SQL 2000. Any ideas?
Shafiee.
"Narayana Vyas Kondreddi" wrote:

> Are you able to ping the SQL Server? What error are you getting when you t
ry
> connecting to the server using Query Analyzer?
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "shafiee" <mohamed.shafee@.gmail.com> wrote in message
> news:Ov0k0dSrFHA.304@.TK2MSFTNGP11.phx.gbl...
> fix
>
>|||If SQL Server is running and you can ping the server, one
possibility is that the server is listening on shared memory
only which means only local connections will be allowed. Use
the server network utility on the SQL Server box to make
sure you have protocols enabled. You can also check the SQL
Server error log from when the instance started to see what
protocols, ports SQL Server is listening on. If it's only
Shared Memory, enable TCP/IP on the server using the server
network utility.
-Sue
On Tue, 30 Aug 2005 19:59:04 -0700, "Shafiee"
<Shafiee@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hi Narayana,
>Yes I am able to ping to the server. The server isn't listening to client
>requests. The version of SQL server installed is SQL 2000. Any ideas?
>Shafiee.
>"Narayana Vyas Kondreddi" wrote:
>

Can't Connect to Reportserver using Management Studio

Dear Anyone,

I am having trouble connecting to the report server using SQL Server Management studio. Whenever I try to connect to the report server, I get the following error.

Request failed with Http status 502: Bad Gateway. (Microsoft.SQLServer.Management.UI.RSClient

What puzzles me is that I am using the SQL Server Manager on the local server using the local admin account. I've tried connecting to the server using both the server name and the IP address.

Can anyone please help me shed a light to this problem?

Thanks,

Joseph

Did you try connecting using http://servername/reportserver as the server name? Somehow it looks like the WMI instance enumeration is returning an invalid URL to Management Studio.|||Yes, I've tried tried that. I get the same error. Am I missing something?|||

Well, this error is getting returned from the network stack, it's not specific to ReportServer. Are you getting this for all of these?

http://localhost/reportserver

http://servername/reportserver

http://ipaddress/reportserver

And I assume Report Manager is working fine?

|||Brian -

I have a similar issue. and I think it's a WMI issue. How can I reset it or start over with it?

When I try

http://localhost/reportserver

http://servername/reportserver

http://ipaddress/reportserver

I get 5 bars than it hangs. Any ideas
|||i get the same problem, has any of you solved it already?|||I am in a similar situation.

I think the WMI interface is disabled/misconfigured/dead/something. I am trying to create a security extension so reporting services can be added to a current website using the already in place login to handle authentication ( which is it's own set of issues . I had the sample working and then, I assume, something changed and now the sample dies tryign to open the WMI scope. Invalid namespace. I am unable to use SQL Server management Studio ( SSMS ) to connect to the report server

It just says:

Cannot connect to localhost.

Additional Information:
Client found response content type of '', but expected 'text/html'.
The request failed with an empty response. ( Microsoft.SqlServer.Management.UI.RSClient )

How can I check the WMI is running? Configured correctly?

The firewall is turned OFF.

Can't connect to MySQL 2005 Express

I'm trying to upsize an Access database to SQL 2005 Express. When I follow the wizard and I've tried all ways of connecting to the database I get the following error

Connection failed
SQL State '01000'
SQL Server Error 53
[Microsoft] [ODBC SQL Server Driver][DBNETLIB] ConnectionOpen()).
Connection failed
SQL State '08001'
SQL Server Error 17
[Microsoft] [ODBC SQL Server Driver][DBNETLIB] SQL Server does not exist or access denied

I've tried using local host and typing the exact server connection string from the SQL Express Management tool and nothing is working

How come I can't do this? Everyone says this is easy and straight forward -- not for me.

The most common cause of this is using the wrong instance name. SQL Express installs by default to an instance name of SQLEXPRESS that you must specify when connecting. You can not use the machine name alone, or just (local) for example.

When the Upsize wizard asks for the server, specify

<machinename>\SQLEXPRESS

and see how that works.

Regards,

Mike Wachal
SQL Express team

-
Mark the best posts as Answers!

Can't connect remotely to MSDE 2000 DB on WinXP Home Machine

Hi All
Having 'Google-ised' I've found that there does appear to be a problem
connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN), but
I haven't found what the concrete solution is.
It definitely appears to be a Windows inflicted problem, as I can connect to
the DB no problem if I create and connect to the ODBC DSN on the same
machine as the MSDE installation and if I use a remote Apple Mac machine to
connect to it via a combo of a router program and the local ODBC DSN then it
works fine.
I have also eliminated the other possibilities by disabling all of the
firewalls (ie Windows' own and Norton) and ultimately when I put the full
blown version of SQL Server on the same machine the remote connection works
perfectly.
Looking through the sites it appears that you have to put
DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
queries are:
Is it a problem with the original MSDE 2000 installer being installed on a
WinXP SP2 machine or just a later version, ie MSDE SP3?
Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
SP1?
Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE 2000
installer or do you have to update it to Service Pack 3 to perform this
task?
Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
Is there anyway of patching/fixing this installation to correct it or have I
got to de-tach the DBs and re-install MSDE with this
DISABLENETWORKPROTOCOLS=0 switch in the ini?
ThanksHi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/distsql/distsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>|||Hi John
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:O6Rcs%237jFHA.2644@.TK2MSFTNGP09.phx.gbl...
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/distsql/distsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>|||I've just checked the log and it still doesn't state that it's using TCP/IP
even though the network util only has TCP/IP in the right-hand box:
2005-07-25 18:42:40.29 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2005-07-25 18:42:40.60 server SQL Server configured for thread mode
processing.
2005-07-25 18:42:40.60 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2005-07-25 18:42:40.62 spid3 Starting up database 'master'.
2005-07-25 18:42:41.04 server Using 'SSNETLIB.DLL' version '8.0.194'.
2005-07-25 18:42:41.07 spid5 Starting up database 'model'.
2005-07-25 18:42:41.12 spid3 Server name is 'FREDPC'.
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 4
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 5
2005-07-25 18:42:41.35 spid5 Clearing tempdb database.
2005-07-25 18:42:42.54 spid5 Starting up database 'tempdb'.
2005-07-25 18:42:42.65 spid3 Recovery complete.
2005-07-25 18:42:56.09 server SQL server listening on Shared Memory,
Named Pipes. <<<<
2005-07-25 18:42:56.09 server SQL Server is ready for client connections
2005-07-25 18:43:17.17 spid51 Starting up database 'DemoData'.
2005-07-25 19:08:22.85 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
What am I doing wrong?
"Macsicarr" <No3@.Spam67.com> wrote in message
news:ulbflFUkFHA.3164@.TK2MSFTNGP15.phx.gbl...
Hi John
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:O6Rcs%237jFHA.2644@.TK2MSFTNGP09.phx.gbl...
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/distsql/distsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>|||Hi
You need to make sure that TCP/IP is in the client protocols (using the
client network configuration utitilty on the client) as well as on the
server. You may want to try pinging the server from the client. If it
responds try using telnet to connect to the port you are using (the
default port is 1433).
You @.@.VERSION shows that no patches or service packs have been
installed. http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37.
John

Can't Connect or see databases

I am having problem connecting to a database using EM or Query analyzer. Bot
h
applications start up fine. When I click on the database folder to expand it
in EM or the drop down in Query Analyzer, both applications hangs and nothin
g
happens. The SQL services started fine. Please help.
EmmaI just realized that I am only having problem connecting to one particular
db. I can connect to the other db on the server use the USE command in Query
Analyzer. When I try to connect to the offending database, QA just hangs
stating that it is executing query batch...
Any idea how I can correct this problem? The log file for the offending db
is full and I am trying to shrink it using dbcc.
Thenks
Emma
"Emma" wrote:

> I am having problem connecting to a database using EM or Query analyzer. B
oth
> applications start up fine. When I click on the database folder to expand
it
> in EM or the drop down in Query Analyzer, both applications hangs and noth
ing
> happens. The SQL services started fine. Please help.
> Emma
>|||Did you try backing up the log for the offending database
first? You can execute the statement from master.
-Sue
On Tue, 25 Jul 2006 06:59:02 -0700, Emma
<Emma@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I just realized that I am only having problem connecting to one particular
>db. I can connect to the other db on the server use the USE command in Quer
y
>Analyzer. When I try to connect to the offending database, QA just hangs
>stating that it is executing query batch...
>Any idea how I can correct this problem? The log file for the offending db
>is full and I am trying to shrink it using dbcc.
>Thenks
>Emma
>"Emma" wrote:
>