[veritus]

I tried searching the forums but nothing came up regarding my issues. I am installing BES Express 4.2 on a Windows 2003 SP1 box that has Exchange 2003 SP2 installed. I am only running BES for 2 users, so installing on my exchange server shouldn't be a problem. I select local database install at the prompt, but before setup completes I get the following error message: "Setup failed to configure the server. Refer to the server error logs and setup error logs for more information." Any thoughts? I think the problems is related to MSDE, but I'm not sure.

Cheers!

Chris

P.S. Here is a copy of the MSSQL log.

--------------------------------------------------------

2007-09-04 12:40:50.85 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.2 (Build 3790: Service Pack 1)

2007-09-04 12:40:50.85 server Copyright (C) 1988-2002 Microsoft Corporation.
2007-09-04 12:40:50.85 server All rights reserved.
2007-09-04 12:40:50.85 server Server Process ID is 4732.
2007-09-04 12:40:50.85 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG'.
2007-09-04 12:40:50.85 server SQL Server is starting at priority class 'normal'(2 CPUs detected).
2007-09-04 12:40:50.97 server SQL Server configured for thread mode processing.
2007-09-04 12:40:50.99 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2007-09-04 12:40:51.03 spid2 Starting up database 'master'.
2007-09-04 12:40:51.28 server Using 'SSNETLIB.DLL' version '8.0.766'.
2007-09-04 12:40:51.28 spid5 Starting up database 'model'.
2007-09-04 12:40:51.32 spid2 Server name is '****EX01'.
2007-09-04 12:40:51.32 spid2 Skipping startup of clean database id 4
2007-09-04 12:40:51.33 spid2 Skipping startup of clean database id 5
2007-09-04 12:40:51.33 spid2 Skipping startup of clean database id 6
2007-09-04 12:40:51.38 server SQL server listening on 192.168.0.102: 1433.
2007-09-04 12:40:51.38 server SQL server listening on 127.0.0.1: 1433.
2007-09-04 12:40:51.38 spid5 Clearing tempdb database.
2007-09-04 12:40:51.39 server SQL server listening on TCP, Shared Memory, Named Pipes.
2007-09-04 12:40:51.41 server SQL Server is ready for client connections
2007-09-04 12:40:51.50 spid5 Starting up database 'tempdb'.
2007-09-04 12:40:51.57 spid2 Recovery complete.
2007-09-04 12:40:51.57 spid2 SQL global counter collection task is created.
2007-09-04 12:41:05.74 spid2 SQL Server is terminating due to 'stop' request from Service Control Manager.

[MWPatterson]

It probably has to do with the fact that you are trying to install it on the same system as Exchange. Exchange either uses MSDE or SQL. It looks like BES Express does not like the fact that either of the 2 are already on the system as it is made to run in a specific way and use MSDE. As it probably installs a version and sets up the database for it to work off of.

[semiar]

Originally Posted by MWPatterson

It probably has to do with the fact that you are trying to install it on the same system as Exchange. Exchange either uses MSDE or SQL. It looks like BES Express does not like the fact that either of the 2 are already on the system as it is made to run in a specific way and use MSDE. As it probably installs a version and sets up the database for it to work off of.

I have setup a couple of server like that and never had an issue. I suggest creating the database, then try installing. I also suggest using SQL Express over MSDE.

[veritus]

Well, I decided to create the database on my SQL server and everything is working fine. Exchange doesn't run on SQL and I had no SQL instances installed on the exchange server. So, I'm still confused as to why it didn't work. Thanks for the replies!