EVDRE error after adding new member - AFTER installing SQL 2008 R2 SP1 CU2

Question

Hi guys.
We're seeing the same error as detailed in Link:[Re: EVDRE error AFTER expanding on a newly added member, sometimes....;
Basically, any new members that are added appear in the SQL tables, but throw out "EVDRE has encountered a problem..." when trying to use them.
Generally, this problem clear up if we leave the member overnight (although why this should be, I have no idea - the system does nothing extra overnight).
We have tried processing the cube, full processing of the application and even a server reboot, all to no avail.
However, the generally accepted fix for this is to upgrade SQL 2008 R2 to SP1 CU2 (SQL 10.50.2772)
This system was patched to that level before BPC was ever installed, precisely to avoid this problem.
This is not the first time that we have seen this behaviour.
I have experienced it in one other environment, which I keep meaning to rebuild.
These installations are in completely different environments.  The only similarities are that they both use Windows Server 2008 R2 and SQL 2008 R2.
The issue only started to appear in this second environment today (we have 3 other environments with the same software version that do not have the problem).
It had been assumed before today that the first problematic environment might need a rebuild due to this issue being caused by some other factor.
However, this is now far too coincidental to be the case.
Has anyone seen similar issues even after patching to v10.50.2772, or does anyone have any suggestions at all.
I could really do with a quick win on this one.
Thanks

Answer 1

Hi,
i've had the same issue in the same days. I confirm that the issue appear after adding any member and it's clear overnight.
My system is different:
Windows Server 2008 NT 6.0 <X64> (Build 6002: Service Pack 2) Enterprise Edition
and Microsoft SQL Server 2008 Enterprise Edition (SP1) - 10.0.2841.0 (X64)
The issue appears in the last months.
It's occurs only on specific machine (always the same client), in the same moment other machines can open the same input schedule and expand without problem.
I've noted also that when I cancel the added member the issue disappear, the same behaviour with APShell.
I have the same configuration on development and test environment, same version of O.S. and SQL server, but there I don't have problem. The only difference is that these two environments are single server (application and DB server on the same machine) Instead, the production environment is multiserver (2 application server + DB server).
Maybe there is a service that take a long time for sincronization (it's triggered in the night?).
Could you verify if on some machine the evdre works fine and and that when you delete the  added member evdre starts to work?
Kind regards
Roberto
Edited by: Roberto Vidotti on Dec 19, 2011 6:01 PM