SSAS 2012 in a hardened windows 2012 environment

All the specific details are not exactly clear. But if you harden your windows 2012 server in such a way that the Users and Everyone local Windows groups no longer have the User Right : Bypass traverse checking(SeChangeNotifyPrivilege) Then it can be that you might get one or both of the following problems: a) If you…

0

"Analysis Services MOLAP Performance Guide for SQL Server 2012 and 2014" has been released

Thanks to the efforts of our US support colleagues Karan Gulati and Jon Burchel we now have an updated version of the SSAS performance guide available.  The “Analysis Services MOLAP Performance Guide for SQL Server 2012 and 2014” document can be downloaded from MSDN via the following link: http://msdn.microsoft.com/en-us/library/dn749781.aspx As the name suggests it contains advice…


How to connect to clustered Analysis Services instances

While clustered SSAS instances have been around for a while, we noted that there is still some confusion about the recommended way for connecting to clustered instances and our supportability policy. Let’s start with the hopefully well known behavior for non-clustered SSAS instances. Stand-alone Instances All default SSAS instances will listen on port tcp 2383….


you may obtain a .dstore related file system error when processing TFS cube

Recently we have seen a number of issues where TFS cube processing failed with a file system error. The error is always referencing the decode store (.dstore) of the primary key attribute (FileSK) of the “File” dimension. The error message typically looks similar to this: Exception Message: File system error: The following file is corrupted:…


SQL Server 2012 SP1 CU3 release fixes frequent SP1 issues

We normally don’t comment much on Cumulative Update releases since the best source for this type of information is the blog of the SQL server release services team : http://blogs.msdn.com/b/sqlreleaseservices/ . However, adding to the SP1 issue that was described in previous blog by Guillaume Fourrat we observed two further SSAS related problems that affected several customers….


1 hour timeout for data refreshes in Powerpivot for Sharepoint

In the previous blog post I explained that we have a 1 hour timeout in Powerpivot for Excel due to the inherited default SSAS instance properties. Now you might argue that this timeout should not pose a problem in the Powerpivot for Sharepoint environment. After all we are using a standalone SSAS instance in Sharepoint mode….


1 hour timeout for data imports in Powerpivot for Excel

This article describes an issue you may face when your data import in Powerpivot for Excel takes longer than 1 hour. Typically you should not run into this type of issue because Powerpivot for Excel was designed as an interactive tool with moderate amounts of data in mind. 1 hour should give you ample time to import all…


SSAS project deployment fails with error "Internal error: Invalid enumeration value. Please call customer support."

Recently I have seen this error popping up more frequently. It can occur when you modify a SSAS project in Visual Studio 2008 (or BIDS 2008) and try to deploy it against an existing SSAS 2008 R2 database. The full error message will usually also mention a “storagemode” element and a metadata error for instantiating…


Where did my process progress events go?

Today’s post is about an elusive issue that was keeping us busy for a while. When you process SSAS objects (database, cube, partition, dimension etc.) manually in SQL Server Management Studio (SSMS) or Business Intelligence Development Studio (BIDS), then you get a nice progress report window that shows you all processing stages:  However, sometimes you do…


Issues with using msolap.x provider name in linked server definition

During a recent investigation I realised that a number of people are using MSOLAP.x as the provider name for a linked server e.g. MSOLAP.4 when creating a linked server… e.g. EXEC master.dbo.sp_addlinkedserver @server = N’lsname’, @srvproduct=N’msolap’, @provider=N’MSOLAP.4′, @datasrc=N’servera\inst’, @catalog=N’SSASDBName’ /* For security reasons the linked server remote logins password is changed with ######## */ EXEC…

0