> Allowing SQL Server to run as ‘LOCAL SYSTEM’ is not recommended.
>
> A better alternative is to use the following steps:
>
> Windows XP
> --------------
> 1.) Show hidden folders by doing the following:
> a.) Open Windows Explorer and select "Tools | Folder Options..." from
> the menu
> b.) Click the "View" tab and make sure that "Show hidden files and
> folders" is selected
> c.) Click "OK"
> 2.) Click on the "My Computer" link in the left-hand navigation pane of
> Windows Explorer
> 3.) Navigate to the following folder, where <user> is your XP user name:
> C:\Documents and Settings\<user>\Local Settings\Application Data\Microsoft
> 4.) Right-click on the "Business Contact Manager" folder and select
> "Properties"
> 5.) Select the "Security" tab
> 6.) If "NETWORK SERVICE" is not listed in the "Group or user names:" list,
> click "Add..."
> 7.) Type "Network Service" and click "Check Names" to ensure the name
> resolves correctly. If it resolves correctly, you'll see the text change to
> all uppercase and underlined.
> 8.) Click "OK"
> 9.) Select "NETWORK SERVICE" from the list of users and check the following
> permissions:
> a.) Read
> b.) Write
>
> Windows Vista
> -----------------
> Similar to above steps, except that the folder path is as follows:
> C:\Users\<USER>\AppData\Local\Microsoft
>
> --
> Visit team blog at
http://blogs.msdn.com/bcm> This posting is provided "AS IS" with no warranties, and confers no rights
>
>
> "DM Nelson" wrote:
>
> > How do you accomplish this? Can I do this if logged into a MS Exchnage Server?
> >
> > "Luther" wrote:
> >
> > > These sound like symptoms of the security changes in sql server etc.
> > >
> > > If changing the sql service user to yourself fixed the problems, then
> > > there's a bug in the beta where the service cannot create the db file
> > > in a user folder.
> > >
> > > Changing user to Local Service will also work because Local Service is
> > > effectively the same as administrator. That does present a security
> > > risk in that if a user can take control of sql, they then have control
> > > of the entire machine.
> > >
> > > LionNet wrote:
> > > > Thanks SO much! It was setup to log in under Network Service, and I actually
> > > > changed it to Local Service (rather than a specific admin user account) and
> > > > that took care of it.
> > > >
> > > > "SusanG" wrote:
> > > >
> > > > > I've had so many install and DB creation issues with Beta 2007, but this
> > > > > might help -I think I had your issue (of the many I've experienced), and I
> > > > > made a note to Self that this worked:
> > > > > Assuming SQL installed OK and service MICROSOFTSMLBIZ instance is running,
> > > > > and you have the BCM Folder structure installed (mine installed by default to
> > > > > C:\Program Files\Microsoft Small Business\Business Contact Manager) -
> > > > >
> > > > > I went into SQL Server and changed the service startup to use the same
> > > > > account as I was logged in as when I installed the Beta (which is in Admin
> > > > > group) then re-started service.
> > > > >
> > > > > Went back to Outlook and attempted to create a DB and poof! it worked!
> > > > > strange, but true!
> > > > >
> > > > > "LionNet" wrote:
> > > > >
> > > > > > I've installed the Office 2007 beta fine and the Outlook/BCM too. Starting
> > > > > > Outlook brings up database creation but every attempt fails. It start up the
> > > > > > process (after selecting the express option) but fails with error "Database
> > > > > > creation unsuccessful." Any suggestions?
> > >
> > >