June 15, 2016 at 2:24 pm
I had to make a change to the Clustered Disk. Basically we put to much disk on the Cluster and I needed to move everything to the new disk. :hehe:
I stopped all of the Services, added the Clustered Disks and Dependencies, moved the files and folders, re-lettered the drives to make sure that they matched (the ideas is that SQL Server would be none the wiser), and then started up my Services.
SQL Server services had zero problems. Everything came up and all of the Databases that were there were online. However, SSAS not so much. It just fails to start.
So, I know that I moved some of the files on disks, but the drive letters are the same and when I go to look for the configuration files (the Program Files directory and System Databases never moved) it all looks right. However, Windows is not really providing me with much in the way of information on why its not starting. Just a generic "1067" message.
I have read that this can be fixed by re-installing, but this is a Cluster. Not sure if that is a solution in this case.
Any help is appreciated.
Regards, Irish
June 15, 2016 at 3:53 pm
For anyone who comes along later, I wanted to let you know that I was able to fix it.
Here's what I had to do.
1) I needed to add the Clustered Disk Dependencies.
Oh, I remembered to do it for SQL Server on the Cluster, but I did not do it for the SQL Server Analytics.
2) I had to give the Windows Account running the SQL Server Service rights to the drives that I just added.
Rookie mistake. Honestly, when you install a Cluster from the ground up this is all done for you. It would be super easy to forge this!
I figured this all out after having to move another instance and then it dawned on me that you have to be able to see the drives to use them.
Hope this helps the next guy/gal!
Regards, Irish
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply