MSDE 2000

I'm trying to install this application but i get an error
Setup failed to configure the server. Refer to the server error logs and setup error logs for more information.
I'm running Windows XP SP2.
Could my SP2 be causing me problems considering I successfully installed it previously.
Many thanksWhat do the error logs say? That will be the key to solving theproblem. You might consider using the verbose setup log fileswitch on your SETUP.EXE command:

/L*v [filename]

sql

MSDB database

I have under SQL Server 2000 Standard Version with SP3a on Windows 2000 SP4
a Database Maintenance plan to backup transaction logs of all databases
hourly.
This job has been frequently failing, and the reason is that on the MSDB
database, the Recovery option has for some mysterious reason frequently been
reset from FULL to SIMPLE, and in order to get transaction logs backing up,
it needs to be set to FULL.
anyone has any ideas why/what process, etc. would reset the recovery option
from FULL to SIMPLE?> I have under SQL Server 2000 Standard Version with SP3a on Windows 2000
SP4
> a Database Maintenance plan to backup transaction logs of all databases
> hourly.
Backing up the transaction logs from all databases seems like overkill.
What is the point, e.g. for tempdb?

> anyone has any ideas why/what process, etc. would reset the recovery
option
> from FULL to SIMPLE?
This is the way SQL Server works.
http://www.support.microsoft.com/?id=257856
If you really want to back up msdb every hour, then you can make a task in
your job to temporarily set the recovery model to FULL. However this won't
accomplish much as the transaction logs won't be complete (and maybe not
even usable, depending on how you plan to use them).
If you want the behavior to be different, you can let Microsoft know how you
feel: sqlwish@.microsoft.com
Aaron Bertrand
SQL Server MVP|||Aaron Bertrand - MVP wrote:

> option
> This is the way SQL Server works.
> http://www.support.microsoft.com/?id=257856
>
that link is interesting. sort of contradicts the line from BOL "All recove
ry
models are supported for model, msdb and distribution." since full recovery
on
msdb only works until sqlagent is restarted.
i always prefer to have a dbmp for user databases and one for system databas
es.
in the system one, i don't back up transaction logs.
i think it's sort of goofy that the transaction log backup from a dbmp will
try
to backup the logs for db's in simple recovery and then generate errors. i'
ve
written a script that skips simple recovery db's for the log backups, why ca
n't
microsoft implement it in the dbmp jobs?

MSDB database

I have under SQL Server 2000 Standard Version with SP3a on Windows 2000 SP4
a Database Maintenance plan to backup transaction logs of all databases
hourly.
This job has been frequently failing, and the reason is that on the MSDB
database, the Recovery option has for some mysterious reason frequently been
reset from FULL to SIMPLE, and in order to get transaction logs backing up,
it needs to be set to FULL.
anyone has any ideas why/what process, etc. would reset the recovery option
from FULL to SIMPLE?> I have under SQL Server 2000 Standard Version with SP3a on Windows 2000
SP4
> a Database Maintenance plan to backup transaction logs of all databases
> hourly.
Backing up the transaction logs from all databases seems like overkill.
What is the point, e.g. for tempdb?
> anyone has any ideas why/what process, etc. would reset the recovery
option
> from FULL to SIMPLE?
This is the way SQL Server works.
http://www.support.microsoft.com/?id=257856
If you really want to back up msdb every hour, then you can make a task in
your job to temporarily set the recovery model to FULL. However this won't
accomplish much as the transaction logs won't be complete (and maybe not
even usable, depending on how you plan to use them).
If you want the behavior to be different, you can let Microsoft know how you
feel: sqlwish@.microsoft.com
--
Aaron Bertrand
SQL Server MVP|||Aaron Bertrand - MVP wrote:
> > anyone has any ideas why/what process, etc. would reset the recovery
> option
> > from FULL to SIMPLE?
> This is the way SQL Server works.
> http://www.support.microsoft.com/?id=257856
>
that link is interesting. sort of contradicts the line from BOL "All recovery
models are supported for model, msdb and distribution." since full recovery on
msdb only works until sqlagent is restarted.
i always prefer to have a dbmp for user databases and one for system databases.
in the system one, i don't back up transaction logs.
i think it's sort of goofy that the transaction log backup from a dbmp will try
to backup the logs for db's in simple recovery and then generate errors. i've
written a script that skips simple recovery db's for the log backups, why can't
microsoft implement it in the dbmp jobs?