This is the story of a case which took me some time to diagnose, and which I considered worth sharing, not because it's potential to become a common problem in many customer scenarios, but more because how interesting the troubleshooting steps could be.
Problem Description: Analysis Manager fails with the following error “Unable to connect to the registry on the Server (MyOLAPServer) or you are not a member of OLAP Administrators group”, when trying to connect to a clustered instance and the cluster resource was owned by one of the nodes. Because when it was owned by the other node, Analysis Manager was able to connect to the clustered instance of Analysis Services. Troubleshooting:
Somebody installed Analysis Services in one node, pointing the Data Folder to the shared Disk Resource (E:\...), and putting the binaries in the local disk, default location (C:\Program Files\Microsoft Analysis Services\Bin). Then, on the secondary node, Analysis Services was installed to have the Data Folder pointing to the shared disk again (E:), which is correct, BUT this time the location for the binaries was set to E:\Program Files\Microsoft Analysis Services\Bin. With that situation, the value RootDir under HKLM\SOFTWARE\Microsoft\OLAP Server\CurrentVersion was inconsistent across the two nodes. Primary node was pointing to C:\ drive while secondary pointed to E:\. But it was inconsistent for a short period of time. Why? Once you bring online a clustered resource (Analysis Services) which you have configured to synchronize a certain registry key (HKLM\SOFTWARE\Microsoft\OLAP Server\Server Connection Info), it actually keeps it synchronized.
So, at failover time from primary to secondary node, it overwrote the E:\Program Files\Microsoft Analysis Services\Bin with C:\Program Files\Microsoft Analysis Services\Bin as it was in the primary node.
If you don’t apply Service Pack 4 you don’t experience this issue. But when you apply SP4, it goes to the registry to see what’s the location where it has to deploy the binaries (HKLM\SOFTWARE\Microsoft\OLAP Server\CurrentVersion à RootDir) and it’s wrongly set to C:\Program Files\Microsoft Analysis Services\Bin in both nodes. So, the first node is correctly patched, but the second ends up with a new directory with the SP4 version of the binaries, which is not used by anyone.
Of course, all this was done after having attempted the known and documented reasons like http://support.microsoft.com/kb/812601, http://support.microsoft.com/kb/231951, etc.
End of story!
Hope you enjoyed it.