Errors in the OLAP storage engine
Job is scheduled to process a cube. The job failed with the below errors:
Description: Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Dim ID', Name of 'Dim ID' was being processed.
End Error Error: 2015-01-02 02:17:52.73
Code: 0xC11F000D
Source: Process Dimensions Analysis Services Execute DDL Task
Description: Errors in the OLAP storage engine: An error occurred while the 'HID' attribute of the 'Dim ID' dimension from the database was being processed.
End Error Error: 2015-01-02 02:17:52.75
Code: 0xC1060000
Source: Process Dimensions Analysis Services Execute DDL Task
Description: OLE DB error: OLE DB or ODBC error: Operation canceled; HY008.
End Error Error: 2015-01-02 02:17:52.76
Code: 0xC11F000C
Source: Process Dimensions Analysis Services Execute DDL Task
Description: Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Dim Nme', Name of 'Dim Nme' was being processed.
End Error Error: 2015-01-02 02:17:52.76
Code: 0xC11F000D
Source: Process Dimensions Analysis Services Execute DDL Task
Description: Errors in the OLAP storage engine: An error occurred while the 'NME' attribute of the 'Dim Nme' dimension from the database was being processed.
End Error Error: 2015-01-02 02:17:52.78
Code: 0xC1060000
Source: Process Dimensions Analysis Services Execute DDL Task
Description: OLE DB error: OLE DB or ODBC error: Operation canceled; HY008.
End Error Error: 2015-01-02 02:17:52.78
Code: 0xC11F000C
Source: Process Dimensions Analysis Services Execute DDL Task
Description: Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Dim Ky', Name of 'Dim Ky' was being processed.
End Error Error: 2015-01-02 02:17:52.79
Code: 0xC11F000D
Source: Process Dimensions Analysis Services Execute DDL Task Description: Errors in the OLAP storage engine: An error occurred while the 'KY' attribute of the 'Dim Ky' dimension from the database was being processed.
End Error Error: 2015-01-02 02:17:52.81
Code: 0xC11F000D
Source: Process Dimensions Analysis Services Execute DDL Task
Description: Errors in the OLAP storage engine: An error occurred while the 'Id' attribute of the 'Dim Txt' dimension from the database was being processed.
End Error Error: 2015-01-02 02:17:52.81
Code: 0xC11F000D
Source: Process Dimensions Analysis Services Execute DDL Task
Description: Errors in the OLAP storage engine: An error occurred while the 'Id' attribute of the 'VWIprve' dimension from the database was being processed.
End Error DTExec: The package execution returned DTSER_FAILURE (1).
Started: 1:00:22 AM
Finished: 2:18:02 AM
Elapsed: 4660.47 seconds. The package execution failed. The step failed.
Please help!!!!!!
Hi,
According to your description, you create a SSIS package to process SSAS cube, the problem is that you are experiencing the error "Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Dim Nme', Name of 'Dim Nme'
was being processed“ while executing the job, right?
Based on my research, the issue can be caused by that you haven't set a primary key in your dimension table. Here is a blog that describe this issue, please see:
http://blogs.microsoft.co.il/barbaro/2014/03/03/errors-in-the-olap-storage-engine-processing-a-large-dimension/
Regards
Charlie Liao
TechNet Community Support
Similar Messages
-
Hi
We are using SSAS 2008 r2 and have a cube on our data warehouse, this has been running fine for quite a while now.
However it failed yesterday with the error message:
Errors in the OLAP storage engine: The attribute key cannot be found when processing: Table:
'Performance_Fact', Column: 'accountexternalId', Value: '9474'. The attribute is 'External Id'."
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."
An error occurred while processing the '2011' partition of the 'Fact' measure group for the 'DB' cube from the DB database.
Please can someone help me to resolve the error, I don't understand what it means.
ThanksHello,
The error means that you have a key in the fact data which don't exist in the related dimension. Ensure that the dimension is also processed so that it contains all used keys.
Olaf Helper
[ Blog] [ Xing] [ MVP] -
Errors in the OLAP storage engine: An error occurred while processing the indexes for the partition of the measure group of the cube from the database.
I have dropped and recreated a fact table to refresh the data as the table is having identity columns. So not able to directly insert data. After that cube is throwing above error.
Please suggest.Hi Md,
It hard to analyse the issue base on the limited information, Are there any error message on the log? Under C:\Program Files\Microsoft SQL Server\MSAS11.\OLAP\Log (this could be different for your server), there are 3 log files that are generated:
msmdrrv.log
FlightRecorderCurrent.trc
FightRecorderBack.trc
The msmdrrv.log simply points to the other two logs. There might be some detail information for this error. Please provide us the detail information about it, so that we can make further analysis.
Regards,
Charlie Liao
TechNet Community Support -
<Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'vFactUTC_201304_INCR_UPDATE_TEMP_qtfcw_' partition of the 'vFact' measure
group for the 'vAMGenericUTC' cube from the AC_OLAP database."
Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
Any idea abt this error
Putting details error ..
<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="3238395904"
Description="OLE DB error: OLE DB or ODBC error: Cannot execute the query
"SELECT
"Tbl1002"."idUTCDateTime"
"Col1145","Tbl1002"."idLocalDateTime"
"Col1146","Tbl1002"."idDateKey"
"Col1147","Tbl1002"."idUTCDateKey"
"Col1148","Tbl1002"."idMinuteKey"
"Col1149","Tbl1002"."idUTCMinuteKey"
"Col1150","Tbl1002"."idInstance"
"Col1151","Tbl1002"."idMetricKey"
"Col1152","Tbl1002"."idKSKey"
"Col1153","Tbl1002"."idMaintenanceKey"
"Col1154","Tbl1002"."MetricMin"
"Col1155","Tbl1002"."MetricMax"
"Col1156","Tbl1002"."MetricCount"
"Col1157","Tbl1002"."MetricSum"
"Col1158","Tbl1002"."MetricLog"
"Col1159","Tbl1002"."MetricSumOfSquares"
"Col1160","Tbl1002"."MetricSumOfLogSquares"
"Col1161","Tbl1002"."idTextData"
"Col1162","Tbl1002"."idLoad"
"Col1143",CONVERT(smalldatetime,"Tbl1002"."idDateKey",0)
"Expr1004",CONVERT(smallint,"Tbl1002"."idMinuteKey",0)
"Expr1006",(1)
"Expr1008" FROM
"DM_VSQL51_SOPM33_QDB"."dbo"."vData"
"Tbl1002" WHERE
"Tbl1002"."idLocalDateTime">=(1362096000)
AND "Tbl1002"."idLocalDateTime"<=(1364774399)
AND "Tbl1002"."idLoad">=(9243)
AND "Tbl1002"."idLoad"<=(9304)"
against OLE DB provider "SQLNCLI10" for linked server
"DM_DS_SOPM33_QDB". ; 42000; The OLE DB provider
"SQLNCLI10" for linked server
"DM_DS_SOPM33_QDB" reported an error. Execution terminated by the provider because a resource limit was reached.;
42000." Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
<Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'vFact_201303_INCR_UPDATE_TEMP_he3dx_' partition of the 'vFact' measure
group for the 'vAMGeneric' cube from the AC_OLAP database."
Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
<Error
ErrorCode="3238002695"
Description="Internal error: The operation terminated unsuccessfully."
Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
<Error
ErrorCode="3238002695"
Description="Internal error: The operation terminated unsuccessfully."
Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
<Error
ErrorCode="3239837698"
Description="Server: The operation has been cancelled."
Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
<Error
ErrorCode="3238395904"
Description="OLE DB error: OLE DB or ODBC error: Operation canceled; HY008."
Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
<Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'vFact_201304_INCR_UPDATE_TEMP_kq5tw_' partition of the 'vFact' measure
group for the 'vAMGeneric' cube from the AC_OLAP database."
Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
<Error
ErrorCode="3238002695"
Description="Internal error: The operation terminated unsuccessfully."
Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
<Error
ErrorCode="3238002695"
Description="Internal error: The operation terminated unsuccessfully."
Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
<Error
ErrorCode="3238395904"
Description="OLE DB error: OLE DB or ODBC error: Operation canceled; HY008."
Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
<Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'vFactUTC_201304_INCR_UPDATE_TEMP_qtfcw_' partition of the 'vFactUTC'
measure group for the 'vAMGenericUTC' cube from the AC_OLAP database."
Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
<Error
ErrorCode="3238002695"
Description="Internal error: The operation terminated unsuccessfully."
Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
<Error
ErrorCode="3238002695"
Description="Internal error: The operation terminated unsuccessfully."
Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
</Messages>
</root>
</results>
</return>against OLE DB provider
"SQLNCLI10" for linked server
"DM_DS_SOPM33_QDB". ; 42000; The OLE DB provider
"SQLNCLI10" for linked server
"DM_DS_SOPM33_QDB" reported an error. Execution terminated by the provider because a resource limit was reached.;
42000." Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
Hi Born,
Have you check your disk space? This issue might be caused by not enougl disk sapce. Here is a similar thread about this topic:
http://social.technet.microsoft.com/Forums/en-US/sqlanalysisservices/thread/1783c640-5d4d-4086-bbdc-05adc45e3816/
If you have any feedback on our support, please click
here.
Regards,
Elvis Long
TechNet Community Support -
Errors in the OLAP storage engine: The attribute key cannot be found when processing
this is the absolute worst error message in all of computing. I despise it. Here is my situation.
SSAS 2008 R2.
I have one dimension. I have not even built my cube yet. only a dimension. I am trying to process it. I can process it when I only have a single attribute, they key. it is a composite key. When I add a new attribute (integer),
I get the error message. There are no null values. There are no blanks as its an integer.
The attribute key cannot be found where? I'm processing the dimension you idiot. there is not even a cube yet in order for any key to be found or not.Hi Baracus,
According to your description, you get the error "Errors in the OLAP storage engine: The attribute key cannot be found when processing" when processing your cube, right?
Generally, the detail error message should like
Table: 'dbo_FactSales', Column: 'ProductID', Value: '1111'. The attribute is 'Product ID'
The above error explains that the fact table named "FactSales" contains column ProductID with value "1111" but the same ProductID is not present in your dimension table. There is a primary key - foreign key relationship exist
between the ProductID column of dimension table and fact table named "FactSales" and cube is unable to find ProductID with value 1111 in the dimension table.
At this time, what we need to do is to check either your dimension and fact table contains the value mentioned in the error message ( Value: '1111' in the above example). Here are some links about troubleshoot this issue, please see:
http://www.businessintelligence-solutions.com/ssas-typical-error-attribute-key-processing/
http://www.youtube.com/watch?v=5O7IAjvtAF4
If this is not what you want, please provide us more information about you issue, so that we can make further analysis.
Regards,
Charlie Liao
If you have any feedback on our support, please click
here.
Charlie Liao
TechNet Community Support -
Errors in the OLAP storage engine: A duplicate attribute key has been found when processing
Hi dear MSDN Community,
I am facing a problem while processing a cube with a customer hierarchy as follows:
Global Account --> Main Customer --> Master Customer --> Customer
The data comes from a flatted parent child table, that is, I create an extra column for every level of the hierarchy in the customer view. If a level is empty, then the value is filled with the previous value. Then I can use the property:
HideMemberIf = OnlyChildWithParentName for the intermediate levels (Main and Master Customer)
HideMemberIf = ParentName For the leafs (Customer)
HideMemberIf = never for the root (Global Account)
Consider this example:
Then, for the root level I am using as the key the fields in yellow in order to avoid duplicates. However, I am getting the error message "Errors in the OLAP storage engine: A duplicate attribute key has been found when processing" while processing.
I analyzed the query that SSAS issues to the server (select distinct ....) and I think it should work but it is still failing.
I had similar problems with the intermediate levels but I was able to solve it using a similar procedure.
Any help will be appreciated.
Kind Regards.When are you having this error? While processing the dimension or during cube processing?
http://blog.oraylis.de/2013/08/a-duplicate-attribute-key-has-been-found-during-processing-revisited/
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 -
The attribute is 'Date Key'. Errors in the OLAP storage engine:
I have a Datetime column in my source table 'LastUpdatedDateTime' in this format '2012-08-15 14:58:42.467' and I have converted to integer using (YEAR(LastUpdatedDateTime) * 10000) + (MONTH(LastUpdatedDateTime) * 100) + DAY(LastUpdatedDateTime)
in my Fact table in the SSIS using a derived Column. Now when I run it in the SSAS I get an error
Erors in the OLAP storage engine: The attribute key cannot be found when processing: Table: 'Fact table', Column: 'LastUpdatedDateKey', Value: '20120815'.
EbenezerHi Ebenezer,
This error occurs when the Value: '20120815' is missing in dimension but available in Fact, probably in Date dimension in your case.
Have you converted the Datekey in Date dim to same format ?
If converted please check whether Value: '20120815' is available in Date dimension table.
Saurabh Kamath -
I am running BPC MS 7.5 and tried to do a full optimization and got the error below.
Unfortunately it did not appear to put the data back to its original state and I had to restore to a back up!
Can anyone tell me how to resolve this error - I am not a techie more an application man so in "English" would help me.
==============[System Error Tracing]==============
[System Name] : OLAPServerHandler
[Message Type] : ErrorMessage
[Job Name] : Olap9Manager : CubeProcess
[DateTime] : 6/22/2011 11:45:32 AM
[UserId] :
[Exception]
DetailMsg : {Microsoft.AnalysisServices.OperationException: Errors in the OLAP storage engine: The attribute key cannot be found when processing: Table: 'dbo_tblFactConsolidation', Column: 'ACCOUNT', Value: 'CTLICBFR010'. The attribute is 'Account_ID1'.
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 'Consolidation' partition of the 'Consolidation' measure group for the 'Consolidation' cube from the EBIQUITYTRAIN database.
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.
Internal error: The operation terminated unsuccessfully.
Server: The operation has been cancelled.
ThanksHi,
Usually, this kind of error message comes from invalid records in your fact tables.
Check out SAP Note 1098683.
Hope this will help you.
Kind Regards,
Patrick -
Errors in OLAP storage engine when processing application
Hi
After changing a logic in the application, we processed the application but it did not complete successfully due to the following error:
Error message:: CreateOLAPCubeForApplication:CreateCube:Errors in the OLAP storage engine: The attribute key cannot be found when processing: Table: 'dbo_tblFactQuality', Column: 'QACCOUNT', Value: '%ACCOUNTS%'. The attribute is 'QAccount_ID1'.
When trying other applications they showed errors with reference to the measure group, e.g.:
Error message:: Errors in the metadata manager. No dimension relationships exist within the 'Ownership' measure group.
Thanks for your help.
MelanieHi,
This kind of error will come when you have some invalid member defined in your fact table. you can use the following SQL query to check it.
select * from tblfact"yourapplication" where "dimension" not in (select id from mbr"dimension" where calc = 'N')
The same query needs to be run in wbtable and fac2 table.
These selection should return 0 records.
If it is returning something then you have to delete these records (replace "select * "with delete).
You can run this for all the applications and all the dimensions. However, I believe, you can check in your Quality application and the QACCOUNT dimension.
You can see for which dimension, there is an invalid member. This member might be getting created through one of your script logics.
Hope this helps. -
Can't get the INNODB storage engine to start with Leopard MySQL server...
As shipped by apple. In the /etc/my.cnf file it says to just uncomment the stuff related to innodb and all will be well. I did that, restarted the Mysql server and when I take a look at the available storage engines using phpmyadmin, innodb is turned off...
The following SQL runs:
CREATE TABLE `Puzzles` (
`id` int(10) unsigned NOT NULL auto_increment,
`initialState` char(81) NOT NULL default '',
`solution` char(81) NOT NULL default '',
`levelOfDifficulty` int(11) NOT NULL default '5',
`numberOfClues` smallint(5) unsigned NOT NULL default '0',
PRIMARY KEY (`id`),
UNIQUE KEY `initialState` (`initialState`),
KEY `levelOfDifficulty` (`levelOfDifficulty`),
KEY `numberOfClues` (`numberOfClues`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=780 ;
But when I look at the table, it's a MyIsam table.
Heres the innodb part of the /etc/my.cnf file:
# Uncomment the following if you are using InnoDB tables
innodbdata_homedir = /var/mysql/
innodbdata_filepath = ibdata1:2000M;ibdata2:10M:autoextend
innodblog_group_homedir = /var/mysql/
innodblog_archdir = /var/mysql/
# You can set ..buffer_poolsize up to 50 - 80 %
# of RAM but beware of setting memory usage too high
innodbbuffer_poolsize = 384M
innodbadditional_mem_poolsize = 20M
# Set ..log_filesize to 25 % of buffer pool size
innodblog_filesize = 100M
innodblog_buffersize = 8M
innodbflush_log_at_trxcommit = 1
innodblock_waittimeout = 50
No errors in the logs visible through Server Admin. Did Apple put the MySQL configuration files somewhere non-standard and leave the /etc/my.cnf file around to fool us?
Any pointers will be helpful or should I just build the fink package and give up on the shipped Leopard package (so far I'm not too impressed with Leopard).
Best,
Dick MunroeThe problem turned out to be the sizes of the INNODB log and data files. Apparently, the initial startup of MySQL causes these files to be built. The numbers that you uncomment in the my.cnf file aren't related in any way to these sizes and the innodb storage engine won't start unless they match. Stop the server, delete the files, and restart the server and you're off and running. The logs on Leopard Server have NO indication that this has occurred. I found the problem by installing the Mac OS kit from mysql.com and looking in those logs. Interesting question is why that information is missing from the log for Leopard Server when the information is clearly available (as show by running the mysql server).
Best,
Dick Munroe -
RSCRM_BAPI giving Error in the OLAP-Check - Data Retraction
Hello,
we have an integrated planing using a cube in BW. From this cube data has been retracted to R/3 using a retraction query.
Problem: We needed to compress the cube due to to many partitions on the database. From that moment on the retraction failed yielding an empty query result. After investigating we found that this error appears on the Olap-Check in the RSCRM_BAPI transaction:
Original in German: InfoCube enthält Daten in seiner E-Tabelle.
Translated to english: The InfoCube has data in its E-Table.
For now we made a backup of the original cube, cleared the cube and loaded the data back into the cube. So we kind of compressed all requests into one due to the full load. But this is only a workaround.
Can someone give any hints or ideas how we can solve the retraction problem with a compressed cube without clearing it?
ThanksFollow these steps and hopefully it should resolve your query
1. If there is no table to link then Create a dummy table and link it in physical layer
2. Move it to BMM layer
3. In case the spreadsheet table also links to a table from another data-source then create the links from BMM layer only.
4. Move it to presentation layer and job done.. -
Error with the Shared Variable Engine
Hi,
I have a problem with the Shared Variable Engine,
A .doc File is attached to this message, decribing the problem with pictures.
I will be glad if anyone can help me.
Sincerely yours
Amitai Abramson
Attachments:
Question.doc 819 KBHi Amitai,
Good afternoon and I hope your well.
A member of the team from NI Israel contacted me regarding this post.
I want to provide you with extra details on how to resolve your issue - i.e. Repair (Or Re-install) the Shared Variable Engine.
If you use the MsiBlast Tool it will populate a list of all MSI NI Installers. One of these will be NI Variable Engine. On the right-hand side you can the click 'Repair'. I would also Repair the engine support for the versions of LabVIEW you have installed. Please see attachments for MsiBlast and a screenshoot of the MSIBlast screen.
If this doesn't work I would recommend re-installing LabVIEW using the following guide, which I posted on this forum. (second post by me).
Please let me know how you get on,
Kind Regards,
James.
Message Edited by Hillman on 12-03-2008 12:19 PM
Message Edited by Hillman on 12-03-2008 12:19 PM
Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help!
Attachments:
Repair Shared Variable Engine.JPG 97 KB
msiBlast.zip 110 KB -
ALEAUD back to ECC when we have an error in the receiver adapter engine
Hello friends,
My scenario is ECC (async) to SOAP (sync) and back to ECC (async = ALEAUD). I'm using aync/sync bridge is receiver SOAP adapter.
Is it possible to send back an ALEAUD automatically when I have an error in my receiver SOAP adapter? If so can you please explain how to achieve that?
Your help is greatly appreciated,
Thank you in advance,
Kind regards,
JohnHi,
The below reports will helps you to get alerts when any error in target end..
IDX_NOALE - you can configure what kind of acknowledgement you want to request for the send message type. for example you can configure for only error acknowledgements.
IDX_ALEREQUEST - you can configure to send back an acknowledgement as PI message, so that you can control the ALEAUD content by mapping.
Thanks & Regards,
A.Neelima. -
Error Message The OLAP Type Requested counld not be found
After analyzer completely install in Win98 SE (Eng) without any error message. However, when the user connect to Essbase then the message come up as shown in the subject.Any idea to resolve this error message??ThanksLouis
This behavior occurs only If I put a <cfapplication> tag on my cfm page.
When I put the <cfapplication> tag in an explicit file Application.cfm, cfc syntax error messages appears correctly.
Maybe just a problem with my configuration (IIS7), but perhaps an indication... -
When I deploy the cube which is sitting on my PC (local) the following 4 errors come up:
Error 1 The datasource , 'AdventureWorksDW', contains an ImpersonationMode that that is not supported for processing operations. 0 0
Error 2 Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'Adventure Works DW', Name of 'AdventureWorksDW'. 0 0
Error 3 Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Customer', Name of 'Customer' was being processed. 0 0
Error 4 Errors in the OLAP storage engine: An error occurred while the 'Customer Alternate Key' attribute of the 'Customer' dimension from the 'Analysis Services Tutorial' database was being processed. 0 0Sorry hit the wrong button there. That is not entire solution and setting it to default would work when using a single box and not in a distributed application solution. If you are creating the analysis database manually or using the wizard then you can
set the impersonation to your heart content as long as the right permission has been set on the analysis server.
In my case I was using MS Project Server 2010 to create the database in the OLAP configuration section. The situation is that the underlying build script has been configured to use the default setting which is the SQL Service account and this account does
not have permission in Project Server I believe.
Changing the account to match the Project service account allowed for a successful build \ creation of the database. My verdict is that this is a bug in Project Server because it needs to include the option to choose impersonation when creating the Database
this way it will not use the default which led to my error in the first place. I do not think there is a one fix for all in relations to this problem it is an environment by environment issue and should be resolved as such. But the idea around fixing it is
if you are using the SQL Analysis server service account as the account creating the database and cubes then default or service account is fine. If you are using a custom account then set that custom account in the impersonation details after you have granted
it SQL analysis administrator role. You can remove that role after the DB is created and harden it by creating a role with administrative permissions.
Hope this helps.
Maybe you are looking for
-
Credit Account - Not getting changed
Hi all, Normally when I change my Payer in Sales order header , credit account in sales order VBAK - KNKLI gets changed. But currently even when i change the payer in SO abd it gets changed, but still it show the old payer number as credit account in
-
Can't edit a specific playlist and change order of songs.
I set up a new playlist and am unable to move the songs around to the order I want. My other playlists are letting me edit/move around the order without a problem. How can I access the edit feature for my "blocked" playlist.
-
Developing a CLDC mobile application
hi.. I m developing an mobile CLDC application and It is an SMS related application. Every character in the message is to be replaced with a string. So, should I maintain a database table of that replacment strings which scans and replace this entry
-
How do I access files on my Macbook from my iMac?
I'm about four months new to my Macbook and I'd like to access just files on my Macbook from my husband's iMac. We have wi-fi in the house. Thanks!
-
Want to get a xml blob as a varchar2
Hi Guys, What is the max size of letters we could use in varchar2 in oracle9? (Is it 4000?) Reason to ask this is that I have an xml document as a blob and want to show it in my client. I wanna create a view that will do something like Utl_Raw.Cast_T