Cube does not build anymore (after a MDX query error)

[Pawel]

I need to ask for help. Again.
Actually I believe that my problem is the same as reported in topic
http://www.microsoft.com/communitie...b5fd871a79df&lang=en&cr=US&sloc=en-us&m=1&p=1,
but there was no reply to that question.

I had a cube building configuration running more or less OK for a couple of
days, but I observed a strange behavior that the time reported by the people
in my teams does not sum up in "actual work", but is calculated separately as
billable in non-billable. I do not know if that is by design or a bug of some
kind, but I decided to outsmart OPS and create my own calculated MDX field
that would sum these two up. That seemed a interesting excercise and a fast
solution to get an ad-hoc report... How silly.

I made some stupid mistake in the query and the cube rightly did not build.
So I went back to the GUI and deleted the faulty MDX field. All seemed OK at
the time.
But the cube still does not build, showing (sic!) the same error as before.
I checked many times if the wrong query does not sit somewhere in the GUI
but not. I even reset the cube configuration removing all custom fields from
cube dimensions and saving the configuration, hoping that this will refresh
the definition. In vain. The error still shows up.
I am pretty sure that the buggy DMX query is still cached/stored somewhere
in OPS or Analysis Services, only the GUI does not show it. But I have no
idea where to look for it or how to refresh the configuration.

I could not find anything in the documenattion nor on the Internet...

Does anyone have any ideas?

Thanks in advance,

Pawel

 

[Pawel]

I forgot to post the actual error report. Here it is:
---
Failed to build the OLAP cubes. Error: Analysis Services session failed with
the following error: Failed to process the Analysis Services database
XXXAnalysis_DB on the XXX server. Error: Server: Operation completed with 20
problems logged. Parser: The syntax for 'Work' is incorrect.
---
A note: I am not sure what are those 20 problems mentioned in the text, but
they are not likely related to the problem described. When I run the
processing of the reporting database directly in the SQL server management
studio I receive a couple of (reported and ignored) errors indicating that
some of the old test timesheets were not cleaned up when I removed all test
enterprise objects a couple of weeks ago. There are still references to
non-existent project UIDs in the timesheet tables of the OPS reporting
database.

Thanks,

Pawel

 

[Robbie Inglis]

Hi. We are experienceing the same issue, if you have resolved this, can you please advise how, thanks.

 

[Marc Soester [MVP]]

what is the error message?