MSDE TCP listen problem

I have recently installed a MSDE 2000 (unfortunately with no service pack yet) on a Standard Windows 2003 server. I have used the srvntcn.exe utility to make the MSDE server listen on TCP/IP port 1433. But it will not listen on that port! Or any other TCP
/IP port!! There is no information in the ERRORLOG file. This file just tells me, that MSDE is listening on Named Pipes and Shared Memory.
I have tried making my own application listen on port 1433 to see if there were some security settings on that port. And my application had no problem in listening on port 1433.
After looking in the Event Viewer I found a solution to my problem: Windows 2003 Server automatically close down TCP/IP listening for MSDE, if MSDE is not updated with a Service Pack. MSDE without Service Pack is not very secure to virusses like Slammer.
|||As a side note, this does not just occur for MSDE 2000. TCP/IP is shutdown
for all editions of SQL Server 2000 without service pack 3 on Windows 2003.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||I have updated with sp3a , but Windows 2003 server still automatically close
down TCP/IP listening for SQL , How do I alter it manual ?
"Finn Rasmussen" <anonymous@.discussions.microsoft.com> bl
news:BD399D59-0EA9-4981-82D7-1F4ADED91C4C@.microsoft.com g...
> After looking in the Event Viewer I found a solution to my problem:
Windows 2003 Server automatically close down TCP/IP listening for MSDE, if
MSDE is not updated with a Service Pack. MSDE without Service Pack is not
very secure to virusses like Slammer.

MSDE TCP listen problem

I have recently installed a MSDE 2000 (unfortunately with no service pack ye
t) on a Standard Windows 2003 server. I have used the srvntcn.exe utility to
make the MSDE server listen on TCP/IP port 1433. But it will not listen on
that port! Or any other TCP
/IP port!! There is no information in the ERRORLOG file. This file just tell
s me, that MSDE is listening on Named Pipes and Shared Memory.
I have tried making my own application listen on port 1433 to see if there w
ere some security settings on that port. And my application had no problem i
n listening on port 1433.After looking in the Event Viewer I found a solution to my problem: Windows
2003 Server automatically close down TCP/IP listening for MSDE, if MSDE is n
ot updated with a Service Pack. MSDE without Service Pack is not very secure
to virusses like Slammer.|||As a side note, this does not just occur for MSDE 2000. TCP/IP is shutdown
for all editions of SQL Server 2000 without service pack 3 on Windows 2003.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||I have updated with sp3a , but Windows 2003 server still automatically close
down TCP/IP listening for SQL , How do I alter it manual ?
"Finn Rasmussen" <anonymous@.discussions.microsoft.com> bl
news:BD399D59-0EA9-4981-82D7-1F4ADED91C4C@.microsoft.com g...
> After looking in the Event Viewer I found a solution to my problem:
Windows 2003 Server automatically close down TCP/IP listening for MSDE, if
MSDE is not updated with a Service Pack. MSDE without Service Pack is not
very secure to virusses like Slammer.

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 service stops and does not restart, it takes reboot to restar

Dears,
We have a problem with MSDE 2000 installed on win2003, the services get
stoped after some time and it does not restart mannual , it gets start only
after we reboot the system.
Advice us some solutions for the same.
Thanks in Advance.
Dinesh Bhandare.
Hi Dinesh,
If it won't start, there should be something in the system event log to give
you a hint.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Dinesh Bhandare" <DineshBhandare@.discussions.microsoft.com> wrote in
message news:02550A8E-80EC-4FBB-8197-58B0E435FCA4@.microsoft.com...
> Dears,
> We have a problem with MSDE 2000 installed on win2003, the services get
> stoped after some time and it does not restart mannual , it gets start
> only
> after we reboot the system.
> Advice us some solutions for the same.
> Thanks in Advance.
> Dinesh Bhandare.
>
sql

MSDE Service permissions

Hi All,
I'm installing MSDE 2000 with a custom application (launched using
setup.exe, not integrating merge modules) and am having a problem with the
service permissions for SQL services. The custom app installer is being
build with Installshield Pro 6.3.
Everything works fine for admin users, but MSDE won't start for non-admin
users. The MSSQL$Instance service won't start unless it's logging on a Local
System.
I need non-admin users to have access to the database.
Is there any way to setup MSDE on install to work for everyone?
What does one need to do to manually configure it after install to work for
everyone?
Thanks,
leon.
hi Leon,
"LM" <leonm@.vtn-tech.com> ha scritto nel messaggio
news:Oe0QyXhhEHA.904@.TK2MSFTNGP09.phx.gbl...
> Hi All,
> I'm installing MSDE 2000 with a custom application (launched using
> setup.exe, not integrating merge modules) and am having a problem with the
> service permissions for SQL services. The custom app installer is being
> build with Installshield Pro 6.3.
> Everything works fine for admin users, but MSDE won't start for non-admin
> users. The MSSQL$Instance service won't start unless it's logging on a
Local
> System.
> I need non-admin users to have access to the database.
> Is there any way to setup MSDE on install to work for everyone?
> What does one need to do to manually configure it after install to work
for
> everyone?
usually MSDE is installed setting the relative services account to
LocalSystem, that provide (far) enought privileges (on the local machine)
for all logged users...
have a look at
http://msdn.microsoft.com/library/de...l/THCMCh18.asp
for more restrictions..
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
|||Hi Andrea,
By default the services use Local System option for log on. This worked fine
for all admin users but did not work for a non-admin user. When a non-admin
user logs in (local or domain user), the services won't start using Local
System. (side note: this is on a WinXP Pro machine). The non-admin user
cannot start or stop any service.
We did get it to work for the non-admin user by using the local
administrator account for log on (I goofed when trying it the first time by
using domain admin password instead of local admin password). This is not
the way we want to go, but it's the only way it does work right now.
I did find one thing via your link, in the Installation Recommendations:
"Create a least privileged local account with which to run the SQL Server
service. Use this account when you are prompted for service settings during
setup. Do not use the local system account or an administrator account. "
There is no prompt when installing MSDE. What exactly is a "least priviledge
local account"?
Any other suggestions are most welcome!
Thanks for your help.
leon.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2okhj5Fbml6lU1@.uni-berlin.de...[vbcol=seagreen]
> hi Leon,
> "LM" <leonm@.vtn-tech.com> ha scritto nel messaggio
> news:Oe0QyXhhEHA.904@.TK2MSFTNGP09.phx.gbl...
the[vbcol=seagreen]
non-admin
> Local
> for
> usually MSDE is installed setting the relative services account to
> LocalSystem, that provide (far) enought privileges (on the local machine)
> for all logged users...
> have a look at
>
http://msdn.microsoft.com/library/de...l/THCMCh18.asp
> for more restrictions..
> --
> 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
>
|||hi Leon,
"LM" <leonm@.vtn-tech.com> ha scritto nel messaggio
news:eO0WPBthEHA.2908@.TK2MSFTNGP10.phx.gbl...
> Hi Andrea,
> By default the services use Local System option for log on. This worked
fine
> for all admin users but did not work for a non-admin user. When a
non-admin
> user logs in (local or domain user), the services won't start using Local
> System. (side note: this is on a WinXP Pro machine). The non-admin user
> cannot start or stop any service.
actually they shoul'd run, as all this is intended to work this way... SQL
Server is run under another privileged account than the current logged
account, which only needs to connect to the specified server and query for
information..
perhaps you have to check your local policies...

> We did get it to work for the non-admin user by using the local
> administrator account for log on (I goofed when trying it the first time
by
> using domain admin password instead of local admin password). This is not
> the way we want to go, but it's the only way it does work right now.
I usually use a local account (not LocalSystem), with enought rights on
relevent share(s) if needed..

> I did find one thing via your link, in the Installation Recommendations:
> "Create a least privileged local account with which to run the SQL Server
> service. Use this account when you are prompted for service settings
during
> setup. Do not use the local system account or an administrator account. "
> There is no prompt when installing MSDE. What exactly is a "least
priviledge
> local account"?
no, there's not... that info is for a full blown SQL Server installation..
you have to set that property after MSDE installed, accessing the services
management applet... perhaps it can be done via WMI, but never tried it..
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
|||more,
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> ha scritto nel messaggio
news:2omoccFcfn07U1@.uni-berlin.de...[vbcol=seagreen]
> hi Leon,
> "LM" <leonm@.vtn-tech.com> ha scritto nel messaggio
> news:eO0WPBthEHA.2908@.TK2MSFTNGP10.phx.gbl...
Local[vbcol=seagreen]
they do not have to... set the service's "start at boostrap" property...
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
|||The instructions on the SQLServer Installation Recommendations say to create
a new user, remove it from the users group and use it for the service login.
We created an "msde" user, removed it from Users group, set it as the Log On
As account (it is listed in the "Log on as a service" policy), gave full
access rights for the data files to Everyone, and it doesn't work.
So you have installed MSDE 2000 A and had its service (MSDE$InstanceName)
starting with a non-admin log in?
If so, you must have some magic touch because we're trying this on 2
separate machines with the same failure on each. We'll be trying it on a
fresh XP install shortly, but I don't really expect different results.
Even when logged into the XP as an administrator, setting the MSDE service
login account to "msde" causes the service to fail on a start attempt. It
gives the following error:
Could not start the MSDE$... service on Local Computer.
Error 5: Access is Denied
How do you access the "start at boostrap" property of a service?
thanks,
leon.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2omogoFcbbrgU1@.uni-berlin.de...[vbcol=seagreen]
> more,
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> ha scritto nel messaggio
> news:2omoccFcfn07U1@.uni-berlin.de...
> Local
user
> they do not have to... set the service's "start at boostrap" property...
> --
> 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
>
|||hi Leon,
"LM" <leonm@.vtn-tech.com> ha scritto nel messaggio
news:%233zBrHvhEHA.644@.tk2msftngp13.phx.gbl...
> The instructions on the SQLServer Installation Recommendations say to
create
> a new user, remove it from the users group and use it for the service
login.
> We created an "msde" user, removed it from Users group, set it as the Log
On
> As account (it is listed in the "Log on as a service" policy), gave full
> access rights for the data files to Everyone, and it doesn't work.
> So you have installed MSDE 2000 A and had its service (MSDE$InstanceName)
> starting with a non-admin log in?
> If so, you must have some magic touch because we're trying this on 2
> separate machines with the same failure on each. We'll be trying it on a
> fresh XP install shortly, but I don't really expect different results.
> Even when logged into the XP as an administrator, setting the MSDE service
> login account to "msde" causes the service to fail on a start attempt. It
> gives the following error:
> Could not start the MSDE$... service on Local Computer.
> Error 5: Access is Denied
I do always use a local admin account, and I never use the special
LocalSystem account, created just for this purpose and never use an actual
local or domain administrator account. The account must be in the local
Administrators group if you're installing SQL Server on Windows NT or
Windows 2000. You can create this account before you begin installing SQL
Server, or you can change the account under which SQL Server runs at a later
time.
Setting less privileges is intended in not using a Domain Admin account for
network protection.
> How do you access the "start at boostrap" property of a service?
in the service management, select Startup Mode = automatic
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
|||Hi Andrea
Sorry, referring to the automatic service startup as "start at bootstrap"
property is a little different terminology than I am used to. I do
understand the automatic startup option.
We will just include some instructions for setting up the app for non-admin
users.
Thanks for your help.
leon.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2ong8qFcg0ccU1@.uni-berlin.de...[vbcol=seagreen]
> hi Leon,
> "LM" <leonm@.vtn-tech.com> ha scritto nel messaggio
> news:%233zBrHvhEHA.644@.tk2msftngp13.phx.gbl...
> create
> login.
Log[vbcol=seagreen]
> On
(MSDE$InstanceName)[vbcol=seagreen]
service[vbcol=seagreen]
It
> I do always use a local admin account, and I never use the special
> LocalSystem account, created just for this purpose and never use an actual
> local or domain administrator account. The account must be in the local
> Administrators group if you're installing SQL Server on Windows NT or
> Windows 2000. You can create this account before you begin installing SQL
> Server, or you can change the account under which SQL Server runs at a
later
> time.
> Setting less privileges is intended in not using a Domain Admin account
for
> network protection.
> in the service management, select Startup Mode = automatic
> --
> 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 Service Manager on XP Pro SP2

I recently installed MSDE 2K on a Windows XP SP2 system. Everything appears
to be working fine, with the exception of the service manager. For some
reason, it will not find the system on the local network and will not
connect to it if I type the name in the server name area. Is this normal or
am I just missing something? Thanks in advance.
hi David,
"David Young" <cdyoung@.uta.edu> ha scritto nel messaggio
news:eBToEMg3EHA.3840@.tk2msftngp13.phx.gbl
> I recently installed MSDE 2K on a Windows XP SP2 system. Everything
> appears to be working fine, with the exception of the service
> manager. For some reason, it will not find the system on the local
> network and will not connect to it if I type the name in the server
> name area. Is this normal or am I just missing something? Thanks in
> advance.
actually, for local instances connections, WinXP sp2 should not be a
problem, but only for remote connections :D
as regard the Service Manager not showing the instance name, this is a known
issue when network protocols are disabled (default setting) as you can see
in http://support.microsoft.com/default...b;EN-US;814132
as regard directly typing in the instance name... did you provide the name
in the ComputerName\InstanceName format ( or just (local)\InstanceName) ?
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

MSDE service manager just stops???

HI every one
I hope i dont sound too dumb here but i am having some problems with MSDE
I have it installed on my local machine and SQL server 2000 is also installed as i use the Enterprise manager to work on my database.
I dont have server software as my OS is win XP pro.
The problem i have is that after a while the MSDE service manager just stops and i cant get it to restart. and the only way is to uninstall it and reinstall.
i have tried to get the 2000 MSDE installed but i seem to not be able to get that working.
It is frustrating as i am developing a databse at home for a client (work experience) but i spend so much time keeping my shonky system running i loose time in developing.
is there somewhere i can learn to set my system up so i can develop a sql DB at home, or am i flogging a dead horsse.
any help greatly appreciated
Greg
Have you looked in the event log for errors?
"GREGO" wrote:

> HI every one
> I hope i dont sound too dumb here but i am having some problems with MSDE
> I have it installed on my local machine and SQL server 2000 is also installed as i use the Enterprise manager to work on my database.
> I dont have server software as my OS is win XP pro.
> The problem i have is that after a while the MSDE service manager just stops and i cant get it to restart. and the only way is to uninstall it and reinstall.
> i have tried to get the 2000 MSDE installed but i seem to not be able to get that working.
> It is frustrating as i am developing a databse at home for a client (work experience) but i spend so much time keeping my shonky system running i loose time in developing.
> is there somewhere i can learn to set my system up so i can develop a sql DB at home, or am i flogging a dead horsse.
> any help greatly appreciated
> Greg
|||Do you mean the windows event log?
i cant access the SQL server log as it is shut down and i cant access it
regards
greg
"Nigel Rivett" wrote:
[vbcol=seagreen]
> Have you looked in the event log for errors?
> "GREGO" wrote:
|||The SQL Server log is just a text file under the SQL Server directory,
normally in the LOG directory. Load the most recent one into Notepad and see
if there are any errors.
Jim
"GREGO" <GREGO@.discussions.microsoft.com> wrote in message
news:B074205A-A3A6-48DB-8EBB-350E3118AFDE@.microsoft.com...[vbcol=seagreen]
> Do you mean the windows event log?
> i cant access the SQL server log as it is shut down and i cant access it
> regards
> greg
> "Nigel Rivett" wrote:
MSDE[vbcol=seagreen]
installed as i use the Enterprise manager to work on my database.[vbcol=seagreen]
stops and i cant get it to restart. and the only way is to uninstall it and
reinstall.[vbcol=seagreen]
to get that working.[vbcol=seagreen]
(work experience) but i spend so much time keeping my shonky system
running i loose time in developing.[vbcol=seagreen]
sql DB at home, or am i flogging a dead horsse.[vbcol=seagreen]

MSDE Service Accounts

Hi Guys,
Is there a way to specify the accounts under which the MSSQL and Agent
services will run during installation? I did not see an option in the switch
commands in the setup.exe.
Also, changing those accounts without EM seems to be pretty involved. Is
there any other way to change those accounts? I need to be able to change
these accounts for replication.
Thanks,
Maer
Hi,
How to change the startup account:-
1. Control Panel - Admin tools -- Services
2. Double click above the MSSQL Server service
3. In the Log on tab, change the OS user name and enter the password, Click
ok and restart the service.
Note:
Do the same for SQL Agent service.
Thanks
Hari
MCDBA
"Maer" <maer@.auditleverage.com> wrote in message
news:eYIePa$dEHA.3792@.TK2MSFTNGP09.phx.gbl...
> Hi Guys,
> Is there a way to specify the accounts under which the MSSQL and Agent
> services will run during installation? I did not see an option in the
switch
> commands in the setup.exe.
> Also, changing those accounts without EM seems to be pretty involved.
Is
> there any other way to change those accounts? I need to be able to change
> these accounts for replication.
> Thanks,
> Maer
>
|||you need to use an iss file. Check out
Setup Initialization File Details and Advanced Installation Options for more
info on how to do this.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:uw%230XxFeEHA.2812@.tk2msftngp13.phx.gbl...
> Hi,
> How to change the startup account:-
> 1. Control Panel - Admin tools -- Services
> 2. Double click above the MSSQL Server service
> 3. In the Log on tab, change the OS user name and enter the password,
Click[vbcol=seagreen]
> ok and restart the service.
> Note:
> Do the same for SQL Agent service.
> Thanks
> Hari
> MCDBA
>
> "Maer" <maer@.auditleverage.com> wrote in message
> news:eYIePa$dEHA.3792@.TK2MSFTNGP09.phx.gbl...
Agent[vbcol=seagreen]
> switch
involved.[vbcol=seagreen]
> Is
change
>
|||Thank you. But isn't this just part of the changes? Don't I also have to
set the right permissions in certain folders and registry keys for the
account I am changing the service to?
I was wondering if there was a utility that would do all that
automatically.
Thanks again,
Maer
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:uw%230XxFeEHA.2812@.tk2msftngp13.phx.gbl...
> Hi,
> How to change the startup account:-
> 1. Control Panel - Admin tools -- Services
> 2. Double click above the MSSQL Server service
> 3. In the Log on tab, change the OS user name and enter the password,
Click[vbcol=seagreen]
> ok and restart the service.
> Note:
> Do the same for SQL Agent service.
> Thanks
> Hari
> MCDBA
>
> "Maer" <maer@.auditleverage.com> wrote in message
> news:eYIePa$dEHA.3792@.TK2MSFTNGP09.phx.gbl...
Agent[vbcol=seagreen]
> switch
involved.[vbcol=seagreen]
> Is
change
>

MSDE Service Accounts

Hi Guys,
Is there a way to specify the accounts under which the MSSQL and Agent
services will run during installation? I did not see an option in the switch
commands in the setup.exe.
Also, changing those accounts without EM seems to be pretty involved. Is
there any other way to change those accounts? I need to be able to change
these accounts for replication.
Thanks,
Maer
Hi,
How to change the startup account:-
1. Control Panel - Admin tools -- Services
2. Double click above the MSSQL Server service
3. In the Log on tab, change the OS user name and enter the password, Click
ok and restart the service.
Note:
Do the same for SQL Agent service.
Thanks
Hari
MCDBA
"Maer" <maer@.auditleverage.com> wrote in message
news:eYIePa$dEHA.3792@.TK2MSFTNGP09.phx.gbl...
> Hi Guys,
> Is there a way to specify the accounts under which the MSSQL and Agent
> services will run during installation? I did not see an option in the
switch
> commands in the setup.exe.
> Also, changing those accounts without EM seems to be pretty involved.
Is
> there any other way to change those accounts? I need to be able to change
> these accounts for replication.
> Thanks,
> Maer
>
|||you need to use an iss file. Check out
Setup Initialization File Details and Advanced Installation Options for more
info on how to do this.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:uw%230XxFeEHA.2812@.tk2msftngp13.phx.gbl...
> Hi,
> How to change the startup account:-
> 1. Control Panel - Admin tools -- Services
> 2. Double click above the MSSQL Server service
> 3. In the Log on tab, change the OS user name and enter the password,
Click[vbcol=seagreen]
> ok and restart the service.
> Note:
> Do the same for SQL Agent service.
> Thanks
> Hari
> MCDBA
>
> "Maer" <maer@.auditleverage.com> wrote in message
> news:eYIePa$dEHA.3792@.TK2MSFTNGP09.phx.gbl...
Agent[vbcol=seagreen]
> switch
involved.[vbcol=seagreen]
> Is
change
>
|||Thank you. But isn't this just part of the changes? Don't I also have to
set the right permissions in certain folders and registry keys for the
account I am changing the service to?
I was wondering if there was a utility that would do all that
automatically.
Thanks again,
Maer
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:uw%230XxFeEHA.2812@.tk2msftngp13.phx.gbl...
> Hi,
> How to change the startup account:-
> 1. Control Panel - Admin tools -- Services
> 2. Double click above the MSSQL Server service
> 3. In the Log on tab, change the OS user name and enter the password,
Click[vbcol=seagreen]
> ok and restart the service.
> Note:
> Do the same for SQL Agent service.
> Thanks
> Hari
> MCDBA
>
> "Maer" <maer@.auditleverage.com> wrote in message
> news:eYIePa$dEHA.3792@.TK2MSFTNGP09.phx.gbl...
Agent[vbcol=seagreen]
> switch
involved.[vbcol=seagreen]
> Is
change
>
sql

MSDE Seems to Install - Service Manager Loads - No Connection

Hi,
I uninstalled MSDE 2000 prior to installing SQL Server 2000 Developer
Edition. I then found I could not use Developer Edition with Visual Basic
..net Standard Edition and tried to reinstall MSDE. The installation seems
to go fine but when the Service Manager loads is tells me "Not Connected -
\\" no servers are in the Server drop-down and no services are listed in
the Services drop-down. I am very new to all of this and would very much
appreciate any help/advice you could offer. I have since uninstalled
Developer Edition to no avail. I am running Windows XP Pro.
Regards
Barry-Jon
hi Barry-Jon,
Microsoft wrote:
> Hi,
> I uninstalled MSDE 2000 prior to installing SQL Server 2000 Developer
> Edition. I then found I could not use Developer Edition with Visual
> Basic .net Standard Edition and tried to reinstall MSDE. The
> installation seems to go fine but when the Service Manager loads is
> tells me "Not Connected - \\" no servers are in the Server drop-down
> and no services are listed in the Services drop-down. I am very new
> to all of this and would very much appreciate any help/advice you
> could offer. I have since uninstalled Developer Edition to no avail.
> I am running Windows XP Pro.
> Regards
> Barry-Jon
please have a look at
http://support.microsoft.com/default...b;EN-US;814132 ...
you can modify this behaviour enabling the desired/required network protocol
by running the Server Network Utility (svrnetcn.exe)...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||"Microsoft" <barryjonoconnell_spam_no@.yahoo.co.uk> wrote in message
news:ucCLTwKEFHA.1188@.tk2msftngp13.phx.gbl...
> Hi,
> I uninstalled MSDE 2000 prior to installing SQL Server 2000 Developer
> Edition. I then found I could not use Developer Edition with Visual Basic
> .net Standard Edition and tried to reinstall MSDE. The installation seems
> to go fine but when the Service Manager loads is tells me "Not Connected -
> \\" no servers are in the Server drop-down and no services are listed in
> the Services drop-down. I am very new to all of this and would very much
> appreciate any help/advice you could offer. I have since uninstalled
> Developer Edition to no avail. I am running Windows XP Pro.
> Regards
> Barry-Jon
I posted this in the vb group as well, but just in case...
I'm not sure you're doing anything wrong, but perhaps the instructions we
use for classroom/lab installs of MSDE to work with Visual Studio .NET 2003
will be helpful:
<quote>
1. Before you begin, check the PC to ensure there are no remnants of prior
MSDE installation attempts hanging around. The place to check is: C:\Program
Files\Microsoft SQL Server. If you locate a folder named Microsoft SQL
Server, delete it and its contents!
2. Execute the file: SQL2KDeskSP3.exe(or whatever the file name for your
MSDE download is). This step will extract the contents of the file to a
designated folder. Make a note of the destination folder. You'll need it
later. This step does not install MSDE (although the dialogs seem to hint
that it does)!
4. Navigate to the folder you created in Step 2. In that folder, you will
find a subfolder named MSDE. In MSDE, you will find SETUP.EXE. Executing
SETUP.EXE will install MSDE.
5. To execute SETUP.EXE correctly, you must supply an instance name and a
system administrator password as part of the command: i.e. the command must
be:
SETUP.EXE INSTANCENAME="NetSDK" SAPWD="yourSAPassword"
where yourSAPassword is your actual system administrator password. This
password is needed only to install MDSE, not to use it. Access to MSDE is
controlled by normal "NT Security" which should allow users access based on
network logon and password. It is very important the the INSTANCENAME
parameter be NetSDK, as this name will enable you to generate the sample
databases automatically instead of having to run SQL scripts from the
command line.
6. Once installation is complete, you must reboot the PC before you will
see MSDE. After the reboot, you should see the MSDE icon in SysTray.
7. You now must execute the file: ConfigSamples.exe to configure sample
applications and MSDE system databases. This step will also create user
databases in the following location: C:\Program Files\Microsoft SQL
Server\MSSQL\Data.
</quote>
If you have trouble locating the ConfigSamples.exe, it's a small file
(56k) and I can send it to your email if needed.
Hope this helps.
Peter [MVP Visual Developer]
Jack of all trades, master of none.
|||Thanks Peter - that looks pretty much like what I did in the end. Saved
your post in case I ever forget :-)
"Peter van der Goes" <p_vandergoes@.toadstool.u> wrote in message
news:edfqWhQEFHA.3592@.TK2MSFTNGP15.phx.gbl...
> "Microsoft" <barryjonoconnell_spam_no@.yahoo.co.uk> wrote in message
> news:ucCLTwKEFHA.1188@.tk2msftngp13.phx.gbl...
> I posted this in the vb group as well, but just in case...
> I'm not sure you're doing anything wrong, but perhaps the instructions we
> use for classroom/lab installs of MSDE to work with Visual Studio .NET
> 2003 will be helpful:
> <quote>
> 1. Before you begin, check the PC to ensure there are no remnants of
> prior MSDE installation attempts hanging around. The place to check is:
> C:\Program Files\Microsoft SQL Server. If you locate a folder named
> Microsoft SQL Server, delete it and its contents!
>
> 2. Execute the file: SQL2KDeskSP3.exe(or whatever the file name for your
> MSDE download is). This step will extract the contents of the file to a
> designated folder. Make a note of the destination folder. You'll need it
> later. This step does not install MSDE (although the dialogs seem to hint
> that it does)!
>
> 4. Navigate to the folder you created in Step 2. In that folder, you will
> find a subfolder named MSDE. In MSDE, you will find SETUP.EXE. Executing
> SETUP.EXE will install MSDE.
>
> 5. To execute SETUP.EXE correctly, you must supply an instance name and a
> system administrator password as part of the command: i.e. the command
> must be:
>
> SETUP.EXE INSTANCENAME="NetSDK" SAPWD="yourSAPassword"
>
> where yourSAPassword is your actual system administrator password. This
> password is needed only to install MDSE, not to use it. Access to MSDE is
> controlled by normal "NT Security" which should allow users access based
> on network logon and password. It is very important the the INSTANCENAME
> parameter be NetSDK, as this name will enable you to generate the sample
> databases automatically instead of having to run SQL scripts from the
> command line.
>
> 6. Once installation is complete, you must reboot the PC before you will
> see MSDE. After the reboot, you should see the MSDE icon in SysTray.
>
> 7. You now must execute the file: ConfigSamples.exe to configure sample
> applications and MSDE system databases. This step will also create user
> databases in the following location: C:\Program Files\Microsoft SQL
> Server\MSSQL\Data.
> </quote>
>
> If you have trouble locating the ConfigSamples.exe, it's a small file
> (56k) and I can send it to your email if needed.
>
> Hope this helps.
>
> --
> Peter [MVP Visual Developer]
> Jack of all trades, master of none.
>

MSDE Problem - SQL Server not found or access denied

I am running the MSDE 2000 Setup off the SQL Server 2000 Developer Edition CD.

After installation is complete, there is a service under the Control Panel -> Services window
called MSSQL$GregInstance. I then start that service.

But now when I try to connect to the database using

osql -E -S GregInstance

I get told that the SQL Server does not exist or access denied. Even though the server is running. I have also tried

osql -E -S localhost

but no luck. Why can it not find the instance of SQL Server?

Note : SQL Server 2000 is not installed on the machine, only this MSDE instance.

Thanks
GregNot to worry, I forgot to add in the name of the pc with a \ before the instance name...

i.e

osql -E -S GREG\GregInstance

MSDE on SBS2003 from Network

I have created a new MSDE instance on my SBS 2003 Standard server, using
MSDE setup.
The service is started, and I can access the MSDE instance locally on the
server, but I am unable to access it from other PCs on the network (in the
domain).
Specifically, I am using SQL Server Enterprise Manager. It reports the
message "Sql Server does not exist or access denied" when I try to connect
to the instance (using "myserver\instance-name"). I tried ISQL and also get
access denied.
I installed Enterprise Manager locally on the server and it connects to the
instance without problem.
Looking at the Properties/General/Network Configuration I can see TCPIP is
enabled and now using port 1433 (although it was set to port 0 after
installation?).
My user account is a valid login with the "System Administrator" role an has
dbo access to all databases.
The Windows Firewall allows port 1433 at the client and no firewall on the
server.
What else to check?
richlm wrote:

>I have created a new MSDE instance on my SBS 2003 Standard server, using
>MSDE setup.
>The service is started, and I can access the MSDE instance locally on the
>server, but I am unable to access it from other PCs on the network (in the
>domain).
>Specifically, I am using SQL Server Enterprise Manager. It reports the
>message "Sql Server does not exist or access denied" when I try to connect
>to the instance (using "myserver\instance-name"). I tried ISQL and also
>get access denied.
The default for MSDE is to not listen to the network, only the local
machine.

>I installed Enterprise Manager locally on the server and it connects to
>the instance without problem.
>Looking at the Properties/General/Network Configuration I can see TCPIP is
>enabled and now using port 1433 (although it was set to port 0 after
>installation?).
This was in the Server Network Utility, yes?
Has the MSDE instance been restarted since you enabled a network protocol?

>My user account is a valid login with the "System Administrator" role an
>has dbo access to all databases.
>The Windows Firewall allows port 1433 at the client and no firewall on the
>server.
The Windows Firewall on a client is irrelevant, since it has no impact on
outgoing connections. It would only be of interest if MSDE (or SQL) was
installed on the workstation itself.
Out of interest, where did you get the SQL client utilities from? They're
not included with SBS2003 Standard, nor are you licenced to use them in an
SBS2003 Standard environment.
Steve Foster [SBS MVP]
MVPs do not work for Microsoft. Please reply only to the newsgroups.
|||Yes, TCP 1433 is at the top of the list of "enabled protocols" in the server
network utility, and I restarted the MSDE service after setting the port.
But I just realized that cliconfg does not allow me to choose which MSDE
instance to apply the changes to.
I just found a Microsoft support notice "Server Network Utility may display
incorrect protocol properties in SQL Server 2000" at
http://support.microsoft.com/?kbid=887700 - I'll investigate this further
(although I'm using SP4 so the hotfix does not apply).
As for licencing, I have an MSDN Universal subscription which includes the
use of SQL client tools for development purposes. But thanks for the
reminder, and I'll re-check the licence terms to make sure I've not
misunderstood something about where the tools can be used.
Richard.
|||richlm wrote:

>Yes, TCP 1433 is at the top of the list of "enabled protocols" in the
>server network utility, and I restarted the MSDE service after setting the
>port.
>But I just realized that cliconfg does not allow me to choose which MSDE
>instance to apply the changes to.
Eh?

>I just found a Microsoft support notice "Server Network Utility may
>display incorrect protocol properties in SQL Server 2000" at
>http://support.microsoft.com/?kbid=887700 - I'll investigate this further
>(although I'm using SP4 so the hotfix does not apply).
>As for licencing, I have an MSDN Universal subscription which includes the
>use of SQL client tools for development purposes. But thanks for the
>reminder, and I'll re-check the licence terms to make sure I've not
>misunderstood something about where the tools can be used.
AIUI, the MSDN licence does not cover using the SQL client utilities to
manage a production server. So, unless your SBS is only used for your
development network, you are not legally allowed to use the MSDN licence
to manage SQL services on SBS. But hey, IANAL, nor a member of the licence
police...
Steve Foster [SBS MVP]
MVPs do not work for Microsoft. Please reply only to the newsgroups.
|||OK - I should be running svrnetcn.exe and not cliconfg.exe...
Now I can choose the instance - and can confirm that the problem referred to
at http://support.microsoft.com/?kbid=887700 also applies to SP4. The
workaround suggested there (choose another instance then go back to the one
you really wanted) refreshes the UI correctly.
But I still can't connect remotely using EM or OSQL - yet both work locally.
I've googled to the end of the earth and not found other suggestions so my
guess now is it's probably due to the fact I have installed VS2005 on my
client - which also installs SQL 2005 express.
When I try to connect using OSQL I get the following error:
[SQL Native Client]Unable to complete login process due to delay in opening
server connection.
This perhaps implies my client PC is "broken" for connecting to SQL 2000
instances?
The version of "SQL Server Native Client" I currently use is 9.00.1314.06.
I think I'll wait for SQL 2005 launch in a couple of weeks, where
(hopefully) this problem goes away.
Can anyone confirm this?
|||Richard Money wrote:

>OK - I should be running svrnetcn.exe and not cliconfg.exe...
>Now I can choose the instance - and can confirm that the problem referred
>to at http://support.microsoft.com/?kbid=887700 also applies to SP4. The
>workaround suggested there (choose another instance then go back to the
>one you really wanted) refreshes the UI correctly.
>But I still can't connect remotely using EM or OSQL - yet both work
>locally. I've googled to the end of the earth and not found other
>suggestions so my guess now is it's probably due to the fact I have
>installed VS2005 on my client - which also installs SQL 2005 express.
>When I try to connect using OSQL I get the following error:
>[SQL Native Client]Unable to complete login process due to delay in
>opening server connection.
>This perhaps implies my client PC is "broken" for connecting to SQL 2000
>instances?
>The version of "SQL Server Native Client" I currently use is 9.00.1314.06.
>I think I'll wait for SQL 2005 launch in a couple of weeks, where
>(hopefully) this problem goes away.
>Can anyone confirm this?
I don't know whether SQL2005 beta client tools can communicate with
SQL2000. I suspect that that is something likely to be left until very
close to RTM (and may require that SQL2000 gets an update of some sort).
I'd stick to trying with SQL2000 client utilities.
Steve Foster [SBS MVP]
MVPs do not work for Microsoft. Please reply only to the newsgroups.
|||Pretty sure that my problem connecting to MSDE over network was due to a
pre-release version of SQL2005 Express (sept. CTP) on my client.
Have just successfully installed the RTM of SQL Express on SBS as a named
instance, enabled networking using the SQL Server Configuration Manager, and
I can connect to the instance from VS2005 (RTM) running on another machine.
The default SBS instances for Sharepoint and SBSMonitoring are still running
MSDE (and still work!).
Now I'm happy:-)

MSDE on SBS2003

Hi, I'm about going to be using a database on the MSDE installed with
Windows SBS 2003. The problem is that in the service manager there are no
servers or services listed. Do I have to reinstall? Thanks.
Message posted via http://www.droptable.com
Supposed to be based on a security update.
"
Known issue, it doesn't matter. SQL/MSDE is actually running, and if you
want, you can delete the link to the SQL Manager in Start Menu -> All
Programs -> Startup, if you don't want to see the icon"
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Ben Harrison via droptable.com" <forum@.nospam.droptable.com> schrieb im
Newsbeitrag news:fb473d43c11745b68136ae18440f2383@.droptable.co m...
> Hi, I'm about going to be using a database on the MSDE installed with
> Windows SBS 2003. The problem is that in the service manager there are no
> servers or services listed. Do I have to reinstall? Thanks.
> --
> Message posted via http://www.droptable.com
|||hi Ben,
Ben Harrison via droptable.com wrote:
> Hi, I'm about going to be using a database on the MSDE installed with
> Windows SBS 2003. The problem is that in the service manager there
> are no servers or services listed. Do I have to reinstall? Thanks.
MSDE installs by default disabling network protocols and remote connections,
and this can prevent instances to be enlisted in the service manager combo,
as described in
http://support.microsoft.com/default...b;EN-US;814132
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

msde not starting

Hallo Guys

I am running MSDE with Sage Taxation Suite v10. However when I try to start MSDE with SQL Server Service Manager, it will not start, it tries to start, but then stops.

Why might this be happening and is there a possible fix for this problem.

Thank you

Pls provide the error log details and event viewer details as it will be easy to trouble shoot the problem

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 Installation on a XP Professional WS.

Hello,
I'm experiencing 2 problems after MSDE installation on a XP Pro workstation
on a network.
1. The SQL Service Manager don't show the default instance. If I put
manually is OK, but on every reboot it lose the instance name and show me
nothing.
2. it's impossible to login from an external computer or create any kind of
connection (ODBC or .udl file).
For information the setup was make:
with an .ini file containing
[Options]
INSTANCENAME=fgsoftware
SAPWD=xyzxyz
SECURITYMODE=SQL
The computer is SP2 full patched.
After the first problems I deactivated the windows firewall.
Help me!!!
TIA
Francesco Garganese
FG software
Can't help you with 1 unfortunately - it has happened to me but I've never
quite worked out why...
To log in from an external computer you need to have set the
DISABLENETWORKPROTOLS flag to false when installing. See the readme that
comes with the installer for more details on command line switches.
Also, MSDE from Service Pack 3a onwards, installs in Windows Authentication
mode only by default. see the following kb article for more info:
http://support.microsoft.com/default...;EN-US;Q325022
If you're trying to access it from another machine that is not logged in as
a *domain* user on the same domain (i.e. you must be running a Windows 2003
Server Domain Controller somewhere) then you can only connect using Mixed
Mode Authentication, which as the above article will tell you is disabled by
default.
"Francesco Garganese" <FrancescoGarganese@.discussions.microsoft.com> wrote
in message news:CD18E7C6-6E32-4D27-974D-C744C580C820@.microsoft.com...
> Hello,
> I'm experiencing 2 problems after MSDE installation on a XP Pro
> workstation
> on a network.
> 1. The SQL Service Manager don't show the default instance. If I put
> manually is OK, but on every reboot it lose the instance name and show me
> nothing.
> 2. it's impossible to login from an external computer or create any kind
> of
> connection (ODBC or .udl file).
> For information the setup was make:
> with an .ini file containing
> [Options]
> INSTANCENAME=fgsoftware
> SAPWD=xyzxyz
> SECURITYMODE=SQL
> The computer is SP2 full patched.
> After the first problems I deactivated the windows firewall.
> Help me!!!
> TIA
> --
> Francesco Garganese
> FG software
|||Thank you very much Ben, adding DISABLENETWORKPROTOLS=0 in the paramenters
and reinstalling both problems are resolved!
Sincerely
Francesco Garganese
FG software

MSDE installation error

Hi, are days that i'm trying to install MSDE on my computer (windows XP service pack 1).
The problem is that when I run the setup program from console using "SAPWD=(Some password) SecurityMode=SQL", it fails with that error log:

--- LOG START
2003-08-15 17:56:13.12 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)

2003-08-15 17:56:13.12 server Copyright (C) 1988-2002 Microsoft Corporation.
2003-08-15 17:56:13.12 server All rights reserved.
2003-08-15 17:56:13.12 server Server Process ID is 3076.
2003-08-15 17:56:13.12 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG'.
2003-08-15 17:56:13.14 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2003-08-15 17:56:13.18 server SQL Server configured for thread mode processing.
2003-08-15 17:56:13.21 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2003-08-15 17:56:13.29 spid3 Warning ******************
2003-08-15 17:56:13.29 spid3 SQL Server started in single user mode. Updates allowed to system catalogs.
2003-08-15 17:56:13.87 spid3 Starting up database 'master'.
2003-08-15 17:56:15.76 server Using 'SSNETLIB.DLL' version '8.0.766'.
2003-08-15 17:56:15.76 spid5 Starting up database 'model'.
2003-08-15 17:56:15.87 spid3 Server name is 'ALEX'.
2003-08-15 17:56:15.87 spid3 Skipping startup of clean database id 5
2003-08-15 17:56:15.87 spid3 Skipping startup of clean database id 6
2003-08-15 17:56:15.87 spid3 Starting up database 'msdb'.
2003-08-15 17:56:17.18 spid5 Clearing tempdb database.
2003-08-15 17:56:18.70 server SQL server listening on Shared Memory.
2003-08-15 17:56:18.70 server SQL Server is ready for client connections
2003-08-15 17:56:21.43 spid5 Starting up database 'tempdb'.
2003-08-15 17:56:22.56 spid3 Recovery complete.
2003-08-15 17:56:22.56 spid3 SQL global counter collection task is created.
2003-08-15 17:56:22.93 spid3 Warning: override, autoexec procedures skipped.
2003-08-15 17:56:36.48 spid3 SQL Server is terminating due to 'stop' request from Service Control Manager.
--- LOG END

if anybody can help, I would really appreciate!
Alex.After this are you not able to start MSSql services on the computer? What is the version of ssnetlib.dll, sqlservr.exe?

-Kashif|||No.
The only usefull files i can find under the "Microsoft SQL Server" directory that the setup creates, are the log files.
When the setup program fails, it goes backward, in a sort of rollback and it deletes any other files it had installed during the installation process.
That's why, I think, I can't find any of those files you are talking about (ssnetlib.dll and sqlservr.exe) on my computer.|||Do you have some dbs in the DATA dir under the sql server install folder - if yes please move that some place else before starting setup.

Hope that helps
Kashif|||The only files I have in the DATA dir are tempdb.mdf and templog.ldf|||Can you move these dbs to a different directory on your machien and then try the MSDE installation.

-Kashif|||ok..
I moved them all in a different location so that the DATA directory was empty... didn't work.
The log file still report the same error.
I looked on the net and i found out i'm not the only one with that problem, but i couldn't find anyone who could provide a solution.
What can I do?|||Any ideas?|||Ok..
I found by myself what was wrong..
I'm running Windows XP home edition, while the professional edition is needed.
Hope this will help people with the same problem.

MSDE Installation

How do I set the SQLServerAgent service on automatically when I run the
installation? By default, the MSSQLServer service is set as automatic, but
the SQLServerAgent is Manual
hi Roy,
"Roy" <Roy@.discussions.microsoft.com> ha scritto nel messaggio
news:C42372B4-330B-4418-89E4-2F167D703AB8@.microsoft.com...
> How do I set the SQLServerAgent service on automatically when I run the
> installation? By default, the MSSQLServer service is set as automatic, but
> the SQLServerAgent is Manual
actually there's no way to set this at install time
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 Installation

When I install MSDE (MSDERelA) it installs fine, but it doesn't start the
service.
I am deploying this to a large number of computers and I don't want to have
to require them to reboot or go into the component services console in order
to use the database.
It there a why to start the service as soon as it installs without user
having to go into the services console or reboot?Hi Lance,
From your descriptions, I understood that you MSDE instance will not be
launched unless you reboot your box or go into the services console. Have I
understood you? If there is anything I misunderstood, please feel free to
let me know:)
Based on my scope, after the installation, the service is started by
default. Look in Task Manager and you should see the service running. You
can use any application that connects to the service or you can issue osql
commands to work with the service.
Are there any error log shown during the setup? If you are installing the
MSDE stand-alone, will the service be started?
Anyway, if the service is not started by default, you could try to start it
with a DOS command "net start <Service Name>" in your application.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

MSDE install problems

hi ppl,
I get the following an error prompt/box pops up during
installation saying :
"Service 'MSSQLSERVER' (MSSQLSERVER) Could not be installed. Verify
that you have sufficient priviledge to install system services"
-cancel- -retry- -ignore- buttons, this has now happened 4 times
consistently.

Retry does not work, cancelling and ignore end the installation but theC:\Program Files\Microsoft SQL Server\... and subdir as well as
registry entries are created.

After this any re-install cancels (disappears) unless i manually
remove C:\Program Files\Microsoft SQL Server\ dirs and registry
entries. IF i do this then and try installing again then i get
"Service 'MSSQLSERVER' (MSSQLSERVER) Could not be installed. ..."
error again.

the parameters im using are:
BLANKSAPWD=1, REINSTALL=All , REINSTALLMODE=omus, disablerollback=1.
and switches:
/L*v MSDE_log.txt

i have attached log file.
Please help a stoopid newbie :(Please ignore this previous message, I seemed to have bypassed this old error, this old error only appeared when I don't specify an instance name.

When i do now specify one, then I get this error:

Starting custom action InstallPerfMon
Registering performance counters from sqlctr.ini
PerfmonLoad routine returned error code 267
Action ended 0:18:23: InstallFinalize. Return value 3.

I tried numerous things but the only stuff that works is when I make a C:\Program Files\Microsoft SQL Server\MSSQL\Binn directory and copy sqlctr.ini and sqlctr.h into it (which i poached from an install that didnt rollback).

But this results in the following error:

Starting custom action InstallSQLAgentSecurity
LoadLibrary failed for C:\Program Files\Microsoft SQL Server\Mssql\BinnMSSQL$DONALD007\Binn\SEMNT.DLL. GetLastError() returned: 126
Action ended 0:05:57: InstallFinalize. Return value 3.

Does anyone know how to solve this?
btw here are parameters

REINSTALL=All
REINSTALLMODE=omus
COLLATION=Latin1_General_CI_AS
TARGETDIR=C:\Program Files\Microsoft SQL Server\Mssql\Binn
DATADIR=C:\Program Files\Microsoft SQL Server\Mssql\Data
SAPWD=1111
INSTANCENAME=Donald007

This is a clean install of msde using sql service pack 3 on win xp pro.

I have attached a copy of my log file that is generated when this "LoadLibrary failed.." error occurs.

I also noticed that in the services i can still see a SQLSERVERAGENT even though this service is not started and the file it refers to has been deleted.

Originally posted by deekay2003
hi ppl,
I get the following an error prompt/box pops up during
installation saying :
"Service 'MSSQLSERVER' (MSSQLSERVER) Could not be installed. Verify
that you have sufficient priviledge to install system services"
-cancel- -retry- -ignore- buttons, this has now happened 4 times
consistently.

Retry does not work, cancelling and ignore end the installation but theC:\Program Files\Microsoft SQL Server\... and subdir as well as
registry entries are created.

After this any re-install cancels (disappears) unless i manually
remove C:\Program Files\Microsoft SQL Server\ dirs and registry
entries. IF i do this then and try installing again then i get
"Service 'MSSQLSERVER' (MSSQLSERVER) Could not be installed. ..."
error again.

the parameters im using are:
BLANKSAPWD=1, REINSTALL=All , REINSTALLMODE=omus, disablerollback=1.
and switches:
/L*v MSDE_log.txt

i have attached log file.
Please help a stoopid newbie :(