MSDB database restore: manager

Showing posts with label manager. Show all posts

Friday, March 30, 2012

MSDE and Enterprise Manager?

I am a complete sql newbie! For the life of me I can't figure out how to get Enterprise Manager to connect with MSDE. Something about mixed mode or tcp/ip settings? But no one's ever really clear on how to do these things. I've uninstalled MSDE until I can get more info.

I just need a quick walk-through on how to install msde to work with EM. This is what I used when MSDE requested a strong password:

setup INSTANCENAME="InstanceName" SECURITYMODE=SQL SAPWD="AStrongSAPwd"

Is this correct? Any help would be appreciated.

Thanks.

You access it by address or servername + \ + Instance name:

Server\MSDEInstanceName

|||

What part are you having a problem with?

Tell EM to connect to the server\instancename using sql authentication login sa, password AStrongPWD.

|||If you have the full SQL Server installed then you install the MSDE as a named instance and right click at the top of the Enterprise manager of the full version to register the MSDE and you can manage it directly. If you have the MSDE installed then you install the full version as a named instance and repeat the above. I have registered 68 SQL Server 7/2000 in one XP box so if you have more questions post again. Hope this helps.|||

Thanks to everyone for their help.

I had the eval version of 2000 installed but it's expired. I would now like to use EM with MSDE to connect to the database on my website. I re-installed MSDE but it's only showing the local database.

When I try to register my online domain (ip address) it fails. Says sql may not be running. But it is running. I know it's something basic and silly I'm not doing, but I'm still very new to sql. Is there any other very basic step I may be missing?

Again, thanks for everyone's help...sorry for all the newbie questions.

|||

Which is probably correct because your SQL Server service maybe off, the developer edition is $40 in the link below but you could get it for less because when you are using hosting company you need Enterprise manager. Hope this helps.

http://www.provantage.com/buy-22053391-microsoft-backoffice-sql-server-2000-developer-edition-shopping.htm

MSDE and Enterprise Manager Trouble

I have installed an MSDE instance on my PC. I have used both the setup.exe program and installed MSDE with the merge modules. Everything works fine - I am able to programmatically connect to the database and execute all of my statements. However, when I t
ry to register the database with Enterprise Manager, Enterprise Manager doesn't see the instance. Similarly, my program that uses SQLDMO.DLL to enumerate all servers does not see the MSDE instance. Both the database, my program, and Enterprise Manager are
running locally on the same machine.
This is a development box, and I have had to uninstall MSDE by hand several times by removing registry keys manually. I suspect that my problem is that I have deleted a key that I needed. Does anyone have any clues? Thanks in advance.
Rob Reagan
MSDE with Sp3a or MSDE Release A installs by default without network
connections enabled and will not advertise itself on the network. You can
still register the instance in Enterprise Manager by typing the name in the
textbox during registration.
You can install MSDE with network connections, see the "Customizing Desktop
Engine Setup.exe" topic in Books Online for details. You can also enable
network connections after installation with (I think) svrnetcn.exe in the
Tools\Bin directory, but I have no MSDe instance to check that at the
moment.
Jacco Schalkwijk
SQL Server MVP
"Rob Reagan" <RobReagan@.discussions.microsoft.com> wrote in message
news:AEC24187-ADA9-48D1-ADC3-837FEE031CEB@.microsoft.com...
> I have installed an MSDE instance on my PC. I have used both the setup.exe
program and installed MSDE with the merge modules. Everything works fine - I
am able to programmatically connect to the database and execute all of my
statements. However, when I try to register the database with Enterprise
Manager, Enterprise Manager doesn't see the instance. Similarly, my program
that uses SQLDMO.DLL to enumerate all servers does not see the MSDE
instance. Both the database, my program, and Enterprise Manager are running
locally on the same machine.
> This is a development box, and I have had to uninstall MSDE by hand
several times by removing registry keys manually. I suspect that my problem
is that I have deleted a key that I needed. Does anyone have any clues?
Thanks in advance.
> Rob Reagan

MSDE and Enterprise Manager

I have just installed (new clean install) of MSDE 3a. On another machine I have enterprise manager, and I thought I would be able to access it, but when I try to register it in EM it gives me the following error: SERVERNAME - SQL Server does not exist or access denied, Connection Open(Connect(). I have done this in the past with no problem. Did I forget a parameter on the install of 3a to allow other machines to access or do I have some other security issue?Depends on the configuration of MSDE. If you have enabled (using sapwd flag on setup.exe) SQL authentication, you can authenticate with these credentials. However, I did not try to connect to an MSDE instance running on another box with Enterprise Manager yet. But AFAIK, SQL auth should work fine in this case.|||I did configure it for SQL authentication.sql

MSDE and Enterprise Manager

If you have a machine running MSDE and you use Enterprise
Manager to connect to it, should you be able to set up
database maintenance plans that will delete expired
backups?
I'm seeing a situation where you can set up the
maintenance plan but the drop down box for the type of
period (days, weeks, etc) after which to delete expired
backups is blank.
My first thought is that there's an issue with using EM
to set up maintenance plans on MSDE.
Thanks for any assistance.
hi Charles,
"Charles Allen" <callen@.bkd.com> ha scritto nel messaggio
news:3d2c01c4c1ec$13e369d0$a301280a@.phx.gbl
> If you have a machine running MSDE and you use Enterprise
> Manager to connect to it, should you be able to set up
> database maintenance plans that will delete expired
> backups?
> I'm seeing a situation where you can set up the
> maintenance plan but the drop down box for the type of
> period (days, weeks, etc) after which to delete expired
> backups is blank.
> My first thought is that there's an issue with using EM
> to set up maintenance plans on MSDE.
> Thanks for any assistance.
unfortunately, your first thought should be that you are not licensed to use
Enterprise Manager against MSDE instances, and you should rely on self based
solutions or third party tools
(http://www.microsoft.com/sql/msde/partners/default.asp or
http://www.aspfaq.com/show.asp?id=2442 , google for others)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks for your message. My understanding of the licensing is you can use
Enterprise Manager IF you own a copy of SQL Server Standard or greater. If my
understanding is correct, then the issue goes back to functionality. Do you
agree?
In case you are wondering, you might use MSDE even if you have an installed
version of SQL Server if the application you are using is based on one or the
other. Great Plains, for example, knows which one you are using and has
specific licenses.
"Andrea Montanari" wrote:

> hi Charles,
> "Charles Allen" <callen@.bkd.com> ha scritto nel messaggio
> news:3d2c01c4c1ec$13e369d0$a301280a@.phx.gbl
> unfortunately, your first thought should be that you are not licensed to use
> Enterprise Manager against MSDE instances, and you should rely on self based
> solutions or third party tools
> (http://www.microsoft.com/sql/msde/partners/default.asp or
> http://www.aspfaq.com/show.asp?id=2442 , google for others)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||That's not quite correct. The Appropriate Uses of MSDE FAQ at
http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp says the following:
Q. Can I use SQL Server tools and services in conjunction with MSDE?
A. You can only use SQL Server tools and services in conjunction with
MSDE if you acquired MSDE through SQL Server 2000 (Developer Edition,
Standard Edition, or Enterprise Edition), and if you are using MSDE in
conjunction with a properly licensed copy of SQL Server 2000. Visit the How
to Buy page for information on obtaining a valid SQL Server license.
Note: The tools and services included with SQL Server Developer
Edition may not be used to manage production server environments.
The following utilities are installed by the MSDE setup application
and are provided without restrictions for use with the copy of MSDE that is
installed by your application: bcp.exe, cnfgsvr.exe, dcomscm.exe, osql.exe,
sqlmaint.exe, sqlmangr.exe, scm.exe, sqladhlp.exe, and svrnetcn.exe. The
dtsrun.exe utility is also provided, but can only be used to run existing
Data Transformation Services (DTS) packages against the copy of MSDE
installed by your application; it cannot be used to develop new DTS
packages.
The key phrase here is "using MSDE in conjuntion with a properly licensed
copy of SQL Server 2000." Simply owning a copy of SQL Server Standard
Edition isn't enough, and you'll have to talk to your laywer to figure out
what that phrase means. All I've been told is that it doesn't apply in most
cases and requires a room full of lawyers and a white board to understand.
Rather than go through all that, you're probably better off putting Andrea's
suggestion to work and using a third-party tool.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Charles Allen" <CharlesAllen@.discussions.microsoft.com> wrote in message
news:18142445-2FBB-43EC-9719-8751C5AC767D@.microsoft.com...[vbcol=seagreen]
> Thanks for your message. My understanding of the licensing is you can use
> Enterprise Manager IF you own a copy of SQL Server Standard or greater. If
> my
> understanding is correct, then the issue goes back to functionality. Do
> you
> agree?
> In case you are wondering, you might use MSDE even if you have an
> installed
> version of SQL Server if the application you are using is based on one or
> the
> other. Great Plains, for example, knows which one you are using and has
> specific licenses.
> "Andrea Montanari" wrote:
begin 666 ts.gif
J1TE&.#EA`0`!`( ``````/___R'Y! $`````+ `````!``$```(!1 `[
`
end

MSDE and Enterprise manager

-ENTERPRISE MANAGER .
. .
.
http://www.aspfaq.com/show.asp?id=2442
Really? I tend to disagree. (?)
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Tomer" <Tomek13@.bezeqint.net> wrote in message
news:eMYhPqoPEHA.3012@.tk2msftngp13.phx.gbl...
> -ENTERPRISE MANAGER .
> . .
> .
> http://www.aspfaq.com/show.asp?id=2442
>
|||I concur with your findings Aaron.
Steve Plender
"Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
news:uCM9EvoPEHA.2740@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Really? I tend to disagree. (?)
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
>
>
> "Tomer" <Tomek13@.bezeqint.net> wrote in message
> news:eMYhPqoPEHA.3012@.tk2msftngp13.phx.gbl...
[vbcol=seagreen]

>

Monday, March 26, 2012

MSDE 2000 Release A won't talk

MSDE 2000 Release A installed under windows 2000 pro will not
communicate with SQL Server Manager nor MS Access on peer computer.
Can someone help?
Have set DISABLENETWORKPROTOCOLS=0 at install time.
Install log shows installation successful..
Control Panel> Admin Tools> Services section shows SQL server instance
running.
Disabling firewall has no effect.
SQL Server Manager (icon at bottom right in task tray - this
starts/stops Server instances), on same computer as SQL Server
instance, shows only instance "H" which is the same as the computer
name. (This instance was uninstalled before new instance was
installed.) Typing new instance name ("H\ABC" and variations) into
top combo box produces error messages such as "wrong format for name",
"Network path not found" "RPC service not running". What is the
correct computer/name format? Key problem is clearly that Service
Manager can't communicate with this local MSDE instance.
All Windows 2000 updates from MS web site have been installed.
Objective is to operate MS Access on computer X (also running Win 2000
Pro) with computer H as a peer that hosts MSDE.
Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system?
Have you installed SP3a?
Steve
<noname@.noname.com> wrote in message
news:40d55341.11850570@.nntp.flfrd.phub.net.cable.r ogers.com...
> MSDE 2000 Release A installed under windows 2000 pro will not
> communicate with SQL Server Manager nor MS Access on peer computer.
> Can someone help?
> Have set DISABLENETWORKPROTOCOLS=0 at install time.
> Install log shows installation successful..
> Control Panel> Admin Tools> Services section shows SQL server instance
> running.
> Disabling firewall has no effect.
> SQL Server Manager (icon at bottom right in task tray - this
> starts/stops Server instances), on same computer as SQL Server
> instance, shows only instance "H" which is the same as the computer
> name. (This instance was uninstalled before new instance was
> installed.) Typing new instance name ("H\ABC" and variations) into
> top combo box produces error messages such as "wrong format for name",
> "Network path not found" "RPC service not running". What is the
> correct computer/name format? Key problem is clearly that Service
> Manager can't communicate with this local MSDE instance.
> All Windows 2000 updates from MS web site have been installed.
> Objective is to operate MS Access on computer X (also running Win 2000
> Pro) with computer H as a peer that hosts MSDE.
> Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system?
|||Hi Steve,
MSDE 2000A already contains SQL Server SP3a updates.
Mark
Ottawa, Canada
On Tue, 22 Jun 2004 15:25:07 -0400, "Steve Thompson"
<stevethompson@.nomail.please> wrote:

>Have you installed SP3a?
>Steve

MSDE 2000 Release A won't talk

MSDE 2000 Release A installed under Windows 2000 pro will not
communicate with SQL Server Manager nor MS Access on peer computer.
Can someone help?
Have set DISABLENETWORKPROTOCOLS=0 at install time.
Install log shows installation successful..
Control Panel> Admin Tools> Services section shows SQL server instance
running.
Disabling firewall has no effect.
SQL Server Manager (icon at bottom right in task tray - this
starts/stops Server instances), on same computer as SQL Server
instance, shows only instance "H" which is the same as the computer
name. (This instance was uninstalled before new instance was
installed.) Typing new instance name ("H\ABC" and variations) into
top combo box produces error messages such as "wrong format for name",
"Network path not found" "RPC service not running". What is the
correct computer/name format' Key problem is clearly that Service
Manager can't communicate with this local MSDE instance.
All Windows 2000 updates from MS web site have been installed.
Objective is to operate MS Access on computer X (also running Win 2000
Pro) with computer H as a peer that hosts MSDE.
Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system'Have you installed SP3a?
Steve
<noname@.noname.com> wrote in message
news:40d55341.11850570@.nntp.flfrd.phub.net.cable.rogers.com...
> MSDE 2000 Release A installed under Windows 2000 pro will not
> communicate with SQL Server Manager nor MS Access on peer computer.
> Can someone help?
> Have set DISABLENETWORKPROTOCOLS=0 at install time.
> Install log shows installation successful..
> Control Panel> Admin Tools> Services section shows SQL server instance
> running.
> Disabling firewall has no effect.
> SQL Server Manager (icon at bottom right in task tray - this
> starts/stops Server instances), on same computer as SQL Server
> instance, shows only instance "H" which is the same as the computer
> name. (This instance was uninstalled before new instance was
> installed.) Typing new instance name ("H\ABC" and variations) into
> top combo box produces error messages such as "wrong format for name",
> "Network path not found" "RPC service not running". What is the
> correct computer/name format' Key problem is clearly that Service
> Manager can't communicate with this local MSDE instance.
> All Windows 2000 updates from MS web site have been installed.
> Objective is to operate MS Access on computer X (also running Win 2000
> Pro) with computer H as a peer that hosts MSDE.
> Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system'|||Hi Steve,
MSDE 2000A already contains SQL Server SP3a updates.
Mark
Ottawa, Canada
On Tue, 22 Jun 2004 15:25:07 -0400, "Steve Thompson"
<stevethompson@.nomail.please> wrote:

>Have you installed SP3a?
>Steve

MSDE 2000 Release A wont talk

MSDE 2000 Release A installed under windows 2000 pro will not
communicate with SQL Server Manager nor MS Access on peer computer.
Can someone help?

Have set DISABLENETWORKPROTOCOLS=0 at install time.

Install log shows installation successful..

Control Panel> Admin Tools> Services section shows SQL server instance
running.

Disabling firewall has no effect.

SQL Server Manager (icon at bottom right in task tray - this
starts/stops Server instances), on same computer as SQL Server
instance, shows only instance "H" which is the same as the computer
name. (This instance was uninstalled before new instance was
installed.) Typing new instance name ("H\ABC" and variations) into
top combo box produces error messages such as "wrong format for name",
"Network path not found" "RPC service not running". What is the
correct computer/name format?? Key problem is clearly that Service
Manager can't communicate with this local MSDE instance.

All Windows 2000 updates from MS web site have been installed.

Objective is to operate MS Access on computer X (also running Win 2000
Pro) with computer H as a peer that hosts MSDE.

Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
--
Mark Ferguson<noname@.noname.com> wrote in message
news:40d53097.2976249@.nntp.flfrd.phub.net.cable.ro gers.com...
> MSDE 2000 Release A installed under windows 2000 pro will not
> communicate with SQL Server Manager nor MS Access on peer computer.
> Can someone help?
> Have set DISABLENETWORKPROTOCOLS=0 at install time.
> Install log shows installation successful..
> Control Panel> Admin Tools> Services section shows SQL server instance
> running.
> Disabling firewall has no effect.
> SQL Server Manager (icon at bottom right in task tray - this
> starts/stops Server instances), on same computer as SQL Server
> instance, shows only instance "H" which is the same as the computer
> name. (This instance was uninstalled before new instance was
> installed.) Typing new instance name ("H\ABC" and variations) into
> top combo box produces error messages such as "wrong format for name",
> "Network path not found" "RPC service not running". What is the
> correct computer/name format?? Key problem is clearly that Service
> Manager can't communicate with this local MSDE instance.
> All Windows 2000 updates from MS web site have been installed.
> Objective is to operate MS Access on computer X (also running Win 2000
> Pro) with computer H as a peer that hosts MSDE.
> Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
> --
> Mark Ferguson

I must admit that I don't know the difference between MSDE Release A and
MSDE SP3a. There is no clear information on the MS site (or at least I
couldn't find it), but the download sizes are different, so the obvious
conclusion is that they are different versions. If this assumption is
correct, then you might be seeing this issue:

http://support.microsoft.com/defaul...010&Product=sql

However, I could be wrong, so perhaps you can check some more things. Can
you actually connect to the instance on H using a local osql.exe command
also on H? If you're logged on to Windows as an administrator, then this
should be enough:

osql -S H\ABC -E

If that works, then presumably the problem is the Service Manager itself
(possibly as described in the article above). If you can connect, you can
then check the version with this query:

1> select @.@.version
2> go

If you don't see version 8.00.760, then you don't have SP3a, so I would
completely remove MSDE and then install MSDE SP3a. See "Remove all known
instances of SQL Server" in this article:

http://support.microsoft.com/defaul...991&Product=sql

If you cannot connect with osql.exe, then what error message do you get? In
the final analysis, however, I would suggest that Server Manager is a small,
unimportant component which probably is not worth worrying about. As long as
MSDE is running and you can connect from client applications with no
problems, then I would not spend too much time trying to make it work.

Regarding connecting from a different PC (with Access or any other tool),
there are a number of possible connection issues:

http://support.microsoft.com/defaul...306&Product=sql

I guess when you say "peer" you mean that the PCs are in a workgroup, not a
domain. If this is the case, then trusted connections can be awkward - the
article above has a link to another KB article which describes a possible
workaround. Mixed security using SQL logins should work fine, but is not
generally recommended unless there is no other alternative.

Simon|||Hi

You may get more help in the microsoft.public.sqlserver.msde newsgroup.

John
<noname@.noname.com> wrote in message
news:40d53097.2976249@.nntp.flfrd.phub.net.cable.ro gers.com...
> MSDE 2000 Release A installed under windows 2000 pro will not
> communicate with SQL Server Manager nor MS Access on peer computer.
> Can someone help?
> Have set DISABLENETWORKPROTOCOLS=0 at install time.
> Install log shows installation successful..
> Control Panel> Admin Tools> Services section shows SQL server instance
> running.
> Disabling firewall has no effect.
> SQL Server Manager (icon at bottom right in task tray - this
> starts/stops Server instances), on same computer as SQL Server
> instance, shows only instance "H" which is the same as the computer
> name. (This instance was uninstalled before new instance was
> installed.) Typing new instance name ("H\ABC" and variations) into
> top combo box produces error messages such as "wrong format for name",
> "Network path not found" "RPC service not running". What is the
> correct computer/name format?? Key problem is clearly that Service
> Manager can't communicate with this local MSDE instance.
> All Windows 2000 updates from MS web site have been installed.
> Objective is to operate MS Access on computer X (also running Win 2000
> Pro) with computer H as a peer that hosts MSDE.
> Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
> --
> Mark Ferguson|||"Simon Hayes" <sql@.hayes.ch> wrote in message
news:40d5ade5$1_2@.news.bluewin.ch...
|
| <noname@.noname.com> wrote in message
| news:40d53097.2976249@.nntp.flfrd.phub.net.cable.ro gers.com...
| > MSDE 2000 Release A installed under windows 2000 pro will not
| > communicate with SQL Server Manager nor MS Access on peer computer.
| > Can someone help?
| >
| > Have set DISABLENETWORKPROTOCOLS=0 at install time.
| >
| > Install log shows installation successful..
| >
| > Control Panel> Admin Tools> Services section shows SQL server instance
| > running.
| >
| > Disabling firewall has no effect.
| >
| > SQL Server Manager (icon at bottom right in task tray - this
| > starts/stops Server instances), on same computer as SQL Server
| > instance, shows only instance "H" which is the same as the computer
| > name. (This instance was uninstalled before new instance was
| > installed.) Typing new instance name ("H\ABC" and variations) into
| > top combo box produces error messages such as "wrong format for name",
| > "Network path not found" "RPC service not running". What is the
| > correct computer/name format?? Key problem is clearly that Service
| > Manager can't communicate with this local MSDE instance.
| >
| > All Windows 2000 updates from MS web site have been installed.
| >
| > Objective is to operate MS Access on computer X (also running Win 2000
| > Pro) with computer H as a peer that hosts MSDE.
| >
| > Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
| > --
| > Mark Ferguson
|
| I must admit that I don't know the difference between MSDE Release A and
| MSDE SP3a. There is no clear information on the MS site (or at least I
| couldn't find it), but the download sizes are different, so the obvious
| conclusion is that they are different versions. If this assumption is
| correct, then you might be seeing this issue:
|
| http://support.microsoft.com/defaul...010&Product=sql
|
| However, I could be wrong, so perhaps you can check some more things. Can
| you actually connect to the instance on H using a local osql.exe command
| also on H? If you're logged on to Windows as an administrator, then this
| should be enough:
|
| osql -S H\ABC -E
|
| If that works, then presumably the problem is the Service Manager itself
| (possibly as described in the article above). If you can connect, you can
| then check the version with this query:
|
| 1> select @.@.version
| 2> go
|
| If you don't see version 8.00.760, then you don't have SP3a, so I would
| completely remove MSDE and then install MSDE SP3a. See "Remove all known
| instances of SQL Server" in this article:
|
| http://support.microsoft.com/defaul...991&Product=sql
|
| If you cannot connect with osql.exe, then what error message do you get? In
| the final analysis, however, I would suggest that Server Manager is a small,
| unimportant component which probably is not worth worrying about. As long as
| MSDE is running and you can connect from client applications with no
| problems, then I would not spend too much time trying to make it work.
|
| Regarding connecting from a different PC (with Access or any other tool),
| there are a number of possible connection issues:
|
| http://support.microsoft.com/defaul...306&Product=sql
|
| I guess when you say "peer" you mean that the PCs are in a workgroup, not a
| domain. If this is the case, then trusted connections can be awkward - the
| article above has a link to another KB article which describes a possible
| workaround. Mixed security using SQL logins should work fine, but is not
| generally recommended unless there is no other alternative.
|
| Simon
|
|

MSDE 2000 Release A is a developer version (SDK) of Microsoft SQL Server 2000
Desktop Engine SP3a. SELECT @.@.VERSION returns the same version info for both.

This brief description of Microsoft SQL Server 2000 Desktop Engine (MSDE 2000)
Release A is quoted from the download page -
<
MSDE 2000 Release A is functionally equivalent to SQL Server 2000 Desktop
Engine SP3a except for the following:

New licensing agreement

Removal of the merge modules that can be used to embed MSDE 2000 Release A
with applications

New ReadMeMSDE2000A.htm that contains information specific to this release.

This new version of MSDE contains all the fixes that are included with SQL
Server 2000 SP3a version of MSDE.

http://www.microsoft.com/downloads/...&DisplayLang=en
Additional information can be found in the Microsoft SQL Server 2000 Desktop
Engine
(MSDE 2000) Release A ReadMe

http://download.microsoft.com/downl...meMSDE2000A.htm

Additions to the SQL Server 2000 Desktop Engine (MSDE) Release A
ReadmeMSDE2000A.htm File
http://support.microsoft.com/?kbid=829925

Dan|||<noname@.noname.com> wrote in message
news:40d53097.2976249@.nntp.flfrd.phub.net.cable.ro gers.com...
| MSDE 2000 Release A installed under windows 2000 pro will not
| communicate with SQL Server Manager nor MS Access on peer computer.
| Can someone help?
|
| Have set DISABLENETWORKPROTOCOLS=0 at install time.
|
| Install log shows installation successful..
|
| Control Panel> Admin Tools> Services section shows SQL server instance
| running.
|
| Disabling firewall has no effect.
|
| SQL Server Manager (icon at bottom right in task tray - this
| starts/stops Server instances), on same computer as SQL Server
| instance, shows only instance "H" which is the same as the computer
| name. (This instance was uninstalled before new instance was
| installed.) Typing new instance name ("H\ABC" and variations) into
| top combo box produces error messages such as "wrong format for name",
| "Network path not found" "RPC service not running". What is the
| correct computer/name format?? Key problem is clearly that Service
| Manager can't communicate with this local MSDE instance.
|
| All Windows 2000 updates from MS web site have been installed.
|
| Objective is to operate MS Access on computer X (also running Win 2000
| Pro) with computer H as a peer that hosts MSDE.
|
| Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
| --
| Mark Ferguson

Hi Mark,

There is known bug when reinstalling with same instance name.
Follow the instructions for editing the registry keys given in
the article at:
http://support.microsoft.com/defaul...kb;en-us;823467

If that fails then you will have to uninstall MSDE 2000 Release A
and follow the instructions for editing the registry keys given in
the article at:
http://support.microsoft.com/defaul...kb;en-us;320873
Then reinstall MSDE 2000 Release A

Hope this helps.

Dan|||Thanks John, but I dont see a newsgroup named
microsoft.public.sqlserver.msde. I just checked for new groups and
that one doesn't show up there either. Not sure where i might find
this group.

On Sun, 20 Jun 2004 16:07:34 GMT, "John Bell"
<jbellnewsposts@.hotmail.com> wrote:

>Hi
>You may get more help in the microsoft.public.sqlserver.msde newsgroup.
>John
><noname@.noname.com> wrote in message
>news:40d53097.2976249@.nntp.flfrd.phub.net.cable.ro gers.com...
>> MSDE 2000 Release A installed under windows 2000 pro will not
>> communicate with SQL Server Manager nor MS Access on peer computer.
>> Can someone help?
>>
>> Have set DISABLENETWORKPROTOCOLS=0 at install time.
>>
>> Install log shows installation successful..
>>
>> Control Panel> Admin Tools> Services section shows SQL server instance
>> running.
>>
>> Disabling firewall has no effect.
>>
>> SQL Server Manager (icon at bottom right in task tray - this
>> starts/stops Server instances), on same computer as SQL Server
>> instance, shows only instance "H" which is the same as the computer
>> name. (This instance was uninstalled before new instance was
>> installed.) Typing new instance name ("H\ABC" and variations) into
>> top combo box produces error messages such as "wrong format for name",
>> "Network path not found" "RPC service not running". What is the
>> correct computer/name format?? Key problem is clearly that Service
>> Manager can't communicate with this local MSDE instance.
>>
>> All Windows 2000 updates from MS web site have been installed.
>>
>> Objective is to operate MS Access on computer X (also running Win 2000
>> Pro) with computer H as a peer that hosts MSDE.
>>
>> Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
>> --
>> Mark Ferguson|||Hi

Try the news.microsoft.com news server or
http://groups.google.com/groups?hl=...sqlserver.msde

John

<Mark_Ferguson@.noname.com> wrote in message
news:40d736bf.12602391@.nntp.flfrd.phub.net.cable.r ogers.com...
> Thanks John, but I dont see a newsgroup named
> microsoft.public.sqlserver.msde. I just checked for new groups and
> that one doesn't show up there either. Not sure where i might find
> this group.
> On Sun, 20 Jun 2004 16:07:34 GMT, "John Bell"
> <jbellnewsposts@.hotmail.com> wrote:
> >Hi
> >You may get more help in the microsoft.public.sqlserver.msde newsgroup.
> >John
> ><noname@.noname.com> wrote in message
> >news:40d53097.2976249@.nntp.flfrd.phub.net.cable.ro gers.com...
> >> MSDE 2000 Release A installed under windows 2000 pro will not
> >> communicate with SQL Server Manager nor MS Access on peer computer.
> >> Can someone help?
> >>
> >> Have set DISABLENETWORKPROTOCOLS=0 at install time.
> >>
> >> Install log shows installation successful..
> >>
> >> Control Panel> Admin Tools> Services section shows SQL server instance
> >> running.
> >>
> >> Disabling firewall has no effect.
> >>
> >> SQL Server Manager (icon at bottom right in task tray - this
> >> starts/stops Server instances), on same computer as SQL Server
> >> instance, shows only instance "H" which is the same as the computer
> >> name. (This instance was uninstalled before new instance was
> >> installed.) Typing new instance name ("H\ABC" and variations) into
> >> top combo box produces error messages such as "wrong format for name",
> >> "Network path not found" "RPC service not running". What is the
> >> correct computer/name format?? Key problem is clearly that Service
> >> Manager can't communicate with this local MSDE instance.
> >>
> >> All Windows 2000 updates from MS web site have been installed.
> >>
> >> Objective is to operate MS Access on computer X (also running Win 2000
> >> Pro) with computer H as a peer that hosts MSDE.
> >>
> >> Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
> >> --
> >> Mark Ferguson|||>I must admit that I don't know the difference between MSDE Release A and
>MSDE SP3a. There is no clear information on the MS site (or at least I
>couldn't find it), but the download sizes are different, so the obvious
>conclusion is that they are different versions. If this assumption is
>correct, then you might be seeing this issue:
>http://support.microsoft.com/defaul...010&Product=sql
This article applies to MSDE Service pack . I have installed MSDE
2000A which includes Service Pack 3. The symptoms don't and conditions
don't apply, nor do the workaround instructions make sense.
>However, I could be wrong, so perhaps you can check some more things. Can
>you actually connect to the instance on H using a local osql.exe command
>also on H? If you're logged on to Windows as an administrator, then this
>should be enough:
>osql -S H\ABC -E
This works. But the SQL Server *is* running - we knew that.

>If that works, then presumably the problem is the Service Manager itself
>(possibly as described in the article above). If you can connect, you can
>then check the version with this query:
>1> select @.@.version
>2> go
Result is:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copy
right (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT
5.0 (Build 2195: Service Pack 4)

>If you don't see version 8.00.760, then you don't have SP3a, so I would
>completely remove MSDE and then install MSDE SP3a. See "Remove all known
>instances of SQL Server" in this article:
>http://support.microsoft.com/defaul...991&Product=sql

Thank you... This may be very useful indeed.
>If you cannot connect with osql.exe, then what error message do you get? In
>the final analysis, however, I would suggest that Server Manager is a small,
>unimportant component which probably is not worth worrying about. As long as
>MSDE is running and you can connect from client applications with no
>problems, then I would not spend too much time trying to make it work.
>Regarding connecting from a different PC (with Access or any other tool),
>there are a number of possible connection issues:
>http://support.microsoft.com/defaul...306&Product=sql
>I guess when you say "peer" you mean that the PCs are in a workgroup, not a
>domain. If this is the case, then trusted connections can be awkward - the
>article above has a link to another KB article which describes a possible
>workaround. Mixed security using SQL logins should work fine, but is not
>generally recommended unless there is no other alternative.

You are correct, the two computers are not in a domain and so there is
no user authentication provided by a domain server. Thanks for the
link I will look it up.

The Server Manager is only important in that its a good first
indication that everything is working at the local computer - an
encouraging first sign, insofar as the client computer cannot connect
to the server.
>Simon
>
I am also working on the problem of fixing ports used by the SQL
Server. The instance now installed is named and so uses dynamic ports
rather than the fixed 1433 and 1434 ports. The question is: what does
the SQL Server Manager use?|||I think you are correct. I need to uninstall MSDE2000A and then fix up
the registry or re-install windows 2000. I have already uninstalled
the old default version that came with MS office. I have also
installed the MSDE2000A version several times.

I have never checked the MDAC version (don't know how), but that may
also be a problem.

I need to try these and then request more help.

Many thanks.
Mark.

On Mon, 21 Jun 2004 05:22:56 -0400, "Daniel A. Thomas"
<dathomas@.--spam--istar.ca> wrote:

>Hi Mark,
>There is known bug when reinstalling with same instance name.
>Follow the instructions for editing the registry keys given in
>the article at:
>http://support.microsoft.com/defaul...kb;en-us;823467
>If that fails then you will have to uninstall MSDE 2000 Release A
>and follow the instructions for editing the registry keys given in
>the article at:
>http://support.microsoft.com/defaul...kb;en-us;320873
>Then reinstall MSDE 2000 Release A
>Hope this helps.
>Dan|||OK, John. The google web page is the same as the MS Discussion forum
for SQL Server. I posted a similar article there, but no help came
there.

Mark.

On Mon, 21 Jun 2004 19:56:20 GMT, "John Bell"
<jbellnewsposts@.hotmail.com> wrote:

>Hi
>Try the news.microsoft.com news server or
>http://groups.google.com/groups?hl=...sqlserver.msde
>John|||I'm grateful for the help from you all, but the one real symptom of
the problem with the Service Manager is its error message:
"The format of the computer name is inavlid."

This is the response to asking it to find the instance ABC on the
computer named "H" - (H\ABC). Recall that running osql.exe against the
name H\ABC works fine.

Mark.

msde 2000 on windows 2003 server

I "Managed" to install msde on windows 2003 server but the sql service manager does list an thing to connect to.
what am i doing wrong does mdse work on windows 2003 server and how do i fix it ?
Hi,
I have found the following KB article that describes a similar scenario.
http://support.microsoft.com/default...&Product=sql2k
#appliesto
================================================== ==========================
================================================== =========
BUG: The SQL Server 2000 Service Manager Utility Does Not List Instances
That Have Not Enabled Network Connections
View products that this article applies to.
BUG #: 363267 (SHILOH_BUGS)
SYMPTOMS
If you configure an instance of SQL Server 2000 or SQL Server 2000 Desktop
Engine (also known as MSDE 2000) to disallow network connections, that
instance will not appear in the SQL Server 2000 Service Manager utility.
CAUSE
The SQL Server ODBC driver does not return instance names to the SQL
Service Manager if the instance does not support network connections.
WORKAROUND
To work around this behavior, stop and then start the service for the
instance by following these steps:
Right-click My Computer, and then click Manage.
Double-click Services and Applications in the left-hand screen.
Double-click Services.
Right-click the service for the instance of SQL Server. The name of the
service for a default instance of SQL Server 2000 is MSSQLServer. The name
of the service for a named instance of SQL Server 2000 is
MSSQL$instancename.
Click the action that you want applied to the instance, such as stop or
start.
================================================== ==========================
================================================== =========
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.

Friday, March 23, 2012

MSDE 2000 Downloaded and Installed But where is Enterprise Manager

Dear Experts,
I have downloaded MSDE 2000RelA and i installed it. But where is the
Enterprise Manager and Query Analyzer a-la SQL Server 7.0? Any help would be
greatly appreciated
Thanks
Manish
--
Three Cheers to Technet for the Help!Hi,
MSDE will not come with Enterprise manager or Query analyser. You have to
use the command prompt utilizty OSQL to execute all
the TSQL commands. See the details of OSQL utility in books online.
You could also download and use the WEB data ADMIN free tool from microsoft
site.
http://www.microsoft.com/downloads/details.aspx?FamilyId=C039A798-C57A-419E-ACBC-2A332CB7F959&displaylang=en
Thanks
Hari
SQL Server MVP
"Manish Sawjiani" <ManishSawjiani@.discussions.microsoft.com> wrote in
message news:42FB064A-B6B7-4F20-A3D4-C437096682E1@.microsoft.com...
> Dear Experts,
> I have downloaded MSDE 2000RelA and i installed it. But where is the
> Enterprise Manager and Query Analyzer a-la SQL Server 7.0? Any help would
> be
> greatly appreciated
> Thanks
> Manish
> --
> Three Cheers to Technet for the Help!|||Thanks Hari
--
Three Cheers to Technet for the Help!
"Hari Prasad" wrote:
> Hi,
> MSDE will not come with Enterprise manager or Query analyser. You have to
> use the command prompt utilizty OSQL to execute all
> the TSQL commands. See the details of OSQL utility in books online.
> You could also download and use the WEB data ADMIN free tool from microsoft
> site.
> http://www.microsoft.com/downloads/details.aspx?FamilyId=C039A798-C57A-419E-ACBC-2A332CB7F959&displaylang=en
> Thanks
> Hari
> SQL Server MVP
>
> "Manish Sawjiani" <ManishSawjiani@.discussions.microsoft.com> wrote in
> message news:42FB064A-B6B7-4F20-A3D4-C437096682E1@.microsoft.com...
> > Dear Experts,
> > I have downloaded MSDE 2000RelA and i installed it. But where is the
> > Enterprise Manager and Query Analyzer a-la SQL Server 7.0? Any help would
> > be
> > greatly appreciated
> >
> > Thanks
> > Manish
> > --
> > Three Cheers to Technet for the Help!
>
>

MSDE 2000 Downloaded and Installed But where is Enterprise Manager

Wednesday, March 21, 2012

MSDE 2000 and enterprise (enterprize) manager remotely

Hey all.
Can you use enterprise manager to connect to an MSDE 2000 version of
SQL Server across the internet? Ignoring firewalls (server was placed
outside firewall to see if thats where the connection problem was)
We get the 'SQL Server does not exist or access denied
ConnectionOpen(Connect())' error when trying to connect to a clients
database on their server over the internet. However, everything looks
ok and I can vpn into their machine and connect to the server using
enterprise manager on a terminal service session on their servers.
This in itself is a pain and we would rather have their server
registered in our enterprise manager.
Does the same answer apply if the server was an installation of SQL
Server standard edition?Licensing questions aside:
Yes. Note that MSDE doesn't by default listen to any netlibs. If you can
connect to the same MSDE after VPN, then this shouldn't be an issue. I
suggest you, on the client, make sure that TCP IP is at the top of the list
in Client Network Utility. Also try connecting using IP address. And as for
port numbers,
The IP netlib uses 1433 for a default instance.
The IP netlib uses 1434 for the port resolution query and whatever the
instance picked at the first startup for the actual data traffic.
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"Karl Rhodes" <karl.rhodes@.keywave.com> wrote in message
news:7cee27c2.0402110245.64167e99@.posting.google.com...
> Hey all.
> Can you use enterprise manager to connect to an MSDE 2000 version of
> SQL Server across the internet? Ignoring firewalls (server was placed
> outside firewall to see if thats where the connection problem was)
> We get the 'SQL Server does not exist or access denied
> ConnectionOpen(Connect())' error when trying to connect to a clients
> database on their server over the internet. However, everything looks
> ok and I can vpn into their machine and connect to the server using
> enterprise manager on a terminal service session on their servers.
> This in itself is a pain and we would rather have their server
> registered in our enterprise manager.
> Does the same answer apply if the server was an installation of SQL
> Server standard edition?|||I have tested my theory out by installing MSDE on my workstation and
tryng to connect from another machine across the internet, with little
success, thats why I asked.
Do you have any other ideas why we wouldnt be able to register their
server in enterprise manager?
I can only register it in enterprise manager on the terminal server box,
not on my local ent manager.
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||Is the terminal server the machine where MSDE is installed? Remember that
MSDE doesn't listen to any netlibs by default. Apart from that and the
things I mentioned in my first post, I don't know what it might be.
Firewalls is the most common reason for this.
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"Karl Rhodes" <karl.rhodes@.keywave.com> wrote in message
news:OZpfufJ8DHA.452@.TK2MSFTNGP11.phx.gbl...
> I have tested my theory out by installing MSDE on my workstation and
> tryng to connect from another machine across the internet, with little
> success, thats why I asked.
> Do you have any other ideas why we wouldnt be able to register their
> server in enterprise manager?
> I can only register it in enterprise manager on the terminal server box,
> not on my local ent manager.
>
>
> *** Sent via Developersdex http://www.examnotes.net ***
> Don't just participate in USENET...get rewarded for it!|||As far as I I know, yes the MSDE is on the same server as the terminal
services. BUT, When I log on terminal services and have a look at the
properties of the server (terminal services enterprise manager) it says
tcpip is enabled. Does this mean that this library is available and
SHOULD work across the internet?
remove 'REMOVESPAM.' for email
Karl Rhodes
Internet Solutions Architect
The Learning Business & Keywave
www.thelearningbiz.com
www.keywave.com
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!

MSDE 2000 and enterprise (enterprize) manager remotely

Monday, March 19, 2012

MSDE + Entreprise Manager.....again

But I thing that question has never been asked before...:-)
I use Entreprise manager to manage my MSDE on my windows XP machine.
I also have on my network a SQL Server 2000.
My problem is that I cannot add my MSDE to my Entreprise manager localted on
my SQL box.
Is this by design? Can I manage my MSDE remotely from my SQL box?
Thanks
JP
JP Breton wrote:
> But I thing that question has never been asked before...:-)
> I use Entreprise manager to manage my MSDE on my windows XP machine.
> I also have on my network a SQL Server 2000.
> My problem is that I cannot add my MSDE to my Entreprise manager localted on
> my SQL box.
> Is this by design? Can I manage my MSDE remotely from my SQL box?
> Thanks
> JP
>
Hi,
there is the option DISABLENETWORKPROTOCOLS by installing MSDE, if
DISABLENETWORKPROTOCOLS=1 you can't reach the MSDE instance remotely.
Matthias Beuder
Wenn schon Mails an diesen Account sein mssen, dann bitte mit *from NG*
im Subject. Ansonsten landet die Nachricht direkt im Trash-Ordner!
Please add *from NG* to subject, otherwise the message will be moved to
the trash directory!
http://www.beuder.de
|||thanks Mathias
"Matthias Beuder" <newsgroup.user@.beuder.de> wrote in message
news:d8bvf8$2go$1@.online.de...
> JP Breton wrote:
> Hi,
> there is the option DISABLENETWORKPROTOCOLS by installing MSDE, if
> DISABLENETWORKPROTOCOLS=1 you can't reach the MSDE instance remotely.
> --
> Matthias Beuder
> Wenn schon Mails an diesen Account sein mssen, dann bitte mit *from NG*
> im Subject. Ansonsten landet die Nachricht direkt im Trash-Ordner!
> Please add *from NG* to subject, otherwise the message will be moved to
> the trash directory!
> http://www.beuder.de

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
>

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 GaethofsDear 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:
>> 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 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:
>> 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
>

MSDE / ODBC install problem...please help...

I have installed MSDE (and ODBC) at my client site on their 2003 server. I
have attached my SQL database via Teratrax Database Manager to the MSDE
server however when I try to setup the ODBC connection it doesn't list the
database in the drop-down. I cannot attach to the database from my notebook
either because I am not authenticated onto their domain.
I have also applied the regedit on the LoginMode key setting it to 2 and
rebooted but I still cannot connect to the database via the ODBC manager.
What am I doing wrong? I am NOT good with the scripts for configuring things
- generally I use the Enterprise Manager.
Try running the client config (cliconfig.exe) and create an alias for the
server. Specify the protocol to talk to it - (probably TCP/IP vs. named
pipes). On my system its in \windows\system32.
Brian
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:46518420-EF43-475F-BECA-9E5A7E6A21D2@.microsoft.com...
>I have installed MSDE (and ODBC) at my client site on their 2003 server. I
> have attached my SQL database via Teratrax Database Manager to the MSDE
> server however when I try to setup the ODBC connection it doesn't list the
> database in the drop-down. I cannot attach to the database from my
> notebook
> either because I am not authenticated onto their domain.
> I have also applied the regedit on the LoginMode key setting it to 2 and
> rebooted but I still cannot connect to the database via the ODBC manager.
> What am I doing wrong? I am NOT good with the scripts for configuring
> things
> - generally I use the Enterprise Manager.

MSDE (SQL Server does not exist or access denied.)

Hi all,
I'm getting this error message when I try to connect my MSDE database from other machine using enterprise manager application. Both of the machines are WinXP SP2. I found some solution such as using 'SQLServer Network Utility' but didn't work out for me. I even can not connect my database on my computer using TCP/IP. When I connect with name, it worked fine. I already enable both TCP/IP and Named pipe protocol on the MSDE machine.
If someone has solution on that please let me know.

Thanks,
MyoDid you open the ports on the computers ?

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||If you have SQL Server 2005 installed on the same box as the MSDE, you need make sure SQL Browser is running. Make sure the ports (UDP/1434 and your TCP Port) are open if firewall exists. Also try file sharing between machines and make it work, otherwise NP won't work. When you use cliconfg.exe, make TCP and NP are on the client protocol lists.|||
Yes,
There is also SQL 2000 and 2005Express running together with MSDE. I already changed the port no and try to connect it. But, still didn't work out. I tried at the other machine and it works. I don't know why it still doesn't work at this machine. May be I miss some configuration. I'll try again. Thanks for the message.

Regards,
Myo|||

I have exactly the same issue. I have installed MSDE2000 on a PC with Windows XP Professional and SP2. I have tried everything to connect to another remote server and still get the same error message

I have added ports 135 and ports 445 to the firewall but again without much success. Does anyone out there have any ideas on how to get this working?

|||You will first have to determine the port that MSDE is using by starting the application Srvnetcn.exe naviagte to TCP and note that number down. After this you will have to create an exclude filter for the firewall for the application sqlservr.exe using this number and the 1434 UDP for incoming request. That should egt you started for SQL Server.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

Hi Jens,

Many thanks for your prompt response. I have tried all your suggestions but still cannot gain access to a remote database. TCP/IP is running on port 1433, using Srvnetcn.exe to check, and I have added both the entries you have suggested to the firewall exclude lists. Any other ideas? Thanks in advance

Monday, March 12, 2012

MSDE & SQL Server Agent

Can anyone tell me if the SQL Server Agent is included with MSDE? I realize
that Query Analyzer and Enterprise Manager are not included. I intend to use
MSDE for a project and would like to create jobs that will get scheduled by
SQL Server Agent.
Thanks.
Yes, Agent is included.
Andrew J. Kelly SQL MVP
"Amos Soma" <amos_j_soma@.y_a_hoo.com> wrote in message
news:jMqdnVEia9dLsULdRVn-vA@.buckeye-express.com...
> Can anyone tell me if the SQL Server Agent is included with MSDE? I
realize
> that Query Analyzer and Enterprise Manager are not included. I intend to
use
> MSDE for a project and would like to create jobs that will get scheduled
by
> SQL Server Agent.
> Thanks.
>

Friday, March 30, 2012

MSDE and Enterprise Manager?

MSDE and Enterprise Manager Trouble

MSDE and Enterprise Manager

MSDE and Enterprise Manager

MSDE and Enterprise manager

Monday, March 26, 2012

MSDE 2000 Release A won't talk

MSDE 2000 Release A won't talk

MSDE 2000 Release A wont talk

msde 2000 on windows 2003 server

Friday, March 23, 2012

MSDE 2000 Downloaded and Installed But where is Enterprise Manager

MSDE 2000 Downloaded and Installed But where is Enterprise Manager

MSDE 2000 Downloaded and Installed But where is Enterprise Manager

Wednesday, March 21, 2012

MSDE 2000 and enterprise (enterprize) manager remotely

MSDE 2000 and enterprise (enterprize) manager remotely

Monday, March 19, 2012

MSDE + Entreprise Manager.....again

MSDE / SQL - SERVER

MSDE / SQL - SERVER

MSDE / ODBC install problem...please help...

MSDE (SQL Server does not exist or access denied.)

Monday, March 12, 2012

MSDE & SQL Server Agent

MSDB database restore

Blog Archive

About Me