Answered by:
New install of CRM 2013 on SQL 2012

Question
-
I am getting the following error when I try to install CRM 2013. I have verified all the permissions are correct and I can navigate to the data folder using the install account. What could be missing?
09:49:12| Info| DatabaseFilesValidator linking to help topic: html/7fdded02-0c2a-4487-a6f0-62682b06b89e.htm
09:49:12| Error| Check CrmDatabaseFilesValidator : Failure: Unable to open the physical file "<a href="file://\\\<instancedbsfolder>\MSSQL11.SQLDEV01\MSSQL\Data\DefaultCRM_MSCRM.mdf">\\<server>\<instancedbsfolder>\MSSQL11.SQLDEV01\MSSQL\Data\DefaultCRM_MSCRM.mdf". Operating system error 5: "5(Access is denied.)".Wednesday, June 24, 2015 3:04 PM
Answers
-
This one we took to Microsoft. By default the install package will try to verify permissions from the very top level of the path to the actual store for the databases. Even thought the service account had the proper permissions where the data was going to be stored because permissions could not be set at the very top share level this install would fail. We had to install to a local drive and move the databases to the CIFS share after.
Microsoft technician said that he will be creating an internal knowledge base for this and they are looking at changing the install media to allow for this situation or to allow an override of this check.
- Marked as answer by JenniferNHS Friday, July 10, 2015 9:38 PM
Friday, July 10, 2015 9:38 PM
All replies
-
From the paths in the error, it looks like this is when the .mdf file is copied to a location on the SQL Server - does <server> refer to the SQL Server, or the Crm Server ?
The install account will need read-write permission on the default directory on SQL Server - is that what you refer to as 'the data folder' ?
Microsoft CRM MVP - http://mscrmuk.blogspot.com/ http://www.excitation.co.uk
Wednesday, June 24, 2015 4:01 PMModerator -
Server refers to the sql server. Correct data folder is the default location for the sql instance.Wednesday, June 24, 2015 4:02 PM
-
This one we took to Microsoft. By default the install package will try to verify permissions from the very top level of the path to the actual store for the databases. Even thought the service account had the proper permissions where the data was going to be stored because permissions could not be set at the very top share level this install would fail. We had to install to a local drive and move the databases to the CIFS share after.
Microsoft technician said that he will be creating an internal knowledge base for this and they are looking at changing the install media to allow for this situation or to allow an override of this check.
- Marked as answer by JenniferNHS Friday, July 10, 2015 9:38 PM
Friday, July 10, 2015 9:38 PM