network error

Hello,
I get the following error:
Server: Msg 11, Level 16, State 1, Line 1
General network error. Check your network documentation.
Need help.
I have 2 sql server instances on two different machines.
Created a linked serve between SERVE1 and SERVER2.
Tried to run a select query using four-part-naming-convention from server1
to get the query results.
From Server1 ran the following query:
select * from servername2.datbasename.owner.tablename
got the following error message:
Server: Msg 11, Level 16, State 1, Line 1
General network error. Check your network documentation.
Need help to resolve this issue.
Don
Go into Enterprise Manager and click on the linked server. See if you can
see any of the tables. If not, you haven't got the connection setup
correctly. Take the parameters from the linked table and try to connect
with the same authentication in Query Analyzer. Does that work? I'm
assuming you can ping the other server? Also, if the second server is an
instance, let us know if you have "Hide Server" checked in the server
configuration on that server.
"Dony" <donb@.yahoo.com> wrote in message
news:enTc1PMtEHA.1216@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I get the following error:
> Server: Msg 11, Level 16, State 1, Line 1
> General network error. Check your network documentation.
>
> Need help.
> I have 2 sql server instances on two different machines.
> Created a linked serve between SERVE1 and SERVER2.
> Tried to run a select query using four-part-naming-convention from server1
> to get the query results.
> From Server1 ran the following query:
> select * from servername2.datbasename.owner.tablename
> got the following error message:
> Server: Msg 11, Level 16, State 1, Line 1
> General network error. Check your network documentation.
> Need help to resolve this issue.
> Don
>
>

network error

Hello,
> I get the following error:
> Server: Msg 11, Level 16, State 1, Line 1
> General network error. Check your network documentation.
>
> Need help.
> I have 2 sql server instances on two different machines.
> Created a linked serve between SERVE1 and SERVER2.
> Tried to run a select query using four-part-naming-convention from server1
> to get the query results.
> From Server1 ran the following query:
> select * from servername2.datbasename.owner.tablename
> got the following error message:
> Server: Msg 11, Level 16, State 1, Line 1
> General network error. Check your network documentation.
> Need help to resolve this issue.
> Don
>
>
Hi
Check the destination server for login failures.
See if you can run a system stored procedure like sp_who2 against server2.
Regards
Mike
"Dony" wrote:

> Hello,
>
>
>

network error

Hello,
> I get the following error:
> Server: Msg 11, Level 16, State 1, Line 1
> General network error. Check your network documentation.
>
> Need help.
> I have 2 sql server instances on two different machines.
> Created a linked serve between SERVE1 and SERVER2.
> Tried to run a select query using four-part-naming-convention from server1
> to get the query results.
> From Server1 ran the following query:
> select * from servername2.datbasename.owner.tablename
> got the following error message:
> Server: Msg 11, Level 16, State 1, Line 1
> General network error. Check your network documentation.
> Need help to resolve this issue.
> Don
>
>Hi
Check the destination server for login failures.
See if you can run a system stored procedure like sp_who2 against server2.
Regards
Mike
"Dony" wrote:

> Hello,
>
>
>

network error

Hello,
I get the following error:
Server: Msg 11, Level 16, State 1, Line 1
General network error. Check your network documentation.
Need help.
I have 2 sql server instances on two different machines.
Created a linked serve between SERVE1 and SERVER2.
Tried to run a select query using four-part-naming-convention from server1
to get the query results.
From Server1 ran the following query:
select * from servername2.datbasename.owner.tablename
got the following error message:
Server: Msg 11, Level 16, State 1, Line 1
General network error. Check your network documentation.
Need help to resolve this issue.
DonGo into Enterprise Manager and click on the linked server. See if you can
see any of the tables. If not, you haven't got the connection setup
correctly. Take the parameters from the linked table and try to connect
with the same authentication in Query Analyzer. Does that work? I'm
assuming you can ping the other server? Also, if the second server is an
instance, let us know if you have "Hide Server" checked in the server
configuration on that server.
"Dony" <donb@.yahoo.com> wrote in message
news:enTc1PMtEHA.1216@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I get the following error:
> Server: Msg 11, Level 16, State 1, Line 1
> General network error. Check your network documentation.
>
> Need help.
> I have 2 sql server instances on two different machines.
> Created a linked serve between SERVE1 and SERVER2.
> Tried to run a select query using four-part-naming-convention from server1
> to get the query results.
> From Server1 ran the following query:
> select * from servername2.datbasename.owner.tablename
> got the following error message:
> Server: Msg 11, Level 16, State 1, Line 1
> General network error. Check your network documentation.
> Need help to resolve this issue.
> Don
>
>

need urgent help with sa account...

background sql2k on win2k3
i started getting this error msg when accessing properties page of 'sa'
and 'buildin/administrators' accounts in sql.
Error 21776 [SQL-DMO]the name 'dbo' was not found in the Users
Collection. If the name is qualified name,
use [] to separate various parts of the name, and try again.
i previously disabled the sa right for 'buildin/administrators' and now
i can't add the sa rights back to the group because of this err. i
can't modifiy the 'sa' account for the same reason. i tried to delete
'buildin/administrators' group and add it back but now i can't add it
back either.
1. how to add back the 'buildin/administrators' group?
2. how to fix this error? it doesn't happen to other non-sa accounts.
thank you!!What commadn where you executing to add the security group to sql server
again, Where you able to connect anyway (so did you turned on mixed auth. ?)
Jens Suessmeyer.
"=== Steve L ===" <steve.lin@.powells.com> schrieb im Newsbeitrag
news:1114720021.174631.14500@.g14g2000cwa.googlegroups.com...
> background sql2k on win2k3
> i started getting this error msg when accessing properties page of 'sa'
> and 'buildin/administrators' accounts in sql.
> Error 21776 [SQL-DMO]the name 'dbo' was not found in the Users
> Collection. If the name is qualified name,
> use [] to separate various parts of the name, and try again.
> i previously disabled the sa right for 'buildin/administrators' and now
> i can't add the sa rights back to the group because of this err. i
> can't modifiy the 'sa' account for the same reason. i tried to delete
> 'buildin/administrators' group and add it back but now i can't add it
> back either.
> 1. how to add back the 'buildin/administrators' group?
> 2. how to fix this error? it doesn't happen to other non-sa accounts.
> thank you!!
>|||> 1. how to add back the 'buildin/administrators' group?
EXEC sp_grantlogin 'BUILTIN\Administrators'
EXEC sp_addsrvrolemember 'BUILTIN\Administrators', 'symin'

> 2. how to fix this error? it doesn't happen to other non-sa accounts.
This error may be caused by an incorrect database owner in one or more of
your databases. You can correct the owner with sp_changedbowner like the
example below. See http://support.microsoft.com/kb/q218172/ for more
information.
USE MyDatabase
EXEC sp_changedbowner ''MyOwnerLogin'
Hope this helps.
Dan Guzman
SQL Server MVP
"=== Steve L ===" <steve.lin@.powells.com> wrote in message
news:1114720021.174631.14500@.g14g2000cwa.googlegroups.com...
> background sql2k on win2k3
> i started getting this error msg when accessing properties page of 'sa'
> and 'buildin/administrators' accounts in sql.
> Error 21776 [SQL-DMO]the name 'dbo' was not found in the Users
> Collection. If the name is qualified name,
> use [] to separate various parts of the name, and try again.
> i previously disabled the sa right for 'buildin/administrators' and now
> i can't add the sa rights back to the group because of this err. i
> can't modifiy the 'sa' account for the same reason. i tried to delete
> 'buildin/administrators' group and add it back but now i can't add it
> back either.
> 1. how to add back the 'buildin/administrators' group?
> 2. how to fix this error? it doesn't happen to other non-sa accounts.
> thank you!!
>|||Dan, Thanks for saving my day!!! simply executed the two commands you
sent me. 'BUILTIN\Administrators' was back and all the problems
mysteriously went away. i did detach like 8 databases from the other
server and attached to this server before this happened. i think that
might be one of the problems. although i'm not sure in general, who
should be the owner of all the databases in SQL Server land. since my
accout has sa right, quite often it showes i'm the owner of a database,
but sometimes it's sa, and sometimes it's the domain account created
for running the service (with sa privileges).|||I usually specify the 'sa' login as the owner of production databases and
make it a practice to change the owner following a database restore or
attach. This works well when only symin role members can create
dbo-owned objects. In cases where non-symin role members create
dbo-owned objects, you can create a login that is used only for database
ownership.
Hope this helps.
Dan Guzman
SQL Server MVP
"=== Steve L ===" <steve.lin@.powells.com> wrote in message
news:1114788026.433970.131740@.o13g2000cwo.googlegroups.com...
> Dan, Thanks for saving my day!!! simply executed the two commands you
> sent me. 'BUILTIN\Administrators' was back and all the problems
> mysteriously went away. i did detach like 8 databases from the other
> server and attached to this server before this happened. i think that
> might be one of the problems. although i'm not sure in general, who
> should be the owner of all the databases in SQL Server land. since my
> accout has sa right, quite often it showes i'm the owner of a database,
> but sometimes it's sa, and sometimes it's the domain account created
> for running the service (with sa privileges).
>