During setup we get the following error message:
"Setup failed to configure server; refer to the server error logs and setup
logs for more information"

Anyone knows the source of this error message and/or knows where to look for
these error logs?

Thanks,
Piet van der Plas

I found this Error.log in the folder Microsoft SQL Server. Hope this helps:

2003-11-21 08:38:43.25 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-11-21 08:38:43.25 server Copyright (C) 1988-2002 Microsoft
Corporation.
2003-11-21 08:38:43.25 server All rights reserved.
2003-11-21 08:38:43.25 server Server Process ID is 812.
2003-11-21 08:38:43.25 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$MICROSOFTBCM\LOG\ERRORLOG'.
2003-11-21 08:38:43.28 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2003-11-21 08:38:43.48 server SQL Server configured for thread mode
processing.
2003-11-21 08:38:43.50 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2003-11-21 08:38:43.57 spid3 Warning ******************
2003-11-21 08:38:43.57 spid3 SQL Server started in single user mode.
Updates allowed to system catalogs.
2003-11-21 08:38:43.68 spid3 Starting up database 'master'.
2003-11-21 08:38:44.12 server Using 'SSNETLIB.DLL' version '8.0.766'.
2003-11-21 08:38:44.12 spid5 Starting up database 'model'.
2003-11-21 08:38:44.20 spid3 Server name is 'ITR10\MICROSOFTBCM'.
2003-11-21 08:38:44.20 spid3 Skipping startup of clean database id 5
2003-11-21 08:38:44.20 spid3 Skipping startup of clean database id 6
2003-11-21 08:38:44.20 spid3 Starting up database 'msdb'.
2003-11-21 08:38:44.68 spid5 Clearing tempdb database.
2003-11-21 08:38:46.29 spid5 Starting up database 'tempdb'.
2003-11-21 08:38:46.48 spid3 Recovery complete.
2003-11-21 08:38:46.48 spid3 SQL global counter collection task is
created.
2003-11-21 08:38:46.51 spid3 Warning: override, autoexec procedures
skipped.
2003-11-21 08:38:47.12 server SQL server listening on Shared Memory.
2003-11-21 08:38:47.14 server SQL Server is ready for client connections
2003-11-21 08:40:48.35 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.

"Piet van der Plas" <(E-Mail Removed)> wrote in message
news:3fbdc9b7$0$155$(E-Mail Removed)...
> During setup we get the following error message:
> "Setup failed to configure server; refer to the server error logs and
setup
> logs for more information"
>
> Anyone knows the source of this error message and/or knows where to look
for
> these error logs?
>
> Thanks,
> Piet van der Plas
>
>
>
>
>

Go to the Program Files\Microsoft SQL Server folder and delete the MSSQL$MicrosoftBCM folder. Then try rerunning BCM setup.
--
Sue Mosher, Outlook MVP
Outlook and Exchange solutions at http://www.slipstick.com
Author of
Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx


"Piet van der Plas" <(E-Mail Removed)> wrote in message news:3fbdc9b7$0$155$(E-Mail Removed)...
> During setup we get the following error message:
> "Setup failed to configure server; refer to the server error logs and setup
> logs for more information"
>
> Anyone knows the source of this error message and/or knows where to look for
> these error logs?
>
> Thanks,
> Piet van der Plas
>
>
>
>
>