MSDE / SQL - SERVER

Dear all,
I have installed both environments on my system, running windows 2000.
When I start the SQL Enterprise Manager I can see 1 SQL Server Group,
containing two branches:
- (local) (windows nt) which contains the msde
- named instance which contains the sql server 2000
I have an application running in which I can make a selection between
servers. After installing sql server the servers running on my system are no
longer presented. My application still runs with the msde server if I type in
the name of the server but not with the sql server.
To check wehther the problem is caused by the application or not, I tried to
create a DSN (odbc data source) on my system. Because there the server is
also requested. When I click on the list box for the server no servers are
presented. When I type in the name I get an error message that the connection
failed.
sql server error: 1231
.....
sqlstate: '08001'
sql server error: 17
[microsoft][odbc sql server dirver][dbnetlib]sql server does not exist or
access denied
Because I did not see the servers available in the list box I the server
does not exist part of the message seems to match my problem. But looking
into the enterprise manager I have it up and running.
Has someone experienced this in the past and solved it. Can you share the
solution for this problem.
regards,
Danny Gaethofs
Dear all,
I have to rephrase my problem statement. After a bit of experimenting I am
able to get connected to both msde and sql server using my application.
However the problem I described that the servers are not shown in the list
box that opens for example when you create a data source remains.
Because this is a bit crucial when creating new connections can someone help
me out with this and explain why it is happening.
regards,
Danny Gaethofs
"Danny Gaethofs" wrote:

> Dear all,
> I have installed both environments on my system, running windows 2000.
> When I start the SQL Enterprise Manager I can see 1 SQL Server Group,
> containing two branches:
> - (local) (windows nt) which contains the msde
> - named instance which contains the sql server 2000
> I have an application running in which I can make a selection between
> servers. After installing sql server the servers running on my system are no
> longer presented. My application still runs with the msde server if I type in
> the name of the server but not with the sql server.
> To check wehther the problem is caused by the application or not, I tried to
> create a DSN (odbc data source) on my system. Because there the server is
> also requested. When I click on the list box for the server no servers are
> presented. When I type in the name I get an error message that the connection
> failed.
> sql server error: 1231
> ....
> sqlstate: '08001'
> sql server error: 17
> [microsoft][odbc sql server dirver][dbnetlib]sql server does not exist or
> access denied
> Because I did not see the servers available in the list box I the server
> does not exist part of the message seems to match my problem. But looking
> into the enterprise manager I have it up and running.
> Has someone experienced this in the past and solved it. Can you share the
> solution for this problem.
> regards,
> Danny Gaethofs
|||When you say "list box," what object are you referring to? I am assuming
this is the developement configuration. How will the architecture look when
you roll this out to your clients? Will they also have two SQL Server
installations on their workstations? Or, will there be an actual server and
then a local MSDE? Or, might there just be several server installations?
You can use the Client Configuration Utility to simulate the "names" of your
production servers but redirect them to each of the "instances" running in
your developement environment.
First, all SQL Server installations run as an "instance." There is the
default instance and up to 15 named instances on any given host. Or, you
can have 16 named instances. They all comprise the <host name>[\<instance
name>], with the default instance being NULL for the instance name. You can
map those, with the Client Configuration Utility, to just a virtual host
name if you wish.
If multiple instances are running on one server, then they can not all share
the same default 1433 port. The other instances can be configured for
specific ports or can be dynamically generated each time the instance is
restarted. If dynamic, then all of your users will have to be on the same
VLAN, the UDP 1434 port must not be blocked, and they must set their client
configuration to Dynamic Discovery for the port detection.
Hope this narrows down this list of issues for you.
Sincerely,
Anthony Thomas

"Danny Gaethofs" <DannyGaethofs@.discussions.microsoft.com> wrote in message
news:85A69D33-EFD8-4D8E-A908-34027B510269@.microsoft.com...
Dear all,
I have to rephrase my problem statement. After a bit of experimenting I am
able to get connected to both msde and sql server using my application.
However the problem I described that the servers are not shown in the list
box that opens for example when you create a data source remains.
Because this is a bit crucial when creating new connections can someone help
me out with this and explain why it is happening.
regards,
Danny Gaethofs
"Danny Gaethofs" wrote:

> Dear all,
> I have installed both environments on my system, running windows 2000.
> When I start the SQL Enterprise Manager I can see 1 SQL Server Group,
> containing two branches:
> - (local) (windows nt) which contains the msde
> - named instance which contains the sql server 2000
> I have an application running in which I can make a selection between
> servers. After installing sql server the servers running on my system are
no
> longer presented. My application still runs with the msde server if I type
in
> the name of the server but not with the sql server.
> To check wehther the problem is caused by the application or not, I tried
to
> create a DSN (odbc data source) on my system. Because there the server is
> also requested. When I click on the list box for the server no servers are
> presented. When I type in the name I get an error message that the
connection
> failed.
> sql server error: 1231
> ....
> sqlstate: '08001'
> sql server error: 17
> [microsoft][odbc sql server dirver][dbnetlib]sql server does not exist or
> access denied
> Because I did not see the servers available in the list box I the server
> does not exist part of the message seems to match my problem. But looking
> into the enterprise manager I have it up and running.
> Has someone experienced this in the past and solved it. Can you share the
> solution for this problem.
> regards,
> Danny Gaethofs
|||Dear all,
I have removed everything now, both MSDE and SQL Server. I reinstalled MSDE
only and when I try to create a ODBC DSN the system is not showing me the
available server at all.
Is there an explanation for this behavior and how can I solve it.
regards,
Danny
"AnthonyThomas" <Anthony.Thomas@.CommerceBank.com> schreef in bericht
news:uW3wrS43EHA.2012@.TK2MSFTNGP15.phx.gbl...
> When you say "list box," what object are you referring to? I am assuming
> this is the developement configuration. How will the architecture look
> when
> you roll this out to your clients? Will they also have two SQL Server
> installations on their workstations? Or, will there be an actual server
> and
> then a local MSDE? Or, might there just be several server installations?
> You can use the Client Configuration Utility to simulate the "names" of
> your
> production servers but redirect them to each of the "instances" running in
> your developement environment.
> First, all SQL Server installations run as an "instance." There is the
> default instance and up to 15 named instances on any given host. Or, you
> can have 16 named instances. They all comprise the <host name>[\<instance
> name>], with the default instance being NULL for the instance name. You
> can
> map those, with the Client Configuration Utility, to just a virtual host
> name if you wish.
> If multiple instances are running on one server, then they can not all
> share
> the same default 1433 port. The other instances can be configured for
> specific ports or can be dynamically generated each time the instance is
> restarted. If dynamic, then all of your users will have to be on the same
> VLAN, the UDP 1434 port must not be blocked, and they must set their
> client
> configuration to Dynamic Discovery for the port detection.
> Hope this narrows down this list of issues for you.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Danny Gaethofs" <DannyGaethofs@.discussions.microsoft.com> wrote in
> message
> news:85A69D33-EFD8-4D8E-A908-34027B510269@.microsoft.com...
> Dear all,
> I have to rephrase my problem statement. After a bit of experimenting I am
> able to get connected to both msde and sql server using my application.
> However the problem I described that the servers are not shown in the list
> box that opens for example when you create a data source remains.
> Because this is a bit crucial when creating new connections can someone
> help
> me out with this and explain why it is happening.
> regards,
> Danny Gaethofs
> "Danny Gaethofs" wrote:
> no
> in
> to
> connection
>
|||When you run the setup on a system that has or has had the server components
installed, in all likelihood, you have also installed the Client
Configuration utility. Once there, ODBC Administrator is limited as far as
its ability to search out installations. Use the Client Config tool to
define these and then ODBC Administrator to define DSN's on top of that. Be
careful though, because then you are likely forcing the overhead of using
ODBC on top OLEDB. That's just another API layer between you and the
database access.
I would consider using Data Links instead of DSN. These use the native
OLEDB API ans server a similar purpose, persisting the connection parameters
on the local machine. One way to create one quickly is to create a NEW TEXT
FILE, then rename it with the .udl extension. It will automatically be
changed to a Data Link file which can be managed by the Data Link
Administrator.
Sincerely,
Anthony Thomas

"Danny Gaethofs" <dangaet@.home.nl> wrote in message
news:OGKwFlP4EHA.2192@.TK2MSFTNGP14.phx.gbl...
Dear all,
I have removed everything now, both MSDE and SQL Server. I reinstalled MSDE
only and when I try to create a ODBC DSN the system is not showing me the
available server at all.
Is there an explanation for this behavior and how can I solve it.
regards,
Danny
"AnthonyThomas" <Anthony.Thomas@.CommerceBank.com> schreef in bericht
news:uW3wrS43EHA.2012@.TK2MSFTNGP15.phx.gbl...
> When you say "list box," what object are you referring to? I am assuming
> this is the developement configuration. How will the architecture look
> when
> you roll this out to your clients? Will they also have two SQL Server
> installations on their workstations? Or, will there be an actual server
> and
> then a local MSDE? Or, might there just be several server installations?
> You can use the Client Configuration Utility to simulate the "names" of
> your
> production servers but redirect them to each of the "instances" running in
> your developement environment.
> First, all SQL Server installations run as an "instance." There is the
> default instance and up to 15 named instances on any given host. Or, you
> can have 16 named instances. They all comprise the <host name>[\<instance
> name>], with the default instance being NULL for the instance name. You
> can
> map those, with the Client Configuration Utility, to just a virtual host
> name if you wish.
> If multiple instances are running on one server, then they can not all
> share
> the same default 1433 port. The other instances can be configured for
> specific ports or can be dynamically generated each time the instance is
> restarted. If dynamic, then all of your users will have to be on the same
> VLAN, the UDP 1434 port must not be blocked, and they must set their
> client
> configuration to Dynamic Discovery for the port detection.
> Hope this narrows down this list of issues for you.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Danny Gaethofs" <DannyGaethofs@.discussions.microsoft.com> wrote in
> message
> news:85A69D33-EFD8-4D8E-A908-34027B510269@.microsoft.com...
> Dear all,
> I have to rephrase my problem statement. After a bit of experimenting I am
> able to get connected to both msde and sql server using my application.
> However the problem I described that the servers are not shown in the list
> box that opens for example when you create a data source remains.
> Because this is a bit crucial when creating new connections can someone
> help
> me out with this and explain why it is happening.
> regards,
> Danny Gaethofs
> "Danny Gaethofs" wrote:
> no
> in
> to
> connection
>