On long-running cubes (over an hour full process time), I regularly, but not
always, get an error
"A member with key '<value>' was found in the fact table but was not found
in level '<level>' of the dimension '<dimension>'"
The key values are different each time.
The key values are present in the dimension table and they are not new.
There are no updates being done to the data source at the time.
I simply reprocess the cube and it succeeds.
But I've lost hours of production time.
--
Thanks and Good Luck.
Fergus

looks like you are missing an incremental process for that
dimension (which is missing members), prior to cube process.

"Fergus" wrote:

Actually the incrementall update is done in the cube process. However, as I
mentioned, the rows are not new. These cubes are processed every night and
the dimension and fact rows that fail had all previously been successful. If
they were new, I would also have suspected the incremental update. I think
it's a performance or contention issue in OLAP services, but I can't see any
options for retrying or extending timeouts. All I see are options to ignore
errors.
--
Thanks and Good Luck.
Fergus



"Rea" wrote:

Hello Fergus,

I understand that the error "A member with key '<value>' was found in the
fact table but was not found in level '<level>' of the dimension
'<dimension>'" appears though the related rows in fact table are not new.
You could reporcess the cube to work around the issue.

As you know, this problem usually occurs because a dimension key was added
to the fact table, but the dimension key was not added to the dimension.
However, it does not seem to be the cause of your situation.

I still suggest that you try to add an Incrementally process of the related
dimension before the cube process to test though it is supposed to be
included.

Also, I once saw similar issues when there are memory issues on AS server.
You may want to check the memory status of the issue to see if msmdsrv.exe
uses too much memory when the issue occurs. If so, you may try to move some
cubes/databases to different servers, or consider add more physical memory
to the server.

There is a known issue that in Analysis Services SP3, the connections to
Analysis Services services are blocked when the memory that the msmdsrv
process uses exceeds 112.5 percent of the memory conservation threshold
value ( HighMemoryLimit ).
http://support.microsoft.com/?id=823357

Therefore, it's suggested increasing the "Memory Conservation Threshold" to
2G and see if the problem still occurs. We need to restart
SSQLServerOLAPServices to make the change take effect.

Though it does not seem to be a procssing timout issue, you may refer to
the following articles to set timeout value for server to test

221539 PRB: Error 206 While Processing a Large Cube
http://support.microsoft.com/default...b;EN-US;221539

http://msdn.microsoft.com/library/en...erver_1ruc.asp

In addition, please enable logging of processing message in server
properties page, and you may be able to find more clues for the issues.

Since the issue occurs randomly and might be related to performance, it can
be difficult to troubleshoot and resolve in a newsgroup setting due to the
number of variables and the amount of time required to narrow down possible
causes and observe the effects. We will assist as best as we can, but you
may wish to consider contacting CSS for a more timely resolution for these
type issues.

To obtain the phone numbers for specific technology request please take a
look at the web site listed below.
http://support.microsoft.com/default...S;PHONENUMBERS

If anything is unclear or you have any updates, please feel free to let's
know. We look forward to hearing from you.
Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.