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.

MSDE + Restricted Accounts

I appologize if this is in the wrong place. I have MSDE 2000 installed on a
machine to be used only by the local user. It is using mixed-mode authentic
ation. The machine is running windows 2000. When I login as a Restricted Use
r that user can't start the
MQSQL Server service. An Error 5 (Access Denied) is reported. I read in the
KB before that MSDE and even accesss 2000 can not run on restricted user acc
ounts by design. I would just like a link to that KB article. I have searche
d all day for it and I can
't seem to find the right combination of keywords. Thanks so much. Most of t
he KB articles seem to be only for XP, .NET and Office 2003.The problem is that only local admins have permission to stop and start
services.
You should be able to configure the MSSQL service to start automatically,
using a limited user account.
But, as a limited user logging onto a machine, you won't have the ability
to stop and start services.
Here's a referenced to the startup account permissions.
http://www.microsoft.com/technet/pr...n/sp3sec02.mspx
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

MSDE (yes I know this is the wrong group)

I have asked this in the MSDE group and had no replies, so I wondered if, as
it's basically SQL qithout the interface and with limits), whether you
knowledgeable people could answer this for me.
Is there any problems (operationally wise, or conflict wise) with putting
MSDE 2000 A on a Windows 2000 Server which is a domain controller (the
server also has Exchange 2000 and ISA 2000 installed on it)?
I can obviously restrict the memory it can use so that's not a problem, but
I wondered if it would create problems or serious performance issues for the
DC.
Also, if it is OK to install on a DC, is the installation straightforward or
are there any special switches or settings I should use? Or do I just do a
plain install as I would on any machine?
Thanks
KeithIt is not a problem to install it on the DC. There is no difference in
instalation.
Generally it is not recommended because of the Microsoft's concept: one
server - one machine, but there are no problems with that.
Bojidar Alexandrov
"Keith" <@..> wrote in message news:uJZ0UXQLEHA.1484@.tk2msftngp13.phx.gbl...
> I have asked this in the MSDE group and had no replies, so I wondered if,
as
> it's basically SQL qithout the interface and with limits), whether you
> knowledgeable people could answer this for me.
> Is there any problems (operationally wise, or conflict wise) with putting
> MSDE 2000 A on a Windows 2000 Server which is a domain controller (the
> server also has Exchange 2000 and ISA 2000 installed on it)?
> I can obviously restrict the memory it can use so that's not a problem,
but
> I wondered if it would create problems or serious performance issues for
the
> DC.
> Also, if it is OK to install on a DC, is the installation straightforward
or
> are there any special switches or settings I should use? Or do I just do
a
> plain install as I would on any machine?
> Thanks
> Keith
>|||I'd agree with that although I havent needed to do it
Simon|||Keith,
I posted a reply today, where I pointed out a potential issue with your serv
ice account.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Keith" <@..> wrote in message news:uJZ0UXQLEHA.1484@.tk2msftngp13.phx.gbl...
> I have asked this in the MSDE group and had no replies, so I wondered if,
as
> it's basically SQL qithout the interface and with limits), whether you
> knowledgeable people could answer this for me.
> Is there any problems (operationally wise, or conflict wise) with putting
> MSDE 2000 A on a Windows 2000 Server which is a domain controller (the
> server also has Exchange 2000 and ISA 2000 installed on it)?
> I can obviously restrict the memory it can use so that's not a problem, bu
t
> I wondered if it would create problems or serious performance issues for t
he
> DC.
> Also, if it is OK to install on a DC, is the installation straightforward
or
> are there any special switches or settings I should use? Or do I just do
a
> plain install as I would on any machine?
> Thanks
> Keith
>

MSDE (yes I know this is the wrong group)

I have asked this in the MSDE group and had no replies, so I wondered if, as
it's basically SQL qithout the interface and with limits), whether you
knowledgeable people could answer this for me.
Is there any problems (operationally wise, or conflict wise) with putting
MSDE 2000 A on a Windows 2000 Server which is a domain controller (the
server also has Exchange 2000 and ISA 2000 installed on it)?
I can obviously restrict the memory it can use so that's not a problem, but
I wondered if it would create problems or serious performance issues for the
DC.
Also, if it is OK to install on a DC, is the installation straightforward or
are there any special switches or settings I should use? Or do I just do a
plain install as I would on any machine?
Thanks
Keith
It is not a problem to install it on the DC. There is no difference in
instalation.
Generally it is not recommended because of the Microsoft's concept: one
server - one machine, but there are no problems with that.
Bojidar Alexandrov
"Keith" <@..> wrote in message news:uJZ0UXQLEHA.1484@.tk2msftngp13.phx.gbl...
> I have asked this in the MSDE group and had no replies, so I wondered if,
as
> it's basically SQL qithout the interface and with limits), whether you
> knowledgeable people could answer this for me.
> Is there any problems (operationally wise, or conflict wise) with putting
> MSDE 2000 A on a Windows 2000 Server which is a domain controller (the
> server also has Exchange 2000 and ISA 2000 installed on it)?
> I can obviously restrict the memory it can use so that's not a problem,
but
> I wondered if it would create problems or serious performance issues for
the
> DC.
> Also, if it is OK to install on a DC, is the installation straightforward
or
> are there any special switches or settings I should use? Or do I just do
a
> plain install as I would on any machine?
> Thanks
> Keith
>
|||I'd agree with that although I havent needed to do it
Simon
|||Keith,
I posted a reply today, where I pointed out a potential issue with your service account.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Keith" <@..> wrote in message news:uJZ0UXQLEHA.1484@.tk2msftngp13.phx.gbl...
> I have asked this in the MSDE group and had no replies, so I wondered if, as
> it's basically SQL qithout the interface and with limits), whether you
> knowledgeable people could answer this for me.
> Is there any problems (operationally wise, or conflict wise) with putting
> MSDE 2000 A on a Windows 2000 Server which is a domain controller (the
> server also has Exchange 2000 and ISA 2000 installed on it)?
> I can obviously restrict the memory it can use so that's not a problem, but
> I wondered if it would create problems or serious performance issues for the
> DC.
> Also, if it is OK to install on a DC, is the installation straightforward or
> are there any special switches or settings I should use? Or do I just do a
> plain install as I would on any machine?
> Thanks
> Keith
>

MSDE (yes I know this is the wrong group)

I have asked this in the MSDE group and had no replies, so I wondered if, as
it's basically SQL qithout the interface and with limits), whether you
knowledgeable people could answer this for me.
Is there any problems (operationally wise, or conflict wise) with putting
MSDE 2000 A on a Windows 2000 Server which is a domain controller (the
server also has Exchange 2000 and ISA 2000 installed on it)?
I can obviously restrict the memory it can use so that's not a problem, but
I wondered if it would create problems or serious performance issues for the
DC.
Also, if it is OK to install on a DC, is the installation straightforward or
are there any special switches or settings I should use? Or do I just do a
plain install as I would on any machine?
Thanks
KeithIt is not a problem to install it on the DC. There is no difference in
instalation.
Generally it is not recommended because of the Microsoft's concept: one
server - one machine, but there are no problems with that.
Bojidar Alexandrov
"Keith" <@..> wrote in message news:uJZ0UXQLEHA.1484@.tk2msftngp13.phx.gbl...
> I have asked this in the MSDE group and had no replies, so I wondered if,
as
> it's basically SQL qithout the interface and with limits), whether you
> knowledgeable people could answer this for me.
> Is there any problems (operationally wise, or conflict wise) with putting
> MSDE 2000 A on a Windows 2000 Server which is a domain controller (the
> server also has Exchange 2000 and ISA 2000 installed on it)?
> I can obviously restrict the memory it can use so that's not a problem,
but
> I wondered if it would create problems or serious performance issues for
the
> DC.
> Also, if it is OK to install on a DC, is the installation straightforward
or
> are there any special switches or settings I should use? Or do I just do
a
> plain install as I would on any machine?
> Thanks
> Keith
>|||I'd agree with that although I havent needed to do it
Simon|||Keith,
I posted a reply today, where I pointed out a potential issue with your service account.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Keith" <@..> wrote in message news:uJZ0UXQLEHA.1484@.tk2msftngp13.phx.gbl...
> I have asked this in the MSDE group and had no replies, so I wondered if, as
> it's basically SQL qithout the interface and with limits), whether you
> knowledgeable people could answer this for me.
> Is there any problems (operationally wise, or conflict wise) with putting
> MSDE 2000 A on a Windows 2000 Server which is a domain controller (the
> server also has Exchange 2000 and ISA 2000 installed on it)?
> I can obviously restrict the memory it can use so that's not a problem, but
> I wondered if it would create problems or serious performance issues for the
> DC.
> Also, if it is OK to install on a DC, is the installation straightforward or
> are there any special switches or settings I should use? Or do I just do a
> plain install as I would on any machine?
> Thanks
> Keith
>