Chris Swinney
New Member
- Outlook version
- Outlook 2016 64 bit
- Email Account
- Exchange Server
Hi All,
I know this thread is over a year old since the last post, but I have been reading about utilising BCM for Outlook 2013 (and 2010) on SQL 2012 both here an elsewhere on the Internet (with lots of additional comments by Diane and others). We utilise a SQL Express store for some other data and it would be ideal if we could simple create a new instance on this SQL store to BCM data. Of course, the store is running SQL 2012. I would rather have bother the remote and local SQL instance running at the same version so I thought I would add my experiences.
I thought that I would install a local copy of SQL Express 2012 (64 bit) to see what would happen. This was on a new OS install (Windows 7 64 bit) with a fresh copy of Office 2013 (32 bit) and no previous SQL installed (as the intention is to create a base image I can apply to multiple laptops). The Default installation (even if you create an instance name of 'MSSMLBIZ') did NOT work. The reason being that the account that SQL instance starts under by default is an NT SERVICE account called 'MSSQL$MSSMLBIZ'. Whilst a user profile is created in the 'Users' directory for 'MSSQL$MSSMLBIZ', I could not find or add this 'user' to the sercurity properties of the folder, as such when you go to create a database you see an error "unable to create database".
Following the documentation here (Troubleshoot database operations in Business Contact Manager) it seems as though you then need to add read and write access for the account that starts the SQL 'MSSMLBIZ' instance to the 'C:\Users\[username]\AppData\Local\Microsoft\Business Contact Manager' folder but I couldn't add 'NT Service\MSSQL$MSSMLBIZ' to the security properties of the folder (I did NOT try to add the 'SERVICE' account to the security properties of this folder, so I'm not sure if adding this would have worked). Anyhow, I then uninstalled SQL 2012 instance, removed the instance folders and started again but this time using the advice as shown above from 'Forum Admin' and where I was asked during the installation which account I wanted to run the SQL instance, I chose this time 'Network Service'. I then added the 'Network Service' to the security properties of the above folder and hey presto, a database could be created and manipulated without issue.
Now the tricky part, as I am trying to create a base image for our laptops which we can then apply to re-purpose them as required, so the user that may log into the machine will not have the C:\Users\[username]\AppData\Local\Microsoft\Business Contact Manager' setup. I think I should be able to add this folder to the Default Profile with the correct permissions in place, so that when a user logs in for the first time, they will be able to create a database as required. Yes, they will connect to a remote database, but this will have an offline store and of course, it is useful to have the sample database (or test database) setup as well.
Of course, SQL 2014 is now out and I assume that you will require a similar work around.
Cheers
Chris
I know this thread is over a year old since the last post, but I have been reading about utilising BCM for Outlook 2013 (and 2010) on SQL 2012 both here an elsewhere on the Internet (with lots of additional comments by Diane and others). We utilise a SQL Express store for some other data and it would be ideal if we could simple create a new instance on this SQL store to BCM data. Of course, the store is running SQL 2012. I would rather have bother the remote and local SQL instance running at the same version so I thought I would add my experiences.
I thought that I would install a local copy of SQL Express 2012 (64 bit) to see what would happen. This was on a new OS install (Windows 7 64 bit) with a fresh copy of Office 2013 (32 bit) and no previous SQL installed (as the intention is to create a base image I can apply to multiple laptops). The Default installation (even if you create an instance name of 'MSSMLBIZ') did NOT work. The reason being that the account that SQL instance starts under by default is an NT SERVICE account called 'MSSQL$MSSMLBIZ'. Whilst a user profile is created in the 'Users' directory for 'MSSQL$MSSMLBIZ', I could not find or add this 'user' to the sercurity properties of the folder, as such when you go to create a database you see an error "unable to create database".
Following the documentation here (Troubleshoot database operations in Business Contact Manager) it seems as though you then need to add read and write access for the account that starts the SQL 'MSSMLBIZ' instance to the 'C:\Users\[username]\AppData\Local\Microsoft\Business Contact Manager' folder but I couldn't add 'NT Service\MSSQL$MSSMLBIZ' to the security properties of the folder (I did NOT try to add the 'SERVICE' account to the security properties of this folder, so I'm not sure if adding this would have worked). Anyhow, I then uninstalled SQL 2012 instance, removed the instance folders and started again but this time using the advice as shown above from 'Forum Admin' and where I was asked during the installation which account I wanted to run the SQL instance, I chose this time 'Network Service'. I then added the 'Network Service' to the security properties of the above folder and hey presto, a database could be created and manipulated without issue.
Now the tricky part, as I am trying to create a base image for our laptops which we can then apply to re-purpose them as required, so the user that may log into the machine will not have the C:\Users\[username]\AppData\Local\Microsoft\Business Contact Manager' setup. I think I should be able to add this folder to the Default Profile with the correct permissions in place, so that when a user logs in for the first time, they will be able to create a database as required. Yes, they will connect to a remote database, but this will have an offline store and of course, it is useful to have the sample database (or test database) setup as well.
Of course, SQL 2014 is now out and I assume that you will require a similar work around.
Cheers
Chris
