Can't find odbcping.exe

I am trying to troubleshoot a SQL Server connection from my home machine
to an instance of SQL server running on my client's network using
Enterprise Manger and I am going through the steps in the MS KB article
How to troubleshoot connectivity issues in SQL Server 2000,
http://support.microsoft.com/default...;en-us;827422, which
suggests using odbcping.exe.
However, I cannot find this in my local SQL Server directories or in the
server Sql Server directories.
Doe anyone know where it is?
It's not installed by default with SQL 2000. The utility can
be found in the \x86\Binn directory on the SQL Server 2000
CD.
-Sue
On Sun, 12 Dec 2004 00:05:34 -0500, Douglas Forrest
<dforrest@.optonline.net> wrote:

>I am trying to troubleshoot a SQL Server connection from my home machine
>to an instance of SQL server running on my client's network using
>Enterprise Manger and I am going through the steps in the MS KB article
>How to troubleshoot connectivity issues in SQL Server 2000,
>http://support.microsoft.com/default...;en-us;827422, which
>suggests using odbcping.exe.
>However, I cannot find this in my local SQL Server directories or in the
>server Sql Server directories.
>Doe anyone know where it is?
|||Sue Hoegemeier wrote:
> It's not installed by default with SQL 2000. The utility can
> be found in the \x86\Binn directory on the SQL Server 2000
> CD.
> -Sue
> On Sun, 12 Dec 2004 00:05:34 -0500, Douglas Forrest
> <dforrest@.optonline.net> wrote:
>
>
Thanks

can't disable a job in sql2k

Hi all,
I have a job in sql2k box. After the box network name changed. I can't do
any modification to that job anymore.
It says, error 14274 can't update, add or delete a job(or steps or schedule)
that originated from an MSX server.the job was not saved.
ThanksThis problem could be attributable to the originating_server now differing
from the actual server name.
UPDATE msdb..sysjobs SET Originating_Server = Servername
The Microsoft KBase resolution is here :-
http://support.microsoft.com/defaul...b;en-us;Q281642
HTH. Ryan
"mecn" <mecn2002@.yahoo.com> wrote in message
news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or
> schedule) that originated from an MSX server.the job was not saved.
> Thanks
>|||Thats an easy one:
http://support.microsoft.com/defaul...kb;en-us;281642
HTH, jens Suessmeyer.|||It worked.
Thanks lot.
MECN
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:%23g%235A3sEGHA.216@.TK2MSFTNGP15.phx.gbl...
> This problem could be attributable to the originating_server now differing
> from the actual server name.
> UPDATE msdb..sysjobs SET Originating_Server = Servername
> The Microsoft KBase resolution is here :-
> http://support.microsoft.com/defaul...b;en-us;Q281642
> --
> HTH. Ryan
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
>|||In addition to the other posts:
http://www.karaszi.com/SQLServer/in...server_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mecn" <mecn2002@.yahoo.com> wrote in message news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...[v
bcol=seagreen]
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or schedul
e)
> that originated from an MSX server.the job was not saved.
> Thanks
>[/vbcol]

can't disable a job in sql2k

Hi all,
I have a job in sql2k box. After the box network name changed. I can't do
any modification to that job anymore.
It says, error 14274 can't update, add or delete a job(or steps or schedule)
that originated from an MSX server.the job was not saved.
Thanks
This problem could be attributable to the originating_server now differing
from the actual server name.
UPDATE msdb..sysjobs SET Originating_Server = Servername
The Microsoft KBase resolution is here :-
http://support.microsoft.com/default...;en-us;Q281642
HTH. Ryan
"mecn" <mecn2002@.yahoo.com> wrote in message
news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or
> schedule) that originated from an MSX server.the job was not saved.
> Thanks
>
|||Thats an easy one:
http://support.microsoft.com/default...b;en-us;281642
HTH, jens Suessmeyer.
|||It worked.
Thanks lot.
MECN
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:%23g%235A3sEGHA.216@.TK2MSFTNGP15.phx.gbl...
> This problem could be attributable to the originating_server now differing
> from the actual server name.
> UPDATE msdb..sysjobs SET Originating_Server = Servername
> The Microsoft KBase resolution is here :-
> http://support.microsoft.com/default...;en-us;Q281642
> --
> HTH. Ryan
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
>
|||In addition to the other posts:
http://www.karaszi.com/SQLServer/inf...erver_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mecn" <mecn2002@.yahoo.com> wrote in message news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or schedule)
> that originated from an MSX server.the job was not saved.
> Thanks
>

can't disable a job in sql2k

Hi all,
I have a job in sql2k box. After the box network name changed. I can't do
any modification to that job anymore.
It says, error 14274 can't update, add or delete a job(or steps or schedule)
that originated from an MSX server.the job was not saved.
ThanksThis problem could be attributable to the originating_server now differing
from the actual server name.
UPDATE msdb..sysjobs SET Originating_Server = Servername
The Microsoft KBase resolution is here :-
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q281642
--
HTH. Ryan
"mecn" <mecn2002@.yahoo.com> wrote in message
news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or
> schedule) that originated from an MSX server.the job was not saved.
> Thanks
>|||Thats an easy one:
http://support.microsoft.com/default.aspx?scid=kb;en-us;281642
HTH, jens Suessmeyer.|||It worked.
Thanks lot.
MECN
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:%23g%235A3sEGHA.216@.TK2MSFTNGP15.phx.gbl...
> This problem could be attributable to the originating_server now differing
> from the actual server name.
> UPDATE msdb..sysjobs SET Originating_Server = Servername
> The Microsoft KBase resolution is here :-
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q281642
> --
> HTH. Ryan
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
>> Hi all,
>> I have a job in sql2k box. After the box network name changed. I can't do
>> any modification to that job anymore.
>> It says, error 14274 can't update, add or delete a job(or steps or
>> schedule) that originated from an MSX server.the job was not saved.
>> Thanks
>|||In addition to the other posts:
http://www.karaszi.com/SQLServer/info_change_server_name.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mecn" <mecn2002@.yahoo.com> wrote in message news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or schedule)
> that originated from an MSX server.the job was not saved.
> Thanks
>

Can't copy databases across network with copy wizard

I am having trouble copying a database across a network using the copy database wizard.
I am receiving the following error:
'Your SQL Server Service is running under the local system account. You need to change your SQL Server Service account to have the rights to copy files over the network.'
I have gone into services and set up the appropriate account to log unto the network servers with system admin priviledges but this does not solve the problem. Any step by step help would be appreciated.
Regards
You would need to change the destination server to run under
a domain account. Then you need to restart SQL service.
The configuration requirements for using the copy database
wizard can be found in the following article:
INF: Understanding and Troubleshooting the Copy Database
Wizard in SQL Server 2000
http://support.microsoft.com/?id=274463
-Sue
On Wed, 14 Apr 2004 11:26:05 -0700, "JackO"
<anonymous@.discussions.microsoft.com> wrote:

>I am having trouble copying a database across a network using the copy database wizard.
>I am receiving the following error:
>'Your SQL Server Service is running under the local system account. You need to change your SQL Server Service account to have the rights to copy files over the network.'
>I have gone into services and set up the appropriate account to log unto the network servers with system admin priviledges but this does not solve the problem. Any step by step help would be appreciated.
>Regards
|||JackO
Sue answered you correctly. However you will have good results also if you are just willing to take the DB offline temporarily and copy over the files. Then you can attach the DB at the destination. This can be done without shutting down either server.
Jeff
|||Or...you can just backup and restore to the other server.
Nothing is offline, restarted, etc.
-Sue
On Wed, 14 Apr 2004 11:26:05 -0700, "JackO"
<anonymous@.discussions.microsoft.com> wrote:

>I am having trouble copying a database across a network using the copy database wizard.
>I am receiving the following error:
>'Your SQL Server Service is running under the local system account. You need to change your SQL Server Service account to have the rights to copy files over the network.'
>I have gone into services and set up the appropriate account to log unto the network servers with system admin priviledges but this does not solve the problem. Any step by step help would be appreciated.
>Regards

Can't copy databases across network with copy wizard

I am having trouble copying a database across a network using the copy database wizard
I am receiving the following error
'Your SQL Server Service is running under the local system account. You need to change your SQL Server Service account to have the rights to copy files over the network.
I have gone into services and set up the appropriate account to log unto the network servers with system admin priviledges but this does not solve the problem. Any step by step help would be appreciated
RegardsYou would need to change the destination server to run under
a domain account. Then you need to restart SQL service.
The configuration requirements for using the copy database
wizard can be found in the following article:
INF: Understanding and Troubleshooting the Copy Database
Wizard in SQL Server 2000
http://support.microsoft.com/?id=274463
-Sue
On Wed, 14 Apr 2004 11:26:05 -0700, "JackO"
<anonymous@.discussions.microsoft.com> wrote:
>I am having trouble copying a database across a network using the copy database wizard.
>I am receiving the following error:
>'Your SQL Server Service is running under the local system account. You need to change your SQL Server Service account to have the rights to copy files over the network.'
>I have gone into services and set up the appropriate account to log unto the network servers with system admin priviledges but this does not solve the problem. Any step by step help would be appreciated.
>Regards|||Or...you can just backup and restore to the other server.
Nothing is offline, restarted, etc.
-Sue
On Wed, 14 Apr 2004 11:26:05 -0700, "JackO"
<anonymous@.discussions.microsoft.com> wrote:
>I am having trouble copying a database across a network using the copy database wizard.
>I am receiving the following error:
>'Your SQL Server Service is running under the local system account. You need to change your SQL Server Service account to have the rights to copy files over the network.'
>I have gone into services and set up the appropriate account to log unto the network servers with system admin priviledges but this does not solve the problem. Any step by step help would be appreciated.
>Regards

Can't copy databases across network with copy wizard

I am having trouble copying a database across a network using the copy datab
ase wizard.
I am receiving the following error:
'Your SQL Server Service is running under the local system account. You need
to change your SQL Server Service account to have the rights to copy files
over the network.'
I have gone into services and set up the appropriate account to log unto the
network servers with system admin priviledges but this does not solve the p
roblem. Any step by step help would be appreciated.
RegardsYou would need to change the destination server to run under
a domain account. Then you need to restart SQL service.
The configuration requirements for using the copy database
wizard can be found in the following article:
INF: Understanding and Troubleshooting the Copy Database
Wizard in SQL Server 2000
http://support.microsoft.com/?id=274463
-Sue
On Wed, 14 Apr 2004 11:26:05 -0700, "JackO"
<anonymous@.discussions.microsoft.com> wrote:

>I am having trouble copying a database across a network using the copy data
base wizard.
>I am receiving the following error:
>'Your SQL Server Service is running under the local system account. You nee
d to change your SQL Server Service account to have the rights to copy files
over the network.'
>I have gone into services and set up the appropriate account to log unto th
e network servers with system admin priviledges but this does not solve the
problem. Any step by step help would be appreciated.
>Regards|||JackO
Sue answered you correctly. However you will have good results also if you
are just willing to take the DB offline temporarily and copy over the files.
Then you can attach the DB at the destination. This can be done without s
hutting down either server.
Jeff|||Or...you can just backup and restore to the other server.
Nothing is offline, restarted, etc.
-Sue
On Wed, 14 Apr 2004 11:26:05 -0700, "JackO"
<anonymous@.discussions.microsoft.com> wrote:

>I am having trouble copying a database across a network using the copy data
base wizard.
>I am receiving the following error:
>'Your SQL Server Service is running under the local system account. You nee
d to change your SQL Server Service account to have the rights to copy files
over the network.'
>I have gone into services and set up the appropriate account to log unto th
e network servers with system admin priviledges but this does not solve the
problem. Any step by step help would be appreciated.
>Regards

Can''t Connect to SQl via Windows NT Network

Help!

I'm writing some VB.net 2005 windows applications which connect to various tables within SQL Server 2005.

If my programs are running from C drive, I have no problems connecting to my database.

but if i run my exe file from a network drive, then the SQL server doesnt recognise the user's pc, and wont allow my program to access any data.

Can anyone help me with this problem?

What is the exact error message you came across?

Can you answer the question according to the following guidance?

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=362498&SiteID=1

Good Luck!

Ming.

|||I guess you are receiving exception due to security restrictions, right ? This is caused by the CAS defined for network locations making it not possible to use all applications / assemblies from network ressources.

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

The problem was solved by adding a strong name when publishing the program.

cant connect to server from another machine

Hi Friends
I have a sql server (2005 standard edition) on Win xp machine. i can connect to this server from my machine ok but others on the network try to connect i get following error

"An error has occurred during report processing.
Cannot create a connection to data source 'dataSource1'.
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. 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: 0 - No process is on the other end of the pipe.) "

but my remote connection allows remote connects. i also enabled "Named pipes" and "VIA" protocols under sql configuration manager but no avail.
any ideas on this one.
Thanks for your help.

Cheersyou need to config to enable this via surface area config tool|||Thanks for that and actually i tried that too but no avail.|||

Try disabling VIA, and restarting the SQL Server.

|||Peter
VIA is already disabled|||i also have sqlexpress on the same machine ,does it make any difference ?
BTW i stoped sqlexpress service but still made no difference!|||

The error you get most frequently indicates that TCP and/or Named Pipes are not enabled on the target SQL Server 2005.

The first thing is to make sure that these protocols are enables, and then restart the target SQL Server.

If you have SQL Server 2005 client tools installed on the remote client machine you can test the connection over TCP and Named Pipes, resp., by running the following commands:

sqlcmd -E -Stcp:<targetServer>

or

sqlcmd -E -Snp:<targetServer>

Notes:

- the switches -E -S are case sensitive, and must be in capital letters

- replace <targetMachine> with the name of the machine running the target SQL Server 2005.

If you still get errors their text may be helpful in troubleshooting further.

|||Peter
Thank you very much for your help.those 2 commands really helped.

first command (uses tcp) it connected ok but 2nd command(using np) gave an error.
so on target server i enabled Named pipes and restarted server and tried to connect again from remote machine and guess what it connect nicely. and now i can connect to target server from my report manager page also which was originally giving problem.
Thanks again for your help :)

one question remained though we've another sql server on a different machine which has too only TCP/IP enabled but all other PCs in the network able to connect without any problem!!

why my PC was any different ?
Thanks|||

How does your application specify the server in the connection string?

If it uses an alias, does the alias specify Named Pipes as the protocol? Is there any chance the connection string specifies the Named Pipes protocol through the "Network Library" or "Net" property, e.g. as "Network Library=dbnmpntw"?

|||Peter
here my application is Report Manager page (http://localhost/reportserver) and connection does not specify any protocols.

we installed sql server with default settings so i dont think there is any alias|||

I have had identical connection problem problems. The two commands are extremely helpful for diagnosis. I wish I had known them earlier. Thank you!

No matter what I try (enabling, disabling, stopping, restarting, ...), I cannot get TCP work, but the name pipes can be made work easily and I can certainly live with it.

hz

|||

Hi all

I am fascinated by this discussion. I have had similar problems.

I have access to 100 computers in the university library on the same network. Each pc is running Windows XP and has a copy os SQL Server 2005 installed (the full version and express).

I am manually connecting servers (but would love to know how to in T-SQL as well ;-)). A friend has helped me before, and we disabled Named Pipes and enabled TCPIP on some of the computers. We were then able to use the wizzard to connect these computers. I am using SQL Server Authentication, and each database, and all connections are using the same login, and I have set this up to have server role "svsadmin".

Unfortunately this does not work now. I have followed the instructions suggested above (and enabled both TCPIP and Named Pipes), and now, while I am able to connect the servers on different machines, the connected server does not have an icon that indicates that it is either

* started (green triangle) or

* stopped (red triangle)

but an empty little circle at the base of the satabase cream cylinder

I hope I have given the right amount of info.

Thanks in advance.

Greg

|||

Greg

did you mean ,you cant see whether "server" running or not ?

if so "sql server configuration manager" under configuration tools you should be able to see whether sql server running or not.

BTW if you dont use sqlexpress i suggest you uninstall it as it resolved many issues for me.i guess sql server 2005 and sqlexpress conflicting each other!

|||

Hi

Thanks for the response.

I have uninstalled SQL Server Express on 2 of the machines.

The servers are running - I'm sure of that, but unbelievably slowly. I have been able to view (in SQL Server Managment Studio) the contents of tables on either the local or networked server. (The server status is still being denoted by the empty white disc superimposed on the yellow server cylinder...)

So they must be running right? The SQL Server Configuration Manager agrees - but to me the server manager is telling me that the server is running locally, which is the case. The problem relates to the connected database...

Despite deleting the database, unfortunately still getting this unusual situation. I'm able to explore a database on either server from either computer once I have connected the servers. But unfortunately I can not use T-SQL to input into a table on the networked server. (I am using sp_addlinkedserver to link the server successfully.)

Could the problem be a network setting, and if so, what should I ask the network administrator to change?

Thanks

Greg

|||

am out of ideas on this Greg.

BTW after uninstalling sqlexpress have you restarted machines ?

if not give it a try and see .

cant connect to server from another machine

Hi Friends
I have a sql server (2005 standard edition) on Win xp machine. i can connect to this server from my machine ok but others on the network try to connect i get following error

"An error has occurred during report processing.
Cannot create a connection to data source 'dataSource1'.
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. 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: 0 - No process is on the other end of the pipe.) "

but my remote connection allows remote connects. i also enabled "Named pipes" and "VIA" protocols under sql configuration manager but no avail.
any ideas on this one.
Thanks for your help.

Cheersyou need to config to enable this via surface area config tool|||Thanks for that and actually i tried that too but no avail.|||

Try disabling VIA, and restarting the SQL Server.

|||Peter
VIA is already disabled|||i also have sqlexpress on the same machine ,does it make any difference ?
BTW i stoped sqlexpress service but still made no difference!|||

The error you get most frequently indicates that TCP and/or Named Pipes are not enabled on the target SQL Server 2005.

The first thing is to make sure that these protocols are enables, and then restart the target SQL Server.

If you have SQL Server 2005 client tools installed on the remote client machine you can test the connection over TCP and Named Pipes, resp., by running the following commands:

sqlcmd -E -Stcp:<targetServer>

or

sqlcmd -E -Snp:<targetServer>

Notes:

- the switches -E -S are case sensitive, and must be in capital letters

- replace <targetMachine> with the name of the machine running the target SQL Server 2005.

If you still get errors their text may be helpful in troubleshooting further.

|||Peter
Thank you very much for your help.those 2 commands really helped.

first command (uses tcp) it connected ok but 2nd command(using np) gave an error.
so on target server i enabled Named pipes and restarted server and tried to connect again from remote machine and guess what it connect nicely. and now i can connect to target server from my report manager page also which was originally giving problem.
Thanks again for your help :)

one question remained though we've another sql server on a different machine which has too only TCP/IP enabled but all other PCs in the network able to connect without any problem!!

why my PC was any different ?
Thanks|||

How does your application specify the server in the connection string?

If it uses an alias, does the alias specify Named Pipes as the protocol? Is there any chance the connection string specifies the Named Pipes protocol through the "Network Library" or "Net" property, e.g. as "Network Library=dbnmpntw"?

|||Peter
here my application is Report Manager page (http://localhost/reportserver) and connection does not specify any protocols.

we installed sql server with default settings so i dont think there is any alias|||

I have had identical connection problem problems. The two commands are extremely helpful for diagnosis. I wish I had known them earlier. Thank you!

No matter what I try (enabling, disabling, stopping, restarting, ...), I cannot get TCP work, but the name pipes can be made work easily and I can certainly live with it.

hz

|||

Hi all

I am fascinated by this discussion. I have had similar problems.

I have access to 100 computers in the university library on the same network. Each pc is running Windows XP and has a copy os SQL Server 2005 installed (the full version and express).

I am manually connecting servers (but would love to know how to in T-SQL as well ;-)). A friend has helped me before, and we disabled Named Pipes and enabled TCPIP on some of the computers. We were then able to use the wizzard to connect these computers. I am using SQL Server Authentication, and each database, and all connections are using the same login, and I have set this up to have server role "svsadmin".

Unfortunately this does not work now. I have followed the instructions suggested above (and enabled both TCPIP and Named Pipes), and now, while I am able to connect the servers on different machines, the connected server does not have an icon that indicates that it is either

* started (green triangle) or

* stopped (red triangle)

but an empty little circle at the base of the satabase cream cylinder

I hope I have given the right amount of info.

Thanks in advance.

Greg

|||

Greg

did you mean ,you cant see whether "server" running or not ?

if so "sql server configuration manager" under configuration tools you should be able to see whether sql server running or not.

BTW if you dont use sqlexpress i suggest you uninstall it as it resolved many issues for me.i guess sql server 2005 and sqlexpress conflicting each other!

|||

Hi

Thanks for the response.

I have uninstalled SQL Server Express on 2 of the machines.

The servers are running - I'm sure of that, but unbelievably slowly. I have been able to view (in SQL Server Managment Studio) the contents of tables on either the local or networked server. (The server status is still being denoted by the empty white disc superimposed on the yellow server cylinder...)

So they must be running right? The SQL Server Configuration Manager agrees - but to me the server manager is telling me that the server is running locally, which is the case. The problem relates to the connected database...

Despite deleting the database, unfortunately still getting this unusual situation. I'm able to explore a database on either server from either computer once I have connected the servers. But unfortunately I can not use T-SQL to input into a table on the networked server. (I am using sp_addlinkedserver to link the server successfully.)

Could the problem be a network setting, and if so, what should I ask the network administrator to change?

Thanks

Greg

|||

am out of ideas on this Greg.

BTW after uninstalling sqlexpress have you restarted machines ?

if not give it a try and see .

Can't connect to server - real newbie here

SLQ 2000, Win XP Pro network
I installed SQL (developer) 2000 on an XP Pro running SP2 (firewall turned
off)
The SQL server seems to be running fine in that I can access the default
tables from the local computer. The problem is, I can't connect to the SLQ
Server from another XP Pro client computer using Enterprise Manager. That
is, I can't register it. I get a "server does not exist" error.
I've tried both Windows authentication and SQL Server authentication. To
use SQL auth. I'm assuming that all I have to do is create a new login on
the server, which I have done. I've made sure this login is an administrator
with ownership and public rights to each database.
What else should I check or setup?
All help greatly appreciated!!Karl wrote:
> SLQ 2000, Win XP Pro network
> I installed SQL (developer) 2000 on an XP Pro running SP2 (firewall
> turned off)
> The SQL server seems to be running fine in that I can access the
> default tables from the local computer. The problem is, I can't
> connect to the SLQ Server from another XP Pro client computer using
> Enterprise Manager. That is, I can't register it. I get a "server
> does not exist" error.
> I've tried both Windows authentication and SQL Server authentication.
> To use SQL auth. I'm assuming that all I have to do is create a new
> login on the server, which I have done. I've made sure this login is
> an administrator with ownership and public rights to each database.
> What else should I check or setup?
> All help greatly appreciated!!
What name are you using for the SQL Server? Can you see the other PC on
the network. Try using the IP address in case the name is not resolving
properly.
--
David Gugick
Imceda Software
www.imceda.com|||Thank you for the reply.
As it turns out, I was trying this on a new installation of XP Pro running
SP 2 as I mentioned. As soon as I updated SQL 2000 with its service pack 3,
I was able to connect to the server from the client computers. Leave it to
my 14 year old son to suggest this solution. :-)
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:eR5zVb84EHA.3596@.TK2MSFTNGP12.phx.gbl...
> Karl wrote:
> > SLQ 2000, Win XP Pro network
> >
> > I installed SQL (developer) 2000 on an XP Pro running SP2 (firewall
> > turned off)
> >
> > The SQL server seems to be running fine in that I can access the
> > default tables from the local computer. The problem is, I can't
> > connect to the SLQ Server from another XP Pro client computer using
> > Enterprise Manager. That is, I can't register it. I get a "server
> > does not exist" error.
> >
> > I've tried both Windows authentication and SQL Server authentication.
> > To use SQL auth. I'm assuming that all I have to do is create a new
> > login on the server, which I have done. I've made sure this login is
> > an administrator with ownership and public rights to each database.
> >
> > What else should I check or setup?
> >
> > All help greatly appreciated!!
> What name are you using for the SQL Server? Can you see the other PC on
> the network. Try using the IP address in case the name is not resolving
> properly.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>