MSDE SQL Service Manager is not installed

I am installing MSDE from the SQL Server 2000 CD on a W2K
Pro environment. No errors in installation. There is no
service installed to start SQL Server. Any ideas?
hi Rick,
"Rick" <rsexauer@.avayle.com> ha scritto nel messaggio
news:cde901c48a55$bb29d270$a601280a@.phx.gbl...
> I am installing MSDE from the SQL Server 2000 CD on a W2K
> Pro environment. No errors in installation. There is no
> service installed to start SQL Server. Any ideas?
actually, Service Manager should be present in the tray area...
can you please confirm, browsing the installed services in the control
panel->services applet that MSDE is properly installed?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE setup / installation

Hi
I am a beginner in this, may I asked some basic question
1. do I need any version of MSDE before installing MSDE2000 sp3?
2. I have an environment with two servers, each of these has a web server
with a DC running, and I have written a .NET application for administrator
to maintain user a/c in this domain. Now, I would like to use a MSDE server
for keeping logs.
Can I have an installation of MSDE on each of these servers such that the
two installation would synchronize on a periodic basis?
Please note that changes of records are expected on either of these servers!
TIA
hi,
dl wrote:
> Hi
> I am a beginner in this, may I asked some basic question
> 1. do I need any version of MSDE before installing MSDE2000 sp3?
no, you can just directly install MSDE Rel A (sp3a level) and upgrade to sp4
via http://www.microsoft.com/sql/downloads/2000/sp4.mspx MSDE package (or
directly install MSDE at the sp4 level... but currently it's not clear to me
if general users not owning a "required" SQL Server license as per
http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp are eligile for
direct sp4 use... just a note, Microsoft representatives already exposed a
refresh of MSDE Rel A updated at sp4 level will be made available...)

> 2. I have an environment with two servers, each of these has a web
> server with a DC running, and I have written a .NET application for
> administrator to maintain user a/c in this domain. Now, I would like
> to use a MSDE server for keeping logs.
> Can I have an installation of MSDE on each of these servers such that
> the two installation would synchronize on a periodic basis?
> Please note that changes of records are expected on either of these
> servers!
>
yes, you can install MSDE on both servers, and even provide a replication
paht between the 2 MSDE instances, as MSDE supports merge and snapshot
replication
(http://msdn.microsoft.com/library/de...lover_694n.asp)
but, unfortunately, without Enterprise Manager tool it will be not trivial
to set it up
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||In message <ei6anK5cFHA.3488@.tk2msftngp13.phx.gbl>, dl@.?.?.invalid
writes
>Hi
>I am a beginner in this, may I asked some basic question
>1. do I need any version of MSDE before installing MSDE2000 sp3?
If your download file for sp3 is about 60-70mb then know it will install
MSDE at the same time if not present. You would be better using the
MSDERelA package (which includes sp3).

>2. I have an environment with two servers, each of these has a web server
>with a DC running, and I have written a .NET application for administrator
>to maintain user a/c in this domain. Now, I would like to use a MSDE server
>for keeping logs.
>Can I have an installation of MSDE on each of these servers such that the
>two installation would synchronize on a periodic basis?
>Please note that changes of records are expected on either of these servers!
Yes. You can have as many instances per server as you like (well up to
16 anyway - I think thats the right number). Yes you can use DTS to
keep the servers synchronised (you would normally pick one as the master
however). Just make sure your database and table design are decent (ie:
Primary Keys etc).
Andrew D. Newbould E-Mail: newsgroups@.NOSPAMzadsoft.com
ZAD Software Systems Web : www.zadsoft.com

MSDE Settings not being used

I'm trying to install MSDE 2000 in and XP environment. I want to install it in a specific sub-directory therfore, I'm using a setting ini file to give the instance name, target dir and data dir. I've included both the command line and ini file below:
Command Line Entry:
C:\MSDE2000\setup.exe SAPWD="xxxxxx" /settings "C:\SageQuestLou\DispatcherDB.INI" /L*v C:\SageQuestLou\MSDE.LOG
Settings file:
INSTANCENAME=SageQuest
DISABLENETWORKPROTOCOLS=0
SECURITYMODE=SQL
DATADIR="C:\SageQuestLou\Data\"
TARGETDIR="C:\SageQuestLou\"
The installation does occur successfully however it installs using default parameters. However I don't know what the SA password is and it's not where I want it to be.
Can some tell me what wrong with my command line or ini file?
Thanks
Louis
try this to solve pwd problem:
setup /settings="C:\SageQuestLou\DispatcherDB.INI" /i
DISABLENETWORKPROTOCOLS=0 SAPWD=xxxxx SecurityMode=SQL /L*v
C:\SageQuestLou\MSDE.LOG
I'm guessing the SecurityMode param might help here.
"Louis" <anonymous@.discussions.microsoft.com> wrote in message
news:41C137B8-4DEB-430C-A10D-95200B9060A4@.microsoft.com...
> I'm trying to install MSDE 2000 in and XP environment. I want to install
it in a specific sub-directory therfore, I'm using a setting ini file to
give the instance name, target dir and data dir. I've included both the
command line and ini file below:
> Command Line Entry:
> C:\MSDE2000\setup.exe SAPWD="xxxxxx" /settings
"C:\SageQuestLou\DispatcherDB.INI" /L*v C:\SageQuestLou\MSDE.LOG
> Settings file:
> INSTANCENAME=SageQuest
> DISABLENETWORKPROTOCOLS=0
> SECURITYMODE=SQL
> DATADIR="C:\SageQuestLou\Data\"
> TARGETDIR="C:\SageQuestLou\"
> The installation does occur successfully however it installs using default
parameters. However I don't know what the SA password is and it's not where
I want it to be.
> Can some tell me what wrong with my command line or ini file?
>
> Thanks
> Louis

MSDE Replication in Workgroup Enviromnet

We currently have two machines in a workgroup environment and both are
running WIndows XP Pro SP1 and MSDE Sp3.
The problem we have is with the Merge Replication. The publisher writes
snapshot data to the snapshot folder, but the subscriber is unable to open
this file across the network. We get error 5 access denied.
From the subscriber PC through explorer/notepad we can open the file. The
file name is MSmerge_genhistory.bcp
If we were to put the pc into a domain we have no problem. Replication wor
Replication is probably accessing this file through a admin share
something like \\servername\d$\xxxxx\repldata\ which needs admin access to
the distributor machine.
Try configuring a named share like \\servername\repldata and allow access to
relevant user and set that to be the working directory. You can set the
working directory when configuring publisher
or through sp_adddistpublisher or sp_changedistpublisher.
This posting is provided "AS IS" with no warranties, and confers no rights.
OR if you wish to include a script sample in your post please add "Use of
included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm"
"Colin M" <ColinM@.discussions.microsoft.com> wrote in message
news:027D0BE9-2D57-4DF4-888C-173A7FCD3404@.microsoft.com...
> We currently have two machines in a workgroup environment and both are
> running WIndows XP Pro SP1 and MSDE Sp3.
> The problem we have is with the Merge Replication. The publisher writes
> snapshot data to the snapshot folder, but the subscriber is unable to open
> this file across the network. We get error 5 access denied.
> From the subscriber PC through explorer/notepad we can open the file. The
> file name is MSmerge_genhistory.bcp
>
> If we were to put the pc into a domain we have no problem. Replication wor

MSDE over the network

Please help! I've had this problem for FOREVER. It's driving me batty.
I'm installing MSDE in a networked environment. I'm using SQL-DMO to find all
instances of MSDE on the network. *Usually*, this works great.
Unfortunately, sometimes MSDE instances refuse to advertise on the network.
I can't register them in Enterprise Manager or see them with SQL-DMO. I'm
using setup.exe to install these instances, and I'm setting
DISABLENETWORKPROTOCOLS=0. I've run the svrnetcn.exe program, and each
vanished instance is in fact listening via TCP/IP and Remote Procedure Calls.
I've added each instance as an exception in the Windows Firewall on XP SP2.
Each disappeared instance has in fact been started. Local applications can
see these vanished instances, but networked applications cannot. There are no
other firewalls or packet filtering on the network. I'm behind a Microsoft
Wireless Base Station Router. Am I missing something?
This problem is about to drive me insane. I'm using the exact same
installation program and parameters to setup.exe, but some instances just
don't want to play on the network. Any help would be greatly appreciated.
Thanks in advance.
Rob Reagan
rob at digitallabsinc.com
Are any of the MSDE instances installed on XP SP2? If the MSDE instance does
not have SP3 installed then XP will block MSDE from broadcasting its status.
You can see warnings about this in the system event log. This is the same
with Windows Server 2003.
Jim
"Rob Reagan" <RobReagan@.discussions.microsoft.com> wrote in message
news:ED94255F-732F-4DFF-B994-CEAD94B90354@.microsoft.com...
> Please help! I've had this problem for FOREVER. It's driving me batty.
> I'm installing MSDE in a networked environment. I'm using SQL-DMO to find
all
> instances of MSDE on the network. *Usually*, this works great.
> Unfortunately, sometimes MSDE instances refuse to advertise on the
network.
> I can't register them in Enterprise Manager or see them with SQL-DMO. I'm
> using setup.exe to install these instances, and I'm setting
> DISABLENETWORKPROTOCOLS=0. I've run the svrnetcn.exe program, and each
> vanished instance is in fact listening via TCP/IP and Remote Procedure
Calls.
> I've added each instance as an exception in the Windows Firewall on XP
SP2.
> Each disappeared instance has in fact been started. Local applications can
> see these vanished instances, but networked applications cannot. There are
no
> other firewalls or packet filtering on the network. I'm behind a Microsoft
> Wireless Base Station Router. Am I missing something?
> This problem is about to drive me insane. I'm using the exact same
> installation program and parameters to setup.exe, but some instances just
> don't want to play on the network. Any help would be greatly appreciated.
> Thanks in advance.
> Rob Reagan
> rob at digitallabsinc.com
>
|||YOU ARE THE MAN! Thanks so much for that response.
"Jim Young" wrote:

> Are any of the MSDE instances installed on XP SP2? If the MSDE instance does
> not have SP3 installed then XP will block MSDE from broadcasting its status.
> You can see warnings about this in the system event log. This is the same
> with Windows Server 2003.
> Jim
> "Rob Reagan" <RobReagan@.discussions.microsoft.com> wrote in message
> news:ED94255F-732F-4DFF-B994-CEAD94B90354@.microsoft.com...
> all
> network.
> Calls.
> SP2.
> no
>
>

MSDE instance being broadcast

I work in a domain environment with a couple of Enterprise Edition SQL
Servers. Using SSMS, when I go to register a new installation and I 'Browse
for more' in the dialog box, I see a whole bunch of workstations that I know
are set up with MSDE.
How do I keep these machines from broadcasting their presence to the domain?
All these MSDE installs are strictly for local machine use only and none of
them should allow external connections. The fact that they are broadcasting
their presence (they don't have SQL Browser because they are only MSDE) I see
as a security risk. How can I stop this?
Any suggestions.
Thanks
Todd Chittenden
Yes, it is a security risk. It's been some time since I worked with MSDE,
but I would investigate disabling the ports and protocols--much as the
surface area configuration tool does for SQL Express 2005. This can be done
if the applications are coded to use the shared memory provider (and bypass
the network) and are not (in fact) shared on the net.
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:E302F2D1-165D-4DDB-BCA4-9BA587CBB237@.microsoft.com...
>I work in a domain environment with a couple of Enterprise Edition SQL
> Servers. Using SSMS, when I go to register a new installation and I
> 'Browse
> for more' in the dialog box, I see a whole bunch of workstations that I
> know
> are set up with MSDE.
> How do I keep these machines from broadcasting their presence to the
> domain?
> All these MSDE installs are strictly for local machine use only and none
> of
> them should allow external connections. The fact that they are
> broadcasting
> their presence (they don't have SQL Browser because they are only MSDE) I
> see
> as a security risk. How can I stop this?
> Any suggestions.
> Thanks
> --
> Todd Chittenden
>
|||Bill:
That's all well and good, but HOW do I go about configuring an instance of
MSDE when there is no user interface installed because it came packaged as
part of some 3rd party app?
Thanks
Todd Chittenden
"William (Bill) Vaughn" wrote:

> Yes, it is a security risk. It's been some time since I worked with MSDE,
> but I would investigate disabling the ports and protocols--much as the
> surface area configuration tool does for SQL Express 2005. This can be done
> if the applications are coded to use the shared memory provider (and bypass
> the network) and are not (in fact) shared on the net.
> hth
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Todd C" <ToddC@.discussions.microsoft.com> wrote in message
> news:E302F2D1-165D-4DDB-BCA4-9BA587CBB237@.microsoft.com...
>
>
|||Again, it's been some time since I worked with MSDE and no, I know it does
not come with configuration tools. I expect you're going to have to visit
each system and run a reconfig script or use SQL Server Management studio
(not as easy). I found a site that seems to address some of these issues.
http://www.codeproject.com/database/ConfigureMSDE.asp#7. I hope it helps.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:2DF6889A-A64A-483F-BE42-766155FC8AF7@.microsoft.com...[vbcol=seagreen]
> Bill:
> That's all well and good, but HOW do I go about configuring an instance of
> MSDE when there is no user interface installed because it came packaged as
> part of some 3rd party app?
> Thanks
> --
> Todd Chittenden
> "William (Bill) Vaughn" wrote:
|||Bill:
Thanks.
Good stuff!
Todd

MSDE instance being broadcast

I work in a domain environment with a couple of Enterprise Edition SQL
Servers. Using SSMS, when I go to register a new installation and I 'Browse
for more' in the dialog box, I see a whole bunch of workstations that I know
are set up with MSDE.
How do I keep these machines from broadcasting their presence to the domain?
All these MSDE installs are strictly for local machine use only and none of
them should allow external connections. The fact that they are broadcasting
their presence (they don't have SQL Browser because they are only MSDE) I se
e
as a security risk. How can I stop this?
Any suggestions.
Thanks
--
Todd ChittendenYes, it is a security risk. It's been some time since I worked with MSDE,
but I would investigate disabling the ports and protocols--much as the
surface area configuration tool does for SQL Express 2005. This can be done
if the applications are coded to use the shared memory provider (and bypass
the network) and are not (in fact) shared on the net.
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:E302F2D1-165D-4DDB-BCA4-9BA587CBB237@.microsoft.com...
>I work in a domain environment with a couple of Enterprise Edition SQL
> Servers. Using SSMS, when I go to register a new installation and I
> 'Browse
> for more' in the dialog box, I see a whole bunch of workstations that I
> know
> are set up with MSDE.
> How do I keep these machines from broadcasting their presence to the
> domain?
> All these MSDE installs are strictly for local machine use only and none
> of
> them should allow external connections. The fact that they are
> broadcasting
> their presence (they don't have SQL Browser because they are only MSDE) I
> see
> as a security risk. How can I stop this?
> Any suggestions.
> Thanks
> --
> Todd Chittenden
>|||Bill:
That's all well and good, but HOW do I go about configuring an instance of
MSDE when there is no user interface installed because it came packaged as
part of some 3rd party app?
Thanks
--
Todd Chittenden
"William (Bill) Vaughn" wrote:

> Yes, it is a security risk. It's been some time since I worked with MSDE,
> but I would investigate disabling the ports and protocols--much as the
> surface area configuration tool does for SQL Express 2005. This can be don
e
> if the applications are coded to use the shared memory provider (and bypas
s
> the network) and are not (in fact) shared on the net.
> hth
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "Todd C" <ToddC@.discussions.microsoft.com> wrote in message
> news:E302F2D1-165D-4DDB-BCA4-9BA587CBB237@.microsoft.com...
>
>|||Again, it's been some time since I worked with MSDE and no, I know it does
not come with configuration tools. I expect you're going to have to visit
each system and run a reconfig script or use SQL Server Management studio
(not as easy). I found a site that seems to address some of these issues.
http://www.codeproject.com/database...gureMSDE.asp#7. I hope it helps.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:2DF6889A-A64A-483F-BE42-766155FC8AF7@.microsoft.com...[vbcol=seagreen]
> Bill:
> That's all well and good, but HOW do I go about configuring an instance of
> MSDE when there is no user interface installed because it came packaged as
> part of some 3rd party app?
> Thanks
> --
> Todd Chittenden
> "William (Bill) Vaughn" wrote:
>|||Bill:
Thanks.
Good stuff!
Todd

MSDE in Production environment

I have a burning, question, sorry if this has been asked already.

How does the licencing for MSDE work, do you need to "OWN" a valid MS SQL Server licence to use MSDE in production enviroment.

I have a legally purchased copy of Office 2000, which includes MSDE installer. If I want to install this on my webserver for example and run a forum off it (this one for example), the forum will be on the WWW. Will I need a seperate licence for MSDE ?

Please helpAll you will ever need to know is here:

http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp

MSDE Environment

Dear all,
i'm new in MSDE, yet, after i'd installed for MSDE ReleaseA which i
get from SQL web site, i realise that I can't run the MSDE without
fully SQL server install, may i know that whether i can run MSDE
without fully SQL SERVER install? if so, how to use it...
pls give me some guide on that, thanks in advance!! :wink:
MSDE IS Sql Server, and does not need full SQL Server installed (otherwise,
why MSDE?). MSDE Download does not come with good document on how to install
it properly for user who does not have experience on SQL Server. I recommend
search MS Knowledge base with key word "MSDE" to get get more detailed
installation guide.
"themafia907" <themafia907@.yahoo-dot-com.no-spam.invalid> wrote in message
news:JMSdnRvJOr2GFYTfRVn_vA@.giganews.com...
> Dear all,
> i'm new in MSDE, yet, after i'd installed for MSDE ReleaseA which i
> get from SQL web site, i realise that I can't run the MSDE without
> fully SQL server install, may i know that whether i can run MSDE
> without fully SQL SERVER install? if so, how to use it...
> pls give me some guide on that, thanks in advance!! :wink:
>
|||Hi
When you run the MSDE Setup, it installs the SQL Server MSDE Edition Engine.
No tools are supplied with MSDE.
Full editions of SQL Server is not required to run MSDE. MSDE is an stripped
down Edition of SQL Server.
What are you trying to achive?
Regards
Mike
"themafia907" wrote:

> Dear all,
> i'm new in MSDE, yet, after i'd installed for MSDE ReleaseA which i
> get from SQL web site, i realise that I can't run the MSDE without
> fully SQL server install, may i know that whether i can run MSDE
> without fully SQL SERVER install? if so, how to use it...
> pls give me some guide on that, thanks in advance!! :wink:
>