Error in olap report

I am trying to write an olap report using RS2005. I created a datasource
with type "Microsoft Analysis Services" then added a report and defined
measures and dimensions in the query builder. Report is working fine but if
I make any modification, I will not be able to save the report and as soon
as I switch to any other tab (for example click on Preview tab or Data tab)
I will get the error "Microsoft Visual Studio has encountered a problem and
needs to close." I tried same senario by using "Analysis Services Toturial"
cube and I got same result.
Any idea?
Thanks.Actually, I'm used to getting this if I stress my development computer too
much... For bigger reports based on OLAP cubes, I just don't use the preview
function. I tweak my MDX query to just return enough data for the fields to
fill up right, and then I just save as quickly as possible. If you just add
a =" to the beginning of your query and a " at the end and make it be one
long string (no new lines), you will be able to save without the report
going to pieces. Remeber to use the "Save all" button after having added a
new report to your solution, or it will not be saved with your solution.
(But it will be available through "Add existing item".)
Not sure if this is what you wanted to hear, but it might save you from some
frustration.
Kaisa
"Tooraj" <abc@.abc.com> wrote in message
news:uEmibczBGHA.984@.tk2msftngp13.phx.gbl...
>I am trying to write an olap report using RS2005. I created a datasource
>with type "Microsoft Analysis Services" then added a report and defined
>measures and dimensions in the query builder. Report is working fine but if
>I make any modification, I will not be able to save the report and as soon
>as I switch to any other tab (for example click on Preview tab or Data tab)
>I will get the error "Microsoft Visual Studio has encountered a problem and
>needs to close." I tried same senario by using "Analysis Services Toturial"
>cube and I got same result.
> Any idea?
> Thanks.
>

Error in Metadata manager when trying to open calculations

Having an issue when I try to open the calculations tab in BIDS against an OLAP database or a MSAS project. BIDS hangs for a second than comes back with an "unexpected errror" in the middle of the screen and then shuts down. If I check the event viewer I get

Errors in the metadata manager. The configuration property updates were not persisted. Internal error: An unexpected exception occured

I can access every other tab in the project, just not the calculations tab.

Anyone run into this before?

Thanks

FJK,

I think I read some time ago that you could get this message if you have different msolap90.dll installed on your PC in different folders. Could you search for this dll on your PC and if different version found, try to replace dll to match.

Vidas Matelis

Error help when deploying a cube

I'm getting an error message and i'm not sure what it's trying to tell me.

Errors

Warning 1 Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_rpt_vr_flat_cmb_ih_so, Column: idcol, Value: 441183. 0 0

Warning 2 Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Rpt Vr Flat Cmb Ih So of Dimension: Rpt Vr Flat Cmb Ih So from Database: sdw4, Cube: SDW, Measure Group: Rpt Vr Flat Cmb Ih So, Partition: Rpt Vr Flat Cmb Ih So, Record: 441183. 0 0

Error 3 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. 0 0

Error 4 Errors in the OLAP storage engine: An error occurred while processing the 'Rpt Vr Flat Cmb Ih So' partition of the 'Rpt Vr Flat Cmb Ih So' measure group for the 'SDW' cube from the sdw4 database. 0 0

Error 5 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. 0 0

-background-

My cube is just one flat table the only linking it has is to a time table. This table is put together over night for users to query off of, and when we built this table a primary key wasn't a option so we added a auto incermenting col just to give us a key and that is the key is called idcol which i think is telling me something is wrong with that record. but i'm not sure.

suggestions?

Hello! A guess is that you have a factrecord with a time key that is not in the time table/flat file.

HTH

Thomas Ivarsson