Database Creation was unsuccessful (Vista Sp1/ Outlook 2007 Ultimate/ BCM 2007)

C

cjterrence

I has installed Vista with SP1, Outlook ultimate 2007 and BCM 2007. When I
was creating a database, then jump a messge "Database Creation was
unsuccessful". I has try the Oullook online help"Cannot create a Business
Contact Manager database - Database creation is unsuccessful
", follow these step. But I still can't create a database. Now I get the
errorlog, please help me. Thanks.
========================================================================
2009-01-03 13:49:41.30 Server Microsoft SQL Server 2005 - 9.00.2047.00
(Intel X86)
Apr 14 2006 01:12:25
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 6.0 (Build 6001: Service Pack 1)

2009-01-03 13:49:41.30 Server (c) 2005 Microsoft Corporation.
2009-01-03 13:49:41.31 Server All rights reserved.
2009-01-03 13:49:41.31 Server Server process ID is 1948.
2009-01-03 13:49:41.31 Server Logging SQL Server messages in file 'C:\
Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2009-01-03 13:49:41.31 Server This instance of SQL Server last reported
using a process ID of 3376 at 2009/1/3 13:48:44 (local) 2009/1/3 5:48:44 (UTC)
. This is an informational message only; no user action is required.
2009-01-03 13:49:41.31 Server Registry startup parameters:
2009-01-03 13:49:41.31 Server -d C:\Program Files\Microsoft SQL Server\
MSSQL.1\MSSQL\DATA\master.mdf
2009-01-03 13:49:41.31 Server -e C:\Program Files\Microsoft SQL Server\
MSSQL.1\MSSQL\LOG\ERRORLOG
2009-01-03 13:49:41.31 Server -l C:\Program Files\Microsoft SQL Server\
MSSQL.1\MSSQL\DATA\mastlog.ldf
2009-01-03 13:49:41.31 Server -T 840
2009-01-03 13:49:41.31 Server -T 2324
2009-01-03 13:49:41.36 Server SQL Server is starting at normal priority
base (=7). This is an informational message only. No user action is required.
2009-01-03 13:49:41.36 Server Detected 2 CPUs. This is an informational
message; no user action is required.
2009-01-03 13:49:41.67 Server Using dynamic lock allocation. Initial
allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
an informational message only. No user action is required.
2009-01-03 13:49:43.74 Server Could not query the FIPS compliance mode
flag from registry. Error 2(系统找ä¸åˆ°æŒ‡å®šçš„文件。).
2009-01-03 13:49:44.44 Server Database mirroring has been enabled on
this instance of SQL Server.
2009-01-03 13:49:44.66 spid5s Starting up database 'master'.
2009-01-03 13:49:44.74 spid5s Recovery is writing a checkpoint in
database 'master' (1). This is an informational message only. No user action
is required.
2009-01-03 13:49:44.77 spid5s SQL Trace ID 1 was started by login "sa".
2009-01-03 13:49:44.79 spid5s Starting up database 'mssqlsystemresource'.

2009-01-03 13:49:44.79 spid5s The resource database build version is 9.
00.2047. This is an informational message only. No user action is required.
2009-01-03 13:49:44.90 spid8s Starting up database 'model'.
2009-01-03 13:49:44.90 spid5s Server name is 'YLMFWWW-ORRYANI\MSSMLBIZ'.
This is an informational message only. No user action is required.
2009-01-03 13:49:44.90 spid5s Starting up database 'msdb'.
2009-01-03 13:49:45.02 spid8s Clearing tempdb database.
2009-01-03 13:49:45.66 spid8s Starting up database 'tempdb'.
2009-01-03 13:49:45.68 Server A self-generated certificate was
successfully loaded for encryption.
2009-01-03 13:49:45.68 Server Server local connection provider is ready
to accept connection on [ \\.\pipe\SQLLocal\MSSMLBIZ ].
2009-01-03 13:49:45.68 Server Server named pipe provider is ready to
accept connection on [ \\.\pipe\MSSQL$MSSMLBIZ\sql\query ].
2009-01-03 13:49:45.68 Server Dedicated administrator connection support
was not started because it is not available on this edition of SQL Server.
This is an informational message only. No user action is required.
2009-01-03 13:49:45.68 Server SQL Server is now ready for client
connections. This is an informational message; no user action is required.
2009-01-03 13:49:45.75 spid5s Recovery is complete. This is an
informational message only. No user action is required.
2009-01-03 13:49:45.99 spid11s The Service Broker protocol transport is
disabled or not configured.
2009-01-03 13:49:45.99 spid11s The Database Mirroring protocol transport
is disabled or not configured.
2009-01-03 13:49:45.99 spid11s Service Broker manager has started.
2009-01-03 13:52:55.15 Server Server resumed execution after being idle
155 seconds: user activity awakened the server. This is an informational
message only. No user action is required.
2009-01-03 13:52:56.82 spid51 Starting up database 'MSSmallBusiness'.
2009-01-03 13:52:57.05 spid51 index restored for MSSmallBusiness.
sysowners.
2009-01-03 13:52:57.07 spid51 index restored for MSSmallBusiness.
sysschobjs.
2009-01-03 13:52:57.08 spid51 index restored for MSSmallBusiness.
syscolpars.
2009-01-03 13:52:57.08 spid51 index restored for MSSmallBusiness.
sysnsobjs.
2009-01-03 13:52:57.08 spid51 index restored for MSSmallBusiness.
syscerts.
2009-01-03 13:52:57.10 spid51 index restored for MSSmallBusiness.
sysxprops.
2009-01-03 13:52:57.10 spid51 index restored for MSSmallBusiness.
sysscalartypes.
2009-01-03 13:52:57.10 spid51 index restored for MSSmallBusiness.
sysidxstats.
2009-01-03 13:52:57.11 spid51 index restored for MSSmallBusiness.
sysclsobjs.
2009-01-03 13:52:57.11 spid51 index restored for MSSmallBusiness.
sysremsvcbinds.
2009-01-03 13:52:57.13 spid51 index restored for MSSmallBusiness.sysrts.

2009-01-03 13:52:57.14 spid51 index restored for MSSmallBusiness.
sysasymkeys.
2009-01-03 13:52:57.14 spid51 index restored for MSSmallBusiness.
syssqlguides.
2009-01-03 13:52:57.46 spid51 Starting up database 'MSSmallBusiness'.
2009-01-03 13:52:57.71 spid51 Setting database option AUTO_CLOSE to OFF
for database MSSmallBusiness.
2009-01-03 13:52:57.72 spid51 Setting database option RECOVERY to
RECMODEL_70BACKCOMP for database MSSmallBusiness.
2009-01-03 13:52:57.72 spid51 Setting database option RECOVERY to
RECMODEL_70BACKCOMP for database MSSmallBusiness.
2009-01-03 13:52:57.74 spid51 Setting database option
TORN_PAGE_DETECTION to ON for database MSSmallBusiness.
2009-01-03 13:52:57.74 spid51 Setting database option READ_WRITE to ON
for database MSSmallBusiness.
2009-01-03 13:52:57.74 spid51 Setting database option AUTO_SHRINK to OFF
for database MSSmallBusiness.
2009-01-03 13:52:57.74 spid51 Setting database option ANSI_NULL_DEFAULT
to OFF for database MSSmallBusiness.
2009-01-03 13:52:57.74 spid51 Setting database option RECURSIVE_TRIGGERS
to OFF for database MSSmallBusiness.
2009-01-03 13:52:57.75 spid51 Setting database option ANSI_NULLS to OFF
for database MSSmallBusiness.
2009-01-03 13:52:57.75 spid51 Setting database option
CONCAT_NULL_YIELDS_NULL to OFF for database MSSmallBusiness.
2009-01-03 13:52:57.75 spid51 Setting database option
CURSOR_CLOSE_ON_COMMIT to OFF for database MSSmallBusiness.
2009-01-03 13:52:57.75 spid51 Setting database option CURSOR_DEFAULT to
GLOBAL for database MSSmallBusiness.
2009-01-03 13:52:57.75 spid51 Setting database option QUOTED_IDENTIFIER
to OFF for database MSSmallBusiness.
2009-01-03 13:52:57.75 spid51 Setting database option ANSI_WARNINGS to
OFF for database MSSmallBusiness.
2009-01-03 13:52:57.77 spid51 Setting database option
AUTO_CREATE_STATISTICS to ON for database MSSmallBusiness.
2009-01-03 13:52:57.77 spid51 Setting database option
AUTO_UPDATE_STATISTICS to ON for database MSSmallBusiness.
2009-01-03 13:53:03.26 spid52 Setting database option SINGLE_USER to ON
for database MSSmallBusiness.
========================================================================
 
L

Luther

I has installed Vista with SP1, Outlook ultimate 2007 and BCM 2007. When I
was creating a database, then jump a messge "Database Creation was
unsuccessful". I has try the Oullook online help"Cannot create a Business
Contact Manager database - Database creation is unsuccessful
", follow these step. But I still can't create a database. Now I get the
errorlog, please help me. Thanks.
========================================================================
2009-01-03 13:49:41.30 Server Microsoft SQL Server 2005 - 9.00.2047.00
(Intel X86)
Apr 14 2006 01:12:25
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 6.0 (Build 6001: Service Pack 1)

2009-01-03 13:49:41.30 Server (c) 2005 Microsoft Corporation.
2009-01-03 13:49:41.31 Server All rights reserved.
2009-01-03 13:49:41.31 Server Server process ID is 1948.
2009-01-03 13:49:41.31 Server Logging SQL Server messages in file 'C:\
Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2009-01-03 13:49:41.31 Server This instance of SQL Server last reported
using a process ID of 3376 at 2009/1/3 13:48:44 (local) 2009/1/3 5:48:44 (UTC)
. This is an informational message only; no user action is required.
2009-01-03 13:49:41.31 Server Registry startup parameters:
2009-01-03 13:49:41.31 Server -d C:\Program Files\Microsoft SQL Server\
MSSQL.1\MSSQL\DATA\master.mdf
2009-01-03 13:49:41.31 Server -e C:\Program Files\Microsoft SQL Server\
MSSQL.1\MSSQL\LOG\ERRORLOG
2009-01-03 13:49:41.31 Server -l C:\Program Files\Microsoft SQL Server\
MSSQL.1\MSSQL\DATA\mastlog.ldf
2009-01-03 13:49:41.31 Server -T 840
2009-01-03 13:49:41.31 Server -T 2324
2009-01-03 13:49:41.36 Server SQL Server is starting at normal priority
base (=7). This is an informational message only. No user action is required.
2009-01-03 13:49:41.36 Server Detected 2 CPUs. This is an informational
message; no user action is required.
2009-01-03 13:49:41.67 Server Using dynamic lock allocation. Initial
allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. Thisis
an informational message only. No user action is required.
2009-01-03 13:49:43.74 Server Could not query the FIPS compliance mode
flag from registry. Error 2(ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£).
2009-01-03 13:49:44.44 Server Database mirroring has been enabled on
this instance of SQL Server.
2009-01-03 13:49:44.66 spid5s Starting up database 'master'.
2009-01-03 13:49:44.74 spid5s Recovery is writing a checkpoint in
database 'master' (1). This is an informational message only. No user action
is required.
2009-01-03 13:49:44.77 spid5s SQL Trace ID 1 was started by login "sa".
2009-01-03 13:49:44.79 spid5s Starting up database 'mssqlsystemresource'.

2009-01-03 13:49:44.79 spid5s The resource database build version is9.
00.2047. This is an informational message only. No user action is required.
2009-01-03 13:49:44.90 spid8s Starting up database 'model'.
2009-01-03 13:49:44.90 spid5s Server name is 'YLMFWWW-ORRYANI\MSSMLBIZ'.
This is an informational message only. No user action is required.
2009-01-03 13:49:44.90 spid5s Starting up database 'msdb'.
2009-01-03 13:49:45.02 spid8s Clearing tempdb database.
2009-01-03 13:49:45.66 spid8s Starting up database 'tempdb'.
2009-01-03 13:49:45.68 Server A self-generated certificate was
successfully loaded for encryption.
2009-01-03 13:49:45.68 Server Server local connection provider is ready
to accept connection on [ \\.\pipe\SQLLocal\MSSMLBIZ ].
2009-01-03 13:49:45.68 Server Server named pipe provider is ready to
accept connection on [ \\.\pipe\MSSQL$MSSMLBIZ\sql\query ].
2009-01-03 13:49:45.68 Server Dedicated administrator connection support
was not started because it is not available on this edition of SQL Server..
This is an informational message only. No user action is required.
2009-01-03 13:49:45.68 Server SQL Server is now ready for client
connections. This is an informational message; no user action is required..
2009-01-03 13:49:45.75 spid5s Recovery is complete. This is an
informational message only. No user action is required.
2009-01-03 13:49:45.99 spid11s The Service Broker protocol transport is
disabled or not configured.
2009-01-03 13:49:45.99 spid11s The Database Mirroring protocol transport
is disabled or not configured.
2009-01-03 13:49:45.99 spid11s Service Broker manager has started.
2009-01-03 13:52:55.15 Server Server resumed execution after being idle
155 seconds: user activity awakened the server. This is an informational
message only. No user action is required.
2009-01-03 13:52:56.82 spid51 Starting up database 'MSSmallBusiness'..
2009-01-03 13:52:57.05 spid51 index restored for MSSmallBusiness.
sysowners.
2009-01-03 13:52:57.07 spid51 index restored for MSSmallBusiness.
sysschobjs.
2009-01-03 13:52:57.08 spid51 index restored for MSSmallBusiness.
syscolpars.
2009-01-03 13:52:57.08 spid51 index restored for MSSmallBusiness.
sysnsobjs.
2009-01-03 13:52:57.08 spid51 index restored for MSSmallBusiness.
syscerts.
2009-01-03 13:52:57.10 spid51 index restored for MSSmallBusiness.
sysxprops.
2009-01-03 13:52:57.10 spid51 index restored for MSSmallBusiness.
sysscalartypes.
2009-01-03 13:52:57.10 spid51 index restored for MSSmallBusiness.
sysidxstats.
2009-01-03 13:52:57.11 spid51 index restored for MSSmallBusiness.
sysclsobjs.
2009-01-03 13:52:57.11 spid51 index restored for MSSmallBusiness.
sysremsvcbinds.
2009-01-03 13:52:57.13 spid51 index restored for MSSmallBusiness.sysrts.

2009-01-03 13:52:57.14 spid51 index restored for MSSmallBusiness.
sysasymkeys.
2009-01-03 13:52:57.14 spid51 index restored for MSSmallBusiness.
syssqlguides.
2009-01-03 13:52:57.46 spid51 Starting up database 'MSSmallBusiness'..
2009-01-03 13:52:57.71 spid51 Setting database option AUTO_CLOSE to OFF
for database MSSmallBusiness.
2009-01-03 13:52:57.72 spid51 Setting database option RECOVERY to
RECMODEL_70BACKCOMP for database MSSmallBusiness.
2009-01-03 13:52:57.72 spid51 Setting database option RECOVERY to
RECMODEL_70BACKCOMP for database MSSmallBusiness.
2009-01-03 13:52:57.74 spid51 Setting database option
TORN_PAGE_DETECTION to ON for database MSSmallBusiness.
2009-01-03 13:52:57.74 spid51 Setting database option READ_WRITE to ON
for database MSSmallBusiness.
2009-01-03 13:52:57.74 spid51 Setting database option AUTO_SHRINK toOFF
for database MSSmallBusiness.
2009-01-03 13:52:57.74 spid51 Setting database option ANSI_NULL_DEFAULT
to OFF for database MSSmallBusiness.
2009-01-03 13:52:57.74 spid51 Setting database option RECURSIVE_TRIGGERS
to OFF for database MSSmallBusiness.
2009-01-03 13:52:57.75 spid51 Setting database option ANSI_NULLS to OFF
for database MSSmallBusiness.
2009-01-03 13:52:57.75 spid51 Setting database option
CONCAT_NULL_YIELDS_NULL to OFF for database MSSmallBusiness.
2009-01-03 13:52:57.75 spid51 Setting database option
CURSOR_CLOSE_ON_COMMIT to OFF for database MSSmallBusiness.
2009-01-03 13:52:57.75 spid51 Setting database option CURSOR_DEFAULTto
GLOBAL for database MSSmallBusiness.
2009-01-03 13:52:57.75 spid51 Setting database option QUOTED_IDENTIFIER
to OFF for database MSSmallBusiness.
2009-01-03 13:52:57.75 spid51 Setting database option ANSI_WARNINGS to
OFF for database MSSmallBusiness.
2009-01-03 13:52:57.77 spid51 Setting database option
AUTO_CREATE_STATISTICS to ON for database MSSmallBusiness.
2009-01-03 13:52:57.77 spid51 Setting database option
AUTO_UPDATE_STATISTICS to ON for database MSSmallBusiness.
2009-01-03 13:53:03.26 spid52 Setting database option SINGLE_USER toON
for database MSSmallBusiness.
========================================================================
Click to expand...

I don't see an error in th sql log.

Try turning on logging in BCM, (http://beyng.blogspot.com/2008/03/bcm-
v3-logging.html) and then try to create a db again. Hopefully the log
will have some details about the error.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

database creation unsuccessful 2
Error installing BCM into Outlook 2010 beta, I'm getting Error 2 0
Fail to install BCM 2007 (English) on Windows 7 64 bit (Danish) 3
Help, still can not install BCM 0
It goes through install, but then nothing is in outlook 0
BCM 2007: Cannot open local BCM database, but it is created fine . 5
Office 2003 w/BCM on Vista, with a Bottle of Advil & JD 3
BCM for Outlook 2007 wont install - Fails during SQL install. 0

Top