MSDE rel A installation error

I got an error "Setup failed to configure the server". I
have tried to delete the directory "C:\program
files\microsoft sql sever before installation. But I still
get this error. What should i do?
Thank you very much. I spent a week to install this MSDE
but still failed. I am very desperate...
San
hi San,
"San" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:1e5f701c4554e$a0454200$a501280a@.phx.gbl...
> I got an error "Setup failed to configure the server". I
> have tried to delete the directory "C:\program
> files\microsoft sql sever before installation. But I still
> get this error. What should i do?
> Thank you very much. I spent a week to install this MSDE
> but still failed. I am very desperate...
in addition to folder delete, try cealning the Windows Registry too, as
reported in
http://support.microsoft.com/default...;EN-US;Q290991
"Remove a Specific Instance of SQL Server" section...
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
|||Thank you. However, I am confused. It is because that KB
is for those who have sql sever installed before. My
computer did not contains any sql sever before (I think).
Could you give me more hints on what I should delete?
Furthermore, I found a strange registry. It
is "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microso ft SQL
Server Setup.{5B5BFFF9-9D55-45AF-9390-AA4DC1C4EEFE}".
Should I delete this?
Thank you for your help.
San

>--Original Message--
>hi San,
>"San" <anonymous@.discussions.microsoft.com> ha scritto
nel messaggio[vbcol=seagreen]
>news:1e5f701c4554e$a0454200$a501280a@.phx.gbl...
still
>in addition to folder delete, try cealning the Windows
Registry too, as
>reported in
>http://support.microsoft.com/default.aspx?scid=kb;EN-
US;Q290991
>"Remove a Specific Instance of SQL Server" section...
>--
>Andrea Montanari (Microsoft MVP - SQL Server)
>http://www.asql.biz/DbaMgr.shtm
http://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 San,
"San" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:1e59401c45553$1386bba0$a101280a@.phx.gbl...
> Thank you. However, I am confused. It is because that KB
> is for those who have sql sever installed before. My
> computer did not contains any sql sever before (I think).
> Could you give me more hints on what I should delete?
> Furthermore, I found a strange registry. It
> is "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microso ft SQL
> Server Setup.{5B5BFFF9-9D55-45AF-9390-AA4DC1C4EEFE}".
> Should I delete this?
personally I always and only cleared the registry keys reported in the KB
article... as you already read, this does not clear the Windows Installer
registry entries, but I was quiet happy with this method when a MSDE
instance I installed refused to uninstall... I still have this entry in the
Add/Remove programs applet, but I'll remove it ...perhaps =;-D
the hive you notice shoul'd only point to a Temp folder used by the setup
process...
you wrote[vbcol=seagreen]
uncomplete installations can make the system dirty, so you are supposed to
clear it before re-proceeding with new installs...
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
sql

msde memory setting

What memory settings should i configure to tune msde?
Sometimes it will be installed on a PC but at other times it will be an app
server. On the app server i want to take advantage of the increase in memory.
hi,
Keeper wrote:
> What memory settings should i configure to tune msde?
> Sometimes it will be installed on a PC but at other times it will be
> an app server. On the app server i want to take advantage of the
> increase in memory.
usually you should not manually "tune" SQL Server as it is tailored to self
configure it self...
on the other hand, SQL Server is very resources intensive, and is designed
to take advantage of all the installed available memory (in sys32 processes
limit )
and it's a very challenging taks to manual configure it for best
performance..
remember that memory usage is database and application dependent, but usage
and workloads dependent too...
Loosely speaking, SQL Server organize it's memory allocation in two distinct
regions, the "buffer pool" (BPool) and the "memory to leave" (MemToLeave)
regions. (I'm excluding use of AWE in order to provide easy understanding
and because MSDE does not admit it)..
so... the BPool is the primary region SQL Server uses for it's internal
matter, while MemToLeave consists of the virtual memory space within the 1gb
user mode address space and the memory not used by the BPool.
when SQL Server starts, it begins calculating the upper limit the BPool can
reach... if no MaxMemory is set, this value will be set to the amount of the
physical memory or the size of the user mode address space (1gb) , minus the
size of the MemToLeave, whichever is less..
by default, MemToLeave is set to 384mb, 128mb of them are for worker thread
stacks and 256mb for allocation outside the BPool, such as memory for OLE-DB
providers, linked server drivers, NetLib dlls, in process COM objects space
and memory requirements and so on..
when MaxMemory value is explicitally set, this upper limit will only address
BPool region needs...
so only the address space of BPool pages is limited by this configuration
value, while SQL Server memory requirememts outside BPool allocation are not
limited this way...
more, each connection, live or sleeping, will eat about 24kb of memory,
calculated as 12 KB + 3 times the Network Packet Size (default setting that
can be partially customized via sp_configure system stored procedure
modifying the 'user connections' setting), used to store the data structures
holding the connection 's context, as long as for buffer used to send and
receive the relative associated network streams (default to 4KB network
packet setting), that can be stolen from the buffer pool memory region
and/or the MemToLeave memory area...
not limiting the resources, SQL Server can reclaim that memory (up to 1 gb,
in our example) for it's uses, and it will perhaps release it only under
pressure by the OS claiming for additional memory, if it's the case, else it
will maintain that memory in order to cache pages and execution plans...
under OS pressure, SQL Server will try having the Lazy Writer releasing
resources, but you are not granted that this will occur, even if SQL Server
will always try to leave some memory for other OS needs, usually between 4
and 10mb of RAM... so, on SQL Server dedicated servers, you usually see
memory usage climbing to the top and staying there for long time, becouse of
SQL Server tends to keep pages read from disk in memory to increase further
and successive access to those pages, as long as query plans and so on... on
a heavy loaded server, if you add web server duty, you will have resources
contentions for sure...
I strongly advice you for
http://www.windowsitpro.com/Article/...908/37908.html and
http://www.windowsitpro.com/Article/...890/37890.html
another interesting readings:
http://msdn.microsoft.com/library/de...v_03252004.asp
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
|||hi,
Keeper wrote:
> What memory settings should i configure to tune msde?
> Sometimes it will be installed on a PC but at other times it will be
> an app server. On the app server i want to take advantage of the
> increase in memory.
usually you should not manually "tune" SQL Server as it is tailored to self
configure it self...
on the other hand, SQL Server is very resources intensive, and is designed
to take advantage of all the installed available memory (in sys32 processes
limit )
and it's a very challenging taks to manual configure it for best
performance..
remember that memory usage is database and application dependent, but usage
and workloads dependent too...
Loosely speaking, SQL Server organize it's memory allocation in two distinct
regions, the "buffer pool" (BPool) and the "memory to leave" (MemToLeave)
regions. (I'm excluding use of AWE in order to provide easy understanding
and because MSDE does not admit it)..
so... the BPool is the primary region SQL Server uses for it's internal
matter, while MemToLeave consists of the virtual memory space within the 1gb
user mode address space and the memory not used by the BPool.
when SQL Server starts, it begins calculating the upper limit the BPool can
reach... if no MaxMemory is set, this value will be set to the amount of the
physical memory or the size of the user mode address space (1gb) , minus the
size of the MemToLeave, whichever is less..
by default, MemToLeave is set to 384mb, 128mb of them are for worker thread
stacks and 256mb for allocation outside the BPool, such as memory for OLE-DB
providers, linked server drivers, NetLib dlls, in process COM objects space
and memory requirements and so on..
when MaxMemory value is explicitally set, this upper limit will only address
BPool region needs...
so only the address space of BPool pages is limited by this configuration
value, while SQL Server memory requirememts outside BPool allocation are not
limited this way...
more, each connection, live or sleeping, will eat about 24kb of memory,
calculated as 12 KB + 3 times the Network Packet Size (default setting that
can be partially customized via sp_configure system stored procedure
modifying the 'user connections' setting), used to store the data structures
holding the connection 's context, as long as for buffer used to send and
receive the relative associated network streams (default to 4KB network
packet setting), that can be stolen from the buffer pool memory region
and/or the MemToLeave memory area...
not limiting the resources, SQL Server can reclaim that memory (up to 1 gb,
in our example) for it's uses, and it will perhaps release it only under
pressure by the OS claiming for additional memory, if it's the case, else it
will maintain that memory in order to cache pages and execution plans...
under OS pressure, SQL Server will try having the Lazy Writer releasing
resources, but you are not granted that this will occur, even if SQL Server
will always try to leave some memory for other OS needs, usually between 4
and 10mb of RAM... so, on SQL Server dedicated servers, you usually see
memory usage climbing to the top and staying there for long time, becouse of
SQL Server tends to keep pages read from disk in memory to increase further
and successive access to those pages, as long as query plans and so on... on
a heavy loaded server, if you add web server duty, you will have resources
contentions for sure...
I strongly advice you for
http://www.windowsitpro.com/Article/...908/37908.html and
http://www.windowsitpro.com/Article/...890/37890.html
another interesting readings:
http://msdn.microsoft.com/library/de...v_03252004.asp
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
|||i appreciate the information
thanx
"Andrea Montanari" wrote:

> hi,
> Keeper wrote:
> usually you should not manually "tune" SQL Server as it is tailored to self
> configure it self...
> on the other hand, SQL Server is very resources intensive, and is designed
> to take advantage of all the installed available memory (in sys32 processes
> limit )
> and it's a very challenging taks to manual configure it for best
> performance..
> remember that memory usage is database and application dependent, but usage
> and workloads dependent too...
> Loosely speaking, SQL Server organize it's memory allocation in two distinct
> regions, the "buffer pool" (BPool) and the "memory to leave" (MemToLeave)
> regions. (I'm excluding use of AWE in order to provide easy understanding
> and because MSDE does not admit it)..
> so... the BPool is the primary region SQL Server uses for it's internal
> matter, while MemToLeave consists of the virtual memory space within the 1gb
> user mode address space and the memory not used by the BPool.
> when SQL Server starts, it begins calculating the upper limit the BPool can
> reach... if no MaxMemory is set, this value will be set to the amount of the
> physical memory or the size of the user mode address space (1gb) , minus the
> size of the MemToLeave, whichever is less..
> by default, MemToLeave is set to 384mb, 128mb of them are for worker thread
> stacks and 256mb for allocation outside the BPool, such as memory for OLE-DB
> providers, linked server drivers, NetLib dlls, in process COM objects space
> and memory requirements and so on..
> when MaxMemory value is explicitally set, this upper limit will only address
> BPool region needs...
> so only the address space of BPool pages is limited by this configuration
> value, while SQL Server memory requirememts outside BPool allocation are not
> limited this way...
> more, each connection, live or sleeping, will eat about 24kb of memory,
> calculated as 12 KB + 3 times the Network Packet Size (default setting that
> can be partially customized via sp_configure system stored procedure
> modifying the 'user connections' setting), used to store the data structures
> holding the connection 's context, as long as for buffer used to send and
> receive the relative associated network streams (default to 4KB network
> packet setting), that can be stolen from the buffer pool memory region
> and/or the MemToLeave memory area...
> not limiting the resources, SQL Server can reclaim that memory (up to 1 gb,
> in our example) for it's uses, and it will perhaps release it only under
> pressure by the OS claiming for additional memory, if it's the case, else it
> will maintain that memory in order to cache pages and execution plans...
> under OS pressure, SQL Server will try having the Lazy Writer releasing
> resources, but you are not granted that this will occur, even if SQL Server
> will always try to leave some memory for other OS needs, usually between 4
> and 10mb of RAM... so, on SQL Server dedicated servers, you usually see
> memory usage climbing to the top and staying there for long time, becouse of
> SQL Server tends to keep pages read from disk in memory to increase further
> and successive access to those pages, as long as query plans and so on... on
> a heavy loaded server, if you add web server duty, you will have resources
> contentions for sure...
> I strongly advice you for
> http://www.windowsitpro.com/Article/...908/37908.html and
> http://www.windowsitpro.com/Article/...890/37890.html
> another interesting readings:
> http://msdn.microsoft.com/library/de...v_03252004.asp
> --
> 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
>
>

MSDE Maintenance Plan

Hello,

I'm trying to configure my MSDE 2000 installation to dump all databases
and transaction logs to disk every night to be backed up by our backup
software. All goes great in configuring the maintenance plan until I get to
the retention part. I want to configure the backup plan so that it'll delete
OLD backup older than 2 days. When I click the 'Remove files older than" box
and choose 2, but there's nothing in the drop-down box where
Hours/Days/Months should be..
If I fudge it and try to edit the job nothing has saved and the job
fails.. Any help is greatly appreciated..

Thanks,
-Mike-"Michael Nostrom" <nostrom@.binghamton.edu.edu> wrote in message news:<40bdfa79$1_2@.bingnews.binghamton.edu>...
> Hello,
> I'm trying to configure my MSDE 2000 installation to dump all databases
> and transaction logs to disk every night to be backed up by our backup
> software. All goes great in configuring the maintenance plan until I get to
> the retention part. I want to configure the backup plan so that it'll delete
> OLD backup older than 2 days. When I click the 'Remove files older than" box
> and choose 2, but there's nothing in the drop-down box where
> Hours/Days/Months should be..
> If I fudge it and try to edit the job nothing has saved and the job
> fails.. Any help is greatly appreciated..
> Thanks,
> -Mike-

I have no idea what the issue is, but perhaps you can give some more
information. Are you using the latest version of MSDE? And which
operating system are you working with? Have you been able to create a
plan successfully on an MSSQL server (if you have one, but since you
have EM I guess you do)? Have you tried reinstalling the client tools,
and have you applied the latest servicepack to the client tools?

Simon|||"Simon Hayes" <sql@.hayes.ch> wrote in message
news:60cd0137.0406022246.77874ec3@.posting.google.c om...
"Michael Nostrom" <nostrom@.binghamton.edu.edu> wrote in message
news:<40bdfa79$1_2@.bingnews.binghamton.edu>...
> Hello,
> I'm trying to configure my MSDE 2000 installation to dump all
databases
> and transaction logs to disk every night to be backed up by our backup
> software. All goes great in configuring the maintenance plan until I get
to
> the retention part. I want to configure the backup plan so that it'll
delete
> OLD backup older than 2 days. When I click the 'Remove files older than"
box
> and choose 2, but there's nothing in the drop-down box where
> Hours/Days/Months should be..
> If I fudge it and try to edit the job nothing has saved and the job
> fails.. Any help is greatly appreciated..
> Thanks,
> -Mike-

I have no idea what the issue is, but perhaps you can give some more
information. Are you using the latest version of MSDE? And which
operating system are you working with? Have you been able to create a
plan successfully on an MSSQL server (if you have one, but since you
have EM I guess you do)? Have you tried reinstalling the client tools,
and have you applied the latest servicepack to the client tools?

Simon

Windows 2000 SP4
MSDE 2000 (8.00.818) SP3

EM Tools is installed on my workstation for managing other SQL Servers.

I am able to do a simple Dump to Disk, but I want to schedule nightly dumps.

Actually I manually modified the 'Steps' of the backup job and added the
necessary code to get the job to complete successfully..
Thanks anyway Simon...

MSDE installation failure

I am trying to install MSDE 2000 rel A onto a machine running Win XP Pro SP2,
Keep getting error failed to configure the server and my error logs show this
message "Specified driver could not be loaded due to system error 126 (SQL
Server)." Everything that I have found refers to MDAC issues but SP2
installs the latest MDAC 2.81. I ran component checked and everything matched
when run for 2.8 on XP SP2. The only thing Not Found were odbdbcp.dll
sqlsvr32.dll and sqlsvr32.rll and according to documentation Not Found
just means they were not used in the version selected. Any ideas?
Hi,
I'm not sure, but I heard somewhere that MSDE 2000 relA (or sp3a), cann't be
installed on top of Windows XP SP2.
You must uninstall SP2, install MSDE sp3a and reinstall SP2.
I didn't test it.
HTH
AF
"FirePro2005" <FirePro2005@.discussions.microsoft.com> wrote in message
news:3EC1D631-6F00-4B85-A964-FFE79313533A@.microsoft.com...
> I am trying to install MSDE 2000 rel A onto a machine running Win XP Pro
SP2,
> Keep getting error failed to configure the server and my error logs show
this
> message "Specified driver could not be loaded due to system error 126
(SQL
> Server)." Everything that I have found refers to MDAC issues but SP2
> installs the latest MDAC 2.81. I ran component checked and everything
matched
> when run for 2.8 on XP SP2. The only thing Not Found were odbdbcp.dll
> sqlsvr32.dll and sqlsvr32.rll and according to documentation Not
Found
> just means they were not used in the version selected. Any ideas?
|||I have installed MSDE 2000 Rel A on a quite a few machines with XP and
SP2 without such issues. My issue had always been the same - inability
to connect from a remote system. I have finally figure out that by
default MSDE does not install with Network mode turned on. On top of
that, SP 2 blocks all ports, including 1433 used by MSDE, in the
firewall.
So, I have learned to install with the "Mized Mode Authentication"
turned on and also to open up Port 1433.
- manzoor

MSDE Install Failure - Unable to Configure Server

I have seen a few posts loosely related to this issue - but check this one out.

On a windows xp home box, I installed MSDE without an issue. I then upgraded said pc to MDAC 2.7 SP1 (XP) and got the above mentioned "Unable to Configure Server" error.

We have 3 users who are also getting this error when attempting to install the MSDE from our media, so I really need some help on this one!

I'm reasonably sure it is mdac, but I cannot determine the specifics yet. We also have this same issue on one lonely 98 box here in our office.

Does anyone have any experience with this typ of MDAC issue? Anything you could share would be great.Make sure to stop any anti virus application running.

MSDE Event ID 208/17055 (Newbie)

Hello,
We get these events logged every night, apparently when
the SQLAGENT tries to do it's backup. I'm afraid I
didn't configure MSDE on this particular server, and I
don't have any Enterprise Mgr functions on the desktop,
so I'm slightly at a loss as to how to go about resolving
this issue, being that I'm a noob when it comes to SQL.
Any advise, help or pointers would be great.
A pint goes to the first correct answer!
Andy Griggs.
Hello,
If you have another computer with Entreprise manager, you can donnect to the
msde by the network..
Marc Allard
"Andy Griggs" <andrew.griggs@.agile-it.net> a crit dans le message de
news:20dd701c459ec$940620c0$a101280a@.phx.gbl...
> Hello,
> We get these events logged every night, apparently when
> the SQLAGENT tries to do it's backup. I'm afraid I
> didn't configure MSDE on this particular server, and I
> don't have any Enterprise Mgr functions on the desktop,
> so I'm slightly at a loss as to how to go about resolving
> this issue, being that I'm a noob when it comes to SQL.
> Any advise, help or pointers would be great.
> A pint goes to the first correct answer!
> Andy Griggs.