FarrellFritz
asked on
Cannot start SQL Server Analysis Services Service on new SQL Server
Just built a new SQL Server (MS SQL Server 2014 w/SP1) on a newly built (VMWare) Windows Server 2012R2.
Working fine except the SQL Server Analysis Services service will not start.
I get Event ID: 0 Source: MSSQLServerOLAPService
The service cannot be started: The following system error occurred: Access is denied. File system error: Error occurred during the creation of directory: '\\?\D:'.
This began occurring at the completion of the initial install and I have since added a second instance and the service on that instance is experiencing the same issue.
Googled it and none of the "solutions" have worked (and some make no sense [one individual indicated clearing the event logs fixes this]).
Any help appreciated.
Working fine except the SQL Server Analysis Services service will not start.
I get Event ID: 0 Source: MSSQLServerOLAPService
The service cannot be started: The following system error occurred: Access is denied. File system error: Error occurred during the creation of directory: '\\?\D:'.
This began occurring at the completion of the initial install and I have since added a second instance and the service on that instance is experiencing the same issue.
Googled it and none of the "solutions" have worked (and some make no sense [one individual indicated clearing the event logs fixes this]).
Any help appreciated.
it requires another drive d:
ASKER
Already has a D drive and is configured identically to the server it is replacing. Cant have two D drives.
Am I misunderstanding your answer?
Am I misunderstanding your answer?
It says "Access Denied" so I guess that the SSAS service account doesn't have permissions on the folder and subfolders.
ASKER
I think you / were on the right track (permissions issue), but I had already given the MSSQLServerOLAPService account FULL CONTROL rights to the drive including subfolders. Is there possibly another service account involved?
Thanks!
Thanks!
Who is the user that is configured as MSSQLServerOLAPService service account?
ASKER
It is currently set to our domain administrator account
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Took 5 days of research but resolved the issue!
Looks to me like the SQL 2016 installer is flawed.
In previous versions you could (ahead of time) create the folders that you intended to use for OLAP (i.e. D:\Data\OLAP and E:\Data\OLAP for example) and specify these during the SQL installation process.
In 2016 it seems the installer 'forgets' to grant the service account for A/S (Typically NT Service\MSSQLServerOLAPSer vice) appropriate permissions.
It seems just the data folders are affected, logs is okay.
Manually granting full rights to D:\Data AND D:\Data\OLAP will fix the issue. the locale thing in event logs is a bit of a distraction I agree. I've come across this same issue twice in 2 days - the 2nd time I fixed it a lot quicker and am confident I did nothing wrong in both case...
In previous versions you could (ahead of time) create the folders that you intended to use for OLAP (i.e. D:\Data\OLAP and E:\Data\OLAP for example) and specify these during the SQL installation process.
In 2016 it seems the installer 'forgets' to grant the service account for A/S (Typically NT Service\MSSQLServerOLAPSer
It seems just the data folders are affected, logs is okay.
Manually granting full rights to D:\Data AND D:\Data\OLAP will fix the issue. the locale thing in event logs is a bit of a distraction I agree. I've come across this same issue twice in 2 days - the 2nd time I fixed it a lot quicker and am confident I did nothing wrong in both case...
Farrell all you did by the look is 'work around' the issue by moving the default data & log paths.
An extra note, even running the configuration manager and changing the A/S service user still did not work for me - i.e. it did not grant the correct rights even to the new (changed) service user...
An extra note, even running the configuration manager and changing the A/S service user still did not work for me - i.e. it did not grant the correct rights even to the new (changed) service user...