T
Tpitz
I just bought this expensive office suite. office proffesional 2003
The first disk installed ok, but every time I try to install the BCM,
I get the below error log file. I not very educated on SQL but I hate
to waste money on a product I can't use. I've searched high and low
for online solutions to this problem, to no avail. Any help is greatly
appreciated.
2003-12-28 03:14:33.50 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-12-28 03:14:33.50 server Copyright (C) 1988-2002 Microsoft
Corporation.
2003-12-28 03:14:33.50 server All rights reserved.
2003-12-28 03:14:33.50 server Server Process ID is 3236.
2003-12-28 03:14:33.50 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL
Server\MSSQL$MICROSOFTBCM\LOG\ERRORLOG'.
2003-12-28 03:14:33.53 server SQL Server is starting at priority
class 'normal'(1 CPU detected).
2003-12-28 03:14:33.75 server SQL Server configured for thread mode
processing.
2003-12-28 03:14:33.76 server Using dynamic lock allocation. [500]
Lock Blocks, [1000] Lock Owner Blocks.
2003-12-28 03:14:34.01 spid3 Warning ******************
2003-12-28 03:14:34.01 spid3 SQL Server started in single user
mode. Updates allowed to system catalogs.
2003-12-28 03:14:34.18 spid3 Starting up database 'master'.
2003-12-28 03:14:35.48 server Using 'SSNETLIB.DLL' version
'8.0.766'.
2003-12-28 03:14:35.48 spid5 Starting up database 'model'.
2003-12-28 03:14:35.62 spid3 Server name is
'XXXXX26-B\MICROSOFTBCM'.
2003-12-28 03:14:35.62 spid3 Skipping startup of clean database id
5
2003-12-28 03:14:35.62 spid3 Skipping startup of clean database id
6
2003-12-28 03:14:35.62 spid3 Starting up database 'msdb'.
2003-12-28 03:14:36.67 spid5 Clearing tempdb database.
2003-12-28 03:14:38.20 spid5 Starting up database 'tempdb'.
2003-12-28 03:14:38.42 spid3 Recovery complete.
2003-12-28 03:14:38.42 spid3 SQL global counter collection task is
created.
2003-12-28 03:14:38.46 spid3 Warning: override, autoexec
procedures skipped.
2003-12-28 03:14:39.15 server SQL server listening on Shared
Memory.
2003-12-28 03:14:39.15 server SQL Server is ready for client
connections
2003-12-28 03:14:49.00 spid3 SQL Server is terminating due to
'stop' request from Service Control Manager.
The first disk installed ok, but every time I try to install the BCM,
I get the below error log file. I not very educated on SQL but I hate
to waste money on a product I can't use. I've searched high and low
for online solutions to this problem, to no avail. Any help is greatly
appreciated.
2003-12-28 03:14:33.50 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-12-28 03:14:33.50 server Copyright (C) 1988-2002 Microsoft
Corporation.
2003-12-28 03:14:33.50 server All rights reserved.
2003-12-28 03:14:33.50 server Server Process ID is 3236.
2003-12-28 03:14:33.50 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL
Server\MSSQL$MICROSOFTBCM\LOG\ERRORLOG'.
2003-12-28 03:14:33.53 server SQL Server is starting at priority
class 'normal'(1 CPU detected).
2003-12-28 03:14:33.75 server SQL Server configured for thread mode
processing.
2003-12-28 03:14:33.76 server Using dynamic lock allocation. [500]
Lock Blocks, [1000] Lock Owner Blocks.
2003-12-28 03:14:34.01 spid3 Warning ******************
2003-12-28 03:14:34.01 spid3 SQL Server started in single user
mode. Updates allowed to system catalogs.
2003-12-28 03:14:34.18 spid3 Starting up database 'master'.
2003-12-28 03:14:35.48 server Using 'SSNETLIB.DLL' version
'8.0.766'.
2003-12-28 03:14:35.48 spid5 Starting up database 'model'.
2003-12-28 03:14:35.62 spid3 Server name is
'XXXXX26-B\MICROSOFTBCM'.
2003-12-28 03:14:35.62 spid3 Skipping startup of clean database id
5
2003-12-28 03:14:35.62 spid3 Skipping startup of clean database id
6
2003-12-28 03:14:35.62 spid3 Starting up database 'msdb'.
2003-12-28 03:14:36.67 spid5 Clearing tempdb database.
2003-12-28 03:14:38.20 spid5 Starting up database 'tempdb'.
2003-12-28 03:14:38.42 spid3 Recovery complete.
2003-12-28 03:14:38.42 spid3 SQL global counter collection task is
created.
2003-12-28 03:14:38.46 spid3 Warning: override, autoexec
procedures skipped.
2003-12-28 03:14:39.15 server SQL server listening on Shared
Memory.
2003-12-28 03:14:39.15 server SQL Server is ready for client
connections
2003-12-28 03:14:49.00 spid3 SQL Server is terminating due to
'stop' request from Service Control Manager.