Friday, February 24, 2012

Can't connect via Enterprise Manager

Hi All,
We have a MSDE on a W2K server installed. It is running fine and the
application can access it without a problem. We have another server on that
same subnet that has an SQL 2000 server installed. When trying to connect to
the MSDE via the Enterprise Manager, only the local SQL shows up and we
cannot connect to the MSDE instance.
When we go to the ODBC on the MSDE box we see both SQL - the local and the
remote one. On the ODBC on the other server we only see the local one.
Does anybody have an idea what is going on?
Thanks,
Claus
Hi Claus,
Most likely network protocols not enabled. Run svrnetcn.exe and check which
protocols (eg tcp) are enabled. By default, none are.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"cjobes" <cjobes@.nova-tech.org> wrote in message
news:%234wb4E1oEHA.4044@.TK2MSFTNGP10.phx.gbl...
> Hi All,
> We have a MSDE on a W2K server installed. It is running fine and the
> application can access it without a problem. We have another server on
that
> same subnet that has an SQL 2000 server installed. When trying to connect
to
> the MSDE via the Enterprise Manager, only the local SQL shows up and we
> cannot connect to the MSDE instance.
> When we go to the ODBC on the MSDE box we see both SQL - the local and the
> remote one. On the ODBC on the other server we only see the local one.
> Does anybody have an idea what is going on?
> Thanks,
> Claus
>
|||Hi Greg,
Thanks for the answer. I double checked and both protocols (tcp and named
pipe) are enabled.
Claus
"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
news:%23LcQb96oEHA.1160@.tk2msftngp13.phx.gbl...
> Hi Claus,
> Most likely network protocols not enabled. Run svrnetcn.exe and check
which[vbcol=seagreen]
> protocols (eg tcp) are enabled. By default, none are.
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "cjobes" <cjobes@.nova-tech.org> wrote in message
> news:%234wb4E1oEHA.4044@.TK2MSFTNGP10.phx.gbl...
> that
connect[vbcol=seagreen]
> to
the
>
|||Claus,
Have you checked the firewall settings on the second server? If it has
the TCP port used by MSDE blocked you won't be able to connect.
Ron Allen
"cjobes" <cjobes@.nova-tech.org> wrote in message
news:%23WJfzS9oEHA.3460@.tk2msftngp13.phx.gbl...
> Hi Greg,
> Thanks for the answer. I double checked and both protocols (tcp and named
> pipe) are enabled.
> Claus
> "Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
> news:%23LcQb96oEHA.1160@.tk2msftngp13.phx.gbl...
> which
> connect
> the
>
|||Hi Claus,
I might need more inputs to trouble shoot this issue. Before this, you
could try Re- registering the MSDE Server in your Enterprise Manager.
Please use the Register SQL Server Wizard. For the sake of Clarity, I am
outling the steps here.
In the Enterprise Manager, If the MSDE Server is already
Registered, then Select Server, Right Click on the Server and Select Delete
SQL Server Registration.
1. In the Enterprise Manager, Start Register SQL Server Wizard. (Right
Click on SQL Server Group, Select New SQL Server Registration)
2. In the 'Select a SQL Server' page (second page), In the 'Available
Servers' Text box enter the Computer Name on which the MSDE is installed.
(Hope it is a default instance. If it is a Named Instance then enter
Instance Name also eg: Default Instance on Computer Named Test - TEST,
Named Instance 'Test1' on TEST - TEST\Test1 ). Then click 'ADD' button.
Click Next.
3. In the Next Page Select Authentication Mode.
4. In the Next Page Click Next
5. In the Last Page Select Finish.
After few minutes, You would see a screen which should say
'Server Registration completed' Status 'Registered Successfully'.
If this goes through, You would be able to see the MSDE in your Enterprise
manager. In case it fails, Please mail me the exact Error Message that you
would see in the Status column. We would try and troubleshoot it further.
Thanks,
Soma Sekhara Reddy
|||There is no firewall on that server and I'm in the same subnet trying to
connect.
"Ron Allen" <rallen@._nospam_src-us.com> wrote in message
news:eXZzmPJpEHA.1644@.tk2msftngp13.phx.gbl...
> Claus,
> Have you checked the firewall settings on the second server? If it
has[vbcol=seagreen]
> the TCP port used by MSDE blocked you won't be able to connect.
> Ron Allen
> "cjobes" <cjobes@.nova-tech.org> wrote in message
> news:%23WJfzS9oEHA.3460@.tk2msftngp13.phx.gbl...
named[vbcol=seagreen]
on[vbcol=seagreen]
we[vbcol=seagreen]
and[vbcol=seagreen]
one.
>
|||Thanks for your answer. This is what I have tried several times. The answer
I get back is "SQL server not running or access denied". I'm trying to
connect with SQL authentication (sa and password). I'm sure about the sa and
password because I use it in the local ODBC connection and the test works
fine.
I know I'm missing something really obvious - just can't put my finger on
it.
Claus
"Soma Sekhara Reddy" <somsredd@.microsoft.com> wrote in message
news:nyon0IQpEHA.3212@.cpmsftngxa06.phx.gbl...
> Hi Claus,
> I might need more inputs to trouble shoot this issue. Before this, you
> could try Re- registering the MSDE Server in your Enterprise Manager.
> Please use the Register SQL Server Wizard. For the sake of Clarity, I am
> outling the steps here.
> In the Enterprise Manager, If the MSDE Server is already
> Registered, then Select Server, Right Click on the Server and Select
Delete
> SQL Server Registration.
> 1. In the Enterprise Manager, Start Register SQL Server Wizard. (Right
> Click on SQL Server Group, Select New SQL Server Registration)
> 2. In the 'Select a SQL Server' page (second page), In the 'Available
> Servers' Text box enter the Computer Name on which the MSDE is installed.
> (Hope it is a default instance. If it is a Named Instance then enter
> Instance Name also eg: Default Instance on Computer Named Test - TEST,
> Named Instance 'Test1' on TEST - TEST\Test1 ). Then click 'ADD' button.
> Click Next.
> 3. In the Next Page Select Authentication Mode.
> 4. In the Next Page Click Next
> 5. In the Last Page Select Finish.
> After few minutes, You would see a screen which should
say
> 'Server Registration completed' Status 'Registered Successfully'.
> If this goes through, You would be able to see the MSDE in your Enterprise
> manager. In case it fails, Please mail me the exact Error Message that
you
> would see in the Status column. We would try and troubleshoot it further.
> Thanks,
> Soma Sekhara Reddy
>
|||Hi Claus,
Please use the 'ODBCPING' command line utility to check the connectivity.
The syntax is
odbcping -Sservername -Uusername -Ppassword
This tool is loaded with SQL Server client utilities and would be available
on your system. Please do not leave any space betweeb -S and servername,
-S is caps (case sensitive).
Thanks,
Soma Sekhara Reddy

No comments:

Post a Comment