Cube processing problem

Hi, can someone help me, please?
I have a problem with a cube process. I have an SQL SERVER 2014 installed with default instance. When I try to deploy my project I get
an error "The name provided is not a properly formed account name". In "Impersonation information" I mentioned "Use a specific Windows user name and password" How can I fix this problem?

see
https://msdn.microsoft.com/en-us/library/ms187597.aspx
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Similar Messages

SCSM2012: Cube processing failing on two cubes - ConfigItemDimKey not found

Hi
Two of our cubes (SystemCenterSoftwareUpdateCube and SystemCenterPowerManagementCube) has started to fail processing lately. In ServiceManager they the error is just "failed", but in SSAS there is a lot of errors.
Both cubes fails with the following error when SSAS processing them:
"Errors in the OLAP storage engine: The attribute key cannot be found when processing: Table: 'ConfigItemDim', Column: 'ConfigItemDimKey', Value: '7200'. The attribute is 'ConfigItemDimKey'. Errors in the OLAP storage engine: The attribute key was converted
to an unknown member because the attribute key was not found. Attribute ConfigItemDimKey of Dimension: ConfigItemDim from Database: DWASDataBase, Cube: SystemCenterSoftwareUpdateCube, Measure Group: ConfigItemDim, Partition: ConfigItemDim, Record: 7201. Errors
in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation. Errors in the OLAP storage engine: An error occurred while processing the 'ConfigItemDim'
partition of the 'ConfigItemDim' measure group for the 'SystemCenterSoftwareUpdateCube' cube from the DWASDataBase database."
=> My question: is it possible to recreate this ConfigItemDimKey manually (and how), or delete those cube and create them from scratch (back to oob status) ?
Thanks.
/Peter

Hi Peter,
We recently had similar issues with our ChangeAndActivityManagementCube. After a conversation with a Microsoft supporter I was able to work around that problem and so far it hasn't appeared yet.
As you can read from the error message the issues appears when Analysis Services tries to process the ConfigItemDim measure group. During the processing it's looking up the corresponding dimension for attribute key. Now when the Measure Group
is getting processed before the corresponding dimension is processed, it's possible that the attribute key doesn't exist in the dimension table yet and then this error occurs.
What you have to do is the following:
1. Process the dimensions manually using PowerShell and the following code (change the server address and SQL instance and execute it on the AS server):
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.AnalysisServices") > $NULL
$Server = New-Object Microsoft.AnalysisServices.Server
$Server.Connect("YOUR_DW_AS_SERVER\DW_AS_INSTANCE")
$Databases = $Server.Databases
$DWASDB = $Databases["DWASDatabase"]
$Dimensions = New-Object Microsoft.AnalysisServices.Dimension
$Dimensions = $DWASDB.Dimensions
foreach ($Dimension in $Dimensions){$Dimension.Process("ProcessFull")}
2. Then process the affected measure group manually using the SQL Management Studio. You have to connect to the AS Engine, expand the DWASDatabase DB -> Cubes -> Measure Groups -> right click the affected Measure Group and select process ->
leave the standard settings in the next window and press ok.
You have to repeated step 2 for each Masure Group mentioned in the event logs.
3. Now process the entire cube by right clicking the cube in SQL Management Studio and select Process. Now the processing should finish successfully.
Since then the data warehouse cube processing jobs were working fine again too in our installation.
Hope this helps.
Cheers
Alex

Dimensions and Cubes Process OK / database 'Process Full' fails

Hello,
I am having trouble processing SSAS database (SQL 2008R2).
Within BIDS environment I can process all dimensions and two cubes - no problem. But when I try to process the database (Process Full – Sequential/ All in one transaction), I keep getting errors about one specific dimension (however the very same dimension
is processed separately just fine).
Any ideas why this would happen?
Thanks,
Lana

Thanks so much for all your replies! Your help is greatly appreciated
J
Here is the error message I am getting (it is the same for bunch of other attributes of the same dimension called
Item):
Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Item', Name of 'Item' was being processed.
Errors in the OLAP storage engine: An error occurred while the 'Product Group' attribute of the 'Item' dimension from the 'InvCube' database was being processed.
OLE DB error: OLE DB or ODBC error: Operation canceled; HY008.
Errors in the OLAP storage engine: A duplicate attribute key has been found when processing: Table: 'dbo_Item', Column: 'Colour', Value: ''. The attribute is 'Colour'.
Keep in mind that the Key for this dimension is called ItemID and there are no duplicates (I checked). Before processing the cube, I have dozens of procedures (within SSIS package that brings the data into DW) that are checking if all the
keys (FK columns on Fact table) exist within dim tables (PK columns). I also do not allow NULLs or blanks for the dim keys within Fact tables, I replace them with
special “DimName-000” Keys that, again, exist within dim tables.
What I am trying to figure out… why I can process Item dimension just fine on its own (I also process all the other dimensions OK), after that I can process both cubes that are using this (and other) dimension(s) … and I can browse the cubes, getting breakdown
by Item / Colour / Product Group, etc... So, everything seems to work perfectly. However, when I try to process the whole database (with all previously processed dimensions and both cubes - there are only two cubes for now, to make is simple), the process
fails, giving me an error about duplicate attribute key for this specific Item dimension.
Any thoughts?
Thanks again!

SSAS Cube deployment problem

Hi!
I have a problem with a cube process. I have an SQL SERVER 2014 installed with default instance. When I try to deploy my project I get an error "The name provided is not a properly formed account name". How can I fix this problem?
Thanks in advance.

Hi,
SQL Azure database PAAS doesn't support SSAS. Please post your questions regarding SSAS to following MSDN Forum so someone can assist.
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?forum=sqlanalysisservices
Regards,
Mukesh

Cube processing Error

Hi,
   I am using SSAS 2008 R2. We have a job scheduled at 3:00 AM. But today we got this error during cube processing. Please help me to solve this ASAP
Error: 2015-01-07 08:26:49.08     Code: 0xC11F0006
Source: Analysis Services Processing Task 1 Analysis Services Execute DDL Task
Description: Errors in the OLAP storage engine:
The process operation ended because the number of errors encountered during processing reached the defined
limit of allowable errors for the operation.

Hi Anu,
According to your description, you get errors when executing a cube processing task. Right?
The error you posted just tell us there are too many errors during processing. Please pay attention to the errors around this error message. Those error will tell where the root issue happens. We suggest you use SQL Profiler to monitor SSAS. See:
Use SQL Server Profiler to Monitor Analysis Services. Please share those detail error message to us. Also refer to some similar threads below, some advices in the link may help you:
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/61f117bd-b6ac-493a-bbd5-3b912dbe05f0/cube-processing-issue
https://social.msdn.microsoft.com/forums/sqlserver/en-US/006c849c-86e3-454a-8f27-429fadd76273/cube-processing-job-failed
If you have any question, please feel free to ask.
Simon Hou
TechNet Community Support

Cube processing failing

I am experiencing a strange issue . One of our cubes processing is successful when I do it via BIDS or management studio. But when I process the cube via XMLA it gives strange errors, this
was working fine earlier.
<return
xmlns="urn:schemas-microsoft-com:xml-analysis">
<results
xmlns="http://schemas.microsoft.com/analysisservices/2003/xmla-multipleresults">
    <root
xmlns="urn:schemas-microsoft-com:xml-analysis:empty">
      <Exception
xmlns="urn:schemas-microsoft-com:xml-analysis:exception"
/>
      <Messages
xmlns="urn:schemas-microsoft-com:xml-analysis:exception">
        <Error
ErrorCode="3238002695"
Description="Internal error: The operation terminated unsuccessfully."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Warning
WarningCode="1092550657"
Description="Errors in the OLAP storage engine: The attribute key cannot be found when processing: Table: 'DBID_LGCL_DATABASE_SYSTEM_MAP', Column: 'LGCL_DATABASE_KEY',
Value: '671991'. The attribute is 'LGCL DATABASE KEY'."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Warning
WarningCode="2166292482"
Description="Errors in the OLAP storage engine: The attribute key was converted to an unknown member because the attribute key was not found. Attribute LGCL
DATABASE KEY of Dimension: Logical Database from Database: Column_Analytics_QA, Cube: COLUMN_USAGE, Measure Group: LGCL DATABASE SYSTEM MAP, Partition: LGCL DATABASE SYSTEM MAP, Record: 94986."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034310"
Description="Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit
of allowable errors for the operation."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'LGCL DATABASE SYSTEM MAP' partition of the 'LGCL DATABASE SYSTEM MAP'
measure group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034310"
Description="Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit
of allowable errors for the operation."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3239837702"
Description="Server: The current operation was cancelled because another operation in the transaction failed."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_8474' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_8714' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_9102' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034310"
Description="Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit
of allowable errors for the operation."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_8186' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_8282' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_8530' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_9050' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_9002' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_9146' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_8770' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_8642' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_9058' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_8322' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_8658' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_8410' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'BRDGE PHYS LGCL' partition of the 'BRDGE PHYS LGCL' measure group for
the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034310"
Description="Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit
of allowable errors for the operation."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
Any idea what might be the reason?

Please refer another question with the same issue
here
Below is my answer from that post:
From my experience, this may be because of data loading in dimensions or fact while you are processing your cube or (in worst case) the issue is not related to attribute keys at all. Because, if you re process the cube it will process successfully on the same
set of records.
First identify the processing
option for your SSAS cube.
You can use SSIS "Analysis Service processing task" to process dimensions and fact separately.
or
You can process object in batches (Batch
Processing). Using batch processing you can select the objects to be processed and control the processing order.
Also, a batch can run as a series of stand-alone jobs or as a transaction in which the failure of one process causes a rollback of the complete batch.
To aggregate:
Ensure that you are not loading data into fact and dimension while processing cube.
Don't write queries for dirty read
Remember when you process a dimension on ProcessFull or ProcessUpdate; cube will move to unprocessed state and it can
not be queried.

Regarding the tracking the live progress of the cube processing.

Hello,
Good Morning. As we are having multiple cube applicatons as part of our project, there are multiple cubes for which we need to evaluate the completion time for the cube processing.
By referencing one cube, the cube processing is taking one hour one day and some other day, It is taking an hour for completion. Beacuse of this reason, we could not be able to asses the time for completion of cube processing.
Is there any chance to track the live status of the cube processing?. Which means, the expected time for completion? How many measure group processing are completed and how many left?
Please provide your inputs on this.
Thanks in advance.
Regards,
Pradeep.

Hi Kumar,
According to your description, you want to monitor the progress of cube processing. Right?
In Analysis Services, there are several tools can help us monitor the processing performance, like SQL Profiler, AS Trace, Performance Monitor, etc. We can also use XMLA command or DMV to get the information. Please see:
Monitoring processing performance
Monitoring and Tuning Analysis Services with SQL Profiler
However, if you want to get the exact live data of the cube processing, Olaf's script can be an effective solution to get the current processing status for some measures or dimensions. But some information still can't be traced, like expected time for completion,
etc. So for your requirement, it can't be fully achieved.
If you have any question, please feel free to ask.
Simon Hou
TechNet Community Support

Is it mandatory to have OLAP cube processing feature in SCSM ??

Hi All,
We have SCSM 2012 R2 environment with SCSM DW component installed
can we disable the cube processing , if we are not using it ??
or by disabling it will it affect the reporting functionality
Thanks,
Kalai

Hi,
OLAP (Online Analytical Processing) cubes are a new feature in SCSM 2012 that leverage the existing Data Warehouse infrastructure to provide self-service Business Intelligence capabilities to the end user.
To get more details about OLAP cubes, you may go through the article below:
OLAP Cubes in the SCSM Data Warehouse: Introduction
http://blogs.technet.com/b/servicemanager/archive/2012/02/03/olap-cubes-in-the-scsm-data-warehouse-introduction.aspx
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Regardnig the Cube Processing.

Hello Team,
When I tried to process the cube, am getting the folowing window, which shows the cube processing whch is in progress.
My Questions are
. What is the number which we can see as 9 of 13?. Why It is different for each partittion of one measure group?
. For few partitions, the Inprogress one's which we are getting as 9 or 13/12 or 13/7/200000?. What It doest meant for?

Hi,
This is the way that SSAS engine displays that Indexes are getting created.
Regards,
Venkata Koppula

Cube Processing - process Dimension before Measure Groups? How to?

Hi guys.
I noticed that when you choose "Process Cube", Measure groups are processed before Dimensions. Recently I ran into an issue caused by change in data that made the Process Cube job fail, - until I manually processed all Dimensions and then run the
"Process Cube" job again.
- Is there any way to configure it to process Dimensions before Measure Groups???
Cheers!

We use SSIS to automate the cube processing using XMLA scripts. We have a control table where we maintain the list of dimensions and measure group partitions which will be iterated upon and processed by SSIS. It will also log audit information like when
it was started, when it got ended and the process result.
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

AVCD on MAC: are there any processing problems using say, VLC?

AVCD on MAC: are there any processing problems using say, VLC?

We've actually found that the Server 10.6.3 DVD does an amazingly smooth job of upgrading 10.5.8. We've been upgrading our production servers and nothing has gone wrong yet. Snow Leopard employs an archive and install method of upgrading which results in an install which is very close to a clean install. So it's been very convenient for us because our servers are used as Windows PDCs and it's a pain in the *** to have to re-join all PCs to the domain if we start from scratch.

SQL Server Profiler does not capture cube processing queries against the relational database

Hello, experts,
This my first attempt to use SQL Server Profiler to find out why my cube processing is so slow. Here is what I did:
My cube sources its data from a SQL Server database. While the cube processing is going, I launched the profiler connecting to the database engine (note: not the Analysis Services). I choose the "Tuning" template and started the trace. However,
I do not see any query activities (such as, SELECT DISTINCT ...) in the profiler trace window.
Did I do something wrong, or do I have the wrong expectation?
Thank you much in advance.

Hi QQFA,
Agree with Olaf.
Please make sure that you choose the appropriate events to monitor the cube processing queries when using SQL Server Profiler.
And I recommend you review the following links to get more information about tuning Analysis Services with SQL Profiler.
Monitoring and Tuning Analysis Services with SQL Profiler:
http://www.informit.com/articles/article.aspx?p=1745747
Analysis Services Trace Events:
http://msdn.microsoft.com/en-us/library/ms174867.aspx
Thanks,
Lydia Zhang

Improve cube process time

Hi,
I am processing cube with process full. its taking around 15 mins. I planned to improve this by adding indexes to the database. I used SQL Trace while processing & later used the result to the database tuning advisor to get recommendations. I got the
recommendations & i have included those changes to the Database & then processed the cube but there is no improvement. I even tried to get the expensive queries from the trace & run in SSMS with Query execution plan but I am not able to figure
out. Please help.
Thanks
sush

Hi susheel1347,
According to your description, you want to improve the cube processing. Right?
In Analysis Services, cube processing is performed in Analysis Services by executing Analysis Services-generated SQL statements against the underlying relational database. Here we have some advices on improving the cube processing:
Use integer keys if at all possible
Use query binding to optimize processing
Partition measure groups if you have a lot of data
Use ProcessData and ProcessIndex instead of ProcessFull
For more information, please refer to links below:
SQL Server Best Practices Article
Improving cube processing time
If you have any question, please feel free to ask.
Simon Hou
TechNet Community Support

Cube process stuck - finished building aggregations and indexes for the partition

Hi friends
My cube processing stuck up at "Finished building aggregations and indexes for the partition". How can I troubleshoot this.
Appreciate your help.
Royal Thomas

Royal,
Your question is discussed
here and
here also. May be it will help you out.
Best regards.

Cube processing hangs at same query

Hi all,
I'm currently working on a R2 cube. The R1 cube processes perfectly, but the R2 keeps hanging at the same measure group. The weird thing is, nothing has been changed to the DSV. The same fact table is used with 12 mil records, and there is no cross project
relation.
I already did sp_updatestats but nothing worked. Anyone has suggestions? I'm processing parallel

Hi Nat-MS,
I added 3 attributes to the dimensions. The fact table only has 11 mil records and keeps hanging at the same query.
I tried the following things:
-Run query in SSMS, it works.
-No index suggestions, no heavy load on clustered/non clustered indexes
-Tried sequential processing instead of parallel.
-Renamed partitions
-Updated count of my partitions
-Deleted the cube and remade
-Removed relationships in dimension usage and remade them
I'm completely out of ideas here. I will try using the profiler!

Cube processing problem

Similar Messages

Maybe you are looking for