I have 2 sql servers running on different machines. I want to manage both
servers from one machine. When I try to add the other server in the
enterprise manager it gives me the error "sql server does not exist or access
denied". I am using a valid log on user name that is set up on the server, I
have even tried using a windows username. I know that the problem has to lie
in authentication because I know the server exist. Anyone know of anything I
may be doing wrong?"Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> I have 2 sql servers running on different machines. I want to manage both
> servers from one machine. When I try to add the other server in the
> enterprise manager it gives me the error "sql server does not exist or
access
> denied". I am using a valid log on user name that is set up on the
server, I
> have even tried using a windows username. I know that the problem has to
lie
> in authentication because I know the server exist. Anyone know of
anything I
> may be doing wrong?
To rule out the server permissions issue, in other words your account has
permissions on the server itself -- try using an account that has
administrative rights on the target server and sysadmin permissions on SQL
Server.
Steve|||Ok here is what I tried. I went to the remote sql server and created a
windows user that is part of the admin group. I then went to the enterprise
manager on the remote sql server and created a user which I browsed for and
got from the windows users list. I gave that login SA rights on the sql
server. I then went back to the other server and tried to register the
remote sql server using sql authentication. I used the username and password
that I had created and I still get the same error message. Any ideas?
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>|||Another thing I forgot to mention. I also tried to register the other server
on the remote server (the reverse of what I have been trying). When I go to
register the server I see seven or so other servers that we have here at
work; however when I have been doing it on the other computer I only see one
server (that being the remote sql server). I am wondering what may cause
this and if it might have something to do with the login issue.
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>|||Other things I have tried:
Pinging the remote sql server - works fine
telnet to port 1433 on the remote server - does NOT work
there is not a firewall between the two machines.
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>|||Problem Solved: I was really simple actually, all I had to do was go to the
properties of the remote sql server and configure the network configuration
to enable tcp/ip using port 1433
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>sqlsql
Showing posts with label manage. Show all posts
Showing posts with label manage. Show all posts
Tuesday, March 27, 2012
Sunday, March 25, 2012
Connection problem
I have 2 sql servers running on different machines. I want to manage both
servers from one machine. When I try to add the other server in the
enterprise manager it gives me the error "sql server does not exist or access
denied". I am using a valid log on user name that is set up on the server, I
have even tried using a windows username. I know that the problem has to lie
in authentication because I know the server exist. Anyone know of anything I
may be doing wrong?
"Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> I have 2 sql servers running on different machines. I want to manage both
> servers from one machine. When I try to add the other server in the
> enterprise manager it gives me the error "sql server does not exist or
access
> denied". I am using a valid log on user name that is set up on the
server, I
> have even tried using a windows username. I know that the problem has to
lie
> in authentication because I know the server exist. Anyone know of
anything I
> may be doing wrong?
To rule out the server permissions issue, in other words your account has
permissions on the server itself -- try using an account that has
administrative rights on the target server and sysadmin permissions on SQL
Server.
Steve
|||Ok here is what I tried. I went to the remote sql server and created a
windows user that is part of the admin group. I then went to the enterprise
manager on the remote sql server and created a user which I browsed for and
got from the windows users list. I gave that login SA rights on the sql
server. I then went back to the other server and tried to register the
remote sql server using sql authentication. I used the username and password
that I had created and I still get the same error message. Any ideas?
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
|||Another thing I forgot to mention. I also tried to register the other server
on the remote server (the reverse of what I have been trying). When I go to
register the server I see seven or so other servers that we have here at
work; however when I have been doing it on the other computer I only see one
server (that being the remote sql server). I am wondering what may cause
this and if it might have something to do with the login issue.
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
|||Other things I have tried:
Pinging the remote sql server - works fine
telnet to port 1433 on the remote server - does NOT work
there is not a firewall between the two machines.
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
|||Problem Solved: I was really simple actually, all I had to do was go to the
properties of the remote sql server and configure the network configuration
to enable tcp/ip using port 1433
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
sqlsql
servers from one machine. When I try to add the other server in the
enterprise manager it gives me the error "sql server does not exist or access
denied". I am using a valid log on user name that is set up on the server, I
have even tried using a windows username. I know that the problem has to lie
in authentication because I know the server exist. Anyone know of anything I
may be doing wrong?
"Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> I have 2 sql servers running on different machines. I want to manage both
> servers from one machine. When I try to add the other server in the
> enterprise manager it gives me the error "sql server does not exist or
access
> denied". I am using a valid log on user name that is set up on the
server, I
> have even tried using a windows username. I know that the problem has to
lie
> in authentication because I know the server exist. Anyone know of
anything I
> may be doing wrong?
To rule out the server permissions issue, in other words your account has
permissions on the server itself -- try using an account that has
administrative rights on the target server and sysadmin permissions on SQL
Server.
Steve
|||Ok here is what I tried. I went to the remote sql server and created a
windows user that is part of the admin group. I then went to the enterprise
manager on the remote sql server and created a user which I browsed for and
got from the windows users list. I gave that login SA rights on the sql
server. I then went back to the other server and tried to register the
remote sql server using sql authentication. I used the username and password
that I had created and I still get the same error message. Any ideas?
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
|||Another thing I forgot to mention. I also tried to register the other server
on the remote server (the reverse of what I have been trying). When I go to
register the server I see seven or so other servers that we have here at
work; however when I have been doing it on the other computer I only see one
server (that being the remote sql server). I am wondering what may cause
this and if it might have something to do with the login issue.
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
|||Other things I have tried:
Pinging the remote sql server - works fine
telnet to port 1433 on the remote server - does NOT work
there is not a firewall between the two machines.
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
|||Problem Solved: I was really simple actually, all I had to do was go to the
properties of the remote sql server and configure the network configuration
to enable tcp/ip using port 1433
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
sqlsql
Monday, March 19, 2012
Connection management
hello, I'm using Visual Foxpro and ODBC / sql server 2000.
How should i manage conections ? opening and closing it on each form ? or
opening at the begining of application and closing it at application finish
?
Thanks
Open then close not on each form, but lower.
At each transaction, on add open connection then close it.
On Select open connection then close it.
Joe
"Pedro Jose Caceres" wrote:
> hello, I'm using Visual Foxpro and ODBC / sql server 2000.
> How should i manage conections ? opening and closing it on each form ? or
> opening at the begining of application and closing it at application finish
> ?
> Thanks
>
>
How should i manage conections ? opening and closing it on each form ? or
opening at the begining of application and closing it at application finish
?
Thanks
Open then close not on each form, but lower.
At each transaction, on add open connection then close it.
On Select open connection then close it.
Joe
"Pedro Jose Caceres" wrote:
> hello, I'm using Visual Foxpro and ODBC / sql server 2000.
> How should i manage conections ? opening and closing it on each form ? or
> opening at the begining of application and closing it at application finish
> ?
> Thanks
>
>
Connection management
hello, I'm using Visual Foxpro and ODBC / sql server 2000.
How should i manage conections ? opening and closing it on each form ? or
opening at the begining of application and closing it at application finish
?
ThanksOpen then close not on each form, but lower.
At each transaction, on add open connection then close it.
On Select open connection then close it.
Joe
"Pedro Jose Caceres" wrote:
> hello, I'm using Visual Foxpro and ODBC / sql server 2000.
> How should i manage conections ? opening and closing it on each form ? or
> opening at the begining of application and closing it at application fini
sh
> ?
> Thanks
>
>
How should i manage conections ? opening and closing it on each form ? or
opening at the begining of application and closing it at application finish
?
ThanksOpen then close not on each form, but lower.
At each transaction, on add open connection then close it.
On Select open connection then close it.
Joe
"Pedro Jose Caceres" wrote:
> hello, I'm using Visual Foxpro and ODBC / sql server 2000.
> How should i manage conections ? opening and closing it on each form ? or
> opening at the begining of application and closing it at application fini
sh
> ?
> Thanks
>
>
Connection issue across network
I have about 30 machines that I currently manage. I should also say, I just
took over this position as Senior DBA. One machine is a Windows 2003 Quad
Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in the
SQL Admin group and SQL is set for both SQL and WIndows authenication. Here
is the problem, I can not connect to this box from Enterprise Manager from my
desktop. If I Remote Admin into the box everything works fine. If I try to
register the server with any authenication method it doesnt work. I have
tried my personal account, domain accounts, SA, other admin accounts and
they all come back with Server does not exist or access denied. If I log in
locally or via RA everything is fine. Other admins can access this box
remotely and we all have the same security settings. All of the other
servers register fine.
I reviewed the Windows event log and auditing show that SQL has accepted my
authenication as trusted. SQL is using the standard TCP port 1433.
Any ideas?
Thanks,
Raymond S Laubert
MCITP:Adminstration, MCDBA, MCSE, MCT
Raymond Laubert
MCSE, MCDBA, MCT
So you can connect on the server (via TA session) but not from a client.
Consider that the client needs to be permitted to see the server ports and the server ports must be visible outside of the box. Here are a few things to check:
a.. Is the SQL Server Browser service running on the server?
b.. Are the external protocols enabled? (use SQL Server Surface Area Config tool)
c.. On the client, is the firewall configured to permit access to the ports?
d.. Are you trying to connect to the ports or are you letting the DNS server resolve the server instance?
e.. How are you trying to connect to the instance? In code? (Let's see the ConnectionString)
f.. Does the server show up in the list of visible servers in Server Explorer (Visual Studio)?
g.. Is the little yellow wire connected to the back of the server and does it lead (eventually) to the client? ;)
Check out Chapter 9 of my book... it's written for you (personally)... ;)
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
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)
------
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89-488A-9AFB-B44A6B4562BC@.microsoft.com...
>I have about 30 machines that I currently manage. I should also say, I just
> took over this position as Senior DBA. One machine is a Windows 2003 Quad
> Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in the
> SQL Admin group and SQL is set for both SQL and WIndows authenication. Here
> is the problem, I can not connect to this box from Enterprise Manager from my
> desktop. If I Remote Admin into the box everything works fine. If I try to
> register the server with any authenication method it doesnt work. I have
> tried my personal account, domain accounts, SA, other admin accounts and
> they all come back with Server does not exist or access denied. If I log in
> locally or via RA everything is fine. Other admins can access this box
> remotely and we all have the same security settings. All of the other
> servers register fine.
> I reviewed the Windows event log and auditing show that SQL has accepted my
> authenication as trusted. SQL is using the standard TCP port 1433.
> Any ideas?
> Thanks,
> Raymond S Laubert
> MCITP:Adminstration, MCDBA, MCSE, MCT
> --
> Raymond Laubert
> MCSE, MCDBA, MCT
|||Well, lets see...
I can connect to all the other servers via Enterprise Manager, so network
issues are taken care of.
I can connect to this server via Remote Admin and Terminal Server so
Security issues are taken care of.
Other DBAs and support personnel can connect to the server via Enterprise
Manager so configuration issues are taken care of.
Hmmm... I don't have a yellow wire... maybe that is the issue... oh
wait... mine is blue... yep it's connected as well.
Remember, I can connect to the other 29 servers via Enterprise Manager, this
is the only one I can not connect to. Other DBAs can connect to this server
as well as the other 29. We are all in the same security groups. I can ping
the server by address and name, so network is good.
I try not to put easy stuff on the board, but this one has me stumped.
Oh send me a copy of your book and I will proof read it for you, free of
charge of course. Maybe even promote it in the SQL Classes I teach.
Raymond Laubert
MCSE, MCDBA, MCT
"William (Bill) Vaughn" wrote:
[vbcol=seagreen]
> So you can connect on the server (via TA session) but not from a client.
> Consider that the client needs to be permitted to see the server ports and the server ports must be visible outside of the box. Here are a few things to check:
> a.. Is the SQL Server Browser service running on the server?
> b.. Are the external protocols enabled? (use SQL Server Surface Area Config tool)
> c.. On the client, is the firewall configured to permit access to the ports?
> d.. Are you trying to connect to the ports or are you letting the DNS server resolve the server instance?
> e.. How are you trying to connect to the instance? In code? (Let's see the ConnectionString)
> f.. Does the server show up in the list of visible servers in Server Explorer (Visual Studio)?
> g.. Is the little yellow wire connected to the back of the server and does it lead (eventually) to the client? ;)
> Check out Chapter 9 of my book... it's written for you (personally)... ;)
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> 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)
> ------
> "Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89-488A-9AFB-B44A6B4562BC@.microsoft.com...
|||Send me your snail-mail address and I will...
Have you tried ODBC Ping?
Is the SqlBrowser service started?
Has the SQL Server been configured to expose the external protocols? It
sounds like it, but I would double-check. Are you addressing it via DNS
address or by IP? Again, seeing the connectstring would help.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
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)
------
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message
news:46BC5BDF-6A4F-4817-88E1-29A8F83E4FB8@.microsoft.com...[vbcol=seagreen]
> Well, lets see...
> I can connect to all the other servers via Enterprise Manager, so network
> issues are taken care of.
> I can connect to this server via Remote Admin and Terminal Server so
> Security issues are taken care of.
> Other DBAs and support personnel can connect to the server via Enterprise
> Manager so configuration issues are taken care of.
> Hmmm... I don't have a yellow wire... maybe that is the issue... oh
> wait... mine is blue... yep it's connected as well.
> Remember, I can connect to the other 29 servers via Enterprise Manager,
> this
> is the only one I can not connect to. Other DBAs can connect to this
> server
> as well as the other 29. We are all in the same security groups. I can
> ping
> the server by address and name, so network is good.
> I try not to put easy stuff on the board, but this one has me stumped.
> Oh send me a copy of your book and I will proof read it for you, free of
> charge of course. Maybe even promote it in the SQL Classes I teach.
> --
> Raymond Laubert
> MCSE, MCDBA, MCT
>
> "William (Bill) Vaughn" wrote:
took over this position as Senior DBA. One machine is a Windows 2003 Quad
Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in the
SQL Admin group and SQL is set for both SQL and WIndows authenication. Here
is the problem, I can not connect to this box from Enterprise Manager from my
desktop. If I Remote Admin into the box everything works fine. If I try to
register the server with any authenication method it doesnt work. I have
tried my personal account, domain accounts, SA, other admin accounts and
they all come back with Server does not exist or access denied. If I log in
locally or via RA everything is fine. Other admins can access this box
remotely and we all have the same security settings. All of the other
servers register fine.
I reviewed the Windows event log and auditing show that SQL has accepted my
authenication as trusted. SQL is using the standard TCP port 1433.
Any ideas?
Thanks,
Raymond S Laubert
MCITP:Adminstration, MCDBA, MCSE, MCT
Raymond Laubert
MCSE, MCDBA, MCT
So you can connect on the server (via TA session) but not from a client.
Consider that the client needs to be permitted to see the server ports and the server ports must be visible outside of the box. Here are a few things to check:
a.. Is the SQL Server Browser service running on the server?
b.. Are the external protocols enabled? (use SQL Server Surface Area Config tool)
c.. On the client, is the firewall configured to permit access to the ports?
d.. Are you trying to connect to the ports or are you letting the DNS server resolve the server instance?
e.. How are you trying to connect to the instance? In code? (Let's see the ConnectionString)
f.. Does the server show up in the list of visible servers in Server Explorer (Visual Studio)?
g.. Is the little yellow wire connected to the back of the server and does it lead (eventually) to the client? ;)
Check out Chapter 9 of my book... it's written for you (personally)... ;)
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
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)
------
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89-488A-9AFB-B44A6B4562BC@.microsoft.com...
>I have about 30 machines that I currently manage. I should also say, I just
> took over this position as Senior DBA. One machine is a Windows 2003 Quad
> Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in the
> SQL Admin group and SQL is set for both SQL and WIndows authenication. Here
> is the problem, I can not connect to this box from Enterprise Manager from my
> desktop. If I Remote Admin into the box everything works fine. If I try to
> register the server with any authenication method it doesnt work. I have
> tried my personal account, domain accounts, SA, other admin accounts and
> they all come back with Server does not exist or access denied. If I log in
> locally or via RA everything is fine. Other admins can access this box
> remotely and we all have the same security settings. All of the other
> servers register fine.
> I reviewed the Windows event log and auditing show that SQL has accepted my
> authenication as trusted. SQL is using the standard TCP port 1433.
> Any ideas?
> Thanks,
> Raymond S Laubert
> MCITP:Adminstration, MCDBA, MCSE, MCT
> --
> Raymond Laubert
> MCSE, MCDBA, MCT
|||Well, lets see...
I can connect to all the other servers via Enterprise Manager, so network
issues are taken care of.
I can connect to this server via Remote Admin and Terminal Server so
Security issues are taken care of.
Other DBAs and support personnel can connect to the server via Enterprise
Manager so configuration issues are taken care of.
Hmmm... I don't have a yellow wire... maybe that is the issue... oh
wait... mine is blue... yep it's connected as well.
Remember, I can connect to the other 29 servers via Enterprise Manager, this
is the only one I can not connect to. Other DBAs can connect to this server
as well as the other 29. We are all in the same security groups. I can ping
the server by address and name, so network is good.
I try not to put easy stuff on the board, but this one has me stumped.
Oh send me a copy of your book and I will proof read it for you, free of
charge of course. Maybe even promote it in the SQL Classes I teach.
Raymond Laubert
MCSE, MCDBA, MCT
"William (Bill) Vaughn" wrote:
[vbcol=seagreen]
> So you can connect on the server (via TA session) but not from a client.
> Consider that the client needs to be permitted to see the server ports and the server ports must be visible outside of the box. Here are a few things to check:
> a.. Is the SQL Server Browser service running on the server?
> b.. Are the external protocols enabled? (use SQL Server Surface Area Config tool)
> c.. On the client, is the firewall configured to permit access to the ports?
> d.. Are you trying to connect to the ports or are you letting the DNS server resolve the server instance?
> e.. How are you trying to connect to the instance? In code? (Let's see the ConnectionString)
> f.. Does the server show up in the list of visible servers in Server Explorer (Visual Studio)?
> g.. Is the little yellow wire connected to the back of the server and does it lead (eventually) to the client? ;)
> Check out Chapter 9 of my book... it's written for you (personally)... ;)
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> 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)
> ------
> "Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89-488A-9AFB-B44A6B4562BC@.microsoft.com...
|||Send me your snail-mail address and I will...
Have you tried ODBC Ping?
Is the SqlBrowser service started?
Has the SQL Server been configured to expose the external protocols? It
sounds like it, but I would double-check. Are you addressing it via DNS
address or by IP? Again, seeing the connectstring would help.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
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)
------
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message
news:46BC5BDF-6A4F-4817-88E1-29A8F83E4FB8@.microsoft.com...[vbcol=seagreen]
> Well, lets see...
> I can connect to all the other servers via Enterprise Manager, so network
> issues are taken care of.
> I can connect to this server via Remote Admin and Terminal Server so
> Security issues are taken care of.
> Other DBAs and support personnel can connect to the server via Enterprise
> Manager so configuration issues are taken care of.
> Hmmm... I don't have a yellow wire... maybe that is the issue... oh
> wait... mine is blue... yep it's connected as well.
> Remember, I can connect to the other 29 servers via Enterprise Manager,
> this
> is the only one I can not connect to. Other DBAs can connect to this
> server
> as well as the other 29. We are all in the same security groups. I can
> ping
> the server by address and name, so network is good.
> I try not to put easy stuff on the board, but this one has me stumped.
> Oh send me a copy of your book and I will proof read it for you, free of
> charge of course. Maybe even promote it in the SQL Classes I teach.
> --
> Raymond Laubert
> MCSE, MCDBA, MCT
>
> "William (Bill) Vaughn" wrote:
Connection issue across network
I have about 30 machines that I currently manage. I should also say, I just
took over this position as Senior DBA. One machine is a Windows 2003 Quad
Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in the
SQL Admin group and SQL is set for both SQL and WIndows authenication. Here
is the problem, I can not connect to this box from Enterprise Manager from m
y
desktop. If I Remote Admin into the box everything works fine. If I try to
register the server with any authenication method it doesnt work. I have
tried my personal account, domain accounts, SA, other admin accounts and
they all come back with Server does not exist or access denied. If I log in
locally or via RA everything is fine. Other admins can access this box
remotely and we all have the same security settings. All of the other
servers register fine.
I reviewed the Windows event log and auditing show that SQL has accepted my
authenication as trusted. SQL is using the standard TCP port 1433.
Any ideas?
Thanks,
Raymond S Laubert
MCITP:Adminstration, MCDBA, MCSE, MCT
--
Raymond Laubert
MCSE, MCDBA, MCTSo you can connect on the server (via TA session) but not from a client.
Consider that the client needs to be permitted to see the server ports and t
he server ports must be visible outside of the box. Here are a few things to
check:
a.. Is the SQL Server Browser service running on the server?
b.. Are the external protocols enabled? (use SQL Server Surface Area Config
tool)
c.. On the client, is the firewall configured to permit access to the ports?
d.. Are you trying to connect to the ports or are you letting the DNS server
resolve the server instance?
e.. How are you trying to connect to the instance? In code? (Let's see the C
onnectionString)
f.. Does the server show up in the list of visible servers in Server Explore
r (Visual Studio)?
g.. Is the little yellow wire connected to the back of the server and does i
t lead (eventually) to the client? ;)
Check out Chapter 9 of my book... it's written for you (personally)... ;)
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
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)
----
---
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89-488A-9AFB-B44A6B4
562BC@.microsoft.com...
>I have about 30 machines that I currently manage. I should also say, I jus
t
> took over this position as Senior DBA. One machine is a Windows 2003 Quad
> Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in t
he
> SQL Admin group and SQL is set for both SQL and WIndows authenication. Her
e
> is the problem, I can not connect to this box from Enterprise Manager from
my
> desktop. If I Remote Admin into the box everything works fine. If I try
to
> register the server with any authenication method it doesnt work. I have
> tried my personal account, domain accounts, SA, other admin accounts and
> they all come back with Server does not exist or access denied. If I log
in
> locally or via RA everything is fine. Other admins can access this box
> remotely and we all have the same security settings. All of the other
> servers register fine.
> I reviewed the Windows event log and auditing show that SQL has accepted m
y
> authenication as trusted. SQL is using the standard TCP port 1433.
>
> Any ideas?
>
> Thanks,
>
> Raymond S Laubert
> MCITP:Adminstration, MCDBA, MCSE, MCT
> --
> Raymond Laubert
> MCSE, MCDBA, MCT|||Well, lets see...
I can connect to all the other servers via Enterprise Manager, so network
issues are taken care of.
I can connect to this server via Remote Admin and Terminal Server so
Security issues are taken care of.
Other DBAs and support personnel can connect to the server via Enterprise
Manager so configuration issues are taken care of.
Hmmm... I don't have a yellow wire... maybe that is the issue... oh
wait... mine is blue... yep it's connected as well.
Remember, I can connect to the other 29 servers via Enterprise Manager, this
is the only one I can not connect to. Other DBAs can connect to this server
as well as the other 29. We are all in the same security groups. I can pin
g
the server by address and name, so network is good.
I try not to put easy stuff on the board, but this one has me stumped.
Oh send me a copy of your book and I will proof read it for you, free of
charge of course. Maybe even promote it in the SQL Classes I teach.
--
Raymond Laubert
MCSE, MCDBA, MCT
"William (Bill) Vaughn" wrote:
[vbcol=seagreen]
> So you can connect on the server (via TA session) but not from a client.
> Consider that the client needs to be permitted to see the server ports and
the server ports must be visible outside of the box. Here are a few things
to check:
> a.. Is the SQL Server Browser service running on the server?
> b.. Are the external protocols enabled? (use SQL Server Surface Area Con
fig tool)
> c.. On the client, is the firewall configured to permit access to the po
rts?
> d.. Are you trying to connect to the ports or are you letting the DNS se
rver resolve the server instance?
> e.. How are you trying to connect to the instance? In code? (Let's see t
he ConnectionString)
> f.. Does the server show up in the list of visible servers in Server Exp
lorer (Visual Studio)?
> g.. Is the little yellow wire connected to the back of the server and do
es it lead (eventually) to the client? ;)
> Check out Chapter 9 of my book... it's written for you (personally)... ;)
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> 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)
> ----
---
> "Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89
-488A-9AFB-B44A6B4562BC@.microsoft.com...|||Send me your snail-mail address and I will...
Have you tried ODBC Ping?
Is the SqlBrowser service started?
Has the SQL Server been configured to expose the external protocols? It
sounds like it, but I would double-check. Are you addressing it via DNS
address or by IP? Again, seeing the connectstring would help.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
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)
----
---
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message
news:46BC5BDF-6A4F-4817-88E1-29A8F83E4FB8@.microsoft.com...[vbcol=seagreen]
> Well, lets see...
> I can connect to all the other servers via Enterprise Manager, so network
> issues are taken care of.
> I can connect to this server via Remote Admin and Terminal Server so
> Security issues are taken care of.
> Other DBAs and support personnel can connect to the server via Enterprise
> Manager so configuration issues are taken care of.
> Hmmm... I don't have a yellow wire... maybe that is the issue... oh
> wait... mine is blue... yep it's connected as well.
> Remember, I can connect to the other 29 servers via Enterprise Manager,
> this
> is the only one I can not connect to. Other DBAs can connect to this
> server
> as well as the other 29. We are all in the same security groups. I can
> ping
> the server by address and name, so network is good.
> I try not to put easy stuff on the board, but this one has me stumped.
> Oh send me a copy of your book and I will proof read it for you, free of
> charge of course. Maybe even promote it in the SQL Classes I teach.
> --
> Raymond Laubert
> MCSE, MCDBA, MCT
>
> "William (Bill) Vaughn" wrote:
>
took over this position as Senior DBA. One machine is a Windows 2003 Quad
Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in the
SQL Admin group and SQL is set for both SQL and WIndows authenication. Here
is the problem, I can not connect to this box from Enterprise Manager from m
y
desktop. If I Remote Admin into the box everything works fine. If I try to
register the server with any authenication method it doesnt work. I have
tried my personal account, domain accounts, SA, other admin accounts and
they all come back with Server does not exist or access denied. If I log in
locally or via RA everything is fine. Other admins can access this box
remotely and we all have the same security settings. All of the other
servers register fine.
I reviewed the Windows event log and auditing show that SQL has accepted my
authenication as trusted. SQL is using the standard TCP port 1433.
Any ideas?
Thanks,
Raymond S Laubert
MCITP:Adminstration, MCDBA, MCSE, MCT
--
Raymond Laubert
MCSE, MCDBA, MCTSo you can connect on the server (via TA session) but not from a client.
Consider that the client needs to be permitted to see the server ports and t
he server ports must be visible outside of the box. Here are a few things to
check:
a.. Is the SQL Server Browser service running on the server?
b.. Are the external protocols enabled? (use SQL Server Surface Area Config
tool)
c.. On the client, is the firewall configured to permit access to the ports?
d.. Are you trying to connect to the ports or are you letting the DNS server
resolve the server instance?
e.. How are you trying to connect to the instance? In code? (Let's see the C
onnectionString)
f.. Does the server show up in the list of visible servers in Server Explore
r (Visual Studio)?
g.. Is the little yellow wire connected to the back of the server and does i
t lead (eventually) to the client? ;)
Check out Chapter 9 of my book... it's written for you (personally)... ;)
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
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)
----
---
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89-488A-9AFB-B44A6B4
562BC@.microsoft.com...
>I have about 30 machines that I currently manage. I should also say, I jus
t
> took over this position as Senior DBA. One machine is a Windows 2003 Quad
> Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in t
he
> SQL Admin group and SQL is set for both SQL and WIndows authenication. Her
e
> is the problem, I can not connect to this box from Enterprise Manager from
my
> desktop. If I Remote Admin into the box everything works fine. If I try
to
> register the server with any authenication method it doesnt work. I have
> tried my personal account, domain accounts, SA, other admin accounts and
> they all come back with Server does not exist or access denied. If I log
in
> locally or via RA everything is fine. Other admins can access this box
> remotely and we all have the same security settings. All of the other
> servers register fine.
> I reviewed the Windows event log and auditing show that SQL has accepted m
y
> authenication as trusted. SQL is using the standard TCP port 1433.
>
> Any ideas?
>
> Thanks,
>
> Raymond S Laubert
> MCITP:Adminstration, MCDBA, MCSE, MCT
> --
> Raymond Laubert
> MCSE, MCDBA, MCT|||Well, lets see...
I can connect to all the other servers via Enterprise Manager, so network
issues are taken care of.
I can connect to this server via Remote Admin and Terminal Server so
Security issues are taken care of.
Other DBAs and support personnel can connect to the server via Enterprise
Manager so configuration issues are taken care of.
Hmmm... I don't have a yellow wire... maybe that is the issue... oh
wait... mine is blue... yep it's connected as well.
Remember, I can connect to the other 29 servers via Enterprise Manager, this
is the only one I can not connect to. Other DBAs can connect to this server
as well as the other 29. We are all in the same security groups. I can pin
g
the server by address and name, so network is good.
I try not to put easy stuff on the board, but this one has me stumped.
Oh send me a copy of your book and I will proof read it for you, free of
charge of course. Maybe even promote it in the SQL Classes I teach.
--
Raymond Laubert
MCSE, MCDBA, MCT
"William (Bill) Vaughn" wrote:
[vbcol=seagreen]
> So you can connect on the server (via TA session) but not from a client.
> Consider that the client needs to be permitted to see the server ports and
the server ports must be visible outside of the box. Here are a few things
to check:
> a.. Is the SQL Server Browser service running on the server?
> b.. Are the external protocols enabled? (use SQL Server Surface Area Con
fig tool)
> c.. On the client, is the firewall configured to permit access to the po
rts?
> d.. Are you trying to connect to the ports or are you letting the DNS se
rver resolve the server instance?
> e.. How are you trying to connect to the instance? In code? (Let's see t
he ConnectionString)
> f.. Does the server show up in the list of visible servers in Server Exp
lorer (Visual Studio)?
> g.. Is the little yellow wire connected to the back of the server and do
es it lead (eventually) to the client? ;)
> Check out Chapter 9 of my book... it's written for you (personally)... ;)
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> 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)
> ----
---
> "Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89
-488A-9AFB-B44A6B4562BC@.microsoft.com...|||Send me your snail-mail address and I will...
Have you tried ODBC Ping?
Is the SqlBrowser service started?
Has the SQL Server been configured to expose the external protocols? It
sounds like it, but I would double-check. Are you addressing it via DNS
address or by IP? Again, seeing the connectstring would help.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
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)
----
---
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message
news:46BC5BDF-6A4F-4817-88E1-29A8F83E4FB8@.microsoft.com...[vbcol=seagreen]
> Well, lets see...
> I can connect to all the other servers via Enterprise Manager, so network
> issues are taken care of.
> I can connect to this server via Remote Admin and Terminal Server so
> Security issues are taken care of.
> Other DBAs and support personnel can connect to the server via Enterprise
> Manager so configuration issues are taken care of.
> Hmmm... I don't have a yellow wire... maybe that is the issue... oh
> wait... mine is blue... yep it's connected as well.
> Remember, I can connect to the other 29 servers via Enterprise Manager,
> this
> is the only one I can not connect to. Other DBAs can connect to this
> server
> as well as the other 29. We are all in the same security groups. I can
> ping
> the server by address and name, so network is good.
> I try not to put easy stuff on the board, but this one has me stumped.
> Oh send me a copy of your book and I will proof read it for you, free of
> charge of course. Maybe even promote it in the SQL Classes I teach.
> --
> Raymond Laubert
> MCSE, MCDBA, MCT
>
> "William (Bill) Vaughn" wrote:
>
Friday, February 24, 2012
connection broken
Hi,
I,ve tried to manage an SQL Server (MSDE) with Enterprise Manager.
The Server was successfully registered.
But when I try to show the servers properties, or to insert a new login
there is always the following error:
"Error 22528 [SQL-DMO]This server connection has been unexpectedly broke
n
and cannot be reconnected."
What is the problem, and how could I solve it?
Help me, please. Thanks, ChristofWhat OS is it running on? You might want to try running SQL client
configuration utility on the Enterpise Manager PC and see what happens when
you connect with different protocols (eg tcp/ip sockets vs named pipes).
You should also check firewall programs and anti-virus programs to see if
they are blocking named pipes.
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Christof Schdeli" <ch.schaedeli@.gmx.ch> wrote in message
news:ObPgv06fEHA.1972@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I,ve tried to manage an SQL Server (MSDE) with Enterprise Manager.
> The Server was successfully registered.
> But when I try to show the servers properties, or to insert a new login
> there is always the following error:
> "Error 22528 [SQL-DMO]This server connection has been unexpectedly bro
ken
> and cannot be reconnected."
> What is the problem, and how could I solve it?
> Help me, please. Thanks, Christof
>
>|||Hi Andy,
My problem is already solved - I've installed the service-pack 3 of MSDE,
and now, it works fine.
Thanks anyway,
Christof
"Andy Svendsen" <andymcdba1@.NOMORESPAM.yahoo.com> wrote in message
news:eaucXcWgEHA.1196@.TK2MSFTNGP11.phx.gbl...
> What OS is it running on? You might want to try running SQL client
> configuration utility on the Enterpise Manager PC and see what happens
when
> you connect with different protocols (eg tcp/ip sockets vs named pipes).
> You should also check firewall programs and anti-virus programs to see if
> they are blocking named pipes.
> --
> ****************************************
***************************
> Andy S.
> MCSE NT/2000, MCDBA SQL 7/2000
> andymcdba1@.NOMORESPAM.yahoo.com
> Please remove NOMORESPAM before replying.
> Always keep your antivirus and Microsoft software
> up to date with the latest definitions and product updates.
> Be suspicious of every email attachment, I will never send
> or post anything other than the text of a http:// link nor
> post the link directly to a file for downloading.
> This posting is provided "as is" with no warranties
> and confers no rights.
> ****************************************
***************************
> "Christof Schdeli" <ch.schaedeli@.gmx.ch> wrote in message
> news:ObPgv06fEHA.1972@.TK2MSFTNGP09.phx.gbl...
broken[vbcol=seagreen]
>|||Do you resolved them? Please tell me how!
Thanks.
****************************************
******************************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET
resources...
I,ve tried to manage an SQL Server (MSDE) with Enterprise Manager.
The Server was successfully registered.
But when I try to show the servers properties, or to insert a new login
there is always the following error:
"Error 22528 [SQL-DMO]This server connection has been unexpectedly broke
n
and cannot be reconnected."
What is the problem, and how could I solve it?
Help me, please. Thanks, ChristofWhat OS is it running on? You might want to try running SQL client
configuration utility on the Enterpise Manager PC and see what happens when
you connect with different protocols (eg tcp/ip sockets vs named pipes).
You should also check firewall programs and anti-virus programs to see if
they are blocking named pipes.
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Christof Schdeli" <ch.schaedeli@.gmx.ch> wrote in message
news:ObPgv06fEHA.1972@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I,ve tried to manage an SQL Server (MSDE) with Enterprise Manager.
> The Server was successfully registered.
> But when I try to show the servers properties, or to insert a new login
> there is always the following error:
> "Error 22528 [SQL-DMO]This server connection has been unexpectedly bro
ken
> and cannot be reconnected."
> What is the problem, and how could I solve it?
> Help me, please. Thanks, Christof
>
>|||Hi Andy,
My problem is already solved - I've installed the service-pack 3 of MSDE,
and now, it works fine.
Thanks anyway,
Christof
"Andy Svendsen" <andymcdba1@.NOMORESPAM.yahoo.com> wrote in message
news:eaucXcWgEHA.1196@.TK2MSFTNGP11.phx.gbl...
> What OS is it running on? You might want to try running SQL client
> configuration utility on the Enterpise Manager PC and see what happens
when
> you connect with different protocols (eg tcp/ip sockets vs named pipes).
> You should also check firewall programs and anti-virus programs to see if
> they are blocking named pipes.
> --
> ****************************************
***************************
> Andy S.
> MCSE NT/2000, MCDBA SQL 7/2000
> andymcdba1@.NOMORESPAM.yahoo.com
> Please remove NOMORESPAM before replying.
> Always keep your antivirus and Microsoft software
> up to date with the latest definitions and product updates.
> Be suspicious of every email attachment, I will never send
> or post anything other than the text of a http:// link nor
> post the link directly to a file for downloading.
> This posting is provided "as is" with no warranties
> and confers no rights.
> ****************************************
***************************
> "Christof Schdeli" <ch.schaedeli@.gmx.ch> wrote in message
> news:ObPgv06fEHA.1972@.TK2MSFTNGP09.phx.gbl...
broken[vbcol=seagreen]
>|||Do you resolved them? Please tell me how!
Thanks.
****************************************
******************************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET
resources...
Labels:
broken,
connection,
database,
enterprise,
manage,
manager,
microsoft,
msde,
mysql,
oracle,
registered,
server,
servers,
sql,
successfully
connection broken
Hi,
I,ve tried to manage an SQL Server (MSDE) with Enterprise Manager.
The Server was successfully registered.
But when I try to show the servers properties, or to insert a new login
there is always the following error:
"Error 22528 [SQL-DMO]This server connection has been unexpectedly broken
and cannot be reconnected."
What is the problem, and how could I solve it?
Help me, please. Thanks, Christof
What OS is it running on? You might want to try running SQL client
configuration utility on the Enterpise Manager PC and see what happens when
you connect with different protocols (eg tcp/ip sockets vs named pipes).
You should also check firewall programs and anti-virus programs to see if
they are blocking named pipes.
************************************************** *****************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
************************************************** *****************
"Christof Schdeli" <ch.schaedeli@.gmx.ch> wrote in message
news:ObPgv06fEHA.1972@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I,ve tried to manage an SQL Server (MSDE) with Enterprise Manager.
> The Server was successfully registered.
> But when I try to show the servers properties, or to insert a new login
> there is always the following error:
> "Error 22528 [SQL-DMO]This server connection has been unexpectedly broken
> and cannot be reconnected."
> What is the problem, and how could I solve it?
> Help me, please. Thanks, Christof
>
>
|||Hi Andy,
My problem is already solved - I've installed the service-pack 3 of MSDE,
and now, it works fine.
Thanks anyway,
Christof
"Andy Svendsen" <andymcdba1@.NOMORESPAM.yahoo.com> wrote in message
news:eaucXcWgEHA.1196@.TK2MSFTNGP11.phx.gbl...
> What OS is it running on? You might want to try running SQL client
> configuration utility on the Enterpise Manager PC and see what happens
when[vbcol=seagreen]
> you connect with different protocols (eg tcp/ip sockets vs named pipes).
> You should also check firewall programs and anti-virus programs to see if
> they are blocking named pipes.
> --
> ************************************************** *****************
> Andy S.
> MCSE NT/2000, MCDBA SQL 7/2000
> andymcdba1@.NOMORESPAM.yahoo.com
> Please remove NOMORESPAM before replying.
> Always keep your antivirus and Microsoft software
> up to date with the latest definitions and product updates.
> Be suspicious of every email attachment, I will never send
> or post anything other than the text of a http:// link nor
> post the link directly to a file for downloading.
> This posting is provided "as is" with no warranties
> and confers no rights.
> ************************************************** *****************
> "Christof Schdeli" <ch.schaedeli@.gmx.ch> wrote in message
> news:ObPgv06fEHA.1972@.TK2MSFTNGP09.phx.gbl...
broken
>
|||Do you resolved them? Please tell me how!
Thanks.
************************************************** ********************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...
I,ve tried to manage an SQL Server (MSDE) with Enterprise Manager.
The Server was successfully registered.
But when I try to show the servers properties, or to insert a new login
there is always the following error:
"Error 22528 [SQL-DMO]This server connection has been unexpectedly broken
and cannot be reconnected."
What is the problem, and how could I solve it?
Help me, please. Thanks, Christof
What OS is it running on? You might want to try running SQL client
configuration utility on the Enterpise Manager PC and see what happens when
you connect with different protocols (eg tcp/ip sockets vs named pipes).
You should also check firewall programs and anti-virus programs to see if
they are blocking named pipes.
************************************************** *****************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
************************************************** *****************
"Christof Schdeli" <ch.schaedeli@.gmx.ch> wrote in message
news:ObPgv06fEHA.1972@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I,ve tried to manage an SQL Server (MSDE) with Enterprise Manager.
> The Server was successfully registered.
> But when I try to show the servers properties, or to insert a new login
> there is always the following error:
> "Error 22528 [SQL-DMO]This server connection has been unexpectedly broken
> and cannot be reconnected."
> What is the problem, and how could I solve it?
> Help me, please. Thanks, Christof
>
>
|||Hi Andy,
My problem is already solved - I've installed the service-pack 3 of MSDE,
and now, it works fine.
Thanks anyway,
Christof
"Andy Svendsen" <andymcdba1@.NOMORESPAM.yahoo.com> wrote in message
news:eaucXcWgEHA.1196@.TK2MSFTNGP11.phx.gbl...
> What OS is it running on? You might want to try running SQL client
> configuration utility on the Enterpise Manager PC and see what happens
when[vbcol=seagreen]
> you connect with different protocols (eg tcp/ip sockets vs named pipes).
> You should also check firewall programs and anti-virus programs to see if
> they are blocking named pipes.
> --
> ************************************************** *****************
> Andy S.
> MCSE NT/2000, MCDBA SQL 7/2000
> andymcdba1@.NOMORESPAM.yahoo.com
> Please remove NOMORESPAM before replying.
> Always keep your antivirus and Microsoft software
> up to date with the latest definitions and product updates.
> Be suspicious of every email attachment, I will never send
> or post anything other than the text of a http:// link nor
> post the link directly to a file for downloading.
> This posting is provided "as is" with no warranties
> and confers no rights.
> ************************************************** *****************
> "Christof Schdeli" <ch.schaedeli@.gmx.ch> wrote in message
> news:ObPgv06fEHA.1972@.TK2MSFTNGP09.phx.gbl...
broken
>
|||Do you resolved them? Please tell me how!
Thanks.
************************************************** ********************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...
Labels:
broken,
connection,
database,
enterprise,
manage,
manager,
microsoft,
msde,
mysql,
oracle,
registered,
server,
servers,
sql,
successfully
Subscribe to:
Posts (Atom)