bcm install

  • Thread starter Thread starter tpitz
  • Start date Start date
T

tpitz

I just bought this expensive office suite. office
profesional 2003
The first disk installed ok, but on the 2nd disk every
time I try to install the BCM,
I get the below error log file. I dont think i have an
sql server. and i dont know what a service control
manager is. 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.
 
You might get a more informative solution by posting to the
microsoft.public.office.setup ng
David
 
This group is an appropriate group, although an SQL group might be best -
the office people won't know any more than we do.

The service control manager is the SQL tray icon. Open it an insure it's
running.

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Coauthor, OneNote 2003 for Windows (Visual QuickStart Guide)


Search for answers: http://groups.google.com
Most recent posts to the Outlook newsgroups:
http://groups.google.com/groups?as_ugroup=microsoft.public.outlook.*&num=30

DL said:
You might get a more informative solution by posting to the
microsoft.public.office.setup ng
David

tpitz said:
I just bought this expensive office suite. office
profesional 2003
The first disk installed ok, but on the 2nd disk every
time I try to install the BCM,
I get the below error log file. I dont think i have an
sql server. and i dont know what a service control
manager is. 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.
Click to expand...
Click to expand...
 
Back
Top