Can't find microsoft.sqlserver.execpackagetaskwrap.dll in Sept CTP

I'm trying to find the following reference for a VS2005 C# project but can't see to locate it on two of my machines which uses Sept CTP install (Ent & Dev) both with SQL2K already installed:

Namespace: Microsoft.SqlServer.Dts.Tasks.ExecutePackageTask
Assembly: Microsoft.SqlServer.ExecPackageTaskWrap (in microsoft.sqlserver.execpackagetaskwrap.dll)

The only thing that I can find is ..\Program Files\Microsoft SQL Server\90\DTS\Binn\ExecPackageTask.dll

Is that the same thing or am I missing something? Thanks.

It's in the GAC.

|||Thanks but I still can't reference it in my C# project. Is it referenceable or use within another namespace?|||

Try this:

Right click References --> Add Reference in your C# project
In Add Reference dialog select Browse page.
In File Name type:

%windir%\assembly\GAC_MSIL\Microsoft.SqlServer.ExecPackageTaskWrap\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.ExecPackageTaskWrap.dll

P.S. You don't need it if you access properties using TaskHost.Properties[]

sql

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?

cant connect to sql server, error

hi if someone could help, i appreciate: i have windows 2003 server and sql server 2000, i have a few machines connected via odbc and seems to work fine, my problem is when i try to make a new connection via odbc, appears: sql server odbc error: ConnectionOpen and server does not exist or access denied, i try few things, make a ping to the server and i got response, check the users and passwords, the mdac, check that the port 1433 is established in the client network utility, etc, now when i do a telnet to the server the port 1433, appears and error: couldnt connect,i believe this is why i cant make a odbc connection, but i cant figure it out how to make the port listens my petitions., now if itsa supossed to be closed, why the others machines cant connect just fine?

Do you already review the firewall for sql server ports?

http://support.microsoft.com/kb/287932/en

Cant connect to SQL server 2000 instance from domain machines

Hi
We currently have installed sql2005 (installed first as default
instance) and sql 2000 with a named instance. When developing sites
and using connection strings, we can access the sql2000 db fine by
using SERVERNAME\INSTANCENAME.
However, if we try to connect via enterprise manager from any other
machine on the domain, we cannot seem to use SERVERNAME\INSTANCENAME
and the instance name alone wont work either.
How do we get round this as at present, we are having to log into the
database server to make any changes etc!!!
Novice here so excuse me if I have missed anything obvious!
Cheers
RajThe easiest workaround would be to connect to the instance using its IP
address followed by a comma and then the port number. You should not use just
hte instance name alone. The SQL Server instance name is not a newtwork name
and won't get resolved to an IP/port number.
Can you connect to the default instance (SQL2005) from a machine where you
can't connect to the SQL2000 instance using ServerName\Instance?
Linchi
"karwalr@.hotmail.com" wrote:
> Hi
> We currently have installed sql2005 (installed first as default
> instance) and sql 2000 with a named instance. When developing sites
> and using connection strings, we can access the sql2000 db fine by
> using SERVERNAME\INSTANCENAME.
> However, if we try to connect via enterprise manager from any other
> machine on the domain, we cannot seem to use SERVERNAME\INSTANCENAME
> and the instance name alone wont work either.
> How do we get round this as at present, we are having to log into the
> database server to make any changes etc!!!
> Novice here so excuse me if I have missed anything obvious!
> Cheers
> Raj
>|||Managed to sort it. I set it up on my client machine Client Network
Alias to map to the server and the port as suggested. Found the
documentation at Microsoft..
http://support.microsoft.com/kb/265808/en-us
Many thanks!

Cant connect to SQL server 2000 instance from domain machines

Hi
We currently have installed sql2005 (installed first as default
instance) and sql 2000 with a named instance. When developing sites
and using connection strings, we can access the sql2000 db fine by
using SERVERNAME\INSTANCENAME.
However, if we try to connect via enterprise manager from any other
machine on the domain, we cannot seem to use SERVERNAME\INSTANCENAME
and the instance name alone wont work either.
How do we get round this as at present, we are having to log into the
database server to make any changes etc!!!
Novice here so excuse me if I have missed anything obvious!
Cheers
RajThe easiest workaround would be to connect to the instance using its IP
address followed by a comma and then the port number. You should not use jus
t
hte instance name alone. The SQL Server instance name is not a newtwork name
and won't get resolved to an IP/port number.
Can you connect to the default instance (SQL2005) from a machine where you
can't connect to the SQL2000 instance using ServerName\Instance?
Linchi
"karwalr@.hotmail.com" wrote:

> Hi
> We currently have installed sql2005 (installed first as default
> instance) and sql 2000 with a named instance. When developing sites
> and using connection strings, we can access the sql2000 db fine by
> using SERVERNAME\INSTANCENAME.
> However, if we try to connect via enterprise manager from any other
> machine on the domain, we cannot seem to use SERVERNAME\INSTANCENAME
> and the instance name alone wont work either.
> How do we get round this as at present, we are having to log into the
> database server to make any changes etc!!!
> Novice here so excuse me if I have missed anything obvious!
> Cheers
> Raj
>|||Managed to sort it. I set it up on my client machine Client Network
Alias to map to the server and the port as suggested. Found the
documentation at Microsoft..
http://support.microsoft.com/kb/265808/en-us
Many thanks!

Can't connect to MSDE

I've got two machines: 1) SBS 2003 Server, and 2) WinXP Pro.
SQL Server 2000 is installed on the server box, as well as MSDE for the default
SharePoint and SbsMonitoring databases (SBS setup created those). The
workstation is running MSDE.
The problem is that I can only connect to the workstation's MSDE from the
workstation. EM on the server can see the MSDE instance (the worksation's
machine name appears in the Add SQL Server Registration dialog box), but that's
as far as it can get. When I try to add the instance under a new registration, I
get 'access denied or server doesn't exist' (paraphrased).
I also can't connect via EM to the workstation's MSDE from within a Win98
VirtualPC instance running on the workstation, although I can connect to the
server's instances (both SQL Server and MSDE instances) from within that
instance.
I've compared the property sheets of all the instances to which I can connect
from WinXP, and everything seems to be the same. Nothing shows up in my ISA
logs, so I don't think packets are being blocked. Just in case I created a
temporary packet filter allowing all packets from anywhere (risky, I know), but
it still didn't work. Still nothing in the logs.
Does anyone know what this might be?
TIA,
Jeff
By default MSDE doesn't listen to any netlibs. On a regular SQL Server, you configure this using
"Server Network Utility". I'm not sure whether such comes with MSDE, but that would be the place to
start. The name of the exe is svrnetcn.exe
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jeff Bowman" <write.to.me@.my.addess.com> wrote in message
news:%23Sv%23zABjFHA.3164@.TK2MSFTNGP15.phx.gbl...
> I've got two machines: 1) SBS 2003 Server, and 2) WinXP Pro.
> SQL Server 2000 is installed on the server box, as well as MSDE for the default SharePoint and
> SbsMonitoring databases (SBS setup created those). The workstation is running MSDE.
> The problem is that I can only connect to the workstation's MSDE from the workstation. EM on the
> server can see the MSDE instance (the worksation's machine name appears in the Add SQL Server
> Registration dialog box), but that's as far as it can get. When I try to add the instance under a
> new registration, I get 'access denied or server doesn't exist' (paraphrased).
> I also can't connect via EM to the workstation's MSDE from within a Win98 VirtualPC instance
> running on the workstation, although I can connect to the server's instances (both SQL Server and
> MSDE instances) from within that instance.
> I've compared the property sheets of all the instances to which I can connect from WinXP, and
> everything seems to be the same. Nothing shows up in my ISA logs, so I don't think packets are
> being blocked. Just in case I created a temporary packet filter allowing all packets from anywhere
> (risky, I know), but it still didn't work. Still nothing in the logs.
> Does anyone know what this might be?
> TIA,
> Jeff
>
>
|||That did the trick, thanks for the tip! :-)
(BTW, Server Network Utility appears to be installed with Client Tools.)
Tibor Karaszi wrote:[vbcol=seagreen]
> By default MSDE doesn't listen to any netlibs. On a regular SQL Server, you
> configure this using "Server Network Utility". I'm not sure whether such
> comes with MSDE, but that would be the place to start. The name of the exe is
> svrnetcn.exe
> "Jeff Bowman" <write.to.me@.my.addess.com> wrote in message
> news:%23Sv%23zABjFHA.3164@.TK2MSFTNGP15.phx.gbl...

Can't connect to MSDE

I've got two machines: 1) SBS 2003 Server, and 2) WinXP Pro.
SQL Server 2000 is installed on the server box, as well as MSDE for the defa
ult
SharePoint and SbsMonitoring databases (SBS setup created those). The
workstation is running MSDE.
The problem is that I can only connect to the workstation's MSDE from the
workstation. EM on the server can see the MSDE instance (the worksation's
machine name appears in the Add SQL Server Registration dialog box), but tha
t's
as far as it can get. When I try to add the instance under a new registratio
n, I
get 'access denied or server doesn't exist' (paraphrased).
I also can't connect via EM to the workstation's MSDE from within a Win98
VirtualPC instance running on the workstation, although I can connect to the
server's instances (both SQL Server and MSDE instances) from within that
instance.
I've compared the property sheets of all the instances to which I can connec
t
from WinXP, and everything seems to be the same. Nothing shows up in my ISA
logs, so I don't think packets are being blocked. Just in case I created a
temporary packet filter allowing all packets from anywhere (risky, I know),
but
it still didn't work. Still nothing in the logs.
Does anyone know what this might be?
TIA,
JeffBy default MSDE doesn't listen to any netlibs. On a regular SQL Server, you
configure this using
"Server Network Utility". I'm not sure whether such comes with MSDE, but tha
t would be the place to
start. The name of the exe is svrnetcn.exe
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jeff Bowman" <write.to.me@.my.addess.com> wrote in message
news:%23Sv%23zABjFHA.3164@.TK2MSFTNGP15.phx.gbl...
> I've got two machines: 1) SBS 2003 Server, and 2) WinXP Pro.
> SQL Server 2000 is installed on the server box, as well as MSDE for the de
fault SharePoint and
> SbsMonitoring databases (SBS setup created those). The workstation is runn
ing MSDE.
> The problem is that I can only connect to the workstation's MSDE from the
workstation. EM on the
> server can see the MSDE instance (the worksation's machine name appears in
the Add SQL Server
> Registration dialog box), but that's as far as it can get. When I try to a
dd the instance under a
> new registration, I get 'access denied or server doesn't exist' (paraphras
ed).
> I also can't connect via EM to the workstation's MSDE from within a Win98
VirtualPC instance
> running on the workstation, although I can connect to the server's instanc
es (both SQL Server and
> MSDE instances) from within that instance.
> I've compared the property sheets of all the instances to which I can conn
ect from WinXP, and
> everything seems to be the same. Nothing shows up in my ISA logs, so I don
't think packets are
> being blocked. Just in case I created a temporary packet filter allowing a
ll packets from anywhere
> (risky, I know), but it still didn't work. Still nothing in the logs.
> Does anyone know what this might be?
> TIA,
> Jeff
>
>|||That did the trick, thanks for the tip! :-)
(BTW, Server Network Utility appears to be installed with Client Tools.)
Tibor Karaszi wrote:[vbcol=seagreen]
> By default MSDE doesn't listen to any netlibs. On a regular SQL Server, yo
u
> configure this using "Server Network Utility". I'm not sure whether such
> comes with MSDE, but that would be the place to start. The name of the exe
is
> svrnetcn.exe
> "Jeff Bowman" <write.to.me@.my.addess.com> wrote in message
> news:%23Sv%23zABjFHA.3164@.TK2MSFTNGP15.phx.gbl...

Can't connect to MSDE

I've got two machines: 1) SBS 2003 Server, and 2) WinXP Pro.
SQL Server 2000 is installed on the server box, as well as MSDE for the default
SharePoint and SbsMonitoring databases (SBS setup created those). The
workstation is running MSDE.
The problem is that I can only connect to the workstation's MSDE from the
workstation. EM on the server can see the MSDE instance (the worksation's
machine name appears in the Add SQL Server Registration dialog box), but that's
as far as it can get. When I try to add the instance under a new registration, I
get 'access denied or server doesn't exist' (paraphrased).
I also can't connect via EM to the workstation's MSDE from within a Win98
VirtualPC instance running on the workstation, although I can connect to the
server's instances (both SQL Server and MSDE instances) from within that
instance.
I've compared the property sheets of all the instances to which I can connect
from WinXP, and everything seems to be the same. Nothing shows up in my ISA
logs, so I don't think packets are being blocked. Just in case I created a
temporary packet filter allowing all packets from anywhere (risky, I know), but
it still didn't work. Still nothing in the logs.
Does anyone know what this might be?
TIA,
JeffBy default MSDE doesn't listen to any netlibs. On a regular SQL Server, you configure this using
"Server Network Utility". I'm not sure whether such comes with MSDE, but that would be the place to
start. The name of the exe is svrnetcn.exe
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jeff Bowman" <write.to.me@.my.addess.com> wrote in message
news:%23Sv%23zABjFHA.3164@.TK2MSFTNGP15.phx.gbl...
> I've got two machines: 1) SBS 2003 Server, and 2) WinXP Pro.
> SQL Server 2000 is installed on the server box, as well as MSDE for the default SharePoint and
> SbsMonitoring databases (SBS setup created those). The workstation is running MSDE.
> The problem is that I can only connect to the workstation's MSDE from the workstation. EM on the
> server can see the MSDE instance (the worksation's machine name appears in the Add SQL Server
> Registration dialog box), but that's as far as it can get. When I try to add the instance under a
> new registration, I get 'access denied or server doesn't exist' (paraphrased).
> I also can't connect via EM to the workstation's MSDE from within a Win98 VirtualPC instance
> running on the workstation, although I can connect to the server's instances (both SQL Server and
> MSDE instances) from within that instance.
> I've compared the property sheets of all the instances to which I can connect from WinXP, and
> everything seems to be the same. Nothing shows up in my ISA logs, so I don't think packets are
> being blocked. Just in case I created a temporary packet filter allowing all packets from anywhere
> (risky, I know), but it still didn't work. Still nothing in the logs.
> Does anyone know what this might be?
> TIA,
> Jeff
>
>|||That did the trick, thanks for the tip! :-)
(BTW, Server Network Utility appears to be installed with Client Tools.)
Tibor Karaszi wrote:
> By default MSDE doesn't listen to any netlibs. On a regular SQL Server, you
> configure this using "Server Network Utility". I'm not sure whether such
> comes with MSDE, but that would be the place to start. The name of the exe is
> svrnetcn.exe
> "Jeff Bowman" <write.to.me@.my.addess.com> wrote in message
> news:%23Sv%23zABjFHA.3164@.TK2MSFTNGP15.phx.gbl...
>> I've got two machines: 1) SBS 2003 Server, and 2) WinXP Pro.
>> SQL Server 2000 is installed on the server box, as well as MSDE for the
>> default SharePoint and SbsMonitoring databases (SBS setup created those).
>> The workstation is running MSDE. The problem is that I can only connect to
>> the workstation's MSDE from the
>> workstation. EM on the server can see the MSDE instance (the worksation's
>> machine name appears in the Add SQL Server Registration dialog box), but
>> that's as far as it can get. When I try to add the instance under a new
>> registration, I get 'access denied or server doesn't exist' (paraphrased). I
>> also can't connect via EM to the workstation's MSDE from within a Win98
>> VirtualPC instance running on the workstation, although I can connect to the
>> server's instances (both SQL Server and MSDE instances) from within that
>> instance. I've compared the property sheets of all the instances to which I
>> can
>> connect from WinXP, and everything seems to be the same. Nothing shows up in
>> my ISA logs, so I don't think packets are being blocked. Just in case I
>> created a temporary packet filter allowing all packets from anywhere (risky,
>> I know), but it still didn't work. Still nothing in the logs. Does anyone
>> know what this might be?
>> TIA,
>> Jeff

Can't connect from Server A to B but B to A

I have two machines with SQL2000 on both machines.
Machine A is a member of the domain, Machine B is in a workgroup with
the same name as the domain.
Using Enterprise manager I can connect from Machine B and manage the
SQL server on machine A.
When trying to connect from Machine A to manage SQL server on Machine
B I get an error 'SQL Server does not exist or access denied'.
I have double checked username/password several times.
Client Network Utility are set to TCP/IP and Named Pipes on both
machines.
Ping works fines. I can also access shared folders from A to B and
vice versa.
What else could be the problem?Can you connect via SQL Login.
If you're connecting via Windows Login, be sure the account has the same
name and password on both side. Also, check to see if BUILTIN\<account> is
allowed access on serverB. If not, take a look at 'sp_grantlogin' in book
online and give it access.
-oj
"Tosch" <tosch_nospam@.swissonline.ch> wrote in message
news:9hbl51pm68gln1gmqp2ckpk5h1d7a5q7r4@.
4ax.com...
>I have two machines with SQL2000 on both machines.
> Machine A is a member of the domain, Machine B is in a workgroup with
> the same name as the domain.
> Using Enterprise manager I can connect from Machine B and manage the
> SQL server on machine A.
> When trying to connect from Machine A to manage SQL server on Machine
> B I get an error 'SQL Server does not exist or access denied'.
> I have double checked username/password several times.
> Client Network Utility are set to TCP/IP and Named Pipes on both
> machines.
> Ping works fines. I can also access shared folders from A to B and
> vice versa.
> What else could be the problem?
>|||I have tried connecting with SQL Login, no luck. I even tried sa and I
could not connect.
On Mon, 11 Apr 2005 13:54:05 -0700, "oj" <nospam_ojngo@.home.com>
wrote:

>Can you connect via SQL Login.
>If you're connecting via Windows Login, be sure the account has the same
>name and password on both side. Also, check to see if BUILTIN\<account> is
>allowed access on serverB. If not, take a look at 'sp_grantlogin' in book
>online and give it access.|||Hi
What happens if you try to do a telnet to server B using the port specified
in server B's TCP/IP Clinet configuration? By doing this, you can determine
if server B listen's properly on the correct port.
Regards
Steen
Tosch wrote:[vbcol=seagreen]
> I have tried connecting with SQL Login, no luck. I even tried sa and I
> could not connect.
>
> On Mon, 11 Apr 2005 13:54:05 -0700, "oj" <nospam_ojngo@.home.com>
> wrote:
>

Can't connect from Server A to B but B to A

I have two machines with SQL2000 on both machines.
Machine A is a member of the domain, Machine B is in a workgroup with
the same name as the domain.
Using Enterprise manager I can connect from Machine B and manage the
SQL server on machine A.
When trying to connect from Machine A to manage SQL server on Machine
B I get an error 'SQL Server does not exist or access denied'.
I have double checked username/password several times.
Client Network Utility are set to TCP/IP and Named Pipes on both
machines.
Ping works fines. I can also access shared folders from A to B and
vice versa.
What else could be the problem?
Can you connect via SQL Login.
If you're connecting via Windows Login, be sure the account has the same
name and password on both side. Also, check to see if BUILTIN\<account> is
allowed access on serverB. If not, take a look at 'sp_grantlogin' in book
online and give it access.
-oj
"Tosch" <tosch_nospam@.swissonline.ch> wrote in message
news:9hbl51pm68gln1gmqp2ckpk5h1d7a5q7r4@.4ax.com...
>I have two machines with SQL2000 on both machines.
> Machine A is a member of the domain, Machine B is in a workgroup with
> the same name as the domain.
> Using Enterprise manager I can connect from Machine B and manage the
> SQL server on machine A.
> When trying to connect from Machine A to manage SQL server on Machine
> B I get an error 'SQL Server does not exist or access denied'.
> I have double checked username/password several times.
> Client Network Utility are set to TCP/IP and Named Pipes on both
> machines.
> Ping works fines. I can also access shared folders from A to B and
> vice versa.
> What else could be the problem?
>
|||I have tried connecting with SQL Login, no luck. I even tried sa and I
could not connect.
On Mon, 11 Apr 2005 13:54:05 -0700, "oj" <nospam_ojngo@.home.com>
wrote:

>Can you connect via SQL Login.
>If you're connecting via Windows Login, be sure the account has the same
>name and password on both side. Also, check to see if BUILTIN\<account> is
>allowed access on serverB. If not, take a look at 'sp_grantlogin' in book
>online and give it access.
|||Hi
What happens if you try to do a telnet to server B using the port specified
in server B's TCP/IP Clinet configuration? By doing this, you can determine
if server B listen's properly on the correct port.
Regards
Steen
Tosch wrote:[vbcol=seagreen]
> I have tried connecting with SQL Login, no luck. I even tried sa and I
> could not connect.
>
> On Mon, 11 Apr 2005 13:54:05 -0700, "oj" <nospam_ojngo@.home.com>
> wrote:

Can't connect from Server A to B but B to A

I have two machines with SQL2000 on both machines.
Machine A is a member of the domain, Machine B is in a workgroup with
the same name as the domain.
Using Enterprise manager I can connect from Machine B and manage the
SQL server on machine A.
When trying to connect from Machine A to manage SQL server on Machine
B I get an error 'SQL Server does not exist or access denied'.
I have double checked username/password several times.
Client Network Utility are set to TCP/IP and Named Pipes on both
machines.
Ping works fines. I can also access shared folders from A to B and
vice versa.
What else could be the problem?Can you connect via SQL Login.
If you're connecting via Windows Login, be sure the account has the same
name and password on both side. Also, check to see if BUILTIN\<account> is
allowed access on serverB. If not, take a look at 'sp_grantlogin' in book
online and give it access.
--
-oj
"Tosch" <tosch_nospam@.swissonline.ch> wrote in message
news:9hbl51pm68gln1gmqp2ckpk5h1d7a5q7r4@.4ax.com...
>I have two machines with SQL2000 on both machines.
> Machine A is a member of the domain, Machine B is in a workgroup with
> the same name as the domain.
> Using Enterprise manager I can connect from Machine B and manage the
> SQL server on machine A.
> When trying to connect from Machine A to manage SQL server on Machine
> B I get an error 'SQL Server does not exist or access denied'.
> I have double checked username/password several times.
> Client Network Utility are set to TCP/IP and Named Pipes on both
> machines.
> Ping works fines. I can also access shared folders from A to B and
> vice versa.
> What else could be the problem?
>|||I have tried connecting with SQL Login, no luck. I even tried sa and I
could not connect.
On Mon, 11 Apr 2005 13:54:05 -0700, "oj" <nospam_ojngo@.home.com>
wrote:
>Can you connect via SQL Login.
>If you're connecting via Windows Login, be sure the account has the same
>name and password on both side. Also, check to see if BUILTIN\<account> is
>allowed access on serverB. If not, take a look at 'sp_grantlogin' in book
>online and give it access.|||Hi
What happens if you try to do a telnet to server B using the port specified
in server B's TCP/IP Clinet configuration? By doing this, you can determine
if server B listen's properly on the correct port.
Regards
Steen
Tosch wrote:
> I have tried connecting with SQL Login, no luck. I even tried sa and I
> could not connect.
>
> On Mon, 11 Apr 2005 13:54:05 -0700, "oj" <nospam_ojngo@.home.com>
> wrote:
>> Can you connect via SQL Login.
>> If you're connecting via Windows Login, be sure the account has the
>> same name and password on both side. Also, check to see if
>> BUILTIN\<account> is allowed access on serverB. If not, take a look
>> at 'sp_grantlogin' in book online and give it access.