MSDE on WinXP Pro SP2 joined to a domain

Hi,
I have a problem that I cannot find a resolution to.
Recently, I got a laptop and I installed WinXP Pro SP2 on it.
I did this at home so was not near my office domain so I temporarily setup
the laptop as a workgroup computer instead of joining the domain.
Once installed, I then installed MSDE2000RelA.
Everything was working fine.
Then I took the laptop to work, joined the domain, and now MSDE can no
longer connect. All I get in the system tray is a computer tower icon with a
white circle on it. Hovering over that pops up "Cannot connect \\". There
should be a green arrow in the circle when services start.
I have tried uninstalling, re-installing, changing user permissions in group
policy for the guest account? - all sorts of things, but nothing fixes this
issue - and I desperately need MSDE to work on the laptop.
I think it has something to do with the laptop being on the domain, but I
don't know (and that doesn't really make sense to me either).
Can anyone point me to a solution?
Cheers,
Rob
hi Rob
Did u set DISABLENETWORKPROTOCOLS=0 parameter while setup?
by default the setup will take 1 (means disable).
just check out
Dil
|||Ah, no I didn't!
Do I have to reinstall or can I update a previous installation with this
setting?
Cheers,
Rob
|||hi Rob,
RobGT wrote:
> Ah, no I didn't!
> Do I have to reinstall or can I update a previous installation with
> this setting?
please run the Server Network Utility (svrnetcn.exe) to enable the desired
network protocol..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Perfect, thankyou.
It appears to now be working fine.
Shame I found it so difficult to locate this information (I searched online
for ages before coming here to ask the question!)
Thanks a million for resolving this so quickly for me!
Cheers,
Rob

MSDE on a 2k Domain Controller

I have asked this before, but it was a while back and then the project got
put on hold, and I can't find the replies - sorry.
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
Anyone?
"Keith" <@..> wrote in message news:ehizqISKEHA.3436@.tk2msftngp13.phx.gbl...
> I have asked this before, but it was a while back and then the project got
> put on hold, and I can't find the replies - sorry.
> 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
>
|||A no-one responded yet...
Yes, you should be fine. One thing to consider is that your service account is now a domain account. I.e., a
potential security issue. (This is because a DC doesn't have any local accounts.)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Keith" <@..> wrote in message news:e2TJLgDLEHA.3704@.TK2MSFTNGP11.phx.gbl...
> Anyone?
>
> "Keith" <@..> wrote in message news:ehizqISKEHA.3436@.tk2msftngp13.phx.gbl...
> but
> the
> or
> a
>
sql

MSDE Named Service Connection Problem

I installed SQL 2000 MSDE 2000RelA on Win2K Adv. Server w/ Win2K SP4 (fully
patched), and operating as the only domain controller. I have also run the
IISLockdown Tool on this server.
I originally ran setup using the following parameters:
setup sapwd="xxxxxxx" and SQL Service Manager was connecting properly.
I later uninstalled MSDE 2000 RelA and re-installed (no reboot in between)
with the following parameters:
setup sapwd="xxxxxxx" instancename=WSUS
I then installed SQL2000 MSDE SP4, and the Service Manager can no longer
connect to any service and appears in the task bar with a blank icon. When I
open the Service Manager, all fields (server,services) are blank. Pressing
start button will give me:
"The service control action cannot be completed as no
service has been selected"
I entered the server's name in the server field, but no services can be
resolved.
I see MSSQL$WSUS service has started. Further down I noticed
SQLAgent$TESTING service had not started. I started that up, but no change.
Also tried to startup MSSQLServerADHelper but it gave me an error.
I then uninstalled SQL2000 MSDE and deleted each of the relevant Registry
keys and SQL Server folder under Program Files.
I again re-installed using the sapwd and instancename parameters but to no
avail.
Can anyone tell me how I can get this working properly?
Thanks!
You could have tried to enter "ComputerName\WSUS" in the service manager
when showed nothing in the server list, and then clicked "Start" button.
Somethimes, for some reason, service manager could not detect any running
SQL/MSDE on the computer/network.
"stantm1" <stantm1@.discussions.microsoft.com> wrote in message
news:5BF4C64E-8D57-4CC1-837B-CB143CCB6329@.microsoft.com...
>I installed SQL 2000 MSDE 2000RelA on Win2K Adv. Server w/ Win2K SP4 (fully
> patched), and operating as the only domain controller. I have also run the
> IISLockdown Tool on this server.
> I originally ran setup using the following parameters:
> setup sapwd="xxxxxxx" and SQL Service Manager was connecting properly.
> I later uninstalled MSDE 2000 RelA and re-installed (no reboot in between)
> with the following parameters:
> setup sapwd="xxxxxxx" instancename=WSUS
> I then installed SQL2000 MSDE SP4, and the Service Manager can no longer
> connect to any service and appears in the task bar with a blank icon. When
> I
> open the Service Manager, all fields (server,services) are blank. Pressing
> start button will give me:
> "The service control action cannot be completed as no
> service has been selected"
> I entered the server's name in the server field, but no services can be
> resolved.
> I see MSSQL$WSUS service has started. Further down I noticed
> SQLAgent$TESTING service had not started. I started that up, but no
> change.
> Also tried to startup MSSQLServerADHelper but it gave me an error.
> I then uninstalled SQL2000 MSDE and deleted each of the relevant Registry
> keys and SQL Server folder under Program Files.
> I again re-installed using the sapwd and instancename parameters but to no
> avail.
> Can anyone tell me how I can get this working properly?
> Thanks!
|||Thanks, Norman. I'll give it a try.
"Norman Yuan" wrote:

> You could have tried to enter "ComputerName\WSUS" in the service manager
> when showed nothing in the server list, and then clicked "Start" button.
> Somethimes, for some reason, service manager could not detect any running
> SQL/MSDE on the computer/network.
> "stantm1" <stantm1@.discussions.microsoft.com> wrote in message
> news:5BF4C64E-8D57-4CC1-837B-CB143CCB6329@.microsoft.com...
>
>
|||Actually it found the instance of sql server just fine. My machine was in
the list of sql servers but when i try to connect to it i have problems.
Just to let you know im using Windows Authentication and i am an
administrator on this machine.
Brent
"Norman Yuan" <NotReal@.NotReal.not> wrote in message
news:usGQBJbLGHA.3496@.TK2MSFTNGP14.phx.gbl...
> You could have tried to enter "ComputerName\WSUS" in the service manager
> when showed nothing in the server list, and then clicked "Start" button.
> Somethimes, for some reason, service manager could not detect any running
> SQL/MSDE on the computer/network.
> "stantm1" <stantm1@.discussions.microsoft.com> wrote in message
> news:5BF4C64E-8D57-4CC1-837B-CB143CCB6329@.microsoft.com...
>

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 installation/connection issues

I installed MSDE (sp3a) in a Windows 2000 server SP4. This is configured to
be a domain controller and (AD turned on). I can use MSDE webadmin to
access the database instance fine. I have a couple of problems.
1. MSSQLServerADHelper service does not startup.
System log message is:
The MSSQLServerADHelper service terminated with service-specific error
3221225572.
Corresponding Application log error is:
'0' is an invalid number of start up parameters. This service takes two
start up parameters.
2.Despite following the instructions in KB article: 840219 I still 'm not
able to login to MSDE using OSQL from a command prompt. Error message is:
Cr>osql -U domain\administrator -P xxxx
Login failed for user 'domain\administrator'. Reason: Not associated with a
trusted SQL Server connection.
Is something wrong with my syntax for the value for the -U parameter? I
restarted the SQL server and the agent services after following the steps in
840219.
Any suggestions appreciated.
hi,
"public.microsoft.com" <lakamsani AT gmail.com> ha scritto nel messaggio
news:%23kZ5Z$cbEHA.3684@.TK2MSFTNGP09.phx.gbl...
> I installed MSDE (sp3a) in a Windows 2000 server SP4. This is configured
to
> be a domain controller and (AD turned on). I can use MSDE webadmin to
> access the database instance fine. I have a couple of problems.
> 1. MSSQLServerADHelper service does not startup.
> System log message is:
> The MSSQLServerADHelper service terminated with service-specific error
> 3221225572.
please have a look at http://tinyurl.com/6qwgg

> 2.Despite following the instructions in KB article: 840219 I still 'm not
> able to login to MSDE using OSQL from a command prompt. Error message is:
> Cr>osql -U domain\administrator -P xxxx
> Login failed for user 'domain\administrator'. Reason: Not associated with
a
> trusted SQL Server connection.
> Is something wrong with my syntax for the value for the -U parameter? I
> restarted the SQL server and the agent services after following the steps
in
> 840219.
for trusted connections, you shoul'd pass the -E parameter (where -E
specifys a trusted connection using you actual WindowsNT login credential)
instead that providing SQL Server authenticated related credentials...
tipically
c:\>osql -E
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 HELP

Hi,
I have 2 PCs that aren't in any domain.
One of PCs, have installed on MSDE. I change the authentication
mode from windows to mixed mode.
Created users inside MSDE.
In the PC with MSDE I can enter with all users, but in the other PC I could
not connect to the server.
I tried to register in Enterprise Manager that MSDE instalation and I get
the following error
SQL Server Enterprise Manager
SQL Server registration failed because of the connection failure displayed
below. Do you wish to Register anyway?
SQL Server does not exist or access denied.
ConnectionOpen (Connect())
Yes No
I already add the TCP 1433 and UDP 1434 ports to windows firewal, I tried to
with the firewall disconected and i get always the same error.
So I think the problem could be in permissions, but how can I set permisons
in one computer to a user from another computer. Don't forget that the pcs
aren't in any domain.
Or how can I put on PC connecting to the MSDE in the other PC?
thanks
Mestre
hi Mestre,
Mestre wrote:
> Hi,
> I have 2 PCs that aren't in any domain.
> One of PCs, have installed on MSDE. I change the authentication
> mode from windows to mixed mode.
> Created users inside MSDE.
> In the PC with MSDE I can enter with all users, but in the other PC I
> could not connect to the server.
> I tried to register in Enterprise Manager that MSDE instalation and I
> get the following error
> --
> SQL Server Enterprise Manager
> --
> SQL Server registration failed because of the connection failure
> displayed below. Do you wish to Register anyway?
> SQL Server does not exist or access denied.
> ConnectionOpen (Connect())
> --
> Yes No
> --
>
> I already add the TCP 1433 and UDP 1434 ports to windows firewal, I
> tried to with the firewall disconected and i get always the same
> error.
> So I think the problem could be in permissions, but how can I set
> permisons in one computer to a user from another computer. Don't
> forget that the pcs aren't in any domain.
> Or how can I put on PC connecting to the MSDE in the other PC?
please have a look at
http://support.microsoft.com/default...06&Product=sql
for the most common causes of this exception.. and of course please verify
that remote access to the instance is enabled with the Server Network
Utility (svrnetcn.exe) as MSDE installs by default disabling all network
protocols...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.16.0 - DbaMgr ver 0.61.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea,
you're right. I discover that, but I ony have time to update the posts
today.
Thanks,
Mestre
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:4271egF1hrbv5U1@.individual.net...
> hi Mestre,
> Mestre wrote:
> please have a look at
> http://support.microsoft.com/default...06&Product=sql
> for the most common causes of this exception.. and of course please verify
> that remote access to the instance is enabled with the Server Network
> Utility (svrnetcn.exe) as MSDE installs by default disabling all network
> protocols...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.16.0 - DbaMgr ver 0.61.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>